Public report of electron-userland/electron-builder, published 17 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 17 November 2026, 02:44 UTC · Survey ID cd_86090626766d4faead47299582744d8a
electron-userland/electron-builder
Measured 17 November 2026, 02:42 UTC, at code version e4ac7ae
First survey, so nothing to compare with yet
CAI scoreAdequate
CriticalWeakAdequateStrongExemplary
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A medium codebase: 65,502 lines of product code in 15 projects, tests not counted · Estimated rebuild effort: about 1.1 person-years · Weakest lens: Production Readiness, 53.8
Findings by how serious they are
64 critical670 serious310 minor
5 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
17 November 2026, 02:42 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 ▸
75of 75 dimensions measured by tools.
985of 1044 findings point to an exact file and line, so you can open each one in the code. The other 59 concern the repository as a whole, such as missing documentation.
75dimensions across 6 lenses, read from 65,502 lines of product code in 15 projects.
electron-userland/electron-builder falls short of our standard for production, in part because it has uses of packages that aren't listed. It scores 56.6 out of 100 and is rated Adequate, and 51 of its 64 critical findings are security problems.
Production Readiness, at 53.8, is the weakest lens by a small margin, and the weakest lens counts most in the score. The best first step for the work it takes is replacing the three deprecated dependencies, worth about 2.5 points. Tidying the declared packages would lift Production Readiness itself, worth about 2.7 points.
Twenty-eight pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Eight settings leave the servers or containers unsafe, and four known security holes in the packages the code depends on can be used by attackers. Pinning each tool to an exact version, correcting the unsafe settings and updating the vulnerable packages would close these risks. Fixing the weaknesses the scanner points to would fix the four security weaknesses in the code, and the four places where the code runs text as code or as a command need a direct call instead. The seven loops of files that import each other need breaking.
The product code is 65,502 lines, about €160,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.
The weakest lenses score close to each other, so improving any of them moves the score.
Code composition: what the lines of code are
Product code 42%Tests 58%
Rebuild cost: about €160,000 · Estimate
Cost to rebuild
€52,000 to €260,000, for 872 to 2,768 hours of work, about 1.1 person-years for 1 to 3 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.8 at a score of 57. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Medium: 65,502 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 3 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (3).
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
Raises the score by about 2.7 points · Medium effort · Dependency Hygiene
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 €160,000 to build again, about 1.1 person-years of work. Its weakest lens is Production Readiness, at 53.8 (Adequate). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 3 Deprecated finding(s) in Dependency Hygiene. Of all the actions in this report, it raises the score most for the work it takes: about 2.5 points for low effort, because it clears the 3 Dependency Hygiene findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 5.5 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 6% to 14% on every change. The history of the code shows how much it changes: about 152,137 lines over the last 90 days, which is about 617,000 lines a year. At that pace, the extra work comes to an estimated 95 to 569.9 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
270 modules, with 635 dependencies between them. 3 loops run through 14 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 230 more are left out to keep it readable.
Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
app-builder-lib.src.core uses builder-util.src.arch, so a change to builder-util.src.arch can break app-builder-lib.src.core, while a change to app-builder-lib.src.core can't break builder-util.src.arch.
Position
Below the diagonal: app-builder-lib.src.core uses a module listed above it, which is the healthy direction.
builder-util-runtime.src.httpExecutor uses builder-util-runtime.src.CancellationToken, so a change to builder-util-runtime.src.CancellationToken can break builder-util-runtime.src.httpExecutor, while a change to builder-util-runtime.src.httpExecutor can't break builder-util-runtime.src.CancellationToken.
Position
Below the diagonal: builder-util-runtime.src.httpExecutor uses a module listed above it, which is the healthy direction.
electron-publish.src uses builder-util-runtime.src.CancellationToken, so a change to builder-util-runtime.src.CancellationToken can break electron-publish.src, while a change to electron-publish.src can't break builder-util-runtime.src.CancellationToken.
Position
Below the diagonal: electron-publish.src uses a module listed above it, which is the healthy direction.
electron-updater.src.types uses builder-util-runtime.src.CancellationToken, so a change to builder-util-runtime.src.CancellationToken can break electron-updater.src.types, while a change to electron-updater.src.types can't break builder-util-runtime.src.CancellationToken.
Position
Below the diagonal: electron-updater.src.types uses a module listed above it, which is the healthy direction.
electron-updater.src.types uses builder-util-runtime.src.updateInfo, so a change to builder-util-runtime.src.updateInfo can break electron-updater.src.types, while a change to electron-updater.src.types can't break builder-util-runtime.src.updateInfo.
Position
Below the diagonal: electron-updater.src.types uses a module listed above it, which is the healthy direction.
app-builder-lib.src.electron.ElectronFramework uses app-builder-lib.src.core, so a change to app-builder-lib.src.core can break app-builder-lib.src.electron.ElectronFramework, while a change to app-builder-lib.src.electron.ElectronFramework can't break app-builder-lib.src.core.
Position
Below the diagonal: app-builder-lib.src.electron.ElectronFramework uses a module listed above it, which is the healthy direction.
14→31 app-builder-lib.src.electron.ElectronFramework uses app-builder-lib.src.Frameworkpart of a loop✕
Connections
3 pairs of types, where a type in app-builder-lib.src.electron.ElectronFramework uses a type in app-builder-lib.src.Framework.
app-builder-lib.src.electron.ElectronFramework uses app-builder-lib.src.Framework, so a change to app-builder-lib.src.Framework can break app-builder-lib.src.electron.ElectronFramework, while a change to app-builder-lib.src.electron.ElectronFramework can't break app-builder-lib.src.Framework.
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.
app-builder-lib.src.options.PlatformSpecificBuildOptions uses app-builder-lib.src.core, so a change to app-builder-lib.src.core can break app-builder-lib.src.options.PlatformSpecificBuildOptions, while a change to app-builder-lib.src.options.PlatformSpecificBuildOptions can't break app-builder-lib.src.core.
Position
Below the diagonal: app-builder-lib.src.options.PlatformSpecificBuildOptions uses a module listed above it, which is the healthy direction.
app-builder-lib.src.options.winOptions uses app-builder-lib.src.core, so a change to app-builder-lib.src.core can break app-builder-lib.src.options.winOptions, while a change to app-builder-lib.src.options.winOptions can't break app-builder-lib.src.core.
Position
Below the diagonal: app-builder-lib.src.options.winOptions uses a module listed above it, which is the healthy direction.
app-builder-lib.src.packagerApi uses builder-util.src.arch, so a change to builder-util.src.arch can break app-builder-lib.src.packagerApi, while a change to app-builder-lib.src.packagerApi can't break builder-util.src.arch.
Position
Below the diagonal: app-builder-lib.src.packagerApi uses a module listed above it, which is the healthy direction.
app-builder-lib.src.packagerApi uses app-builder-lib.src.core, so a change to app-builder-lib.src.core can break app-builder-lib.src.packagerApi, while a change to app-builder-lib.src.packagerApi can't break app-builder-lib.src.core.
Position
Below the diagonal: app-builder-lib.src.packagerApi uses a module listed above it, which is the healthy direction.
17→28 app-builder-lib.src.packagerApi uses app-builder-lib.src.platformPackagerpart of a loop✕
Connections
2 pairs of types, where a type in app-builder-lib.src.packagerApi uses a type in app-builder-lib.src.platformPackager.
app-builder-lib.src.packagerApi uses app-builder-lib.src.platformPackager, so a change to app-builder-lib.src.platformPackager can break app-builder-lib.src.packagerApi, while a change to app-builder-lib.src.packagerApi can't break app-builder-lib.src.platformPackager.
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.
builder-util-runtime.src uses builder-util-runtime.src.CancellationToken, so a change to builder-util-runtime.src.CancellationToken can break builder-util-runtime.src, while a change to builder-util-runtime.src can't break builder-util-runtime.src.CancellationToken.
Position
Below the diagonal: builder-util-runtime.src uses a module listed above it, which is the healthy direction.
builder-util-runtime.src uses builder-util-runtime.src.publishOptions, so a change to builder-util-runtime.src.publishOptions can break builder-util-runtime.src, while a change to builder-util-runtime.src can't break builder-util-runtime.src.publishOptions.
Position
Below the diagonal: builder-util-runtime.src uses a module listed above it, which is the healthy direction.
builder-util-runtime.src uses builder-util-runtime.src.updateInfo, so a change to builder-util-runtime.src.updateInfo can break builder-util-runtime.src, while a change to builder-util-runtime.src can't break builder-util-runtime.src.updateInfo.
Position
Below the diagonal: builder-util-runtime.src uses a module listed above it, which is the healthy direction.
builder-util-runtime.src uses builder-util-runtime.src.httpExecutor, so a change to builder-util-runtime.src.httpExecutor can break builder-util-runtime.src, while a change to builder-util-runtime.src can't break builder-util-runtime.src.httpExecutor.
Position
Below the diagonal: builder-util-runtime.src uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in electron-updater.src.differentialDownloader.DifferentialDownloader uses a type in builder-util-runtime.src.CancellationToken.
electron-updater.src.differentialDownloader.DifferentialDownloader uses builder-util-runtime.src.CancellationToken, so a change to builder-util-runtime.src.CancellationToken can break electron-updater.src.differentialDownloader.DifferentialDownloader, while a change to electron-updater.src.differentialDownloader.DifferentialDownloader can't break builder-util-runtime.src.CancellationToken.
Position
Below the diagonal: electron-updater.src.differentialDownloader.DifferentialDownloader uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in electron-updater.src.differentialDownloader.DifferentialDownloader uses a type in builder-util-runtime.src.updateInfo.
electron-updater.src.differentialDownloader.DifferentialDownloader uses builder-util-runtime.src.updateInfo, so a change to builder-util-runtime.src.updateInfo can break electron-updater.src.differentialDownloader.DifferentialDownloader, while a change to electron-updater.src.differentialDownloader.DifferentialDownloader can't break builder-util-runtime.src.updateInfo.
Position
Below the diagonal: electron-updater.src.differentialDownloader.DifferentialDownloader uses a module listed above it, which is the healthy direction.
electron-updater.src.differentialDownloader.DifferentialDownloader uses builder-util.src.log, so a change to builder-util.src.log can break electron-updater.src.differentialDownloader.DifferentialDownloader, while a change to electron-updater.src.differentialDownloader.DifferentialDownloader can't break builder-util.src.log.
Position
Below the diagonal: electron-updater.src.differentialDownloader.DifferentialDownloader uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in electron-updater.src.differentialDownloader.DifferentialDownloader uses a type in builder-util-runtime.src.httpExecutor.
electron-updater.src.differentialDownloader.DifferentialDownloader uses builder-util-runtime.src.httpExecutor, so a change to builder-util-runtime.src.httpExecutor can break electron-updater.src.differentialDownloader.DifferentialDownloader, while a change to electron-updater.src.differentialDownloader.DifferentialDownloader can't break builder-util-runtime.src.httpExecutor.
Position
Below the diagonal: electron-updater.src.differentialDownloader.DifferentialDownloader uses a module listed above it, which is the healthy direction.
electron-updater.src.differentialDownloader.DifferentialDownloader uses electron-updater.src.types, so a change to electron-updater.src.types can break electron-updater.src.differentialDownloader.DifferentialDownloader, while a change to electron-updater.src.differentialDownloader.DifferentialDownloader can't break electron-updater.src.types.
Position
Below the diagonal: electron-updater.src.differentialDownloader.DifferentialDownloader uses a module listed above it, which is the healthy direction.
electron-updater.src.providers.Provider uses builder-util-runtime.src.CancellationToken, so a change to builder-util-runtime.src.CancellationToken can break electron-updater.src.providers.Provider, while a change to electron-updater.src.providers.Provider can't break builder-util-runtime.src.CancellationToken.
Position
Below the diagonal: electron-updater.src.providers.Provider uses a module listed above it, which is the healthy direction.
electron-updater.src.providers.Provider uses builder-util-runtime.src.httpExecutor, so a change to builder-util-runtime.src.httpExecutor can break electron-updater.src.providers.Provider, while a change to electron-updater.src.providers.Provider can't break builder-util-runtime.src.httpExecutor.
Position
Below the diagonal: electron-updater.src.providers.Provider uses a module listed above it, which is the healthy direction.
electron-updater.src.providers.Provider uses electron-updater.src.types, so a change to electron-updater.src.types can break electron-updater.src.providers.Provider, while a change to electron-updater.src.providers.Provider can't break electron-updater.src.types.
Position
Below the diagonal: electron-updater.src.providers.Provider uses a module listed above it, which is the healthy direction.
app-builder-lib.src.codeSign.win.signManager uses app-builder-lib.src.codeSign.signResult, so a change to app-builder-lib.src.codeSign.signResult can break app-builder-lib.src.codeSign.win.signManager, while a change to app-builder-lib.src.codeSign.win.signManager can't break app-builder-lib.src.codeSign.signResult.
Position
Below the diagonal: app-builder-lib.src.codeSign.win.signManager uses a module listed above it, which is the healthy direction.
app-builder-lib.src.codeSign.win.signManager uses app-builder-lib.src.core, so a change to app-builder-lib.src.core can break app-builder-lib.src.codeSign.win.signManager, while a change to app-builder-lib.src.codeSign.win.signManager can't break app-builder-lib.src.core.
Position
Below the diagonal: app-builder-lib.src.codeSign.win.signManager uses a module listed above it, which is the healthy direction.
app-builder-lib.src.codeSign.win.signManager uses app-builder-lib.src.options.winOptions, so a change to app-builder-lib.src.options.winOptions can break app-builder-lib.src.codeSign.win.signManager, while a change to app-builder-lib.src.codeSign.win.signManager can't break app-builder-lib.src.options.winOptions.
Position
Below the diagonal: app-builder-lib.src.codeSign.win.signManager uses a module listed above it, which is the healthy direction.
app-builder-lib.src.packager uses app-builder-lib.src.node-module-collector.packageManager, so a change to app-builder-lib.src.node-module-collector.packageManager can break app-builder-lib.src.packager, while a change to app-builder-lib.src.packager can't break app-builder-lib.src.node-module-collector.packageManager.
Position
Below the diagonal: app-builder-lib.src.packager uses a module listed above it, which is the healthy direction.
app-builder-lib.src.packager uses builder-util.src.arch, so a change to builder-util.src.arch can break app-builder-lib.src.packager, while a change to app-builder-lib.src.packager can't break builder-util.src.arch.
Position
Below the diagonal: app-builder-lib.src.packager uses a module listed above it, which is the healthy direction.
app-builder-lib.src.packager uses app-builder-lib.src.core, so a change to app-builder-lib.src.core can break app-builder-lib.src.packager, while a change to app-builder-lib.src.packager can't break app-builder-lib.src.core.
Position
Below the diagonal: app-builder-lib.src.packager uses a module listed above it, which is the healthy direction.
app-builder-lib.src.packager uses app-builder-lib.src.packagerApi, so a change to app-builder-lib.src.packagerApi can break app-builder-lib.src.packager, while a change to app-builder-lib.src.packager can't break app-builder-lib.src.packagerApi.
Position
Below the diagonal: app-builder-lib.src.packager uses a module listed above it, which is the healthy direction.
22→28 app-builder-lib.src.packager uses app-builder-lib.src.platformPackagerpart of a loop✕
Connections
2 pairs of types, where a type in app-builder-lib.src.packager uses a type in app-builder-lib.src.platformPackager.
app-builder-lib.src.packager uses app-builder-lib.src.platformPackager, so a change to app-builder-lib.src.platformPackager can break app-builder-lib.src.packager, while a change to app-builder-lib.src.packager can't break app-builder-lib.src.platformPackager.
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.
22→29 app-builder-lib.src.packager uses app-builder-lib.src.configurationpart of a loop✕
Connections
4 pairs of types, where a type in app-builder-lib.src.packager uses a type in app-builder-lib.src.configuration.
app-builder-lib.src.packager uses app-builder-lib.src.configuration, so a change to app-builder-lib.src.configuration can break app-builder-lib.src.packager, while a change to app-builder-lib.src.packager can't break app-builder-lib.src.configuration.
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.
22→31 app-builder-lib.src.packager uses app-builder-lib.src.Frameworkpart of a loop✕
Connections
1 pair of types, where a type in app-builder-lib.src.packager uses a type in app-builder-lib.src.Framework.
app-builder-lib.src.packager uses app-builder-lib.src.Framework, so a change to app-builder-lib.src.Framework can break app-builder-lib.src.packager, while a change to app-builder-lib.src.packager can't break app-builder-lib.src.Framework.
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.
electron-updater.src.AppUpdater uses builder-util-runtime.src.CancellationToken, so a change to builder-util-runtime.src.CancellationToken can break electron-updater.src.AppUpdater, while a change to electron-updater.src.AppUpdater can't break builder-util-runtime.src.CancellationToken.
Position
Below the diagonal: electron-updater.src.AppUpdater uses a module listed above it, which is the healthy direction.
electron-updater.src.AppUpdater uses builder-util-runtime.src.updateInfo, so a change to builder-util-runtime.src.updateInfo can break electron-updater.src.AppUpdater, while a change to electron-updater.src.AppUpdater can't break builder-util-runtime.src.updateInfo.
Position
Below the diagonal: electron-updater.src.AppUpdater uses a module listed above it, which is the healthy direction.
electron-updater.src.AppUpdater uses builder-util.src.log, so a change to builder-util.src.log can break electron-updater.src.AppUpdater, while a change to electron-updater.src.AppUpdater can't break builder-util.src.log.
Position
Below the diagonal: electron-updater.src.AppUpdater uses a module listed above it, which is the healthy direction.
electron-updater.src.AppUpdater uses electron-updater.src.AppAdapter, so a change to electron-updater.src.AppAdapter can break electron-updater.src.AppUpdater, while a change to electron-updater.src.AppUpdater can't break electron-updater.src.AppAdapter.
Position
Below the diagonal: electron-updater.src.AppUpdater uses a module listed above it, which is the healthy direction.
electron-updater.src.AppUpdater uses electron-updater.src.types, so a change to electron-updater.src.types can break electron-updater.src.AppUpdater, while a change to electron-updater.src.AppUpdater can't break electron-updater.src.types.
Position
Below the diagonal: electron-updater.src.AppUpdater uses a module listed above it, which is the healthy direction.
electron-updater.src.AppUpdater uses electron-updater.src.providers.Provider, so a change to electron-updater.src.providers.Provider can break electron-updater.src.AppUpdater, while a change to electron-updater.src.AppUpdater can't break electron-updater.src.providers.Provider.
Position
Below the diagonal: electron-updater.src.AppUpdater uses a module listed above it, which is the healthy direction.
electron-updater.src.differentialDownloader uses builder-util.src.log, so a change to builder-util.src.log can break electron-updater.src.differentialDownloader, while a change to electron-updater.src.differentialDownloader can't break builder-util.src.log.
Position
Below the diagonal: electron-updater.src.differentialDownloader uses a module listed above it, which is the healthy direction.
electron-updater.src.differentialDownloader uses builder-util-runtime.src.httpExecutor, so a change to builder-util-runtime.src.httpExecutor can break electron-updater.src.differentialDownloader, while a change to electron-updater.src.differentialDownloader can't break builder-util-runtime.src.httpExecutor.
Position
Below the diagonal: electron-updater.src.differentialDownloader uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in electron-updater.src.differentialDownloader uses a type in electron-updater.src.differentialDownloader.DifferentialDownloader.
electron-updater.src.differentialDownloader uses electron-updater.src.differentialDownloader.DifferentialDownloader, so a change to electron-updater.src.differentialDownloader.DifferentialDownloader can break electron-updater.src.differentialDownloader, while a change to electron-updater.src.differentialDownloader can't break electron-updater.src.differentialDownloader.DifferentialDownloader.
Position
Below the diagonal: electron-updater.src.differentialDownloader uses a module listed above it, which is the healthy direction.
app-builder-lib.src.macPackager uses app-builder-lib.src.codeSign.signResult, so a change to app-builder-lib.src.codeSign.signResult can break app-builder-lib.src.macPackager, while a change to app-builder-lib.src.macPackager can't break app-builder-lib.src.codeSign.signResult.
Position
Below the diagonal: app-builder-lib.src.macPackager uses a module listed above it, which is the healthy direction.
app-builder-lib.src.macPackager uses builder-util.src.arch, so a change to builder-util.src.arch can break app-builder-lib.src.macPackager, while a change to app-builder-lib.src.macPackager can't break builder-util.src.arch.
Position
Below the diagonal: app-builder-lib.src.macPackager uses a module listed above it, which is the healthy direction.
app-builder-lib.src.macPackager uses app-builder-lib.src.core, so a change to app-builder-lib.src.core can break app-builder-lib.src.macPackager, while a change to app-builder-lib.src.macPackager can't break app-builder-lib.src.core.
Position
Below the diagonal: app-builder-lib.src.macPackager uses a module listed above it, which is the healthy direction.
app-builder-lib.src.macPackager uses app-builder-lib.src.electron.ElectronFramework, so a change to app-builder-lib.src.electron.ElectronFramework can break app-builder-lib.src.macPackager, while a change to app-builder-lib.src.macPackager can't break app-builder-lib.src.electron.ElectronFramework.
Position
Below the diagonal: app-builder-lib.src.macPackager uses a module listed above it, which is the healthy direction.
app-builder-lib.src.macPackager uses app-builder-lib.src.packagerApi, so a change to app-builder-lib.src.packagerApi can break app-builder-lib.src.macPackager, while a change to app-builder-lib.src.macPackager can't break app-builder-lib.src.packagerApi.
Position
Below the diagonal: app-builder-lib.src.macPackager uses a module listed above it, which is the healthy direction.
app-builder-lib.src.macPackager uses app-builder-lib.src.packager, so a change to app-builder-lib.src.packager can break app-builder-lib.src.macPackager, while a change to app-builder-lib.src.macPackager can't break app-builder-lib.src.packager.
Position
Below the diagonal: app-builder-lib.src.macPackager uses a module listed above it, which is the healthy direction.
25→27 app-builder-lib.src.macPackager uses app-builder-lib.src.targets.mac.MacTargetHelperpart of a loop✕
Connections
3 pairs of types, where a type in app-builder-lib.src.macPackager uses a type in app-builder-lib.src.targets.mac.MacTargetHelper.
app-builder-lib.src.macPackager uses app-builder-lib.src.targets.mac.MacTargetHelper, so a change to app-builder-lib.src.targets.mac.MacTargetHelper can break app-builder-lib.src.macPackager, while a change to app-builder-lib.src.macPackager can't break app-builder-lib.src.targets.mac.MacTargetHelper.
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.
25→28 app-builder-lib.src.macPackager uses app-builder-lib.src.platformPackagerpart of a loop✕
Connections
1 pair of types, where a type in app-builder-lib.src.macPackager uses a type in app-builder-lib.src.platformPackager.
app-builder-lib.src.macPackager uses app-builder-lib.src.platformPackager, so a change to app-builder-lib.src.platformPackager can break app-builder-lib.src.macPackager, while a change to app-builder-lib.src.macPackager can't break app-builder-lib.src.platformPackager.
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.
25→29 app-builder-lib.src.macPackager uses app-builder-lib.src.configurationpart of a loop✕
Connections
1 pair of types, where a type in app-builder-lib.src.macPackager uses a type in app-builder-lib.src.configuration.
app-builder-lib.src.macPackager uses app-builder-lib.src.configuration, so a change to app-builder-lib.src.configuration can break app-builder-lib.src.macPackager, while a change to app-builder-lib.src.macPackager can't break app-builder-lib.src.configuration.
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.
electron-updater.src uses builder-util-runtime.src.CancellationToken, so a change to builder-util-runtime.src.CancellationToken can break electron-updater.src, while a change to electron-updater.src can't break builder-util-runtime.src.CancellationToken.
Position
Below the diagonal: electron-updater.src uses a module listed above it, which is the healthy direction.
electron-updater.src uses builder-util-runtime.src.updateInfo, so a change to builder-util-runtime.src.updateInfo can break electron-updater.src, while a change to electron-updater.src can't break builder-util-runtime.src.updateInfo.
Position
Below the diagonal: electron-updater.src uses a module listed above it, which is the healthy direction.
electron-updater.src uses builder-util.src.log, so a change to builder-util.src.log can break electron-updater.src, while a change to electron-updater.src can't break builder-util.src.log.
Position
Below the diagonal: electron-updater.src uses a module listed above it, which is the healthy direction.
electron-updater.src uses electron-updater.src.types, so a change to electron-updater.src.types can break electron-updater.src, while a change to electron-updater.src can't break electron-updater.src.types.
Position
Below the diagonal: electron-updater.src uses a module listed above it, which is the healthy direction.
electron-updater.src uses electron-updater.src.providers.Provider, so a change to electron-updater.src.providers.Provider can break electron-updater.src, while a change to electron-updater.src can't break electron-updater.src.providers.Provider.
Position
Below the diagonal: electron-updater.src uses a module listed above it, which is the healthy direction.
electron-updater.src uses electron-updater.src.AppUpdater, so a change to electron-updater.src.AppUpdater can break electron-updater.src, while a change to electron-updater.src can't break electron-updater.src.AppUpdater.
Position
Below the diagonal: electron-updater.src uses a module listed above it, which is the healthy direction.
app-builder-lib.src.targets.mac.MacTargetHelper uses app-builder-lib.src.codeSign.signResult, so a change to app-builder-lib.src.codeSign.signResult can break app-builder-lib.src.targets.mac.MacTargetHelper, while a change to app-builder-lib.src.targets.mac.MacTargetHelper can't break app-builder-lib.src.codeSign.signResult.
Position
Below the diagonal: app-builder-lib.src.targets.mac.MacTargetHelper uses a module listed above it, which is the healthy direction.
app-builder-lib.src.targets.mac.MacTargetHelper uses builder-util.src.arch, so a change to builder-util.src.arch can break app-builder-lib.src.targets.mac.MacTargetHelper, while a change to app-builder-lib.src.targets.mac.MacTargetHelper can't break builder-util.src.arch.
Position
Below the diagonal: app-builder-lib.src.targets.mac.MacTargetHelper uses a module listed above it, which is the healthy direction.
app-builder-lib.src.targets.mac.MacTargetHelper uses app-builder-lib.src.macPackager, so a change to app-builder-lib.src.macPackager can break app-builder-lib.src.targets.mac.MacTargetHelper, while a change to app-builder-lib.src.targets.mac.MacTargetHelper can't break app-builder-lib.src.macPackager.
Position
Below the diagonal: app-builder-lib.src.targets.mac.MacTargetHelper uses a module listed above it, which is the healthy direction.
app-builder-lib.src.platformPackager uses app-builder-lib.src.codeSign.signResult, so a change to app-builder-lib.src.codeSign.signResult can break app-builder-lib.src.platformPackager, while a change to app-builder-lib.src.platformPackager can't break app-builder-lib.src.codeSign.signResult.
Position
Below the diagonal: app-builder-lib.src.platformPackager uses a module listed above it, which is the healthy direction.
app-builder-lib.src.platformPackager uses builder-util-runtime.src.CancellationToken, so a change to builder-util-runtime.src.CancellationToken can break app-builder-lib.src.platformPackager, while a change to app-builder-lib.src.platformPackager can't break builder-util-runtime.src.CancellationToken.
Position
Below the diagonal: app-builder-lib.src.platformPackager uses a module listed above it, which is the healthy direction.
app-builder-lib.src.platformPackager uses builder-util.src.arch, so a change to builder-util.src.arch can break app-builder-lib.src.platformPackager, while a change to app-builder-lib.src.platformPackager can't break builder-util.src.arch.
Position
Below the diagonal: app-builder-lib.src.platformPackager uses a module listed above it, which is the healthy direction.
app-builder-lib.src.platformPackager uses app-builder-lib.src.core, so a change to app-builder-lib.src.core can break app-builder-lib.src.platformPackager, while a change to app-builder-lib.src.platformPackager can't break app-builder-lib.src.core.
Position
Below the diagonal: app-builder-lib.src.platformPackager uses a module listed above it, which is the healthy direction.
app-builder-lib.src.platformPackager uses app-builder-lib.src.electron.ElectronFramework, so a change to app-builder-lib.src.electron.ElectronFramework can break app-builder-lib.src.platformPackager, while a change to app-builder-lib.src.platformPackager can't break app-builder-lib.src.electron.ElectronFramework.
Position
Below the diagonal: app-builder-lib.src.platformPackager uses a module listed above it, which is the healthy direction.
app-builder-lib.src.platformPackager uses app-builder-lib.src.options.PlatformSpecificBuildOptions, so a change to app-builder-lib.src.options.PlatformSpecificBuildOptions can break app-builder-lib.src.platformPackager, while a change to app-builder-lib.src.platformPackager can't break app-builder-lib.src.options.PlatformSpecificBuildOptions.
Position
Below the diagonal: app-builder-lib.src.platformPackager uses a module listed above it, which is the healthy direction.
app-builder-lib.src.platformPackager uses app-builder-lib.src.packagerApi, so a change to app-builder-lib.src.packagerApi can break app-builder-lib.src.platformPackager, while a change to app-builder-lib.src.platformPackager can't break app-builder-lib.src.packagerApi.
Position
Below the diagonal: app-builder-lib.src.platformPackager uses a module listed above it, which is the healthy direction.
app-builder-lib.src.platformPackager uses app-builder-lib.src.packager, so a change to app-builder-lib.src.packager can break app-builder-lib.src.platformPackager, while a change to app-builder-lib.src.platformPackager can't break app-builder-lib.src.packager.
Position
Below the diagonal: app-builder-lib.src.platformPackager uses a module listed above it, which is the healthy direction.
app-builder-lib.src.platformPackager uses app-builder-lib.src.targets.mac.MacTargetHelper, so a change to app-builder-lib.src.targets.mac.MacTargetHelper can break app-builder-lib.src.platformPackager, while a change to app-builder-lib.src.platformPackager can't break app-builder-lib.src.targets.mac.MacTargetHelper.
Position
Below the diagonal: app-builder-lib.src.platformPackager uses a module listed above it, which is the healthy direction.
28→29 app-builder-lib.src.platformPackager uses app-builder-lib.src.configurationpart of a loop✕
Connections
2 pairs of types, where a type in app-builder-lib.src.platformPackager uses a type in app-builder-lib.src.configuration.
app-builder-lib.src.platformPackager uses app-builder-lib.src.configuration, so a change to app-builder-lib.src.configuration can break app-builder-lib.src.platformPackager, while a change to app-builder-lib.src.platformPackager can't break app-builder-lib.src.configuration.
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.
28→31 app-builder-lib.src.platformPackager uses app-builder-lib.src.Frameworkpart of a loop✕
Connections
1 pair of types, where a type in app-builder-lib.src.platformPackager uses a type in app-builder-lib.src.Framework.
app-builder-lib.src.platformPackager uses app-builder-lib.src.Framework, so a change to app-builder-lib.src.Framework can break app-builder-lib.src.platformPackager, while a change to app-builder-lib.src.platformPackager can't break app-builder-lib.src.Framework.
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.
app-builder-lib.src.configuration uses builder-util.src.arch, so a change to builder-util.src.arch can break app-builder-lib.src.configuration, while a change to app-builder-lib.src.configuration can't break builder-util.src.arch.
Position
Below the diagonal: app-builder-lib.src.configuration uses a module listed above it, which is the healthy direction.
app-builder-lib.src.configuration uses app-builder-lib.src.core, so a change to app-builder-lib.src.core can break app-builder-lib.src.configuration, while a change to app-builder-lib.src.configuration can't break app-builder-lib.src.core.
Position
Below the diagonal: app-builder-lib.src.configuration uses a module listed above it, which is the healthy direction.
app-builder-lib.src.configuration uses app-builder-lib.src.electron.ElectronFramework, so a change to app-builder-lib.src.electron.ElectronFramework can break app-builder-lib.src.configuration, while a change to app-builder-lib.src.configuration can't break app-builder-lib.src.electron.ElectronFramework.
Position
Below the diagonal: app-builder-lib.src.configuration uses a module listed above it, which is the healthy direction.
app-builder-lib.src.configuration uses app-builder-lib.src.platformPackager, so a change to app-builder-lib.src.platformPackager can break app-builder-lib.src.configuration, while a change to app-builder-lib.src.configuration can't break app-builder-lib.src.platformPackager.
Position
Below the diagonal: app-builder-lib.src.configuration uses a module listed above it, which is the healthy direction.
app-builder-lib.src.linuxPackager uses app-builder-lib.src.packager, so a change to app-builder-lib.src.packager can break app-builder-lib.src.linuxPackager, while a change to app-builder-lib.src.linuxPackager can't break app-builder-lib.src.packager.
Position
Below the diagonal: app-builder-lib.src.linuxPackager uses a module listed above it, which is the healthy direction.
app-builder-lib.src.linuxPackager uses app-builder-lib.src.platformPackager, so a change to app-builder-lib.src.platformPackager can break app-builder-lib.src.linuxPackager, while a change to app-builder-lib.src.linuxPackager can't break app-builder-lib.src.platformPackager.
Position
Below the diagonal: app-builder-lib.src.linuxPackager uses a module listed above it, which is the healthy direction.
app-builder-lib.src.Framework uses app-builder-lib.src.core, so a change to app-builder-lib.src.core can break app-builder-lib.src.Framework, while a change to app-builder-lib.src.Framework can't break app-builder-lib.src.core.
Position
Below the diagonal: app-builder-lib.src.Framework uses a module listed above it, which is the healthy direction.
app-builder-lib.src.Framework uses app-builder-lib.src.electron.ElectronFramework, so a change to app-builder-lib.src.electron.ElectronFramework can break app-builder-lib.src.Framework, while a change to app-builder-lib.src.Framework can't break app-builder-lib.src.electron.ElectronFramework.
Position
Below the diagonal: app-builder-lib.src.Framework uses a module listed above it, which is the healthy direction.
app-builder-lib.src.Framework uses app-builder-lib.src.targets.mac.MacTargetHelper, so a change to app-builder-lib.src.targets.mac.MacTargetHelper can break app-builder-lib.src.Framework, while a change to app-builder-lib.src.Framework can't break app-builder-lib.src.targets.mac.MacTargetHelper.
Position
Below the diagonal: app-builder-lib.src.Framework uses a module listed above it, which is the healthy direction.
app-builder-lib.src.Framework uses app-builder-lib.src.platformPackager, so a change to app-builder-lib.src.platformPackager can break app-builder-lib.src.Framework, while a change to app-builder-lib.src.Framework can't break app-builder-lib.src.platformPackager.
Position
Below the diagonal: app-builder-lib.src.Framework uses a module listed above it, which is the healthy direction.
app-builder-lib.src.Framework uses app-builder-lib.src.configuration, so a change to app-builder-lib.src.configuration can break app-builder-lib.src.Framework, while a change to app-builder-lib.src.Framework can't break app-builder-lib.src.configuration.
Position
Below the diagonal: app-builder-lib.src.Framework uses a module listed above it, which is the healthy direction.
app-builder-lib.src.targets uses builder-util-runtime.src.updateInfo, so a change to builder-util-runtime.src.updateInfo can break app-builder-lib.src.targets, while a change to app-builder-lib.src.targets can't break builder-util-runtime.src.updateInfo.
Position
Below the diagonal: app-builder-lib.src.targets uses a module listed above it, which is the healthy direction.
app-builder-lib.src.targets uses builder-util.src.arch, so a change to builder-util.src.arch can break app-builder-lib.src.targets, while a change to app-builder-lib.src.targets can't break builder-util.src.arch.
Position
Below the diagonal: app-builder-lib.src.targets uses a module listed above it, which is the healthy direction.
app-builder-lib.src.targets uses app-builder-lib.src.core, so a change to app-builder-lib.src.core can break app-builder-lib.src.targets, while a change to app-builder-lib.src.targets can't break app-builder-lib.src.core.
Position
Below the diagonal: app-builder-lib.src.targets uses a module listed above it, which is the healthy direction.
app-builder-lib.src.targets uses app-builder-lib.src.platformPackager, so a change to app-builder-lib.src.platformPackager can break app-builder-lib.src.targets, while a change to app-builder-lib.src.targets can't break app-builder-lib.src.platformPackager.
Position
Below the diagonal: app-builder-lib.src.targets uses a module listed above it, which is the healthy direction.
app-builder-lib.src.targets uses app-builder-lib.src.configuration, so a change to app-builder-lib.src.configuration can break app-builder-lib.src.targets, while a change to app-builder-lib.src.targets can't break app-builder-lib.src.configuration.
Position
Below the diagonal: app-builder-lib.src.targets uses a module listed above it, which is the healthy direction.
app-builder-lib.src.targets.linux.snap.SnapTarget uses builder-util.src.arch, so a change to builder-util.src.arch can break app-builder-lib.src.targets.linux.snap.SnapTarget, while a change to app-builder-lib.src.targets.linux.snap.SnapTarget can't break builder-util.src.arch.
Position
Below the diagonal: app-builder-lib.src.targets.linux.snap.SnapTarget uses a module listed above it, which is the healthy direction.
app-builder-lib.src.targets.linux.snap.SnapTarget uses app-builder-lib.src.core, so a change to app-builder-lib.src.core can break app-builder-lib.src.targets.linux.snap.SnapTarget, while a change to app-builder-lib.src.targets.linux.snap.SnapTarget can't break app-builder-lib.src.core.
Position
Below the diagonal: app-builder-lib.src.targets.linux.snap.SnapTarget uses a module listed above it, which is the healthy direction.
app-builder-lib.src.targets.linux.snap.SnapTarget uses app-builder-lib.src.configuration, so a change to app-builder-lib.src.configuration can break app-builder-lib.src.targets.linux.snap.SnapTarget, while a change to app-builder-lib.src.targets.linux.snap.SnapTarget can't break app-builder-lib.src.configuration.
Position
Below the diagonal: app-builder-lib.src.targets.linux.snap.SnapTarget uses a module listed above it, which is the healthy direction.
app-builder-lib.src.targets.linux.snap.SnapTarget uses app-builder-lib.src.linuxPackager, so a change to app-builder-lib.src.linuxPackager can break app-builder-lib.src.targets.linux.snap.SnapTarget, while a change to app-builder-lib.src.targets.linux.snap.SnapTarget can't break app-builder-lib.src.linuxPackager.
Position
Below the diagonal: app-builder-lib.src.targets.linux.snap.SnapTarget uses a module listed above it, which is the healthy direction.
app-builder-lib.src.util uses builder-util.src.arch, so a change to builder-util.src.arch can break app-builder-lib.src.util, while a change to app-builder-lib.src.util can't break builder-util.src.arch.
Position
Below the diagonal: app-builder-lib.src.util uses a module listed above it, which is the healthy direction.
app-builder-lib.src.util uses app-builder-lib.src.core, so a change to app-builder-lib.src.core can break app-builder-lib.src.util, while a change to app-builder-lib.src.util can't break app-builder-lib.src.core.
Position
Below the diagonal: app-builder-lib.src.util uses a module listed above it, which is the healthy direction.
app-builder-lib.src.util uses app-builder-lib.src.options.PlatformSpecificBuildOptions, so a change to app-builder-lib.src.options.PlatformSpecificBuildOptions can break app-builder-lib.src.util, while a change to app-builder-lib.src.util can't break app-builder-lib.src.options.PlatformSpecificBuildOptions.
Position
Below the diagonal: app-builder-lib.src.util uses a module listed above it, which is the healthy direction.
app-builder-lib.src.util uses app-builder-lib.src.packager, so a change to app-builder-lib.src.packager can break app-builder-lib.src.util, while a change to app-builder-lib.src.util can't break app-builder-lib.src.packager.
Position
Below the diagonal: app-builder-lib.src.util uses a module listed above it, which is the healthy direction.
app-builder-lib.src.util uses app-builder-lib.src.platformPackager, so a change to app-builder-lib.src.platformPackager can break app-builder-lib.src.util, while a change to app-builder-lib.src.util can't break app-builder-lib.src.platformPackager.
Position
Below the diagonal: app-builder-lib.src.util uses a module listed above it, which is the healthy direction.
app-builder-lib.src.util uses app-builder-lib.src.configuration, so a change to app-builder-lib.src.configuration can break app-builder-lib.src.util, while a change to app-builder-lib.src.util can't break app-builder-lib.src.configuration.
Position
Below the diagonal: app-builder-lib.src.util uses a module listed above it, which is the healthy direction.
app-builder-lib.src.winPackager uses app-builder-lib.src.codeSign.signResult, so a change to app-builder-lib.src.codeSign.signResult can break app-builder-lib.src.winPackager, while a change to app-builder-lib.src.winPackager can't break app-builder-lib.src.codeSign.signResult.
Position
Below the diagonal: app-builder-lib.src.winPackager uses a module listed above it, which is the healthy direction.
app-builder-lib.src.winPackager uses builder-util.src.arch, so a change to builder-util.src.arch can break app-builder-lib.src.winPackager, while a change to app-builder-lib.src.winPackager can't break builder-util.src.arch.
Position
Below the diagonal: app-builder-lib.src.winPackager uses a module listed above it, which is the healthy direction.
app-builder-lib.src.winPackager uses app-builder-lib.src.options.winOptions, so a change to app-builder-lib.src.options.winOptions can break app-builder-lib.src.winPackager, while a change to app-builder-lib.src.winPackager can't break app-builder-lib.src.options.winOptions.
Position
Below the diagonal: app-builder-lib.src.winPackager uses a module listed above it, which is the healthy direction.
app-builder-lib.src.winPackager uses app-builder-lib.src.packager, so a change to app-builder-lib.src.packager can break app-builder-lib.src.winPackager, while a change to app-builder-lib.src.winPackager can't break app-builder-lib.src.packager.
Position
Below the diagonal: app-builder-lib.src.winPackager uses a module listed above it, which is the healthy direction.
app-builder-lib.src.winPackager uses app-builder-lib.src.platformPackager, so a change to app-builder-lib.src.platformPackager can break app-builder-lib.src.winPackager, while a change to app-builder-lib.src.winPackager can't break app-builder-lib.src.platformPackager.
Position
Below the diagonal: app-builder-lib.src.winPackager uses a module listed above it, which is the healthy direction.
app-builder-lib.src.winPackager uses app-builder-lib.src.configuration, so a change to app-builder-lib.src.configuration can break app-builder-lib.src.winPackager, while a change to app-builder-lib.src.winPackager can't break app-builder-lib.src.configuration.
Position
Below the diagonal: app-builder-lib.src.winPackager uses a module listed above it, which is the healthy direction.
app-builder-lib.src uses app-builder-lib.src.node-module-collector.packageManager, so a change to app-builder-lib.src.node-module-collector.packageManager can break app-builder-lib.src, while a change to app-builder-lib.src can't break app-builder-lib.src.node-module-collector.packageManager.
Position
Below the diagonal: app-builder-lib.src uses a module listed above it, which is the healthy direction.
app-builder-lib.src uses builder-util.src.arch, so a change to builder-util.src.arch can break app-builder-lib.src, while a change to app-builder-lib.src can't break builder-util.src.arch.
Position
Below the diagonal: app-builder-lib.src uses a module listed above it, which is the healthy direction.
app-builder-lib.src uses app-builder-lib.src.core, so a change to app-builder-lib.src.core can break app-builder-lib.src, while a change to app-builder-lib.src can't break app-builder-lib.src.core.
Position
Below the diagonal: app-builder-lib.src uses a module listed above it, which is the healthy direction.
app-builder-lib.src uses app-builder-lib.src.options.PlatformSpecificBuildOptions, so a change to app-builder-lib.src.options.PlatformSpecificBuildOptions can break app-builder-lib.src, while a change to app-builder-lib.src can't break app-builder-lib.src.options.PlatformSpecificBuildOptions.
Position
Below the diagonal: app-builder-lib.src uses a module listed above it, which is the healthy direction.
app-builder-lib.src uses app-builder-lib.src.packagerApi, so a change to app-builder-lib.src.packagerApi can break app-builder-lib.src, while a change to app-builder-lib.src can't break app-builder-lib.src.packagerApi.
Position
Below the diagonal: app-builder-lib.src uses a module listed above it, which is the healthy direction.
app-builder-lib.src uses app-builder-lib.src.packager, so a change to app-builder-lib.src.packager can break app-builder-lib.src, while a change to app-builder-lib.src can't break app-builder-lib.src.packager.
Position
Below the diagonal: app-builder-lib.src uses a module listed above it, which is the healthy direction.
app-builder-lib.src uses app-builder-lib.src.platformPackager, so a change to app-builder-lib.src.platformPackager can break app-builder-lib.src, while a change to app-builder-lib.src can't break app-builder-lib.src.platformPackager.
Position
Below the diagonal: app-builder-lib.src uses a module listed above it, which is the healthy direction.
app-builder-lib.src uses app-builder-lib.src.configuration, so a change to app-builder-lib.src.configuration can break app-builder-lib.src, while a change to app-builder-lib.src can't break app-builder-lib.src.configuration.
Position
Below the diagonal: app-builder-lib.src uses a module listed above it, which is the healthy direction.
app-builder-lib.src uses app-builder-lib.src.Framework, so a change to app-builder-lib.src.Framework can break app-builder-lib.src, while a change to app-builder-lib.src can't break app-builder-lib.src.Framework.
Position
Below the diagonal: app-builder-lib.src uses a module listed above it, which is the healthy direction.
app-builder-lib.src.codeSign.win.signtoolBaseSignManager uses app-builder-lib.src.codeSign.signResult, so a change to app-builder-lib.src.codeSign.signResult can break app-builder-lib.src.codeSign.win.signtoolBaseSignManager, while a change to app-builder-lib.src.codeSign.win.signtoolBaseSignManager can't break app-builder-lib.src.codeSign.signResult.
Position
Below the diagonal: app-builder-lib.src.codeSign.win.signtoolBaseSignManager uses a module listed above it, which is the healthy direction.
app-builder-lib.src.codeSign.win.signtoolBaseSignManager uses app-builder-lib.src.vm.vm, so a change to app-builder-lib.src.vm.vm can break app-builder-lib.src.codeSign.win.signtoolBaseSignManager, while a change to app-builder-lib.src.codeSign.win.signtoolBaseSignManager can't break app-builder-lib.src.vm.vm.
Position
Below the diagonal: app-builder-lib.src.codeSign.win.signtoolBaseSignManager uses a module listed above it, which is the healthy direction.
app-builder-lib.src.codeSign.win.signtoolBaseSignManager uses app-builder-lib.src.core, so a change to app-builder-lib.src.core can break app-builder-lib.src.codeSign.win.signtoolBaseSignManager, while a change to app-builder-lib.src.codeSign.win.signtoolBaseSignManager can't break app-builder-lib.src.core.
Position
Below the diagonal: app-builder-lib.src.codeSign.win.signtoolBaseSignManager uses a module listed above it, which is the healthy direction.
app-builder-lib.src.codeSign.win.signtoolBaseSignManager uses app-builder-lib.src.options.winOptions, so a change to app-builder-lib.src.options.winOptions can break app-builder-lib.src.codeSign.win.signtoolBaseSignManager, while a change to app-builder-lib.src.codeSign.win.signtoolBaseSignManager can't break app-builder-lib.src.options.winOptions.
Position
Below the diagonal: app-builder-lib.src.codeSign.win.signtoolBaseSignManager uses a module listed above it, which is the healthy direction.
app-builder-lib.src.codeSign.win.signtoolBaseSignManager uses app-builder-lib.src.codeSign.win.signManager, so a change to app-builder-lib.src.codeSign.win.signManager can break app-builder-lib.src.codeSign.win.signtoolBaseSignManager, while a change to app-builder-lib.src.codeSign.win.signtoolBaseSignManager can't break app-builder-lib.src.codeSign.win.signManager.
Position
Below the diagonal: app-builder-lib.src.codeSign.win.signtoolBaseSignManager uses a module listed above it, which is the healthy direction.
app-builder-lib.src.codeSign.win.signtoolBaseSignManager uses app-builder-lib.src.winPackager, so a change to app-builder-lib.src.winPackager can break app-builder-lib.src.codeSign.win.signtoolBaseSignManager, while a change to app-builder-lib.src.codeSign.win.signtoolBaseSignManager can't break app-builder-lib.src.winPackager.
Position
Below the diagonal: app-builder-lib.src.codeSign.win.signtoolBaseSignManager uses a module listed above it, which is the healthy direction.
app-builder-lib.src.publish uses builder-util-runtime.src.CancellationToken, so a change to builder-util-runtime.src.CancellationToken can break app-builder-lib.src.publish, while a change to app-builder-lib.src.publish can't break builder-util-runtime.src.CancellationToken.
Position
Below the diagonal: app-builder-lib.src.publish uses a module listed above it, which is the healthy direction.
app-builder-lib.src.publish uses builder-util-runtime.src.publishOptions, so a change to builder-util-runtime.src.publishOptions can break app-builder-lib.src.publish, while a change to app-builder-lib.src.publish can't break builder-util-runtime.src.publishOptions.
Position
Below the diagonal: app-builder-lib.src.publish uses a module listed above it, which is the healthy direction.
app-builder-lib.src.publish uses builder-util-runtime.src.updateInfo, so a change to builder-util-runtime.src.updateInfo can break app-builder-lib.src.publish, while a change to app-builder-lib.src.publish can't break builder-util-runtime.src.updateInfo.
Position
Below the diagonal: app-builder-lib.src.publish uses a module listed above it, which is the healthy direction.
app-builder-lib.src.publish uses builder-util.src.arch, so a change to builder-util.src.arch can break app-builder-lib.src.publish, while a change to app-builder-lib.src.publish can't break builder-util.src.arch.
Position
Below the diagonal: app-builder-lib.src.publish uses a module listed above it, which is the healthy direction.
app-builder-lib.src.publish uses app-builder-lib.src.core, so a change to app-builder-lib.src.core can break app-builder-lib.src.publish, while a change to app-builder-lib.src.publish can't break app-builder-lib.src.core.
Position
Below the diagonal: app-builder-lib.src.publish uses a module listed above it, which is the healthy direction.
app-builder-lib.src.publish uses electron-publish.src, so a change to electron-publish.src can break app-builder-lib.src.publish, while a change to app-builder-lib.src.publish can't break electron-publish.src.
Position
Below the diagonal: app-builder-lib.src.publish uses a module listed above it, which is the healthy direction.
app-builder-lib.src.publish uses app-builder-lib.src.options.PlatformSpecificBuildOptions, so a change to app-builder-lib.src.options.PlatformSpecificBuildOptions can break app-builder-lib.src.publish, while a change to app-builder-lib.src.publish can't break app-builder-lib.src.options.PlatformSpecificBuildOptions.
Position
Below the diagonal: app-builder-lib.src.publish uses a module listed above it, which is the healthy direction.
app-builder-lib.src.publish uses app-builder-lib.src.packagerApi, so a change to app-builder-lib.src.packagerApi can break app-builder-lib.src.publish, while a change to app-builder-lib.src.publish can't break app-builder-lib.src.packagerApi.
Position
Below the diagonal: app-builder-lib.src.publish uses a module listed above it, which is the healthy direction.
app-builder-lib.src.publish uses app-builder-lib.src.packager, so a change to app-builder-lib.src.packager can break app-builder-lib.src.publish, while a change to app-builder-lib.src.publish can't break app-builder-lib.src.packager.
Position
Below the diagonal: app-builder-lib.src.publish uses a module listed above it, which is the healthy direction.
app-builder-lib.src.publish uses app-builder-lib.src.platformPackager, so a change to app-builder-lib.src.platformPackager can break app-builder-lib.src.publish, while a change to app-builder-lib.src.publish can't break app-builder-lib.src.platformPackager.
Position
Below the diagonal: app-builder-lib.src.publish uses a module listed above it, which is the healthy direction.
app-builder-lib.src.publish uses app-builder-lib.src.configuration, so a change to app-builder-lib.src.configuration can break app-builder-lib.src.publish, while a change to app-builder-lib.src.publish can't break app-builder-lib.src.configuration.
Position
Below the diagonal: app-builder-lib.src.publish uses a module listed above it, which is the healthy direction.
app-builder-lib.src.publish uses app-builder-lib.src.winPackager, so a change to app-builder-lib.src.winPackager can break app-builder-lib.src.publish, while a change to app-builder-lib.src.publish can't break app-builder-lib.src.winPackager.
Position
Below the diagonal: app-builder-lib.src.publish uses a module listed above it, which is the healthy direction.
app-builder-lib.src.targets.win.nsis.NsisTarget uses builder-util.src.arch, so a change to builder-util.src.arch can break app-builder-lib.src.targets.win.nsis.NsisTarget, while a change to app-builder-lib.src.targets.win.nsis.NsisTarget can't break builder-util.src.arch.
Position
Below the diagonal: app-builder-lib.src.targets.win.nsis.NsisTarget uses a module listed above it, which is the healthy direction.
app-builder-lib.src.targets.win.nsis.NsisTarget uses app-builder-lib.src.core, so a change to app-builder-lib.src.core can break app-builder-lib.src.targets.win.nsis.NsisTarget, while a change to app-builder-lib.src.targets.win.nsis.NsisTarget can't break app-builder-lib.src.core.
Position
Below the diagonal: app-builder-lib.src.targets.win.nsis.NsisTarget uses a module listed above it, which is the healthy direction.
app-builder-lib.src.targets.win.nsis.NsisTarget uses app-builder-lib.src.winPackager, so a change to app-builder-lib.src.winPackager can break app-builder-lib.src.targets.win.nsis.NsisTarget, while a change to app-builder-lib.src.targets.win.nsis.NsisTarget can't break app-builder-lib.src.winPackager.
Position
Below the diagonal: app-builder-lib.src.targets.win.nsis.NsisTarget uses a module listed above it, which is the healthy direction.
app-builder-lib.src.codeSign.win uses app-builder-lib.src.codeSign.signResult, so a change to app-builder-lib.src.codeSign.signResult can break app-builder-lib.src.codeSign.win, while a change to app-builder-lib.src.codeSign.win can't break app-builder-lib.src.codeSign.signResult.
Position
Below the diagonal: app-builder-lib.src.codeSign.win uses a module listed above it, which is the healthy direction.
app-builder-lib.src.codeSign.win uses app-builder-lib.src.options.winOptions, so a change to app-builder-lib.src.options.winOptions can break app-builder-lib.src.codeSign.win, while a change to app-builder-lib.src.codeSign.win can't break app-builder-lib.src.options.winOptions.
Position
Below the diagonal: app-builder-lib.src.codeSign.win uses a module listed above it, which is the healthy direction.
app-builder-lib.src.codeSign.win uses app-builder-lib.src.codeSign.win.signManager, so a change to app-builder-lib.src.codeSign.win.signManager can break app-builder-lib.src.codeSign.win, while a change to app-builder-lib.src.codeSign.win can't break app-builder-lib.src.codeSign.win.signManager.
Position
Below the diagonal: app-builder-lib.src.codeSign.win uses a module listed above it, which is the healthy direction.
app-builder-lib.src.codeSign.win uses app-builder-lib.src.winPackager, so a change to app-builder-lib.src.winPackager can break app-builder-lib.src.codeSign.win, while a change to app-builder-lib.src.codeSign.win can't break app-builder-lib.src.winPackager.
Position
Below the diagonal: app-builder-lib.src.codeSign.win uses a module listed above it, which is the healthy direction.
app-builder-lib.src.codeSign.win uses app-builder-lib.src.codeSign.win.signtoolBaseSignManager, so a change to app-builder-lib.src.codeSign.win.signtoolBaseSignManager can break app-builder-lib.src.codeSign.win, while a change to app-builder-lib.src.codeSign.win can't break app-builder-lib.src.codeSign.win.signtoolBaseSignManager.
Position
Below the diagonal: app-builder-lib.src.codeSign.win uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 58.7 · Adequate · gated by D2 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
50
High / Critical
A02:2025 — Security Misconfiguration
16
High / Critical
A03:2025 — Software Supply Chain Failures
15
High / Critical
A07:2025 — Authentication Failures
2
High / Critical
Roadmap
Top priorities: Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies; Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing; Resolve the 3 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (3).
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 3 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (3).
Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
Route service-code `console.*` output through the module's structured logger (with named fields), so delivery outcomes and failures reach the log pipeline with a level.
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 — 64
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 — 670
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 — 310
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 5
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 75 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 — 75 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, 985 of 1044 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.
D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the dependency install for test/ failed in the analyzer sandbox (ERR_PNPM_UNSUPPORTED_ENGINE Unsupported environment (bad pnpm and/or Node.js version)), so the suite never ran. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
D11 Test Reliability — 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. Test reliability NOT MEASURED: the JavaScript/TypeScript suite could not be re-run in the analyzer sandbox — the dependency install for test/ failed in the analyzer sandbox (ERR_PNPM_UNSUPPORTED_ENGINE Unsupported environment (bad pnpm and/or Node.js version)), so the suite never ran. This is OUR limitation, not a defect in the repo — it is excluded from the score.
D11 Test Reliability — 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. Test reliability for the vitest suite in test/ was NOT MEASURED: the dependency install for test/ failed in the analyzer sandbox (ERR_PNPM_UNSUPPORTED_ENGINE Unsupported environment (bad pnpm and/or Node.js version)), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
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 naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated per language (docs/plans/deterministic-engine.md, P5; C# and each NeutralApiArms arm pass): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
D23 Boundary Type-Coupling — 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 measured 0/40 valid on a seeded held-out sample of its rows on 98 C# repositories (docs/plans/deterministic-engine/adjudication/P5c-D23-units.md, "Version 1 ON MAIN"): the noise rows were dependencies on layer folders, shared cores and grouping folders read as contexts. By the pre-registered fallback (PREREGISTRATION v37) it publishes no row until version 4 passes its gate. The candidates are counted here, not reported as findings, and the score does not include them.
D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `packages/app-builder-lib/src/forge-maker.ts`, `packages/app-builder-lib/src/platformPackager.ts`, `website/docusaurus.config.ts` 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.
IC1 Incompleteness & stubs — 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. 21 further occurrence(s) are not listed individually; the score already reflects all 61.
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.
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.
R10 Code Duplication — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 13 further occurrence(s) are not listed individually; the score already reflects all 53.
R2 Cyclomatic Complexity — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 184 further occurrence(s) are not listed individually; the score already reflects all 224.
R3 Large Files — 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. 4 further occurrence(s) are not listed individually; the score already reflects all 44.
X3 Exception handling — 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. 13 further occurrence(s) are not listed individually; the score already reflects all 53.
X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala, Rust, Go, Swift, Erlang, F# and Visual Basic source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP log through no library that carries a message's values as fields (pino, winston, bunyan, tslog, LogTape, roarr; Python's logging, structlog; PHP's PSR-3 loggers), so its log calls cannot be judged, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
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 REDACTED Scanning: REDACTED 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.
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.
D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (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.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
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.
91 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was migrate-schema.migrateConfig at 109. A further 1 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 GitlabPublisher.categorizeGitlabError at 16 — 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: packages/electron-publish/src/gitlabPublisher.ts (GitlabPublisher.categorizeGitlabError at 16). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
+ 86 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 1 body over 60 down to 60 or less in Cyclomatic Complexity — start with migrate-schema.migrateConfig (cyclomatic 109). — Refactoring it lifts Cyclomatic Complexity from 5.0 to about 5.9/10.
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.
+ 146 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 1 body over 120 down to 120 or less in Cognitive Complexity — start with migrate-schema.migrateConfig (cognitive 168). — Refactoring it lifts Cognitive Complexity from 2.0 to about 2.7/10.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.8 / 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 11 FileTooLong finding(s) in God Classes — start with migrate-schema-programmatic.ts, REDACTED, AppUpdater.ts. — One of this dimension's main actionable groups (11 warning-level).
Resolve the 5 TooManyMethods finding(s) in God Classes — start with migrate-schema-programmatic.ts, platformPackager.ts, AppUpdater.ts. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 4 FunctionTooLong finding(s) in God Classes — start with electronMac.ts, docusaurus-plugin-changelog.ts, hoist.ts. — One of this dimension's main actionable groups (4 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling3.7 / 10Weak✓ 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.
12 production modules (npm), 1 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 2 module(s) off the main sequence, with abstractness counted on 8 of the 12 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
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 3 Low cohesion finding(s) in Cohesion (LCOM4) — start with macPackager.ts, REDACTED, NsisUpdater.ts. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D10 · Test Quality9.7 / 10Stronggated by 98 serious findings✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
84 skipped (68 with a documented reason), 80 zero-assertion, 2 synchronised by a fixed sleep, no mocking-framework packages referenced (hand-written doubles or no mocking) across 4946 tests.
No assertions: build in the app REDACTED · ×80test/src/BuildTest.ts:124
Fixed-sleep synchronisation: waits for the archive of the same pack before writing app-update.yml, even once finishBuild() drained it · ×2test/src/linux/appImageTargetPackWorkTest.ts:75
Mock-dominated test: aborts and logs error when cache dir resolves to filesystem root · ×6test/src/cliTest.ts:111
Resolve the 80 No assertions finding(s) in Test Quality — start with linuxPackagerTestSuite.ts (9), dmg.e2e.ts (8), msiTestSuite.ts (5). — One of this dimension's main actionable groups (80 warning-level).
Resolve the 16 Skipped test finding(s) in Test Quality — start with nsisUpdaterTest.ts (3), nsisWineTestSuite.ts (2), oneClickInstaller.e2e.ts (2). — One of this dimension's main actionable groups (16 warning-level).
Resolve the 2 Fixed-sleep synchronisation finding(s) in Test Quality — start with appImageTargetPackWorkTest.ts, fpmTargetPackWorkTest.ts. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
51 outdated direct production npm dependency(ies) of 71 graded, 0 pinning defect(s), across 25 REDACTED (13 of them the product) and 5 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 0 direct dependency(ies) — production, development or optional — are marked DEPRECATED by their publisher (the registry's per-version mark, or the lockfile's copy of it when the registry could not be asked); deprecated transitive packages are listed but not charged. Whether any is UNMAINTAINED is not graded — the registry publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, and the frontend dependency lens (R8) answers it in this same run. Known CVEs in this dependency graph are D30's question, read from the manifest there.
Resolve the 3 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (3). — One of this dimension's main actionable groups (3 recommendation-level).
Resolve the 3 Outdated (npm) finding(s) in Dependency Hygiene — start with REDACTED (3). — One of this dimension's main actionable groups (3 recommendation-level).
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
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 1276 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 1276 package(s) this repository's committed lockfile installs for a consumer — its 72 production, optional and peer dependency(ies), across 13 product REDACTED manifest(s), and everything those install in turn. Its 105 `devDependencies` declaration(s), and every package only they reach, are excluded: a consumer installs none of them. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. 1 of them publish no licence this pass can read on registry.npmjs.org — an absent field, `UNLICENSED`, or a `SEE LICENSE IN <file>` pointer into a tarball this pass does not download; that is missing data, not a violation, and none of them is charged. No third-party code was found shipping without a manifest entry (vendored or copied-in directories, licence comments preserved in committed bundles, bundled module paths, compiled wasm modules). This repository publishes itself under MIT, which is its own choice and is not judged here.
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 (16×109=1744); packages/electron-updater/src/AppUpdater.ts (43×31=1333); packages/app-builder-lib/src/targets/win/nsis/NsisTarget.ts (23×37=851) Repeated repair below the complexity floor: packages/electron-updater/src/MacUpdater.ts (7 of 10 changes were fixes); REDACTED (6 of 10 changes were fixes); packages/electron-updater/src/differentialDownloader/multipleRangeDownloader.ts (5 of 8 changes were fixes)
Resolve the 31 Hotspot finding(s) in Churn × Complexity Hotspots — start with REDACTED, AppUpdater.ts, NsisTarget.ts. — One of this dimension's main actionable groups (31 warning-level).
Resolve the 18 Repeated repair finding(s) in Churn × Complexity Hotspots — start with MacUpdater.ts, REDACTED, multipleRangeDownloader.ts. — One of this dimension's main actionable groups (18 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 Factor9.3 / 10Exemplary✓ 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.
16 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is packages/app-builder-lib/src/targets/linux/snap/snapPlugs.ts. Counted over 212 of the 310 production source files in this repository: 97 are under the ~2,400-byte size floor this dimension measures over, and the remaining 1 have no attributable history left to measure.
Off-boarding risk: anonymized user #1
Further sole-owners (lower concentration)
✓ On the Gold path — maintain.
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.
7 deducted task-comment markers across 64047 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
Resolve the 7 TodoComment finding(s) in Explicit Debt — start with smart-config.ts, appxTestSuite.ts, macUpdaterTest.ts. — One of this dimension's main actionable groups (7 warning-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
1 of 2 documentation facets pass in full; short on: F2 example. 76 document(s) read across 16 unit(s).
Documentation: no build, run or usage example · ×11packages/app-builder-lib/README.md:1
What to do
Resolve the 11 Documentation finding(s) in Documentation Quality — start with readme.md (9), README.md (2). — One of this dimension's main actionable groups (11 recommendation-level).
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: 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.
No ADRs foundpackages/electron-builder/package.json:29
What to do
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
2 naming inconsistencies among 29 declarations measured against a convention their peers follow.
`stopAtPackageJSON` spells `JSON` where 27 names in the project spell it `Json` · ×2packages/app-builder-lib/src/electron/search-module.ts:4
What to do
Resolve the 2 `stopAtPackageJSON` spells `JSON` where 27 names in the project spell it… finding(s) in Naming Consistency — start with search-module.ts (2). — One of this dimension's main actionable groups (2 recommendation-level).
Detailed fixes: d21_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether domain types (IDs, enums, value objects) leak across bounded-context boundaries.
Method: Cross-context domain-type leakage via Roslyn structural classification (strongly-typed IDs / value objects) over every public surface. Exhaustive, deterministic, type-level aggregate-boundary check.
Coverage: Bounded contexts derived from NAMESPACE prefix (or graph-inferred where available); cross-boundary domain-type leakage then checked exhaustively over every public member of every type.
173 domain type(s) cross context boundaries across 13 contexts; they are measured and withheld (not published, not scored). Contexts: app-builder-lib, builder-util, builder-util-runtime, dmg-builder, electron-builder, electron-builder-squirrel-windows, electron-forge-maker-appimage, electron-forge-maker-nsis, electron-forge-maker-nsis-web, electron-forge-maker-snap, electron-publish, electron-updater and 1 more.
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.
doc comments repeat the names · ×3packages/app-builder-lib/src/node-module-collector/hoist.ts:163
What to do
Resolve the 31 redundant comment finding(s) in Comment Value — start with index.js (11), githubProviderTest.ts (3), GitLabProvider.ts (2). — One of this dimension's main actionable groups (31 recommendation-level).
Detailed fixes: d24_recommendation.md · top locations in Appendix A, every location in findings.md.
1 of 15 build units (npm) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesionpackages/app-builder-lib/package.json:1
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
24 % of calls cross a namespace and 0 % go through an interface, but 84 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: REDACTED 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.
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
What to do
Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
50 finding(s): 0 critical, 38 high, 12 medium, 0 low. semgrep hit a parse error in 7 file(s) — `packages/app-builder-lib/src/forge-maker.ts` (line 61), `packages/app-builder-lib/src/platformPackager.ts` (line 318), `packages/app-builder-lib/templates/nsis/assistedMessages.yml`, `packages/app-builder-lib/templates/nsis/messages.yml`, `packages/app-builder-lib/templates/nsis/multiUserUi.nsh` (lines 1–230), … (+2 more) — 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 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 4 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 28 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (19), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (28 issue-level).
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).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
Resolve the 4 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-level).
Resolve the 6 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (6). — One of this dimension's main actionable groups (6 warning-level).
Resolve the 3 Low CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 recommendation-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 8 High IaC finding(s) in IaC & Container Security — start with REDACTED (8). — One of this dimension's main actionable groups (8 issue-level).
Resolve the 8 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (5), REDACTED (3). — One of this dimension's main actionable groups (8 warning-level).
Detailed fixes: d31_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.
22 of 213 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is packages/app-builder-lib/src/node-module-collector/hoist.ts. Counted over 213 of the 310 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with hoist.ts. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 21 Orphaned file finding(s) in Knowledge Freshness — start with downloadPlanBuilder.ts, normalizePackageData.ts, AppxCapabilities.ts. — One of this dimension's main actionable groups (21 recommendation-level).
Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
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 — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
The projects app-builder-lib → dmg-builder → app-builder-lib (one cycle inside a mutually-dependent group of 3 projects) form a reference cycle. Cyclic dependencies prevent independent build/test/deploy, blur ownership, and tend to grow into a big ball of mud. Break the cycle by extracting the shared types into a separate project both can reference. — packages/app-builder-lib/package.json:118
What to do
Break project reference cycles by extracting shared abstractions into a separate project; keep the graph a DAG.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
Other · Code Health — Unreviewed-generation residue in this repository's JavaScript/TypeScript: functions whose whole body still throws a "not implemented" error, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings and JSX of non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's JavaScript/TypeScript: functions that only throw a "not implemented" error, functions that take inputs and return a constant or do nothing, async functions that never await, dead `if (false)` branches, and skeleton classes most of whose methods are holes.
Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.
A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×40) — test/src/ArtifactPublisherTest.ts:46, test/src/HoistedNodeModuleTest.ts:298, test/src/globTest.ts:117, …
What to do
Clear the softer debt: re-enable or delete skipped tests, decide whether each empty function is a deliberate no-op (and say so in a comment), and replace blanket `eslint-disable` / `@ts-nocheck` with targeted, justified suppressions.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
website/docs/architecture.md names Electron 43, but the manifest declares `electron` 42.11.16. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — website/docs/architecture.md:19
website/docs/migration/v27-build-changes.md names Electron 44, but the manifest declares `electron` 42.11.16. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — website/docs/migration/v27-build-changes.md:34
What to do
Reconcile the README with reality: website/docs/architecture.md names Electron 43, but the manifest declares `electron` 42.11.16; website/docs/migration/v27-build-changes.md names Electron 44, but the manifest declares `electron` 42.11.16.
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
Do you agree with this assessment?
P2 · Observability7.0 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
`packages/app-builder-lib/src/node-module-collector/hoist.ts` reports through `console.*` at line 206 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/app-builder-lib/src/node-module-collector/hoist.ts:206
`packages/app-builder-lib/src/node-module-collector/hoist.ts` reports through `console.*` at line 218 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/app-builder-lib/src/node-module-collector/hoist.ts:218
`packages/builder-util/src/promise.ts` reports through `console.*` at line 4 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/builder-util/src/promise.ts:4
What to do
Route service-code `console.*` output through the module's structured logger (with named fields), so delivery outcomes and failures reach the log pipeline with a level.
Add a health-check endpoint (@godaddy/terminus or a /health route) so orchestrators and load balancers can probe liveness/readiness.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 10 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:27
What to do
Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
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.
`fs.existsSync` in `copyFFMPEG` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/app-builder-lib/src/electron/injectFFMPEG.ts:70
`fs.existsSync` in `safeParsePlistFile` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/app-builder-lib/src/electron/mac/electronMac.ts:53
`fs.existsSync` in `shouldContinueSearch` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/app-builder-lib/src/electron/search-module.ts:8
`fs.existsSync` in `traverseAncestorDirectories` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/app-builder-lib/src/electron/search-module.ts:28
`readdirSync` in `buildComponentPackage` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/app-builder-lib/src/targets/mac/pkg.ts:279
`zlib.inflateRawSync` in `exec` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/app-builder-lib/src/targets/win/nsis/nsisUtil.ts:266
`realpathSync` in `collectNodeModules` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/app-builder-lib/src/util/NodeModuleCopyHelper.ts:177
`execFileSync` in `suspendSync` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/app-builder-lib/src/vm/ParallelsVm.ts:101
`execFileSync` in `doDownloadUpdate` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — packages/electron-updater/src/MacUpdater.ts:71, packages/electron-updater/src/MacUpdater.ts:81
`rmSync` in `prebuildPlugin` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — website/scripts/docusaurus-plugin-prebuild.ts:146
`execSync` in `prebuildPlugin` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — website/scripts/docusaurus-plugin-prebuild.ts:148
`execSync` in `postBuild` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — website/scripts/docusaurus-plugin-prebuild.ts:160
What to do
TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.
Do you agree with this assessment?
R1 · Type Safety9.8 / 10Exemplary✓ Tool-verified
React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.
Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.
React / JS · Code Health — The share of the scored frontend lines inside a near-exact copy-pasted block of substantial extent (the D4 clone algorithm over JS/TS tokens, D-386; each line once, 10 at none and 0 at a quarter of the lines, as D4): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.
Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Scored on the share of the scored frontend lines inside a reported copy, on the same curve as D4. Deterministic.
11 duplicated blocks under packages/ have copies in at least two of the sibling directories app-builder-lib, builder-util, builder-util-runtime, dmg-builder, electron-builder, electron-builder-squirrel-windows (+6 more sibling(s) not listed) — 5 of them are reported below, and 6 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 11 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 11 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 11 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/builder-util-runtime/src/ProgressCallbackTransform.ts:17
packages/app-builder-lib/src/targets/win/AppxTarget.ts:63 · packages/app-builder-lib/src/targets/win/MsixTarget.ts:161 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — packages/app-builder-lib/src/targets/win/AppxTarget.ts:63
packages/builder-util-runtime/src/ProgressCallbackTransform.ts:17 · packages/electron-updater/src/differentialDownloader/ProgressDifferentialDownloadCallbackTransform.ts:30 — the two spans are one implementation copied and then locally edited — 278 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/builder-util-runtime/src/ProgressCallbackTransform.ts:17
packages/app-builder-lib/src/codeSign/win/authenticodeSignature.ts:210 · packages/electron-updater/src/windowsExecutableVersion.ts:17 — the two spans are one implementation copied and then locally edited — 218 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/app-builder-lib/src/codeSign/win/authenticodeSignature.ts:210
packages/app-builder-lib/src/targets/linux/appimage/AppImageTarget.ts:104 · packages/app-builder-lib/src/targets/linux/appimage/AppImageTarget.ts:137 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/app-builder-lib/src/targets/linux/appimage/AppImageTarget.ts:104
REDACTED:24 · REDACTED:595 — the two spans are one implementation copied and then locally edited — 146 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — REDACTED:24
packages/app-builder-lib/src/node-module-collector/moduleManager.ts:354 · packages/app-builder-lib/src/node-module-collector/moduleManager.ts:390 — the two spans are one implementation copied and then locally edited — 144 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/app-builder-lib/src/node-module-collector/moduleManager.ts:354
packages/app-builder-lib/src/targets/linux/snap/core24.ts:477 · packages/app-builder-lib/src/targets/linux/snap/snapPlugs.ts:200 — the two spans are one implementation copied and then locally edited — 120 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/app-builder-lib/src/targets/linux/snap/core24.ts:477
packages/electron-updater/src/DebUpdater.ts:36 · packages/electron-updater/src/RpmUpdater.ts:33 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — packages/electron-updater/src/DebUpdater.ts:36
packages/electron-updater/src/differentialDownloader/blockMapV3Fetcher.ts:217 · packages/electron-updater/src/differentialDownloader/blockMapV3Fetcher.ts:238 — 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. — packages/electron-updater/src/differentialDownloader/blockMapV3Fetcher.ts:217
packages/electron-updater/src/DebUpdater.ts:16 · packages/electron-updater/src/PacmanUpdater.ts:14 · packages/electron-updater/src/RpmUpdater.ts:16 — the 3 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — packages/electron-updater/src/DebUpdater.ts:16
packages/electron-updater/src/providers/BitbucketProvider.ts:20 · packages/electron-updater/src/providers/KeygenProvider.ts:21 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/electron-updater/src/providers/BitbucketProvider.ts:20
packages/app-builder-lib/src/macPackager.ts:358 · packages/app-builder-lib/src/platformPackager.ts:492 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — packages/app-builder-lib/src/macPackager.ts:358
packages/app-builder-lib/src/targets/linux/snap/coreLegacy.ts:121 · packages/app-builder-lib/src/targets/linux/snap/coreLegacy.ts:187 — 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. — packages/app-builder-lib/src/targets/linux/snap/coreLegacy.ts:121
REDACTED:421 · REDACTED:445 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:421
packages/electron-updater/src/differentialDownloader/DifferentialDownloader.ts:272 · packages/electron-updater/src/differentialDownloader/multipleRangeDownloader.ts:100 — the two spans are one implementation copied and then locally edited — 84 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/electron-updater/src/differentialDownloader/DifferentialDownloader.ts:272
packages/electron-publish/src/gitlabPublisher.ts:237 · packages/electron-publish/src/gitlabPublisher.ts:262 — the two spans are one implementation copied and then locally edited — 66 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/electron-publish/src/gitlabPublisher.ts:237
packages/app-builder-lib/src/node-module-collector/hoist.ts:898 · packages/app-builder-lib/src/node-module-collector/hoist.ts:924 — all 2 copies are in the same file, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — packages/app-builder-lib/src/node-module-collector/hoist.ts:898
packages/app-builder-lib/src/targets/win/AppxTarget.ts:50 · packages/app-builder-lib/src/targets/win/MsixTarget.ts:148 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/app-builder-lib/src/targets/win/AppxTarget.ts:50
packages/electron-publish/src/bitbucketPublisher.ts:66 · packages/electron-publish/src/keygenPublisher.ts:256 — the two spans are one implementation copied and then locally edited — 82 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/electron-publish/src/bitbucketPublisher.ts:66
packages/electron-updater/src/differentialDownloader/downloadPlanBuilder.ts:57 · packages/electron-updater/src/differentialDownloader/downloadPlanBuilder.ts:70 — 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. — packages/electron-updater/src/differentialDownloader/downloadPlanBuilder.ts:57
packages/app-builder-lib/src/codeSign/certInfo.ts:496 · packages/app-builder-lib/src/codeSign/certInfo.ts:553 — 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. — packages/app-builder-lib/src/codeSign/certInfo.ts:496
packages/app-builder-lib/src/targets/linux/FlatpakTarget.ts:70 · packages/app-builder-lib/src/targets/linux/appimage/AppImageTarget.ts:174 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/app-builder-lib/src/targets/linux/FlatpakTarget.ts:70
REDACTED:1019 · REDACTED:1058 — 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. — REDACTED:1019
packages/electron-forge-maker-appimage/main.js:3 · packages/electron-forge-maker-nsis-web/main.js:3 · packages/electron-forge-maker-nsis/main.js:3 · packages/electron-forge-maker-snap/main.js:3 — the 4 copies are spread across 4 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/electron-forge-maker-appimage/main.js:3
packages/electron-updater/src/AppImageUpdater.ts:64 · packages/electron-updater/src/AppUpdater.ts:1577 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — packages/electron-updater/src/AppImageUpdater.ts:64
packages/electron-updater/src/providers/GenericProvider.ts:17 · packages/electron-updater/src/providers/GitHubProvider.ts:50 · packages/electron-updater/src/providers/GitLabProvider.ts:70 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/electron-updater/src/providers/GenericProvider.ts:17
scripts/checkDeps.js:36 · scripts/checkDeps.js:50 — 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. — scripts/checkDeps.js:36
packages/app-builder-lib/src/node-module-collector/npmNodeModulesCollector.ts:34 · packages/app-builder-lib/src/node-module-collector/traversalNodeModulesCollector.ts:28 — the two spans are one implementation copied and then locally edited — 54 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/app-builder-lib/src/node-module-collector/npmNodeModulesCollector.ts:34
REDACTED:534 · REDACTED:545 — 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. — REDACTED:534
packages/app-builder-lib/src/toolsets/appimage.ts:57 · packages/app-builder-lib/src/toolsets/archive.ts:39 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/app-builder-lib/src/toolsets/appimage.ts:57
packages/builder-util-runtime/src/blockMapV3.ts:160 · packages/builder-util-runtime/src/blockMapV3.ts:180 — 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. — packages/builder-util-runtime/src/blockMapV3.ts:160
packages/electron-publish/src/s3/s3UploadHelper.ts:149 · packages/electron-publish/src/s3/s3UploadHelper.ts:215 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/electron-publish/src/s3/s3UploadHelper.ts:149
packages/app-builder-lib/src/fileMatcher.ts:546 · packages/app-builder-lib/src/fileMatcher.ts:658 — the two spans are one implementation copied and then locally edited — 63 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/app-builder-lib/src/fileMatcher.ts:546
packages/app-builder-lib/src/targets/win/winAppUtil.ts:160 · packages/app-builder-lib/src/targets/win/winAppUtil.ts:175 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/app-builder-lib/src/targets/win/winAppUtil.ts:160
REDACTED:468 · REDACTED:190 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:468
packages/electron-updater/src/AppImageUpdater.ts:37 · packages/electron-updater/src/DebUpdater.ts:16 · packages/electron-updater/src/PacmanUpdater.ts:14 · packages/electron-updater/src/RpmUpdater.ts:16 — the 4 copies are spread across 4 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/electron-updater/src/AppImageUpdater.ts:37
REDACTED:238 · packages/electron-updater/src/NsisUpdater.ts:87 — the two spans are one implementation copied and then locally edited — 71 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — REDACTED:238
packages/app-builder-lib/src/node-module-collector/moduleManager.ts:225 · packages/app-builder-lib/src/node-module-collector/moduleManager.ts:286 · packages/app-builder-lib/src/node-module-collector/moduleManager.ts:372 · packages/app-builder-lib/src/node-module-collector/moduleManager.ts:381 · +1 more site(s) not listed — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. — packages/app-builder-lib/src/node-module-collector/moduleManager.ts:225
packages/app-builder-lib/src/publish/PublishManager.ts:771 · packages/builder-util/src/updateManifestSigner.ts:184 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/app-builder-lib/src/publish/PublishManager.ts:771
What to do
Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
React / JS · Architecture — Conformance to the detected frontend architecture layout (feature-sliced / layered src) plus cross-package deep-import rules (D-386).
Method: Conformance to the detected frontend layout (feature-sliced / layered src) plus cross-package deep-import rules, over the module graph. Deterministic.
packages/app-builder-lib/src/util/packageMetadata.ts:178 imports packages/electron-updater/src/index.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/app-builder-lib/src/util/packageMetadata.ts:178
packages/app-builder-lib/src/util/packageMetadata.ts:178 imports electron-updater/package.json, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/app-builder-lib/src/util/packageMetadata.ts:178
scripts/update-package-version-export.js:2 reaches into another package with a relative path (./../packages/app-builder-lib/package.json) — import the package by name instead. — scripts/update-package-version-export.js:2
test/src/asarLoggingTest.ts:1 reaches past another workspace package's public entry into its internals with a relative path (../../packages/app-builder-lib/src/asar/asarUtil) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — test/src/asarLoggingTest.ts:1
test/src/asarPathSafetyTest.ts:2 reaches past another workspace package's public entry into its internals with a relative path (../../packages/app-builder-lib/src/asar/asarUtil) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — test/src/asarPathSafetyTest.ts:2
test/src/cliTest.ts:50 reaches past another workspace package's public entry into its internals with a relative path (../../packages/electron-builder/src/cli/clear-cache) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — test/src/cliTest.ts:50
test/src/cliTest.ts:51 reaches past another workspace package's public entry into its internals with a relative path (../../packages/electron-builder/src/cli/cli-util) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — test/src/cliTest.ts:51
test/src/cliTest.ts:52 reaches past another workspace package's public entry into its internals with a relative path (../../packages/electron-builder/src/cli/create-self-signed-cert) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — test/src/cliTest.ts:52
test/src/cliTest.ts:53 reaches past another workspace package's public entry into its internals with a relative path (../../packages/electron-builder/src/builder) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — test/src/cliTest.ts:53
test/src/cliTest.ts:55 reaches past another workspace package's public entry into its internals with a relative path (../../packages/electron-builder/src/cli/install-app-deps) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — test/src/cliTest.ts:55
test/src/cliTest.ts:57 reaches past another workspace package's public entry into its internals with a relative path (../../packages/electron-builder/src/publish) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — test/src/cliTest.ts:57
test/src/filterTest.ts:18 reaches past another workspace package's public entry into its internals with a relative path (../../packages/app-builder-lib/src/fileMatcher) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — test/src/filterTest.ts:18
test/src/helpers/downloadElectron.ts:11 reaches past another workspace package's public entry into its internals with a relative path (./../../../packages/builder-util) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — test/src/helpers/downloadElectron.ts:11
test/src/legacyConfigGuardTest.ts:6 reaches past another workspace package's public entry into its internals with a relative path (../../packages/app-builder-lib/src/fileMatcher) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — test/src/legacyConfigGuardTest.ts:6
test/src/legacyConfigGuardTest.ts:7 reaches past another workspace package's public entry into its internals with a relative path (../../packages/app-builder-lib/src/toolsets/nsis) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — test/src/legacyConfigGuardTest.ts:7
test/src/migrateProgrammaticSchemaTest.ts:2 reaches past another workspace package's public entry into its internals with a relative path (../../packages/electron-builder/src/cli/migrate-schema) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — test/src/migrateProgrammaticSchemaTest.ts:2
test/src/migrateProgrammaticSchemaTest.ts:17 reaches past another workspace package's public entry into its internals with a relative path (../../packages/electron-builder/src/cli/migrate-schema-programmatic) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — test/src/migrateProgrammaticSchemaTest.ts:17
test/src/migrateSchemaCliTest.ts:5 reaches past another workspace package's public entry into its internals with a relative path (../../packages/electron-builder/src/cli/migrate-schema) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — test/src/migrateSchemaCliTest.ts:5
test/src/migrateSchemaTest.ts:6 reaches past another workspace package's public entry into its internals with a relative path (../../packages/electron-builder/src/cli/migrate-schema) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — test/src/migrateSchemaTest.ts:6
test/src/publishCliTest.ts:2 reaches past another workspace package's public entry into its internals with a relative path (../../packages/electron-builder/src/publish) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — test/src/publishCliTest.ts:2
test/src/publishSignalTest.ts:1 reaches past another workspace package's public entry into its internals with a relative path (../../packages/electron-builder/src/publish) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — test/src/publishSignalTest.ts:1
test/src/publisher/snap/SnapStorePublisherTest.ts:7 reaches past another workspace package's public entry into its internals with a relative path (../../../../packages/electron-publish/src/snapStorePublisher) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — test/src/publisher/snap/SnapStorePublisherTest.ts:7
What to do
Fix the listed violations: import through the target package's declared public entry rather than a deep path into its internals or a relative path into its directory (20 rows); declare the workspace packages these files import in the importing package's own REDACTED dependencies (1 row) — those imports are already bare package specifiers, so the import statements do not change, only the manifest; move the shared test helper into a source directory production code may depend on (1 row).
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.
migrateConfig has cyclomatic complexity 110 and cognitive complexity 180; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:279
(anonymous) has cyclomatic complexity 47 and cognitive complexity 94; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/app-builder-lib/src/node-module-collector/hoist.ts:536
normalizeOptions has cyclomatic complexity 37 and cognitive complexity 72; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/electron-builder/src/builder.ts:33
archive has cyclomatic complexity 34 and cognitive complexity 61; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/app-builder-lib/src/targets/archive.ts:259
compareListedFiles has cyclomatic complexity 34 and cognitive complexity 60; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/app-builder-lib/src/publish/updateManifestVerifier.ts:54
ruleIncludePdb has cyclomatic complexity 34 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/electron-builder/src/cli/migrate-schema-programmatic.ts:1583
(anonymous) has cyclomatic complexity 34 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/app-builder-lib/src/targets/win/MsixTarget.ts:166
validateSignedManifestShape has cyclomatic complexity 33 and cognitive complexity 45; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/builder-util-runtime/src/updateManifestSignature.ts:166
customizeDmg has cyclomatic complexity 33 and cognitive complexity 38; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/dmg-builder/src/dmgUtil.ts:166
rulePlatformAsar has cyclomatic complexity 32 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/electron-builder/src/cli/migrate-schema-programmatic.ts:959
(anonymous) has cyclomatic complexity 32 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/app-builder-lib/src/targets/win/AppxTarget.ts:68
buildInstaller has cyclomatic complexity 31 and cognitive complexity 39; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/app-builder-lib/src/targets/win/nsis/NsisTarget.ts:339
main has cyclomatic complexity 31 and cognitive complexity 36; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — scripts/aggregate-changesets.mjs:524
compute7zCompressArgs has cyclomatic complexity 30 and cognitive complexity 44; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/app-builder-lib/src/targets/archive.ts:171
isInsecureFeedAllowed has cyclomatic complexity 30 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:44
build has cyclomatic complexity 29 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/app-builder-lib/src/targets/linux/FpmTarget.ts:143
check has cyclomatic complexity 29 and cognitive complexity 34; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — scripts/checkDeps.js:23
(anonymous) has cyclomatic complexity 29 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/app-builder-lib/src/util/NodeModuleCopyHelper.ts:88
hoistNodeDependencies has cyclomatic complexity 28 and cognitive complexity 54; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/app-builder-lib/src/node-module-collector/hoist.ts:687
differentialDownloadInstaller has cyclomatic complexity 28 and cognitive complexity 49; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/electron-updater/src/AppUpdater.ts:1526
getResolvedPublishConfig has cyclomatic complexity 28 and cognitive complexity 38; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/app-builder-lib/src/publish/PublishManager.ts:1135
parseDn has cyclomatic complexity 27 and cognitive complexity 55; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/builder-util-runtime/src/rfc2253Parser.ts:45
computeDesktopEntry has cyclomatic complexity 27 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/app-builder-lib/src/targets/linux/LinuxTargetHelper.ts:278
(anonymous) has cyclomatic complexity 26 and cognitive complexity 45; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/app-builder-lib/src/targets/win/MsiTarget.ts:238
ruleWinSign has cyclomatic complexity 26 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/electron-builder/src/cli/migrate-schema-programmatic.ts:1281
migrateElectronDownload has cyclomatic complexity 26 and cognitive complexity 30; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:1184
parseNativeBinaryHeader has cyclomatic complexity 25 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/app-builder-lib/src/util/nativeBinaryVerifier.ts:49
createMacApp has cyclomatic complexity 24 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/app-builder-lib/src/electron/mac/electronMac.ts:28
ruleElectronDownload has cyclomatic complexity 22 and cognitive complexity 34; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/electron-builder/src/cli/migrate-schema-programmatic.ts:1741
getMainFileMatchers has cyclomatic complexity 22 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/app-builder-lib/src/fileMatcher.ts:434
ruleMacSigning has cyclomatic complexity 22 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/electron-builder/src/cli/migrate-schema-programmatic.ts:1439
installPendingUpdate has cyclomatic complexity 22 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:479
getArtifactArchName has cyclomatic complexity 22 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/builder-util/src/arch.ts:57
ruleCustomNsis has cyclomatic complexity 21 and cognitive complexity 44; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/electron-builder/src/cli/migrate-schema-programmatic.ts:1223
readCertInfo has cyclomatic complexity 21 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/app-builder-lib/src/codeSign/certInfo.ts:375
createWindowsInstaller has cyclomatic complexity 21 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:72
doPack has cyclomatic complexity 21 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/app-builder-lib/src/platformPackager.ts:469
doConvertIcon has cyclomatic complexity 20 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/app-builder-lib/src/util/iconConverter.ts:223
migratePlatformAsar has cyclomatic complexity 20 and cognitive complexity 30; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:1080
packAndCheck has cyclomatic complexity 20 and cognitive complexity 30; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — test/src/helpers/packTester.ts:669
Do you agree with this assessment?
R3 · Large Files4.3 / 10Weak✓ 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.
packages/electron-builder/src/cli/migrate-schema-programmatic.ts has 2012 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/electron-builder/src/cli/migrate-schema-programmatic.ts:1
packages/electron-updater/src/AppUpdater.ts has 1745 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/electron-updater/src/AppUpdater.ts:1
REDACTED has 1521 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
packages/app-builder-lib/src/configuration.ts has 1180 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/app-builder-lib/src/configuration.ts:1
packages/app-builder-lib/src/publish/PublishManager.ts has 1121 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/app-builder-lib/src/publish/PublishManager.ts:1
packages/app-builder-lib/src/platformPackager.ts has 1070 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/app-builder-lib/src/platformPackager.ts:1
packages/app-builder-lib/src/node-module-collector/hoist.ts has 1002 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/app-builder-lib/src/node-module-collector/hoist.ts:1
packages/app-builder-lib/src/targets/win/nsis/NsisTarget.ts has 971 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/app-builder-lib/src/targets/win/nsis/NsisTarget.ts:1
packages/app-builder-lib/src/util/electronGet.ts has 957 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/app-builder-lib/src/util/electronGet.ts:1
REDACTED has 903 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
REDACTED has 893 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
packages/app-builder-lib/src/targets/mac/MacTargetHelper.ts has 837 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/app-builder-lib/src/targets/mac/MacTargetHelper.ts:1
packages/app-builder-lib/src/macPackager.ts has 807 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/app-builder-lib/src/macPackager.ts:1
packages/app-builder-lib/src/packager.ts has 714 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/app-builder-lib/src/packager.ts:1
packages/electron-updater/src/differentialDownloader/blockMapV3Fetcher.ts has 713 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/electron-updater/src/differentialDownloader/blockMapV3Fetcher.ts:1
packages/app-builder-lib/src/fileMatcher.ts has 688 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/app-builder-lib/src/fileMatcher.ts:1
packages/builder-util-runtime/src/publishOptions.ts has 677 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/builder-util-runtime/src/publishOptions.ts:1
REDACTED has 614 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
packages/builder-util/src/util.ts has 597 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/builder-util/src/util.ts:1
packages/electron-publish/src/s3/awsCredentials.ts has 522 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/electron-publish/src/s3/awsCredentials.ts:1
packages/app-builder-lib/src/codeSign/certInfo.ts has 509 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/app-builder-lib/src/codeSign/certInfo.ts:1
packages/electron-updater/src/NsisUpdater.ts has 505 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/electron-updater/src/NsisUpdater.ts:1
packages/electron-builder/src/cli/sign-update-manifest.ts has 503 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/electron-builder/src/cli/sign-update-manifest.ts:1
packages/builder-util-runtime/src/blockMapV3.ts has 500 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/builder-util-runtime/src/blockMapV3.ts:1
packages/builder-util/src/fs.ts has 500 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/builder-util/src/fs.ts:1
packages/app-builder-lib/src/targets/linux/snap/coreLegacy.ts has 489 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/app-builder-lib/src/targets/linux/snap/coreLegacy.ts:1
REDACTED has 489 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
packages/app-builder-lib/src/node-module-collector/pnpmNodeModulesCollector.ts has 479 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/app-builder-lib/src/node-module-collector/pnpmNodeModulesCollector.ts:1
packages/electron-updater/src/LinuxUpdater.ts has 476 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/electron-updater/src/LinuxUpdater.ts:1
packages/app-builder-lib/src/targets/win/winAppUtil.ts has 470 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/app-builder-lib/src/targets/win/winAppUtil.ts:1
packages/app-builder-lib/src/util/appFileCopier.ts has 464 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/app-builder-lib/src/util/appFileCopier.ts:1
packages/app-builder-lib/src/util/config/legacyOptions.ts has 464 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/app-builder-lib/src/util/config/legacyOptions.ts:1
packages/app-builder-lib/src/targets/linux/FpmTarget.ts has 463 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/app-builder-lib/src/targets/linux/FpmTarget.ts:1
packages/app-builder-lib/src/targets/linux/snap/core24.ts has 462 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/app-builder-lib/src/targets/linux/snap/core24.ts:1
packages/app-builder-lib/src/options/PlatformSpecificBuildOptions.ts has 461 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/app-builder-lib/src/options/PlatformSpecificBuildOptions.ts:1
packages/app-builder-lib/src/node-module-collector/nodeModulesCollector.ts has 459 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/app-builder-lib/src/node-module-collector/nodeModulesCollector.ts:1
packages/app-builder-lib/src/util/buildOutputVerifier.ts has 459 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/app-builder-lib/src/util/buildOutputVerifier.ts:1
packages/app-builder-lib/src/options/winOptions.ts has 451 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/app-builder-lib/src/options/winOptions.ts:1
packages/app-builder-lib/src/targets/differentialUpdateInfoBuilder.ts has 439 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/app-builder-lib/src/targets/differentialUpdateInfoBuilder.ts:1
packages/builder-util/src/executables.ts has 435 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/builder-util/src/executables.ts:1
What to do
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
Do you agree with this assessment?
R4 · Test Coverage10.0 / 10Exemplary✓ Tool-verified
React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.
Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.
No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. — packages/app-builder-lib/helpers/remote-rebuild.js:1
Do you agree with this assessment?
R6 · Tooling10.0 / 10Exemplary✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each REDACTED script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: REDACTED scanned for test/lint/typecheck script wiring. Deterministic presence check.
Do you agree with this assessment?
R7 · Dead Code9.6 / 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.
Unreachable from the 70 application, 26 tooling and 403 test entry point(s) detected in this repo. Gate removals on `pnpm run compile` — an undetected custom entry would make these reachable.
no import path from any entry point (70 application, 26 tooling, 403 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×3) — scripts/generate-schema.ts, scripts/renderer/src/typedoc2html.ts, scripts/snap-exclude-list.js
Nothing imports this binding — it is safe to review for removal. (×7) — packages/app-builder-lib/src/electron/ElectronFramework.ts:45, packages/app-builder-lib/src/electron/electronVersion.ts:12, packages/app-builder-lib/src/electron/search-module.ts:50, …
Nothing imports THIS copy of 'MAX_RANGES_PER_REQUEST' — but packages/electron-updater/src/differentialDownloader/multipleRangeDownloader.ts:20 in the same directory exports that same name, and it is the copy every import site resolves to. Grepping the name therefore finds live callers that do not reach this binding: it is the dead half of a duplicated pair, left behind when the API moved. Delete it here and keep packages/electron-updater/src/differentialDownloader/multipleRangeDownloader.ts's, or, if this one is meant to be the survivor, repoint the importers before removing the other. — packages/electron-updater/src/differentialDownloader/blockMapV3Fetcher.ts:51
What to do
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
Imported but not declared in any reachable REDACTED — installs work only by hoisting accident. (×3) — REDACTED:1380, REDACTED:1454, REDACTED:1458
Imported only as a TYPE and declared in no reachable REDACTED. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning REDACTED. — test/src/updater/updaterLoginChallengeTest.ts:3
Declared in the root REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×2) — REDACTED:50, REDACTED:55
Declared in packages/app-builder-lib/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. — packages/app-builder-lib/package.json:100
Declared in packages/dmg-builder/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. — packages/dmg-builder/package.json:48
Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×2) — REDACTED:23, REDACTED:25
Every import is type-only — move it to devDependencies. (×2) — packages/app-builder-lib/src/options/FuseOptionsV1.ts:1, packages/electron-updater/src/AppUpdater.ts:43
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
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.
packages/app-builder-lib/src/appInfo.ts → packages/app-builder-lib/src/packager.ts → packages/app-builder-lib/src/appInfo.ts (one verified cycle inside a mutually-dependent group of 67 files) — packages/app-builder-lib/src/appInfo.ts:6
Other · Security — Read from this repository's JavaScript/TypeScript source: cryptographic hygiene (weak hash or cipher, key material fixed in the source) and outbound TLS (certificate validation, protocol version) — facts about code that hold whether or not it serves anything itself. This repository commits the configuration that serves its own HTTP surface, so that configuration was read in full for the security response headers it sets. Of the server controls, two are read where the source shows them: every session or sign-in cookie the code sets is read for HttpOnly, Secure and SameSite at the line that sets it (a raw `Set-Cookie` header, Express, Fastify, Hono, Koa, Next.js, `cookie.serialize`, express-session and cookie-session), and every Node listener for HTTPS enforcement. HSTS, security response headers and input validation are NOT assessed for JavaScript/TypeScript: each is scored as an absence, an absence is only reportable over the production HTTP server, and in this ecosystem the file that opens the port is build output or a framework launcher rather than a file in the source tree. Their absence here is not a finding about this repository.
Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.
MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call. (×2) — packages/app-builder-lib/src/codeSign/certInfo.ts:275, packages/app-builder-lib/src/codeSign/certInfo.ts:277
This code fixes scrypt at N=1,024 (r=8, p=1). A key-derivation function's only defence is the cost of ONE guess, and that cost is this number — the algorithm choice does not set it. Current OWASP guidance is 1,300,000 PBKDF2 iterations with HMAC-SHA1, 600,000 with SHA-256 and 210,000 with SHA-512; scrypt at N=2^17, r=8, p=1 (or an equivalent N·r·p product); Argon2id at 19 MiB of memory and 2 iterations (or an equivalent row); bcrypt at a work factor of at least 10. This figure divides the attacker's work by a factor of tens or hundreds against the same stolen hash, on hardware they already own. Where what is derived is short or low-entropy — a PIN, a numeric parental code, a four-character token — the whole keyspace falls in the time this parameter buys, and no salt or constant-time comparison changes that. Raise the count to the current published figure for the PRF you use, measure it on the slowest hardware that must run it (a target of roughly 100 ms per derivation is the usual budget), and read the value from configuration so a deployment can raise it again without a rebuild. Where the derived value must interoperate with a format someone else fixed, the count cannot move — derive a SEPARATE value for anything you own rather than inheriting the external format's price. — REDACTED:977
None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `netlify.toml` configures this repository's static hosting, including its response headers, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.) — netlify.toml:1
What to do
Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key. This repository constructs a collision-broken hash (MD5/SHA1) at 2 sites, not one: `packages/app-builder-lib/src/codeSign/certInfo.ts:275` (createHash("sha1")), `packages/app-builder-lib/src/codeSign/certInfo.ts:277` (createHash("sha1")). Each is a separate decision — fixing only the line this row cites leaves the others in place.
Raise the cost parameter to current guidance — PBKDF2 at 1,300,000 (HMAC-SHA1), 600,000 (SHA-256) or 210,000 (SHA-512) iterations; scrypt at N=2^17, r=8, p=1; bcrypt at a work factor of 10 or more — or move to a memory-hard KDF (Argon2id, scrypt) where the platform offers one. Read the parameter from configuration and tune it to roughly 100 ms per derivation on the slowest hardware that must run it, so the price can be raised again without shipping new code.
Set security response headers on the surface this repository serves: an `add_header` directive per header in the nginx/Caddy/Apache config, a `_headers` / `vercel.json` / `netlify.toml` entry for a static host, or `helmet()` in the HTTP server. `Content-Security-Policy` is the one that pays for itself first — it is what contains an injected script once one reaches the page — followed by `X-Content-Type-Options: nosniff` and a frame policy (`X-Frame-Options: DENY`, or CSP `frame-ancestors`). Where the app is served from a build container, the header configuration belongs in the image beside the built assets, so it ships with them rather than depending on where it lands.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
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 · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.
Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document2.3 / 10Critical✓ Tool-verified
Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.
Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.
`runInstallPlan` is exported, takes a document from its caller (line 188) and hands it to `installPlanCommands`, which calls itself at line 178 (`installPlanCommands`) with a piece of `plan` — and nowhere in `installPlanCommands` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `installPlanCommands` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/electron-updater/src/LinuxUpdater.ts:178
`mapToObject` is exported and takes `map: RecursiveMap` from its caller, and it calls itself at line 12 (`mapToObject`) with a piece of `map` — and nowhere in `mapToObject` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `mapToObject` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/builder-util-runtime/src/objects.ts:12
`savePlistFile` is exported, takes a document from its caller (line 34) and hands it to `sortObjectKeys`, which calls itself at line 22 (`sortObjectKeys`) with a piece of `obj` (and at line 29) — and nowhere in `sortObjectKeys` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `sortObjectKeys` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/app-builder-lib/src/util/mac/plist.ts:22
What to do
Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
Other · Code Health — Whether 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.
Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.
Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether async functions that make a cancellable request accept or pass on an AbortSignal (adoption curve).
Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.
Only 0/1 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
`getBucketLocation` awaits `https.request(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `https.request(url, { signal })`. — packages/electron-publish/src/s3/bucketLocation.ts:14
What to do
Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether 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.
`debug` at line 122 is called with an argument built by `JSON.stringify(operations, null, 2)` (line 122), whose cost grows with the collection it walks. JavaScript 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 debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/electron-updater/src/differentialDownloader/DifferentialDownloader.ts:122
`debug` at line 365 is called with an argument built by `describeNativeBinary(info)` (line 365), whose cost grows with the collection it walks. JavaScript 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 debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/app-builder-lib/src/util/nativeBinaryVerifier.ts:365
`debug` at line 377 is called with an argument built by `describeNativeBinary(info)` (line 377), whose cost grows with the collection it walks. JavaScript 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 debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/app-builder-lib/src/util/nativeBinaryVerifier.ts:377
`debug` at line 135 is called with an argument built by `args.join(" ")` (line 135), whose cost grows with the collection it walks. JavaScript 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 debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/app-builder-lib/src/node-module-collector/index.ts:135
`debug` at line 103 is called with an argument built by `join(", ")` (line 103), whose cost grows with the collection it walks. JavaScript 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 debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/app-builder-lib/src/asar/asarUtil.ts:103
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 JavaScript's evaluation order, not a guess — then put the construction behind the level check the logger offers (`if (logger.isLevelEnabled('debug'))` for pino and winston, `isDebugEnabled()` for log4js, the repository's own debug flag where it has one), or hand the logger the object and a format string (`logger.debug({ payload }, 'raw request')`) so the serialising happens only when the line is written. Moving the call is not the fix: it is the join/projection/stringify in the argument that is paid, wherever the call sits.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped6.5 / 10Adequate✓ Tool-verified
Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.
Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.
`item.description?`Description="${escapeForXml(item.description)}"`:""` is text this program did not author, and it is written into an unquoted attribute through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML text encoding does not help in an unquoted attribute — whitespace ends it; quote the attribute and encode the value. — packages/app-builder-lib/src/targets/win/MsiTarget.ts:320
`argsAttr` is text this program did not author, and it is written into an unquoted attribute through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML text encoding does not help in an unquoted attribute — whitespace ends it; quote the attribute and encode the value. — packages/app-builder-lib/src/targets/win/winAppUtil.ts:384
What to do
Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element7.5 / 10Strong✓ Tool-verified
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.
This loop runs once per element of `icons`, and the statement it guards acts on the element it is on — `icon`. The test deciding whether that statement runs does not: `iconExtWithDot === ".svg"` reads `icons[0]`, a subscript that does not move, so whatever it answers for that one element it answers for ALL of them. One `if` names the same collection at two different subscripts — the fixed one at line 21, which is the contradiction: either the test was meant to be per-element, in which case every element that differs from the fixed one is handled wrongly and all in the same direction, or it really is one answer for the whole collection, in which case it is being re-asked on every pass and belongs above the loop. The `if` is in the wrong place under both readings. Give the test the loop variable, or hoist it out. — packages/app-builder-lib/src/targets/linux/appimage/appLauncher.ts:31
What to do
Each finding names the test and the statement it guards, which index the same collection at two different subscripts — one fixed, one the loop variable. Confirm from the two, then decide which subscript the test meant. If it was meant to be per-element, give it the loop variable so each element is judged on itself. If it really is one answer for the whole collection, hoist the test OUT of the loop, where a reader can see it is asked once and where it is not re-evaluated on every pass — leaving it inside, reading a fixed element, is the one arrangement that cannot be right under either reading.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×26) — packages/electron-updater/src/AppUpdater.ts:540, packages/electron-updater/src/AppUpdater.ts:1521, REDACTED:57, …
`.then(…, () => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. — packages/electron-updater/src/AppUpdater.ts:790
`.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. (×8) — packages/electron-updater/src/AppUpdater.ts:1420, packages/electron-updater/src/AppUpdater.ts:1423, REDACTED:550, …
`catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included. (×4) — packages/electron-updater/src/providers/GitHubProvider.ts:304, packages/app-builder-lib/src/util/archCompatibility.ts:114, packages/app-builder-lib/src/util/archCompatibility.ts:169, …
`catch (_ignored)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included. — packages/app-builder-lib/src/util/packageMetadata.ts:37
What to do
Swallowed exception (empty catch)
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether strict null checking is enabled and not undermined by heavy `!` assertion — TypeScript's `strictNullChecks` (which `strict` turns on) is what makes `string` exclude `null` and `undefined`, and the postfix `!` is the operator that silences it.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
~2.0 `!` null assertions per 1k TypeScript source lines — 144 assertion(s) across the 71570 source line(s) of the 307 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: packages/app-builder-lib/src/packager.ts (12), packages/app-builder-lib/src/node-module-collector/hoist.ts (11), packages/app-builder-lib/src/asar/asar.ts (8). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
What to do
The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
Do you agree with this assessment?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 2 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
X10 Duplicated predicate — 33 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 5 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 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.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 51 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 — Frontend below the scale floor (5 DOM element(s) < 25) — too little surface to assess accessibility.
AC2 Forms & labels — Frontend below the scale floor (5 DOM element(s) < 25) — too little surface to assess accessibility.
AC3 Page structure — Frontend below the scale floor (5 DOM element(s) < 25) — too little surface to assess accessibility.
AC4 Keyboard semantics — Frontend below the scale floor (5 DOM element(s) < 25) — too little surface to assess accessibility.
AC5 ARIA correctness — Frontend below the scale floor (5 DOM element(s) < 25) — too little surface to assess accessibility.
AC6 Visual & motion safety — Frontend below the scale floor (5 DOM element(s) < 25) — too little surface to assess accessibility.
AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
AX2 Stateful singletons — Not applicable: TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — the dev server (`npm run start`) exited before it served a page. Likely cause (the repository): REDACTED has no "start" script, so `npm run start` could not start the app. Last output: "npm error Missing script: "start" / npm error / npm error Did you mean one of these? / npm error npm star # Mark your favorite packages / npm error npm stars # View packages marked as favorites / npm error / npm error To see a list of scripts, run: / npm error npm run / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered. The cause is in the repository, not in our sandbox: REDACTED has no "start" script, so `npm run start` could not start the app. Nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no data at rest for these controls to protect. If it does persist personal data (through a hosted backend configured outside this repository, for instance), the controls belong to wherever that data is stored.
C2 Access Controls — No access-control surface detected in the analyzed source — this repository stands up no server (no Express, Fastify, Koa, Hono, NestJS or similar app, no Next.js/SvelteKit/Nuxt server route, no edge function), creates no Supabase tables and talks to no hosted backend. Access control is therefore N/A here — a browser application or library is authorized by the server it calls, not by itself; a client-side route guard hides a page and authorizes nothing. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound. If it does (through a hosted backend configured outside this repository, for instance), the limit belongs wherever that data is stored.
C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over. If it does (through a hosted backend configured outside this repository, for instance), the rights are served wherever that data is stored.
D11 Test Reliability — Test reliability not measured — JavaScript/TypeScript suite did not run
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D22 Internal API Consistency — API consistency is measured on C#, TypeScript, Go only; the exposed JavaScript surface was not measured.
D25 ADR Conformance — no ADRs to check
D32 Data Compliance (PII/GDPR) — 3 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D4 Code Duplication — This repository's production source (.ts, .tsx) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage not measured — JavaScript/TypeScript suite
DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a REDACTED, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
R5 Dependency Freshness — uses a bun lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
Project dependency cycle packages/app-builder-lib/package.json:118— The projects app-builder-lib → dmg-builder → app-builder-lib (one cycle inside a mutually-dependent group of 3 projects) form a reference cycle. Cyclic dependencies prevent independent build/test/deploy, blur ownership, and tend to grow into a big ball of mud. Break the cycle by extracting the shared types into a separate project both can reference.
Orphaned knowledge packages/app-builder-lib/src/node-module-collector/hoist.ts:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
No assertions: build in the app REDACTED test/src/BuildTest.ts:124— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: relative index test/src/BuildTest.ts:142— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: www as default dir test/src/BuildTest.ts:218— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: do not exclude build entirely (respect files) test/src/ExtraBuildResourcesTest.ts:184— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: yarn berry using extraMetadata.name should not unpack workspace app test/src/HoistedNodeModuleTest.ts:1038— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: dotted s3 bucket test/src/PublishManager.e2e.ts:273— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: ignore node_modules dev dep test/src/ignoreTest.ts:84— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: local file:// protocol with ${pm} for project outside workspace test/src/packageManagerTest.ts:507— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: AppX test/src/windows/appxTestSuite.ts:15— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: auto launch test/src/windows/appxTestSuite.ts:46— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: application id test/src/windows/appxTestSuite.ts:62— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: languages and not signed (windows store only) test/src/windows/appxTestSuite.ts:95— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: assisted test/src/windows/assistedInstallerTestSuite.ts:13— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: allowElevation false, app requestedExecutionLevel admin test/src/windows/assistedInstallerTestSuite.ts:45— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: assisted, only perMachine test/src/windows/assistedInstallerTestSuite.ts:158— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: assisted, only perMachine and elevated test/src/windows/assistedInstallerTestSuite.ts:170— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: msi test/src/windows/msiTestSuite.ts:34— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: msi no asar test/src/windows/msiTestSuite.ts:63— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: per-user test/src/windows/msiTestSuite.ts:83— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: wix args test/src/windows/msiTestSuite.ts:106— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: same file name in two directories test/src/windows/msiTestSuite.ts:167— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: msiWrapped allows capitalized nsis target test/src/windows/msiWrappedTestSuite.ts:40— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: MSIX test/src/windows/msixTestSuite.ts:11— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: msix auto launch extension test/src/windows/msixTestSuite.ts:42— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: msix application id test/src/windows/msixTestSuite.ts:57— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
Swallowed exception (empty catch) packages/electron-updater/src/AppUpdater.ts:540— 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) packages/electron-updater/src/AppUpdater.ts:790— `.then(…, () => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) packages/electron-updater/src/AppUpdater.ts:1420— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) packages/electron-updater/src/AppUpdater.ts:1423— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) packages/electron-updater/src/AppUpdater.ts:1521— 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) REDACTED:57— 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) REDACTED:123— 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) REDACTED:550— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) packages/electron-updater/src/DownloadedUpdateHelper.ts:233— 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) packages/electron-updater/src/LinuxUpdater.ts:26— 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) packages/electron-updater/src/NsisUpdater.ts:125— 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) packages/electron-updater/src/NsisUpdater.ts:310— 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) REDACTED:102— 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) REDACTED:149— 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) packages/electron-updater/src/util.ts:42— 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) packages/electron-updater/src/windowsExecutableCodeSignatureVerifier.ts:175— 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) packages/electron-updater/src/providers/GitHubProvider.ts:287— 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) packages/builder-util-runtime/src/CancellationToken.ts:56— 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) packages/builder-util/src/executables.ts:182— 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) packages/builder-util/src/fs.ts:42— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) packages/app-builder-lib/src/vm/ParallelsVm.ts:98— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) packages/app-builder-lib/src/vm/ParallelsVm.ts:102— 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) packages/app-builder-lib/src/util/archCompatibility.ts:135— 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) packages/app-builder-lib/src/util/cacheState.ts:102— 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) packages/app-builder-lib/src/util/electronGet.ts:575— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Hotspot: REDACTED REDACTED:279— REDACTED changed 16 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 109 in migrate-schema.migrateConfig at line 279. 3 of those changes were fix/bug commits, and the other 13 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 12:16:46 -08:00' --until='2026-11-16 12:16:46 -08: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: packages/electron-updater/src/AppUpdater.ts packages/electron-updater/src/AppUpdater.ts:1526— packages/electron-updater/src/AppUpdater.ts changed 43 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 31 in AppUpdater.differentialDownloadInstaller at line 1526. 23 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 12:16:46 -08:00' --until='2026-11-16 12:16:46 -08:00' --full-history --no-merges -- packages/electron-updater/src/AppUpdater.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/app-builder-lib/src/targets/win/nsis/NsisTarget.ts packages/app-builder-lib/src/targets/win/nsis/NsisTarget.ts:339— packages/app-builder-lib/src/targets/win/nsis/NsisTarget.ts changed 23 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 37 in NsisTarget.buildInstaller at line 339. 11 of those changes were fix/bug commits, and the other 12 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 12:16:46 -08:00' --until='2026-11-16 12:16:46 -08:00' --full-history --no-merges -- packages/app-builder-lib/src/targets/win/nsis/NsisTarget.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/app-builder-lib/src/publish/PublishManager.ts packages/app-builder-lib/src/publish/PublishManager.ts:1135— packages/app-builder-lib/src/publish/PublishManager.ts changed 23 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 29 in PublishManager.getResolvedPublishConfig at line 1135. 8 of those changes were fix/bug commits, and the other 15 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 12:16:46 -08:00' --until='2026-11-16 12:16:46 -08:00' --full-history --no-merges -- packages/app-builder-lib/src/publish/PublishManager.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: REDACTED REDACTED:262— REDACTED changed 19 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in HttpExecutor.handleResponse at line 262. 16 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 12:16:46 -08:00' --until='2026-11-16 12:16:46 -08: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: packages/electron-updater/src/NsisUpdater.ts packages/electron-updater/src/NsisUpdater.ts:221— packages/electron-updater/src/NsisUpdater.ts changed 17 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in NsisUpdater.doDownloadUpdate at line 221. 7 of those changes were fix/bug commits, and the other 10 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 12:16:46 -08:00' --until='2026-11-16 12:16:46 -08:00' --full-history --no-merges -- packages/electron-updater/src/NsisUpdater.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/app-builder-lib/src/platformPackager.ts packages/app-builder-lib/src/platformPackager.ts:469— packages/app-builder-lib/src/platformPackager.ts changed 16 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in PlatformPackager.doPack at line 469. 5 of those changes were fix/bug commits, and the other 11 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 12:16:46 -08:00' --until='2026-11-16 12:16:46 -08:00' --full-history --no-merges -- packages/app-builder-lib/src/platformPackager.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: REDACTED REDACTED:479— REDACTED changed 15 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in BaseUpdater.installPendingUpdate at line 479. 6 of those changes were fix/bug commits, and the other 9 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 12:16:46 -08:00' --until='2026-11-16 12:16:46 -08: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: packages/app-builder-lib/src/targets/mac/MacTargetHelper.ts packages/app-builder-lib/src/targets/mac/MacTargetHelper.ts:293— packages/app-builder-lib/src/targets/mac/MacTargetHelper.ts changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in MacTargetHelper.buildSignOptions at line 293. 4 of those changes were fix/bug commits, and the other 7 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 12:16:46 -08:00' --until='2026-11-16 12:16:46 -08:00' --full-history --no-merges -- packages/app-builder-lib/src/targets/mac/MacTargetHelper.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/electron-builder/src/cli/migrate-schema-programmatic.ts packages/electron-builder/src/cli/migrate-schema-programmatic.ts:1439— packages/electron-builder/src/cli/migrate-schema-programmatic.ts changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in ConfigCodemod.ruleMacSigning at line 1439. 2 of those changes were fix/bug commits, and the other 10 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 12:16:46 -08:00' --until='2026-11-16 12:16:46 -08:00' --full-history --no-merges -- packages/electron-builder/src/cli/migrate-schema-programmatic.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/app-builder-lib/src/targets/linux/FpmTarget.ts packages/app-builder-lib/src/targets/linux/FpmTarget.ts:143— packages/app-builder-lib/src/targets/linux/FpmTarget.ts changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in FpmTarget.build at line 143. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 12:16:46 -08:00' --until='2026-11-16 12:16:46 -08:00' --full-history --no-merges -- packages/app-builder-lib/src/targets/linux/FpmTarget.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/app-builder-lib/src/targets/linux/snap/coreLegacy.ts packages/app-builder-lib/src/targets/linux/snap/coreLegacy.ts:68— packages/app-builder-lib/src/targets/linux/snap/coreLegacy.ts changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 36 in SnapCoreLegacy.createDescriptor at line 68. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 12:16:46 -08:00' --until='2026-11-16 12:16:46 -08:00' --full-history --no-merges -- packages/app-builder-lib/src/targets/linux/snap/coreLegacy.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/app-builder-lib/src/macPackager.ts packages/app-builder-lib/src/macPackager.ts:127— packages/app-builder-lib/src/macPackager.ts changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in MacPackager.checkForceCodeSigningAtBuildStart at line 127. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 12:16:46 -08:00' --until='2026-11-16 12:16:46 -08:00' --full-history --no-merges -- packages/app-builder-lib/src/macPackager.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/electron-builder/src/builder.ts packages/electron-builder/src/builder.ts:33— packages/electron-builder/src/builder.ts changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 45 in builder.normalizeOptions at line 33. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 12:16:46 -08:00' --until='2026-11-16 12:16:46 -08:00' --full-history --no-merges -- packages/electron-builder/src/builder.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/electron-updater/src/differentialDownloader/DifferentialDownloader.ts packages/electron-updater/src/differentialDownloader/DifferentialDownloader.ts:196— packages/electron-updater/src/differentialDownloader/DifferentialDownloader.ts changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in DifferentialDownloader.writeNewFile at line 196. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 12:16:46 -08:00' --until='2026-11-16 12:16:46 -08:00' --full-history --no-merges -- packages/electron-updater/src/differentialDownloader/DifferentialDownloader.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/builder-util/src/util.ts packages/builder-util/src/util.ts:220— packages/builder-util/src/util.ts changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in util.exec at line 220. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 12:16:46 -08:00' --until='2026-11-16 12:16:46 -08:00' --full-history --no-merges -- packages/builder-util/src/util.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/app-builder-lib/src/publish/updateInfoBuilder.ts packages/app-builder-lib/src/publish/updateInfoBuilder.ts:114— packages/app-builder-lib/src/publish/updateInfoBuilder.ts changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in updateInfoBuilder.createUpdateInfoTasks at line 114. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 12:16:46 -08:00' --until='2026-11-16 12:16:46 -08:00' --full-history --no-merges -- packages/app-builder-lib/src/publish/updateInfoBuilder.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/app-builder-lib/src/targets/archive.ts packages/app-builder-lib/src/targets/archive.ts:259— packages/app-builder-lib/src/targets/archive.ts changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 33 in archive.archive at line 259. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 12:16:46 -08:00' --until='2026-11-16 12:16:46 -08:00' --full-history --no-merges -- packages/app-builder-lib/src/targets/archive.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/app-builder-lib/src/targets/linux/snap/core24.ts packages/app-builder-lib/src/targets/linux/snap/core24.ts:181— packages/app-builder-lib/src/targets/linux/snap/core24.ts changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 33 in SnapCore24.mapSnapOptionsToSnapcraftYAML at line 181. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 12:16:46 -08:00' --until='2026-11-16 12:16:46 -08:00' --full-history --no-merges -- packages/app-builder-lib/src/targets/linux/snap/core24.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/app-builder-lib/src/winPackager.ts packages/app-builder-lib/src/winPackager.ts:238— packages/app-builder-lib/src/winPackager.ts changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in WinPackager.signAndEditResources at line 238. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 12:16:46 -08:00' --until='2026-11-16 12:16:46 -08:00' --full-history --no-merges -- packages/app-builder-lib/src/winPackager.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/electron-updater/src/providers/GitLabProvider.ts packages/electron-updater/src/providers/GitLabProvider.ts:81— packages/electron-updater/src/providers/GitLabProvider.ts changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in GitLabProvider.getLatestVersion at line 81. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 12:16:46 -08:00' --until='2026-11-16 12:16:46 -08:00' --full-history --no-merges -- packages/electron-updater/src/providers/GitLabProvider.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/app-builder-lib/src/node-module-collector/pnpmNodeModulesCollector.ts packages/app-builder-lib/src/node-module-collector/pnpmNodeModulesCollector.ts:251— packages/app-builder-lib/src/node-module-collector/pnpmNodeModulesCollector.ts changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in PnpmNodeModulesCollector.extractProductionDependencyGraph at line 251. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 12:16:46 -08:00' --until='2026-11-16 12:16:46 -08:00' --full-history --no-merges -- packages/app-builder-lib/src/node-module-collector/pnpmNodeModulesCollector.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/app-builder-lib/src/targets/win/nsis/nsisUtil.ts packages/app-builder-lib/src/targets/win/nsis/nsisUtil.ts:202— packages/app-builder-lib/src/targets/win/nsis/nsisUtil.ts changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in UninstallerReader.exec at line 202. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 12:16:46 -08:00' --until='2026-11-16 12:16:46 -08:00' --full-history --no-merges -- packages/app-builder-lib/src/targets/win/nsis/nsisUtil.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/app-builder-lib/src/publish/updateManifestVerifier.ts packages/app-builder-lib/src/publish/updateManifestVerifier.ts:54— packages/app-builder-lib/src/publish/updateManifestVerifier.ts changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 33 in updateManifestVerifier.compareListedFiles at line 54. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 12:16:46 -08:00' --until='2026-11-16 12:16:46 -08:00' --full-history --no-merges -- packages/app-builder-lib/src/publish/updateManifestVerifier.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/builder-util-runtime/src/updateManifestSignature.ts packages/builder-util-runtime/src/updateManifestSignature.ts:166— packages/builder-util-runtime/src/updateManifestSignature.ts changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 33 in updateManifestSignature.validateSignedManifestShape at line 166. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 12:16:46 -08:00' --until='2026-11-16 12:16:46 -08:00' --full-history --no-merges -- packages/builder-util-runtime/src/updateManifestSignature.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Boundary violation [package:test-suite-dependency] packages/app-builder-lib/src/util/packageMetadata.ts:178— packages/app-builder-lib/src/util/packageMetadata.ts:178 imports packages/electron-updater/src/index.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
Boundary violation [package:undeclared-workspace-dep] packages/app-builder-lib/src/util/packageMetadata.ts:178— packages/app-builder-lib/src/util/packageMetadata.ts:178 imports electron-updater/package.json, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
Boundary violation [package:relative-cross-package] scripts/update-package-version-export.js:2— scripts/update-package-version-export.js:2 reaches into another package with a relative path (./../packages/app-builder-lib/package.json) — import the package by name instead.
Boundary violation [package:test-cross-package-internals] test/src/asarLoggingTest.ts:1— test/src/asarLoggingTest.ts:1 reaches past another workspace package's public entry into its internals with a relative path (../../packages/app-builder-lib/src/asar/asarUtil) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:test-cross-package-internals] test/src/asarPathSafetyTest.ts:2— test/src/asarPathSafetyTest.ts:2 reaches past another workspace package's public entry into its internals with a relative path (../../packages/app-builder-lib/src/asar/asarUtil) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:test-cross-package-internals] test/src/cliTest.ts:50— test/src/cliTest.ts:50 reaches past another workspace package's public entry into its internals with a relative path (../../packages/electron-builder/src/cli/clear-cache) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:test-cross-package-internals] test/src/cliTest.ts:51— test/src/cliTest.ts:51 reaches past another workspace package's public entry into its internals with a relative path (../../packages/electron-builder/src/cli/cli-util) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:test-cross-package-internals] test/src/cliTest.ts:52— test/src/cliTest.ts:52 reaches past another workspace package's public entry into its internals with a relative path (../../packages/electron-builder/src/cli/create-self-signed-cert) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:test-cross-package-internals] test/src/cliTest.ts:53— test/src/cliTest.ts:53 reaches past another workspace package's public entry into its internals with a relative path (../../packages/electron-builder/src/builder) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:test-cross-package-internals] test/src/cliTest.ts:55— test/src/cliTest.ts:55 reaches past another workspace package's public entry into its internals with a relative path (../../packages/electron-builder/src/cli/install-app-deps) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:test-cross-package-internals] test/src/cliTest.ts:57— test/src/cliTest.ts:57 reaches past another workspace package's public entry into its internals with a relative path (../../packages/electron-builder/src/publish) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:test-cross-package-internals] test/src/filterTest.ts:18— test/src/filterTest.ts:18 reaches past another workspace package's public entry into its internals with a relative path (../../packages/app-builder-lib/src/fileMatcher) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:test-cross-package-internals] test/src/helpers/downloadElectron.ts:11— test/src/helpers/downloadElectron.ts:11 reaches past another workspace package's public entry into its internals with a relative path (./../../../packages/builder-util) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:test-cross-package-internals] test/src/legacyConfigGuardTest.ts:6— test/src/legacyConfigGuardTest.ts:6 reaches past another workspace package's public entry into its internals with a relative path (../../packages/app-builder-lib/src/fileMatcher) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:test-cross-package-internals] test/src/legacyConfigGuardTest.ts:7— test/src/legacyConfigGuardTest.ts:7 reaches past another workspace package's public entry into its internals with a relative path (../../packages/app-builder-lib/src/toolsets/nsis) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:test-cross-package-internals] test/src/migrateProgrammaticSchemaTest.ts:2— test/src/migrateProgrammaticSchemaTest.ts:2 reaches past another workspace package's public entry into its internals with a relative path (../../packages/electron-builder/src/cli/migrate-schema) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:test-cross-package-internals] test/src/migrateProgrammaticSchemaTest.ts:17— test/src/migrateProgrammaticSchemaTest.ts:17 reaches past another workspace package's public entry into its internals with a relative path (../../packages/electron-builder/src/cli/migrate-schema-programmatic) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:test-cross-package-internals] test/src/migrateSchemaCliTest.ts:5— test/src/migrateSchemaCliTest.ts:5 reaches past another workspace package's public entry into its internals with a relative path (../../packages/electron-builder/src/cli/migrate-schema) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:test-cross-package-internals] test/src/migrateSchemaTest.ts:6— test/src/migrateSchemaTest.ts:6 reaches past another workspace package's public entry into its internals with a relative path (../../packages/electron-builder/src/cli/migrate-schema) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:test-cross-package-internals] test/src/publishCliTest.ts:2— test/src/publishCliTest.ts:2 reaches past another workspace package's public entry into its internals with a relative path (../../packages/electron-builder/src/publish) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:test-cross-package-internals] test/src/publishSignalTest.ts:1— test/src/publishSignalTest.ts:1 reaches past another workspace package's public entry into its internals with a relative path (../../packages/electron-builder/src/publish) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:test-cross-package-internals] test/src/publisher/snap/SnapStorePublisherTest.ts:7— test/src/publisher/snap/SnapStorePublisherTest.ts:7 reaches past another workspace package's public entry into its internals with a relative path (../../../../packages/electron-publish/src/snapStorePublisher) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Repeated repair: packages/electron-updater/src/MacUpdater.ts packages/electron-updater/src/MacUpdater.ts:62— packages/electron-updater/src/MacUpdater.ts changed 10 times in last 90 days and 7 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 13 (its worst body is MacUpdater.doDownloadUpdate at line 62), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(updater): require credentials on every route of the local macOS update proxy (#10581)”; “fix(builder): state the crossOriginHeaders rule in the feed query warning, advisory, changesets and docs (#10568)”; “fix(updater): keep autoUpdater working when bundled into the main process (#10531)”; “fix(updater): only log differential download result on macOS when one was attempted (#10486)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 12:16:46 -08:00' --until='2026-11-16 12:16:46 -08:00' --full-history --no-merges -- packages/electron-updater/src/MacUpdater.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: REDACTED REDACTED:595— REDACTED changed 10 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 13 (its worst body is SigntoolSignManager.computeWindowsSignArgs at line 595), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(win-sign): read ELECTRON_BUILDER_OFFLINE through the shared offline-mode check (#10588)”; “fix(win): do not pass publish tokens to signtool, osslsigncode and makensis (#10586)”; “fix(win): sign .msi with SHA-256 by default (#10374)”; “fix(win): verify the signed installer's publisher matches `publisherName` at build time (#10378)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 12:16:46 -08:00' --until='2026-11-16 12:16:46 -08: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.
Repeated repair: packages/electron-updater/src/differentialDownloader/multipleRangeDownloader.ts packages/electron-updater/src/differentialDownloader/multipleRangeDownloader.ts:81— packages/electron-updater/src/differentialDownloader/multipleRangeDownloader.ts changed 8 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 15 (its worst body is multipleRangeDownloader.doExecuteTasks at line 81), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(updater): parse the multipart boundary of a range response in linear time (#10513)”; “fix(updater): settle differential download on cancel and contain throwing progress listeners (#10356)”; “fix(updater): strip credentials on redirects for every differential download request (#10419)”; “fix(updater): retry with single ranges when a host rejects multi-range requests (#10343)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 12:16:46 -08:00' --until='2026-11-16 12:16:46 -08:00' --full-history --no-merges -- packages/electron-updater/src/differentialDownloader/multipleRangeDownloader.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/electron-builder-squirrel-windows/src/SquirrelWindowsTarget.ts packages/electron-builder-squirrel-windows/src/SquirrelWindowsTarget.ts:288— packages/electron-builder-squirrel-windows/src/SquirrelWindowsTarget.ts changed 8 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 15 (its worst body is SquirrelWindowsTarget.computeEffectiveDistOptions at line 288), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: point configuration errors at existing docs sections (#10462)”; “fix(squirrel): copy Squirrel.exe into appOutDir in build(), not from the queued installer work (#10436)”; “fix(squirrel): wait for zip/7z of the same pack before writing into appOutDir (#10432)”; “fix!: confine copies and linked files by real path, with fileOptions.allowExternalLinks (#10321)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 12:16:46 -08:00' --until='2026-11-16 12:16:46 -08:00' --full-history --no-merges -- packages/electron-builder-squirrel-windows/src/SquirrelWindowsTarget.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/app-builder-lib/src/util/appFileCopier.ts packages/app-builder-lib/src/util/appFileCopier.ts:425— packages/app-builder-lib/src/util/appFileCopier.ts changed 8 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 10 (its worst body is appFileCopier.collectNodeModulesWithLogging at line 425), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: start host programs only from absolute paths via toolsets.executables (#10430)”; “fix: contain mapped app file destinations (#10137)”; “fix!: confine copies and linked files by real path, with fileOptions.allowExternalLinks (#10321)”; “fix(node-modules): reject a collected tree that is missing the app's direct dependencies (#10281)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 12:16:46 -08:00' --until='2026-11-16 12:16:46 -08:00' --full-history --no-merges -- packages/app-builder-lib/src/util/appFileCopier.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: REDACTED REDACTED:88— REDACTED changed 7 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 12 (its worst body is ElectronHttpExecutor.createRequest at line 88), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(updater): keep autoUpdater working when bundled into the main process (#10531)”; “fix(updater): reject redirects to non-http(s) URLs instead of throwing (#10448)”; “fix(updater): strip credentials on redirects for every differential download request (#10419)”; “fix(updater): verify hex sha512 differentially, contain throwing loggers, time out stalled Electron requests (#10366)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 12:16:46 -08:00' --until='2026-11-16 12:16:46 -08: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.
Repeated repair: packages/app-builder-lib/src/index.ts packages/app-builder-lib/src/index.ts:124— packages/app-builder-lib/src/index.ts changed 7 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 10 (its worst body is index.build at line 124), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: start host programs only from absolute paths via toolsets.executables (#10430)”; “fix(forge): make electron-builder makers loadable by current Electron Forge (#10351)”; “fix(docs): repair broken links and anchors (#10305)”; “fix(app-builder-lib): return sign result instead of boolean from windows signing chain (#10104)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 12:16:46 -08:00' --until='2026-11-16 12:16:46 -08:00' --full-history --no-merges -- packages/app-builder-lib/src/index.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/electron-updater/src/DebUpdater.ts packages/electron-updater/src/DebUpdater.ts:53— packages/electron-updater/src/DebUpdater.ts changed 6 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is DebUpdater.planInstall at line 53), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(updater): explain where Linux update authenticity comes from (#10577)”; “fix(updater): install Linux packages without freezing the app (#10094)”; “fix(updater): settle differential download on cancel and contain throwing progress listeners (#10356)”; “fix(electron-updater): keep cached blockmap consistent with cached installer to avoid stale sha512 mismatches (#10098)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 12:16:46 -08:00' --until='2026-11-16 12:16:46 -08:00' --full-history --no-merges -- packages/electron-updater/src/DebUpdater.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/electron-updater/src/providers/GitHubProvider.ts packages/electron-updater/src/providers/GitHubProvider.ts:271— packages/electron-updater/src/providers/GitHubProvider.ts changed 6 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 11 (its worst body is GitHubProvider.computeReleaseNotes at line 271), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(builder): state the crossOriginHeaders rule in the feed query warning, advisory, changesets and docs (#10568)”; “fix(updater): limit the size of update info responses (#10508)”; “fix(updater): treat channel "latest" as stable-only with allowPrerelease (#10360)”; “fix(updater): pick highest version for alpha/beta channel instead of first feed entry (#10289)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 12:16:46 -08:00' --until='2026-11-16 12:16:46 -08:00' --full-history --no-merges -- packages/electron-updater/src/providers/GitHubProvider.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/electron-builder/src/publish.ts packages/electron-builder/src/publish.ts:96— packages/electron-builder/src/publish.ts changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is publish.publishPackageWithTasks at line 96), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: start host programs only from absolute paths via toolsets.executables (#10430)”; “fix: deduplicate publish tasks by value (#10134)”; “fix: clean up publish SIGINT listeners (#10147)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 12:16:46 -08:00' --until='2026-11-16 12:16:46 -08:00' --full-history --no-merges -- packages/electron-builder/src/publish.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/electron-updater/src/LinuxUpdater.ts packages/electron-updater/src/LinuxUpdater.ts:317— packages/electron-updater/src/LinuxUpdater.ts changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is LinuxUpdater.resolveTrustedCommand at line 317), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(updater): refuse unsafe installer paths for gksudo, kdesudo and beesu (#10524)”; “fix(updater): show the install command in the Linux elevation dialog (#10095)”; “fix(updater): install Linux packages without freezing the app (#10094)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 12:16:46 -08:00' --until='2026-11-16 12:16:46 -08:00' --full-history --no-merges -- packages/electron-updater/src/LinuxUpdater.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/app-builder-lib/src/targets/ArchiveTarget.ts packages/app-builder-lib/src/targets/ArchiveTarget.ts:27— packages/app-builder-lib/src/targets/ArchiveTarget.ts changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 11 (its worst body is ArchiveTarget.build at line 27), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(squirrel): wait for zip/7z of the same pack before writing into appOutDir (#10432)”; “fix!: confine copies and linked files by real path, with fileOptions.allowExternalLinks (#10321)”; “fix: Ensure arch is passed to blockmap path macro expansion (#10075)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 12:16:46 -08:00' --until='2026-11-16 12:16:46 -08:00' --full-history --no-merges -- packages/app-builder-lib/src/targets/ArchiveTarget.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/app-builder-lib/src/targets/differentialUpdateInfoBuilder.ts packages/app-builder-lib/src/targets/differentialUpdateInfoBuilder.ts:137— packages/app-builder-lib/src/targets/differentialUpdateInfoBuilder.ts changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 12 (its worst body is differentialUpdateInfoBuilder.locateArchiveHeaderRegions at line 137), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(blockmap): follow-ups to block map v3 (per-platform updater check, prerelease floor, cross-version test) (#10485)”; “fix(nsis): pin the LZMA2 block size of differential-aware packages (#10335)”; “fix: Ensure arch is passed to blockmap path macro expansion (#10075)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 12:16:46 -08:00' --until='2026-11-16 12:16:46 -08:00' --full-history --no-merges -- packages/app-builder-lib/src/targets/differentialUpdateInfoBuilder.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/electron-updater/src/RpmUpdater.ts packages/electron-updater/src/RpmUpdater.ts:50— packages/electron-updater/src/RpmUpdater.ts changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is RpmUpdater.planInstall at line 50), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(updater): install Linux packages without freezing the app (#10094)”; “fix(updater): settle differential download on cancel and contain throwing progress listeners (#10356)”; “fix(electron-updater): keep cached blockmap consistent with cached installer to avoid stale sha512 mismatches (#10098)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 12:16:46 -08:00' --until='2026-11-16 12:16:46 -08:00' --full-history --no-merges -- packages/electron-updater/src/RpmUpdater.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/electron-publish/src/bitbucketPublisher.ts packages/electron-publish/src/bitbucketPublisher.ts:18— packages/electron-publish/src/bitbucketPublisher.ts changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 7 (its worst body is BitbucketPublisher.constructor at line 18), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: point configuration errors at existing docs sections (#10462)”; “fix(docs): repair broken links and anchors (#10305)”; “fix: encode Bitbucket delete filenames (#10150)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 12:16:46 -08:00' --until='2026-11-16 12:16:46 -08:00' --full-history --no-merges -- packages/electron-publish/src/bitbucketPublisher.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/electron-updater/src/PacmanUpdater.ts packages/electron-updater/src/PacmanUpdater.ts:14— packages/electron-updater/src/PacmanUpdater.ts changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 2 (its worst body is PacmanUpdater.doDownloadUpdate at line 14), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(updater): install Linux packages without freezing the app (#10094)”; “fix(updater): settle differential download on cancel and contain throwing progress listeners (#10356)”; “fix(electron-updater): keep cached blockmap consistent with cached installer to avoid stale sha512 mismatches (#10098)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 12:16:46 -08:00' --until='2026-11-16 12:16:46 -08:00' --full-history --no-merges -- packages/electron-updater/src/PacmanUpdater.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/app-builder-lib/src/vm/ParallelsVm.ts packages/app-builder-lib/src/vm/ParallelsVm.ts:11— packages/app-builder-lib/src/vm/ParallelsVm.ts changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is ParallelsVm.parseVmList at line 11), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: start host programs only from absolute paths via toolsets.executables (#10430)”; “fix: start system tools (PowerShell, pwsh, prlctl, wine) by absolute path (#10422)”; “fix(nsis): patch uninstaller icon when extracting the uninstaller and verify its CRC (#10262)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 12:16:46 -08:00' --until='2026-11-16 12:16:46 -08:00' --full-history --no-merges -- packages/app-builder-lib/src/vm/ParallelsVm.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/app-builder-lib/src/vm/vm.ts packages/app-builder-lib/src/vm/vm.ts:59— packages/app-builder-lib/src/vm/vm.ts changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is vm.getWindowsVm at line 59), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: start host programs only from absolute paths via toolsets.executables (#10430)”; “fix: start system tools (PowerShell, pwsh, prlctl, wine) by absolute path (#10422)”; “fix(nsis): patch uninstaller icon when extracting the uninstaller and verify its CRC (#10262)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 12:16:46 -08:00' --until='2026-11-16 12:16:46 -08:00' --full-history --no-merges -- packages/app-builder-lib/src/vm/vm.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Skipped test: (unnamed test) test/src/ArtifactPublisherTest.ts:46— Skipped — switched off by test.skip
Skipped test: should throw when attempting to package a system file test/src/HoistedNodeModuleTest.ts:298— Skipped — switched off by test.skip
Skipped test: outside link test/src/globTest.ts:117— Skipped — switched off by test.skip
Skipped test: assisted test/src/windows/msiTestSuite.ts:191— Skipped — switched off by test.skip
Skipped test: wine=0.0.0 legacy bundle incompatible with modern macOS; covered by wineToolsetSuite test/src/windows/nsisWineTestSuite.ts:25— Skipped — switched off by it.skip
Skipped test: wine@1.0.1 portable bundle not compatible with CI Docker; Linux NSIS coverage in oneClickInstaller.e2e.ts test/src/windows/nsisWineTestSuite.ts:34— Skipped — switched off by it.skip
Skipped test: installerHeaderIcon test/src/windows/oneClickInstaller.e2e.ts:198— Skipped — switched off by test.skip
Skipped test: big file pack test/src/windows/oneClickInstaller.e2e.ts:301— Skipped — switched off by test.skip
Skipped test: delta and msi test/src/windows/squirrelWindowsTestSuite.ts:48— Skipped — switched off by test.skip
Skipped test: azure signing without credentials test/src/windows/winCodeSignTestSuite.ts:169— Skipped — switched off by test.skip
Skipped test: sha512 mismatch error event test/src/updater/nsisUpdaterTest.ts:274— Skipped — switched off by test.skip
Skipped test: test download progress test/src/updater/nsisUpdaterTest.ts:360— Skipped — switched off by test.skip
Skipped test: test downloaded installer test/src/updater/nsisUpdaterTest.ts:668— Skipped — switched off by test.skip
Skipped test: no Applications link test/src/mac/dmg.e2e.ts:274— Skipped — switched off by test.skip
Skipped test: remove password from log test/src/mac/macCodeSignTest.ts:25— Skipped — switched off by test.skip
Skipped test: custom mas test/src/mac/masTest.ts:25— Skipped — switched off by test.skip
Sync-over-async blocking packages/app-builder-lib/src/electron/injectFFMPEG.ts:70— `fs.existsSync` in `copyFFMPEG` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/app-builder-lib/src/electron/mac/electronMac.ts:53— `fs.existsSync` in `safeParsePlistFile` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/app-builder-lib/src/electron/search-module.ts:8— `fs.existsSync` in `shouldContinueSearch` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/app-builder-lib/src/electron/search-module.ts:28— `fs.existsSync` in `traverseAncestorDirectories` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/app-builder-lib/src/targets/mac/pkg.ts:279— `readdirSync` in `buildComponentPackage` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/app-builder-lib/src/targets/win/nsis/nsisUtil.ts:266— `zlib.inflateRawSync` in `exec` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/app-builder-lib/src/util/NodeModuleCopyHelper.ts:177— `realpathSync` in `collectNodeModules` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/app-builder-lib/src/vm/ParallelsVm.ts:101— `execFileSync` in `suspendSync` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/electron-updater/src/MacUpdater.ts:71— `execFileSync` in `doDownloadUpdate` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/electron-updater/src/MacUpdater.ts:81— `execFileSync` in `doDownloadUpdate` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking website/scripts/docusaurus-plugin-prebuild.ts:146— `rmSync` in `prebuildPlugin` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking website/scripts/docusaurus-plugin-prebuild.ts:148— `execSync` in `prebuildPlugin` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking website/scripts/docusaurus-plugin-prebuild.ts:160— `execSync` in `postBuild` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
FileTooLong: cli/migrate-schema-programmatic.ts packages/electron-builder/src/cli/migrate-schema-programmatic.ts— FileTooLong — 1432 significant lines (blank, comment-only and punctuation-only lines excluded), about 94% of them inside a single declaration: ConfigCodemod (130-2167). The bar is 500 significant lines; this is 932 over it, 2.86× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: REDACTED REDACTED— FileTooLong — 989 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 489 over it, 1.98× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/AppUpdater.ts packages/electron-updater/src/AppUpdater.ts— FileTooLong — 952 significant lines (blank, comment-only and punctuation-only lines excluded), about 78% of them inside a single declaration: AppUpdater (147-1723). The bar is 500 significant lines; this is 452 over it, 1.90× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: publish/PublishManager.ts packages/app-builder-lib/src/publish/PublishManager.ts— FileTooLong — 735 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 235 over it, 1.47× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/platformPackager.ts packages/app-builder-lib/src/platformPackager.ts— FileTooLong — 733 significant lines (blank, comment-only and punctuation-only lines excluded), about 86% of them inside a single declaration: PlatformPackager (91-1166). The bar is 500 significant lines; this is 233 over it, 1.47× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: nsis/NsisTarget.ts packages/app-builder-lib/src/targets/win/nsis/NsisTarget.ts— FileTooLong — 669 significant lines (blank, comment-only and punctuation-only lines excluded), about 87% of them inside a single declaration: NsisTarget (96-1073). The bar is 500 significant lines; this is 169 over it, 1.34× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: node-module-collector/hoist.ts packages/app-builder-lib/src/node-module-collector/hoist.ts— FileTooLong — 660 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 160 over it, 1.32× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: util/electronGet.ts packages/app-builder-lib/src/util/electronGet.ts— FileTooLong — 563 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 63 over it, 1.13× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: REDACTED REDACTED— FileTooLong — 545 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 45 over it, 1.09× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/macPackager.ts packages/app-builder-lib/src/macPackager.ts— FileTooLong — 542 significant lines (blank, comment-only and punctuation-only lines excluded), about 88% of them inside a single declaration: MacPackager (78-915). The bar is 500 significant lines; this is 42 over it, 1.08× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/packager.ts packages/app-builder-lib/src/packager.ts— FileTooLong — 501 significant lines (blank, comment-only and punctuation-only lines excluded), about 78% of them inside a single declaration: Packager (95-788). The bar is 500 significant lines; this is 1 over it, 1.00× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
TodoComment test/vitest-scripts/vitest-config/smart-config.ts:92— // TODO: FIX ALL OF THESE 😅 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment test/src/windows/appxTestSuite.ts:94— // todo - check manifest — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment test/src/updater/macUpdaterTest.ts:159— // todo when will be updated to use files — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment test/src/mac/macCodeSignTest.ts:24— // TODO: fix me — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment test/src/helpers/packTester.ts:373— // TODO: consider use hard links for tests — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/app-builder-lib/src/macPackager.ts:807— // todo fileAssociations — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/app-builder-lib/src/util/langs.ts:31— // todo "ro_RO" "el_GR" "et_EE" "ka_GE" — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TooManyMethods: ConfigCodemod packages/electron-builder/src/cli/migrate-schema-programmatic.ts:130— TooManyMethods — 82 methods. The bar is 30 methods; this is 52 over it, 2.73× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: PlatformPackager packages/app-builder-lib/src/platformPackager.ts:91— TooManyMethods — 58 methods. The bar is 30 methods; this is 28 over it, 1.93× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: AppUpdater packages/electron-updater/src/AppUpdater.ts:147— TooManyMethods — 40 methods. The bar is 30 methods; this is 10 over it, 1.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Packager packages/app-builder-lib/src/packager.ts:95— TooManyMethods — 39 methods. The bar is 30 methods; this is 9 over it, 1.30× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: MacTargetHelper packages/app-builder-lib/src/targets/mac/MacTargetHelper.ts:31— TooManyMethods — 31 methods. The bar is 30 methods; this is 1 over it, 1.03× 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.
Duplicated block (10 lines × 2 locations) packages/app-builder-lib/src/codeSign/certInfo.ts:496— packages/app-builder-lib/src/codeSign/certInfo.ts:496 · packages/app-builder-lib/src/codeSign/certInfo.ts:553 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2 locations) packages/app-builder-lib/src/targets/linux/FlatpakTarget.ts:70— packages/app-builder-lib/src/targets/linux/FlatpakTarget.ts:70 · packages/app-builder-lib/src/targets/linux/appimage/AppImageTarget.ts:174 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (10 lines × 2 locations) REDACTED:1019— REDACTED:1019 · REDACTED:1058 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2 locations) packages/electron-updater/src/AppImageUpdater.ts:64— packages/electron-updater/src/AppImageUpdater.ts:64 · packages/electron-updater/src/AppUpdater.ts:1577 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
Duplicated block (10 lines × 2 locations) scripts/checkDeps.js:36— scripts/checkDeps.js:36 · scripts/checkDeps.js:50 — 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.
Swallowed exception (caught, then discarded) packages/electron-updater/src/providers/GitHubProvider.ts:304— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
Swallowed exception (caught, then discarded) packages/app-builder-lib/src/util/archCompatibility.ts:114— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
Swallowed exception (caught, then discarded) packages/app-builder-lib/src/util/archCompatibility.ts:169— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
Swallowed exception (caught, then discarded) packages/app-builder-lib/src/util/cacheState.ts:89— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
Swallowed exception (caught, then discarded) packages/app-builder-lib/src/util/packageMetadata.ts:37— `catch (_ignored)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
FunctionTooLong: electronMac.createMacApp packages/app-builder-lib/src/electron/mac/electronMac.ts:28— FunctionTooLong — createMacApp runs 141 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 41 over it, 1.41× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: docusaurus-plugin-changelog.parseChangelog website/scripts/docusaurus-plugin-changelog.ts:38— FunctionTooLong — parseChangelog runs 137 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 37 over it, 1.37× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: hoist.hoistGraph packages/app-builder-lib/src/node-module-collector/hoist.ts:671— FunctionTooLong — hoistGraph runs 119 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 19 over it, 1.19× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: blockmap.chunkFile packages/app-builder-lib/src/targets/blockmap/blockmap.ts:179— FunctionTooLong — chunkFile runs 106 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 6 over it, 1.06× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: NsisTarget.buildInstaller packages/app-builder-lib/src/targets/win/nsis/NsisTarget.ts:339— MethodTooLong — buildInstaller runs 132 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 32 over it, 1.32× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: AppUpdater.differentialDownloadInstaller packages/electron-updater/src/AppUpdater.ts:1526— MethodTooLong — differentialDownloadInstaller runs 126 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 26 over it, 1.26× 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: FpmTarget.build packages/app-builder-lib/src/targets/linux/FpmTarget.ts:143— MethodTooLong — build runs 125 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 25 over it, 1.25× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: PlatformPackager.doPack packages/app-builder-lib/src/platformPackager.ts:469— MethodTooLong — doPack runs 111 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 11 over it, 1.11× 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 locations) REDACTED:534— REDACTED:534 · REDACTED:545 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2 locations) packages/app-builder-lib/src/toolsets/appimage.ts:57— packages/app-builder-lib/src/toolsets/appimage.ts:57 · packages/app-builder-lib/src/toolsets/archive.ts:39 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (9 lines × 2 locations) packages/builder-util-runtime/src/blockMapV3.ts:160— packages/builder-util-runtime/src/blockMapV3.ts:160 · packages/builder-util-runtime/src/blockMapV3.ts:180 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2 locations) packages/electron-publish/src/s3/s3UploadHelper.ts:149— packages/electron-publish/src/s3/s3UploadHelper.ts:149 · packages/electron-publish/src/s3/s3UploadHelper.ts:215 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
ClassTooLong: ConfigCodemod packages/electron-builder/src/cli/migrate-schema-programmatic.ts:130— ClassTooLong — 1341 significant lines (blank, comment-only and punctuation-only lines excluded), 82 methods. The bar is 400 significant lines; this is 941 over it, 3.35× 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: PlatformPackager packages/app-builder-lib/src/platformPackager.ts:91— ClassTooLong — 627 significant lines (blank, comment-only and punctuation-only lines excluded), 58 methods. The bar is 400 significant lines; this is 227 over it, 1.57× 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: MacPackager packages/app-builder-lib/src/macPackager.ts:78— ClassTooLong — 479 significant lines (blank, comment-only and punctuation-only lines excluded), 28 methods. The bar is 400 significant lines; this is 79 over it, 1.20× 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.
Low cohesion: MacPackager (LCOM4 6) packages/app-builder-lib/src/macPackager.ts:78— MacPackager's methods fall into 6 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 6 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.
Low cohesion: SigntoolBaseSignManager (LCOM4 6) REDACTED:111— SigntoolBaseSignManager's methods fall into 6 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 6 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.
Low cohesion: NsisUpdater (LCOM4 4) packages/electron-updater/src/NsisUpdater.ts:39— NsisUpdater's methods fall into 4 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 4 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.
X17 · Uncapped recursion over a caller-supplied document· Recursive walk over a caller-supplied document has no depth cap · ×3
Recursive walk over a caller-supplied document has no depth cap packages/electron-updater/src/LinuxUpdater.ts:178— `runInstallPlan` is exported, takes a document from its caller (line 188) and hands it to `installPlanCommands`, which calls itself at line 178 (`installPlanCommands`) with a piece of `plan` — and nowhere in `installPlanCommands` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `installPlanCommands` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap packages/builder-util-runtime/src/objects.ts:12— `mapToObject` is exported and takes `map: RecursiveMap` from its caller, and it calls itself at line 12 (`mapToObject`) with a piece of `map` — and nowhere in `mapToObject` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `mapToObject` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap packages/app-builder-lib/src/util/mac/plist.ts:22— `savePlistFile` is exported, takes a document from its caller (line 34) and hands it to `sortObjectKeys`, which calls itself at line 22 (`sortObjectKeys`) with a piece of `obj` (and at line 29) — and nowhere in `sortObjectKeys` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `sortObjectKeys` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
D10 · Test Quality· Fixed-sleep synchronisation · ×2
Fixed-sleep synchronisation: waits for the archive of the same pack before writing app-update.yml, even once finishBuild() drained it test/src/linux/appImageTargetPackWorkTest.ts:75— This test starts work it did not wait for (`zipFinished`, still running when the sleep starts) and then orders itself against it with `new Promise(resolve => setTimeout(resolve, 10))` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
Fixed-sleep synchronisation: waits for the archive of the same pack before writing into appOutDir, even once finishBuild() drained it test/src/linux/fpmTargetPackWorkTest.ts:75— This test starts work it did not wait for (`zipFinished`, still running when the sleep starts) and then orders itself against it with `new Promise(resolve => setTimeout(resolve, 10))` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
Off the main sequence: builder-util — builder-util: abstractness 0.07, instability 0.17, distance 0.77 — zone of pain — concrete and depended on by 5 project(s), so it's rigid to change.
Off the main sequence: builder-util-runtime — builder-util-runtime: abstractness 0.23, instability 0.00, distance 0.77 — zone of pain — concrete and depended on by 6 project(s), so it's rigid to change.
R10 · Code Duplication· Duplicated block with local edits (20 matched lines × 2 locations) · ×2
Duplicated block with local edits (20 matched lines × 2 locations) REDACTED:24— REDACTED:24 · REDACTED:595 — the two spans are one implementation copied and then locally edited — 146 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block with local edits (20 matched lines × 2 locations) packages/app-builder-lib/src/node-module-collector/moduleManager.ts:354— packages/app-builder-lib/src/node-module-collector/moduleManager.ts:354 · packages/app-builder-lib/src/node-module-collector/moduleManager.ts:390 — the two spans are one implementation copied and then locally edited — 144 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (16 lines × 2 locations) packages/electron-updater/src/DebUpdater.ts:36— packages/electron-updater/src/DebUpdater.ts:36 · packages/electron-updater/src/RpmUpdater.ts:33 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
Duplicated block (16 lines × 2 locations) packages/electron-updater/src/differentialDownloader/blockMapV3Fetcher.ts:217— packages/electron-updater/src/differentialDownloader/blockMapV3Fetcher.ts:217 · packages/electron-updater/src/differentialDownloader/blockMapV3Fetcher.ts:238 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2 locations) packages/app-builder-lib/src/macPackager.ts:358— packages/app-builder-lib/src/macPackager.ts:358 · packages/app-builder-lib/src/platformPackager.ts:492 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
Duplicated block (14 lines × 2 locations) packages/app-builder-lib/src/targets/linux/snap/coreLegacy.ts:121— packages/app-builder-lib/src/targets/linux/snap/coreLegacy.ts:121 · packages/app-builder-lib/src/targets/linux/snap/coreLegacy.ts:187 — 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.
R10 · Code Duplication· Duplicated block with local edits (14 matched lines × 2 locations) · ×2
Duplicated block with local edits (14 matched lines × 2 locations) REDACTED:421— REDACTED:421 · REDACTED:445 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block with local edits (14 matched lines × 2 locations) packages/electron-updater/src/differentialDownloader/DifferentialDownloader.ts:272— packages/electron-updater/src/differentialDownloader/DifferentialDownloader.ts:272 · packages/electron-updater/src/differentialDownloader/multipleRangeDownloader.ts:100 — the two spans are one implementation copied and then locally edited — 84 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (11 lines × 2 locations) packages/app-builder-lib/src/targets/win/AppxTarget.ts:50— packages/app-builder-lib/src/targets/win/AppxTarget.ts:50 · packages/app-builder-lib/src/targets/win/MsixTarget.ts:148 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (11 lines × 2 locations) packages/electron-updater/src/differentialDownloader/downloadPlanBuilder.ts:57— packages/electron-updater/src/differentialDownloader/downloadPlanBuilder.ts:57 · packages/electron-updater/src/differentialDownloader/downloadPlanBuilder.ts:70 — 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.
R10 · Code Duplication· Duplicated block with local edits (8 matched lines × 2 locations) · ×2
Duplicated block with local edits (8 matched lines × 2 locations) packages/app-builder-lib/src/fileMatcher.ts:546— packages/app-builder-lib/src/fileMatcher.ts:546 · packages/app-builder-lib/src/fileMatcher.ts:658 — the two spans are one implementation copied and then locally edited — 63 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block with local edits (8 matched lines × 2 locations) REDACTED:238— REDACTED:238 · packages/electron-updater/src/NsisUpdater.ts:87 — the two spans are one implementation copied and then locally edited — 71 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (8 lines × 2 locations) packages/app-builder-lib/src/targets/win/winAppUtil.ts:160— packages/app-builder-lib/src/targets/win/winAppUtil.ts:160 · packages/app-builder-lib/src/targets/win/winAppUtil.ts:175 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (8 lines × 2 locations) REDACTED:468— REDACTED:468 · REDACTED:190 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Weak hash algorithm packages/app-builder-lib/src/codeSign/certInfo.ts:275— MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
Weak hash algorithm packages/app-builder-lib/src/codeSign/certInfo.ts:277— MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
X24 · Document value interpolated into markup unescaped· Untrusted text written into markup unescaped · ×2
Untrusted text written into markup unescaped packages/app-builder-lib/src/targets/win/MsiTarget.ts:320— `item.description?`Description="${escapeForXml(item.description)}"`:""` is text this program did not author, and it is written into an unquoted attribute through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML text encoding does not help in an unquoted attribute — whitespace ends it; quote the attribute and encode the value.
Untrusted text written into markup unescaped packages/app-builder-lib/src/targets/win/winAppUtil.ts:384— `argsAttr` is text this program did not author, and it is written into an unquoted attribute through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML text encoding does not help in an unquoted attribute — whitespace ends it; quote the attribute and encode the value.
migrate-schema.migrateConfig (cyclomatic 109) REDACTED:279— migrate-schema.migrateConfig has cyclomatic complexity 109 (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.
docusaurus-plugin-changelog.parseChangelog (cyclomatic 55) website/scripts/docusaurus-plugin-changelog.ts:38— docusaurus-plugin-changelog.parseChangelog has cyclomatic complexity 55 (threshold 15). Of this number, 42 points are the body's own statements and 13 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
hoist.getNodeHoistInfo (cyclomatic 47) packages/app-builder-lib/src/node-module-collector/hoist.ts:526— hoist.getNodeHoistInfo has cyclomatic complexity 47 (threshold 15). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
NodeModuleCopyHelper.collectNodeModules (cyclomatic 46) packages/app-builder-lib/src/util/NodeModuleCopyHelper.ts:52— NodeModuleCopyHelper.collectNodeModules has cyclomatic complexity 46 (threshold 15). Most of this is not in the body itself: 9 of the 46 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 88, a function literal at line 122, isDirMatched, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
builder.normalizeOptions (cyclomatic 45) packages/electron-builder/src/builder.ts:33— builder.normalizeOptions has cyclomatic complexity 45 (threshold 15). Of this number, 36 points are the body's own statements and 9 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MsixTarget.writeManifest (cyclomatic 37) packages/app-builder-lib/src/targets/win/MsixTarget.ts:152— MsixTarget.writeManifest has cyclomatic complexity 37 (threshold 15). Most of this is not in the body itself: 4 of the 37 points are its own statements and the rest belongs to one function literal inside it that branches (line 166). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
NsisTarget.buildInstaller (cyclomatic 37) packages/app-builder-lib/src/targets/win/nsis/NsisTarget.ts:339— NsisTarget.buildInstaller has cyclomatic complexity 37 (threshold 15). Of this number, 29 points are the body's own statements and 8 belong to one function literal inside it that branches. 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.
AppXTarget.writeManifest (cyclomatic 36) packages/app-builder-lib/src/targets/win/AppxTarget.ts:54— AppXTarget.writeManifest has cyclomatic complexity 36 (threshold 15). Most of this is not in the body itself: 5 of the 36 points are its own statements and the rest belongs to one function literal inside it that branches (line 68). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
SnapCoreLegacy.createDescriptor (cyclomatic 36) packages/app-builder-lib/src/targets/linux/snap/coreLegacy.ts:68— SnapCoreLegacy.createDescriptor has cyclomatic complexity 36 (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.
electronMac.createMacApp (cyclomatic 34) packages/app-builder-lib/src/electron/mac/electronMac.ts:28— electronMac.createMacApp has cyclomatic complexity 34 (threshold 15). Of this number, 25 points are the body's own statements and 9 belong to 5 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ConfigCodemod.ruleIncludePdb (cyclomatic 34) packages/electron-builder/src/cli/migrate-schema-programmatic.ts:1583— ConfigCodemod.ruleIncludePdb has cyclomatic complexity 34 (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.
archive.archive (cyclomatic 33) packages/app-builder-lib/src/targets/archive.ts:259— archive.archive has cyclomatic complexity 33 (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.
updateManifestVerifier.compareListedFiles (cyclomatic 33) packages/app-builder-lib/src/publish/updateManifestVerifier.ts:54— updateManifestVerifier.compareListedFiles has cyclomatic complexity 33 (threshold 15). Of this number, 32 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SnapCore24.mapSnapOptionsToSnapcraftYAML (cyclomatic 33) packages/app-builder-lib/src/targets/linux/snap/core24.ts:181— SnapCore24.mapSnapOptionsToSnapcraftYAML has cyclomatic complexity 33 (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.
updateManifestSignature.validateSignedManifestShape (cyclomatic 33) packages/builder-util-runtime/src/updateManifestSignature.ts:166— updateManifestSignature.validateSignedManifestShape has cyclomatic complexity 33 (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.
ConfigCodemod.rulePlatformAsar (cyclomatic 33) packages/electron-builder/src/cli/migrate-schema-programmatic.ts:959— ConfigCodemod.rulePlatformAsar has cyclomatic complexity 33 (threshold 15). Of this number, 32 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AppUpdater.differentialDownloadInstaller (cyclomatic 31) packages/electron-updater/src/AppUpdater.ts:1526— AppUpdater.differentialDownloadInstaller has cyclomatic complexity 31 (threshold 15). Of this number, 27 points are the body's own statements and 4 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
archive.compute7zCompressArgs (cyclomatic 30) packages/app-builder-lib/src/targets/archive.ts:171— archive.compute7zCompressArgs 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.
MsiTarget.computeFileDeclaration (cyclomatic 30) packages/app-builder-lib/src/targets/win/MsiTarget.ts:222— MsiTarget.computeFileDeclaration has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 5 of the 30 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 238, 338). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
HttpExecutor.handleResponse (cyclomatic 30) REDACTED:262— HttpExecutor.handleResponse has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 14 of the 30 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 341, 319). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
PublishManager.getResolvedPublishConfig (cyclomatic 29) packages/app-builder-lib/src/publish/PublishManager.ts:1135— PublishManager.getResolvedPublishConfig has cyclomatic complexity 29 (threshold 15). Of this number, 27 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
hoist.hoistGraph::hoistNodeDependencies (cyclomatic 28) packages/app-builder-lib/src/node-module-collector/hoist.ts:687— hoist.hoistGraph::hoistNodeDependencies has cyclomatic complexity 28 (threshold 15). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
ConfigCodemod.ruleWinSign (cyclomatic 28) packages/electron-builder/src/cli/migrate-schema-programmatic.ts:1281— ConfigCodemod.ruleWinSign has cyclomatic complexity 28 (threshold 15). Of this number, 26 points are the body's own statements and 2 belong to one function item inside it that branches. 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.
rfc2253Parser.parseDn (cyclomatic 27) packages/builder-util-runtime/src/rfc2253Parser.ts:45— rfc2253Parser.parseDn has cyclomatic complexity 27 (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.
dmgUtil.customizeDmg (cyclomatic 27) packages/dmg-builder/src/dmgUtil.ts:166— dmgUtil.customizeDmg has cyclomatic complexity 27 (threshold 15). Of this number, 25 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
blockmap.chunkFile (cyclomatic 26) packages/app-builder-lib/src/targets/blockmap/blockmap.ts:179— blockmap.chunkFile has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 4 of the 26 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 291, processByte, enterSegmentAt, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
FpmTarget.build (cyclomatic 26) packages/app-builder-lib/src/targets/linux/FpmTarget.ts:143— FpmTarget.build has cyclomatic complexity 26 (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.
ConfigCodemod.ruleAsar (cyclomatic 26) packages/electron-builder/src/cli/migrate-schema-programmatic.ts:841— ConfigCodemod.ruleAsar has cyclomatic complexity 26 (threshold 15). Of this number, 19 points are the body's own statements and 7 belong to 3 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
migrate-schema.migrateElectronDownload (cyclomatic 26) REDACTED:1184— migrate-schema.migrateElectronDownload has cyclomatic complexity 26 (threshold 15). Of this number, 25 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MacTargetHelper.buildSignOptions (cyclomatic 25) packages/app-builder-lib/src/targets/mac/MacTargetHelper.ts:293— MacTargetHelper.buildSignOptions has cyclomatic complexity 25 (threshold 15). Of this number, 14 points are the body's own statements and 11 belong to 3 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
nativeBinaryVerifier.parseNativeBinaryHeader (cyclomatic 25) packages/app-builder-lib/src/util/nativeBinaryVerifier.ts:49— nativeBinaryVerifier.parseNativeBinaryHeader has cyclomatic complexity 25 (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.
certInfo.readCertInfo (cyclomatic 24) packages/app-builder-lib/src/codeSign/certInfo.ts:375— certInfo.readCertInfo has cyclomatic complexity 24 (threshold 15). Of this number, 20 points are the body's own statements and 4 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.
WinPackager.signAndEditResources (cyclomatic 24) packages/app-builder-lib/src/winPackager.ts:238— WinPackager.signAndEditResources 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.
fs.walk (cyclomatic 24) packages/builder-util/src/fs.ts:85— fs.walk has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 9 of the 24 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 113, 129, 107). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
ConfigCodemod.ruleCustomNsis (cyclomatic 23) packages/electron-builder/src/cli/migrate-schema-programmatic.ts:1223— ConfigCodemod.ruleCustomNsis has cyclomatic complexity 23 (threshold 15). Of this number, 21 points are the body's own statements and 2 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
index.Changelog (cyclomatic 23) REDACTED:154— index.Changelog has cyclomatic complexity 23 (threshold 15). Of this number, 20 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
LinuxTargetHelper.computeDesktopEntry (cyclomatic 22) packages/app-builder-lib/src/targets/linux/LinuxTargetHelper.ts:278— LinuxTargetHelper.computeDesktopEntry has cyclomatic complexity 22 (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.
fileMatcher.getMainFileMatchers (cyclomatic 22) packages/app-builder-lib/src/fileMatcher.ts:434— fileMatcher.getMainFileMatchers has cyclomatic complexity 22 (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.
arch.getArtifactArchName (cyclomatic 22) packages/builder-util/src/arch.ts:57— arch.getArtifactArchName has cyclomatic complexity 22 (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.
ConfigCodemod.ruleMacSigning (cyclomatic 22) packages/electron-builder/src/cli/migrate-schema-programmatic.ts:1439— ConfigCodemod.ruleMacSigning has cyclomatic complexity 22 (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.
ConfigCodemod.ruleElectronDownload (cyclomatic 22) packages/electron-builder/src/cli/migrate-schema-programmatic.ts:1741— ConfigCodemod.ruleElectronDownload has cyclomatic complexity 22 (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.
AppUpdater.executeDownload (cyclomatic 22) packages/electron-updater/src/AppUpdater.ts:1363— AppUpdater.executeDownload has cyclomatic complexity 22 (threshold 15). Of this number, 12 points are the body's own statements and 10 belong to 3 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
PnpmNodeModulesCollector.extractProductionDependencyGraph (cyclomatic 21) packages/app-builder-lib/src/node-module-collector/pnpmNodeModulesCollector.ts:251— PnpmNodeModulesCollector.extractProductionDependencyGraph has cyclomatic complexity 21 (threshold 15). Of this number, 18 points are the body's own statements and 3 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.
MacPackager.checkForceCodeSigningAtBuildStart (cyclomatic 21) packages/app-builder-lib/src/macPackager.ts:127— MacPackager.checkForceCodeSigningAtBuildStart has cyclomatic complexity 21 (threshold 15). Of this number, 20 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PlatformPackager.doPack (cyclomatic 21) packages/app-builder-lib/src/platformPackager.ts:469— PlatformPackager.doPack has cyclomatic complexity 21 (threshold 15). Of this number, 19 points are the body's own statements and 2 belong to one function item inside it that branches. 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.
PublishManager.constructor (cyclomatic 21) packages/app-builder-lib/src/publish/PublishManager.ts:217— PublishManager.constructor has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 10 of the 21 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 248, 286, 275). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
windowsInstaller.createWindowsInstaller (cyclomatic 21) REDACTED:72— windowsInstaller.createWindowsInstaller has cyclomatic complexity 21 (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.
GitLabProvider.getLatestVersion (cyclomatic 21) packages/electron-updater/src/providers/GitLabProvider.ts:81— GitLabProvider.getLatestVersion has cyclomatic complexity 21 (threshold 15). Of this number, 14 points are the body's own statements and 7 belong to one function item inside it that branches. 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.
BaseUpdater.installPendingUpdate (cyclomatic 21) REDACTED:479— BaseUpdater.installPendingUpdate has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
NsisUpdater.doDownloadUpdate (cyclomatic 21) packages/electron-updater/src/NsisUpdater.ts:221— NsisUpdater.doDownloadUpdate has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 9 of the 21 points are its own statements and the rest belongs to one function literal inside it that branches (line 262). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
iconConverter.doConvertIcon (cyclomatic 20) packages/app-builder-lib/src/util/iconConverter.ts:223— iconConverter.doConvertIcon has cyclomatic complexity 20 (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.
UninstallerReader.exec (cyclomatic 20) packages/app-builder-lib/src/targets/win/nsis/nsisUtil.ts:202— UninstallerReader.exec has cyclomatic complexity 20 (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.
util.exec (cyclomatic 20) packages/builder-util/src/util.ts:220— util.exec has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 8 of the 20 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 256, 246, 297). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
migrate-schema.migratePlatformAsar (cyclomatic 20) REDACTED:1080— migrate-schema.migratePlatformAsar has cyclomatic complexity 20 (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.
sign-update-manifest.checkListedFiles (cyclomatic 20) packages/electron-builder/src/cli/sign-update-manifest.ts:395— sign-update-manifest.checkListedFiles has cyclomatic complexity 20 (threshold 15). Of this number, 17 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MacPackager.sign (cyclomatic 19) packages/app-builder-lib/src/macPackager.ts:674— MacPackager.sign has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
NsisTarget.configureDefines (cyclomatic 19) packages/app-builder-lib/src/targets/win/nsis/NsisTarget.ts:693— NsisTarget.configureDefines has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
buildOutputVerifier.verifyWindowsArtifacts (cyclomatic 19) packages/app-builder-lib/src/util/buildOutputVerifier.ts:421— buildOutputVerifier.verifyWindowsArtifacts has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
awsCredentials.parseAwsIni (cyclomatic 19) packages/electron-publish/src/s3/awsCredentials.ts:48— awsCredentials.parseAwsIni has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DataSplitter.handleData (cyclomatic 19) packages/electron-updater/src/differentialDownloader/DataSplitter.ts:221— DataSplitter.handleData has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
model.compare (cyclomatic 19) website/src/changelog/model.ts:94— model.compare has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 8 of the 19 points are its own statements and the rest belongs to one function literal inside it that branches (line 102). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
index.findWorkspaceRoot (cyclomatic 18) packages/app-builder-lib/src/node-module-collector/index.ts:71— index.findWorkspaceRoot has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 7 of the 18 points are its own statements and the rest belongs to one function literal inside it that branches (line 106). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
fileTransformer.cleanupPackageJson (cyclomatic 18) packages/app-builder-lib/src/fileTransformer.ts:47— fileTransformer.cleanupPackageJson has cyclomatic complexity 18 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
electronGet.extractZipStreaming (cyclomatic 18) packages/app-builder-lib/src/util/electronGet.ts:205— electronGet.extractZipStreaming has cyclomatic complexity 18 (threshold 15). Of this number, 15 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
electronGet.downloadArtifactToFile (cyclomatic 18) packages/app-builder-lib/src/util/electronGet.ts:470— electronGet.downloadArtifactToFile has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 7 of the 18 points are its own statements and the rest belongs to one function literal inside it that branches (line 502). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
snapcraftBuilder.validateSnapcraftConfig (cyclomatic 18) REDACTED:59— snapcraftBuilder.validateSnapcraftConfig has cyclomatic complexity 18 (threshold 15). Of this number, 16 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
SnapCoreLegacy.buildSnap (cyclomatic 18) packages/app-builder-lib/src/targets/linux/snap/coreLegacy.ts:217— SnapCoreLegacy.buildSnap has cyclomatic complexity 18 (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.
migrate-schema.migrateMacSigning (cyclomatic 18) REDACTED:986— migrate-schema.migrateMacSigning has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
providerFactory.createClient (cyclomatic 18) packages/electron-updater/src/providerFactory.ts:27— providerFactory.createClient has cyclomatic complexity 18 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
hoist.selfCheck::checkNode (cyclomatic 17) packages/app-builder-lib/src/node-module-collector/hoist.ts:842— hoist.selfCheck::checkNode has cyclomatic complexity 17 (threshold 15). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
AsarPackager.processFileSets (cyclomatic 17) packages/app-builder-lib/src/asar/asarUtil.ts:187— AsarPackager.processFileSets has cyclomatic complexity 17 (threshold 15). Of this number, 9 points are the body's own statements and 8 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MacPackager.applyCommonInfo (cyclomatic 17) packages/app-builder-lib/src/macPackager.ts:808— MacPackager.applyCommonInfo has cyclomatic complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body: 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.
snapcraftBuilder.buildSnap (cyclomatic 17) REDACTED:225— snapcraftBuilder.buildSnap 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.
ConfigCodemod.ruleMacEntitlementsAdvisory (cyclomatic 17) packages/electron-builder/src/cli/migrate-schema-programmatic.ts:438— ConfigCodemod.ruleMacEntitlementsAdvisory has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 7 of the 17 points are its own statements and the rest belongs to 3 function items inside it that branch (bypassesDefaults, isNullLiteral, namesEntitlements). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
verify.verify (cyclomatic 17) packages/electron-builder/src/cli/verify.ts:47— verify.verify 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.
DifferentialDownloader.writeNewFile (cyclomatic 17) packages/electron-updater/src/differentialDownloader/DifferentialDownloader.ts:196— DifferentialDownloader.writeNewFile has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to 5 function literals inside it that branch (lines 199, 272, 318, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
AppUpdater.getBlockMapEnd (cyclomatic 17) packages/electron-updater/src/AppUpdater.ts:1764— AppUpdater.getBlockMapEnd has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
macroExpander.expandMacro (cyclomatic 16) packages/app-builder-lib/src/util/macroExpander.ts:5— macroExpander.expandMacro has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 2 of the 16 points are its own statements and the rest belongs to one function literal inside it that branches (line 18). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
AppInfo.constructor (cyclomatic 16) packages/app-builder-lib/src/appInfo.ts:37— AppInfo.constructor has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
nativeBinaryVerifier.findNativeBinaryMismatches (cyclomatic 16) packages/app-builder-lib/src/util/nativeBinaryVerifier.ts:342— nativeBinaryVerifier.findNativeBinaryMismatches has cyclomatic complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
config.getConfig (cyclomatic 16) packages/app-builder-lib/src/util/config/config.ts:51— config.getConfig has cyclomatic complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
wine.getWineToolset (cyclomatic 16) packages/app-builder-lib/src/toolsets/wine.ts:27— wine.getWineToolset has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
NsisTarget.computeFinalScript (cyclomatic 16) packages/app-builder-lib/src/targets/win/nsis/NsisTarget.ts:1006— NsisTarget.computeFinalScript has cyclomatic complexity 16 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
updateInfoBuilder.createUpdateInfoTasks (cyclomatic 16) packages/app-builder-lib/src/publish/updateInfoBuilder.ts:114— updateInfoBuilder.createUpdateInfoTasks 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.
PublishManager.artifactCreatedWithoutExplicitPublishConfig (cyclomatic 16) packages/app-builder-lib/src/publish/PublishManager.ts:372— PublishManager.artifactCreatedWithoutExplicitPublishConfig 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.
PublishManager.createAppUpdateConfiguration (cyclomatic 16) packages/app-builder-lib/src/publish/PublishManager.ts:617— PublishManager.createAppUpdateConfiguration has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
WinPackager.createTargets (cyclomatic 16) packages/app-builder-lib/src/winPackager.ts:68— WinPackager.createTargets has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 6 of the 16 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 96, getCopyElevateHelper, getHelper, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
migrate-schema.migrateIncludePdb (cyclomatic 16) REDACTED:849— migrate-schema.migrateIncludePdb 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.
migrate-schema.migrateSchema (cyclomatic 16) REDACTED:1508— migrate-schema.migrateSchema has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
BlockMapV3Fetcher.doRequest (cyclomatic 16) packages/electron-updater/src/differentialDownloader/blockMapV3Fetcher.ts:387— BlockMapV3Fetcher.doRequest has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 402, 447, 389, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
blockMapV3Fetcher.verifyBlockMapV3 (cyclomatic 16) packages/electron-updater/src/differentialDownloader/blockMapV3Fetcher.ts:637— blockMapV3Fetcher.verifyBlockMapV3 has cyclomatic complexity 16 (threshold 15). Of this number, 9 points are the body's own statements and 7 belong to 2 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
migrate-schema.migrateConfig (cognitive 168) REDACTED:279— migrate-schema.migrateConfig has cognitive complexity 168 (threshold 15). Drivers by points: if/else 70 (122 pts), boolean chains 25, loops 11 (19 pts), ternaries 1 (2 pts) (nesting depth added 61). 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.
docusaurus-plugin-changelog.parseChangelog (cognitive 107) website/scripts/docusaurus-plugin-changelog.ts:38— docusaurus-plugin-changelog.parseChangelog has cognitive complexity 107 (threshold 15). Drivers by points: if/else 27 (66 pts), loops 11 (22 pts), boolean chains 12, ternaries 2 (7 pts) (nesting depth added 55). Of this number, 90 points are the body's own statements and 17 belong to 2 function items inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
hoist.getNodeHoistInfo (cognitive 94) packages/app-builder-lib/src/node-module-collector/hoist.ts:526— hoist.getNodeHoistInfo has cognitive complexity 94 (threshold 15). Drivers by points: if/else 28 (67 pts), boolean chains 15, loops 4 (10 pts), ternaries 1 (2 pts) (nesting depth added 46). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
builder.normalizeOptions (cognitive 77) packages/electron-builder/src/builder.ts:33— builder.normalizeOptions has cognitive complexity 77 (threshold 15). Drivers by points: if/else 23 (39 pts), ternaries 6 (19 pts), loops 6 (13 pts), boolean chains 6 (nesting depth added 36). Of this number, 68 points are the body's own statements and 9 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NodeModuleCopyHelper.collectNodeModules (cognitive 73) packages/app-builder-lib/src/util/NodeModuleCopyHelper.ts:52— NodeModuleCopyHelper.collectNodeModules has cognitive complexity 73 (threshold 15). Drivers by points: if/else 22 (49 pts), boolean chains 15, loops 5 (9 pts) (nesting depth added 31). Of this number, 17 points are the body's own statements and 56 belong to 4 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
archive.archive (cognitive 60) packages/app-builder-lib/src/targets/archive.ts:259— archive.archive has cognitive complexity 60 (threshold 15). Drivers by points: if/else 20 (38 pts), ternaries 6 (14 pts), boolean chains 5, error handling 1 (2 pts), loops 1 (nesting depth added 27). 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.
SnapCoreLegacy.createDescriptor (cognitive 56) packages/app-builder-lib/src/targets/linux/snap/coreLegacy.ts:68— SnapCoreLegacy.createDescriptor has cognitive complexity 56 (threshold 15). Drivers by points: if/else 24 (43 pts), boolean chains 7, loops 2 (5 pts), ternaries 1 (nesting depth added 22). 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.
hoist.hoistGraph::hoistNodeDependencies (cognitive 54) packages/app-builder-lib/src/node-module-collector/hoist.ts:687— hoist.hoistGraph::hoistNodeDependencies has cognitive complexity 54 (threshold 15). Drivers by points: if/else 16 (37 pts), loops 6 (11 pts), boolean chains 6 (nesting depth added 26). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
rfc2253Parser.parseDn (cognitive 54) packages/builder-util-runtime/src/rfc2253Parser.ts:45— rfc2253Parser.parseDn has cognitive complexity 54 (threshold 15). Drivers by points: if/else 16 (43 pts), boolean chains 6, loops 2 (5 pts) (nesting depth added 30). 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.
AppUpdater.differentialDownloadInstaller (cognitive 48) packages/electron-updater/src/AppUpdater.ts:1526— AppUpdater.differentialDownloadInstaller has cognitive complexity 48 (threshold 15). Drivers by points: if/else 19 (26 pts), ternaries 5 (13 pts), error handling 4 (6 pts), boolean chains 3 (nesting depth added 17). Of this number, 44 points are the body's own statements and 4 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MsiTarget.computeFileDeclaration (cognitive 47) packages/app-builder-lib/src/targets/win/MsiTarget.ts:222— MsiTarget.computeFileDeclaration has cognitive complexity 47 (threshold 15). Drivers by points: if/else 18 (30 pts), ternaries 6 (9 pts), loops 2 (5 pts), boolean chains 3 (nesting depth added 18). Most of this is not in the body itself: 5 of the 47 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 238, 338). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
updateManifestVerifier.compareListedFiles (cognitive 47) packages/app-builder-lib/src/publish/updateManifestVerifier.ts:54— updateManifestVerifier.compareListedFiles has cognitive complexity 47 (threshold 15). Drivers by points: ternaries 9 (17 pts), if/else 7 (16 pts), boolean chains 10, loops 2 (4 pts) (nesting depth added 19). Of this number, 46 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ConfigCodemod.ruleCustomNsis (cognitive 46) packages/electron-builder/src/cli/migrate-schema-programmatic.ts:1223— ConfigCodemod.ruleCustomNsis has cognitive complexity 46 (threshold 15). Drivers by points: if/else 14 (31 pts), boolean chains 7, ternaries 2 (7 pts), loops 1 (nesting depth added 22). Of this number, 44 points are the body's own statements and 2 belong to 2 function items inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
NsisTarget.buildInstaller (cognitive 45) packages/app-builder-lib/src/targets/win/nsis/NsisTarget.ts:339— NsisTarget.buildInstaller has cognitive complexity 45 (threshold 15). Drivers by points: if/else 25 (30 pts), boolean chains 13, ternaries 2 (nesting depth added 5). Of this number, 36 points are the body's own statements and 9 belong to one function literal inside it that branches. 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.
updateManifestSignature.validateSignedManifestShape (cognitive 45) packages/builder-util-runtime/src/updateManifestSignature.ts:166— updateManifestSignature.validateSignedManifestShape has cognitive complexity 45 (threshold 15). Drivers by points: if/else 16 (30 pts), boolean chains 11, loops 3 (4 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
util.exec (cognitive 44) packages/builder-util/src/util.ts:220— util.exec has cognitive complexity 44 (threshold 15). Drivers by points: if/else 15 (35 pts), loops 1 (4 pts), ternaries 2 (3 pts), boolean chains 2 (nesting depth added 24). Of this number, 20 points are the body's own statements and 24 belong to 3 function literals inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
fs.walk (cognitive 43) packages/builder-util/src/fs.ts:85— fs.walk has cognitive complexity 43 (threshold 15). Drivers by points: if/else 15 (30 pts), boolean chains 5, loops 3 (5 pts), ternaries 2 (3 pts) (nesting depth added 18). Of this number, 17 points are the body's own statements and 26 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
archive.compute7zCompressArgs (cognitive 41) packages/app-builder-lib/src/targets/archive.ts:171— archive.compute7zCompressArgs has cognitive complexity 41 (threshold 15). Drivers by points: if/else 18 (30 pts), boolean chains 7, ternaries 2 (4 pts) (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.
PublishManager.getResolvedPublishConfig (cognitive 37) packages/app-builder-lib/src/publish/PublishManager.ts:1135— PublishManager.getResolvedPublishConfig has cognitive complexity 37 (threshold 15). Drivers by points: if/else 19 (26 pts), boolean chains 6, ternaries 3 (5 pts) (nesting depth added 9). Of this number, 34 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DataSplitter.handleData (cognitive 37) packages/electron-updater/src/differentialDownloader/DataSplitter.ts:221— DataSplitter.handleData has cognitive complexity 37 (threshold 15). Drivers by points: if/else 17 (32 pts), ternaries 1 (3 pts), boolean chains 1, loops 1 (nesting depth added 17). 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.
SnapCore24.mapSnapOptionsToSnapcraftYAML (cognitive 36) packages/app-builder-lib/src/targets/linux/snap/core24.ts:181— SnapCore24.mapSnapOptionsToSnapcraftYAML has cognitive complexity 36 (threshold 15). Drivers by points: ternaries 13 (17 pts), boolean chains 11, if/else 7 (8 pts) (nesting depth added 5). 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.
HttpExecutor.handleResponse (cognitive 36) REDACTED:262— HttpExecutor.handleResponse has cognitive complexity 36 (threshold 15). Drivers by points: if/else 11 (13 pts), ternaries 6 (12 pts), boolean chains 10, error handling 1 (nesting depth added 8). Most of this is not in the body itself: 14 of the 36 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 341, 319). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
certInfo.readCertInfo (cognitive 35) packages/app-builder-lib/src/codeSign/certInfo.ts:375— certInfo.readCertInfo has cognitive complexity 35 (threshold 15). Drivers by points: if/else 15 (24 pts), ternaries 2 (4 pts), error handling 3, loops 2 (3 pts), boolean chains 1 (nesting depth added 12). Of this number, 31 points are the body's own statements and 4 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.
buildOutputVerifier.verifyWindowsArtifacts (cognitive 35) packages/app-builder-lib/src/util/buildOutputVerifier.ts:421— buildOutputVerifier.verifyWindowsArtifacts has cognitive complexity 35 (threshold 15). Drivers by points: if/else 8 (17 pts), loops 5 (8 pts), ternaries 3 (8 pts), boolean chains 2 (nesting depth added 17). 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.
ConfigCodemod.rulePlatformAsar (cognitive 35) packages/electron-builder/src/cli/migrate-schema-programmatic.ts:959— ConfigCodemod.rulePlatformAsar has cognitive complexity 35 (threshold 15). Drivers by points: if/else 14 (20 pts), boolean chains 13, ternaries 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
sign-update-manifest.checkListedFiles (cognitive 35) packages/electron-builder/src/cli/sign-update-manifest.ts:395— sign-update-manifest.checkListedFiles has cognitive complexity 35 (threshold 15). Drivers by points: if/else 11 (24 pts), boolean chains 5, ternaries 2 (5 pts), loops 1 (nesting depth added 16). Of this number, 32 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
electronGet.extractZipStreaming (cognitive 34) packages/app-builder-lib/src/util/electronGet.ts:205— electronGet.extractZipStreaming has cognitive complexity 34 (threshold 15). Drivers by points: if/else 12 (28 pts), boolean chains 3, loops 3 (nesting depth added 16). Of this number, 25 points are the body's own statements and 9 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
blockmap.chunkFile (cognitive 34) packages/app-builder-lib/src/targets/blockmap/blockmap.ts:179— blockmap.chunkFile has cognitive complexity 34 (threshold 15). Drivers by points: if/else 13 (20 pts), boolean chains 5, ternaries 4 (5 pts), loops 3 (4 pts) (nesting depth added 9). Most of this is not in the body itself: 3 of the 34 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 291, processByte, enterSegmentAt, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ConfigCodemod.ruleIncludePdb (cognitive 34) packages/electron-builder/src/cli/migrate-schema-programmatic.ts:1583— ConfigCodemod.ruleIncludePdb has cognitive complexity 34 (threshold 15). Drivers by points: if/else 15 (17 pts), boolean chains 9, ternaries 6 (8 pts) (nesting depth added 4). 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.
ConfigCodemod.ruleElectronDownload (cognitive 34) packages/electron-builder/src/cli/migrate-schema-programmatic.ts:1741— ConfigCodemod.ruleElectronDownload has cognitive complexity 34 (threshold 15). Drivers by points: if/else 16 (26 pts), loops 2 (4 pts), boolean chains 3, ternaries 1 (nesting depth added 12). 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.
electronMac.createMacApp (cognitive 33) packages/app-builder-lib/src/electron/mac/electronMac.ts:28— electronMac.createMacApp has cognitive complexity 33 (threshold 15). Drivers by points: if/else 23 (25 pts), boolean chains 7, loops 1 (nesting depth added 2). Of this number, 24 points are the body's own statements and 9 belong to 5 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
NsisTarget.computeFinalScript (cognitive 32) packages/app-builder-lib/src/targets/win/nsis/NsisTarget.ts:1006— NsisTarget.computeFinalScript has cognitive complexity 32 (threshold 15). Drivers by points: loops 5 (16 pts), if/else 7 (12 pts), boolean chains 4 (nesting depth added 16). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
FpmTarget.build (cognitive 32) packages/app-builder-lib/src/targets/linux/FpmTarget.ts:143— FpmTarget.build has cognitive complexity 32 (threshold 15). Drivers by points: if/else 21 (24 pts), ternaries 3 (4 pts), boolean chains 3, loops 1 (nesting depth added 4). 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.
nativeBinaryVerifier.parseNativeBinaryHeader (cognitive 31) packages/app-builder-lib/src/util/nativeBinaryVerifier.ts:49— nativeBinaryVerifier.parseNativeBinaryHeader has cognitive complexity 31 (threshold 15). Drivers by points: if/else 11 (17 pts), boolean chains 6, ternaries 3 (6 pts), loops 1 (2 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
nativeBinaryVerifier.findNativeBinaryMismatches (cognitive 31) packages/app-builder-lib/src/util/nativeBinaryVerifier.ts:342— nativeBinaryVerifier.findNativeBinaryMismatches has cognitive complexity 31 (threshold 15). Drivers by points: if/else 6 (20 pts), boolean chains 5, loops 2 (3 pts), ternaries 1 (3 pts) (nesting depth added 17). Of this number, 30 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
iconConverter.doConvertIcon (cognitive 31) packages/app-builder-lib/src/util/iconConverter.ts:223— iconConverter.doConvertIcon has cognitive complexity 31 (threshold 15). Drivers by points: if/else 14 (27 pts), boolean chains 3, ternaries 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
config.normalizeFiles (cognitive 31) packages/app-builder-lib/src/util/config/config.ts:119— config.normalizeFiles has cognitive complexity 31 (threshold 15). Drivers by points: if/else 11 (25 pts), loops 2 (5 pts), boolean chains 1 (nesting depth added 17). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
ConfigCodemod.ruleWinSign (cognitive 31) packages/electron-builder/src/cli/migrate-schema-programmatic.ts:1281— ConfigCodemod.ruleWinSign has cognitive complexity 31 (threshold 15). Drivers by points: if/else 14 (17 pts), boolean chains 9, loops 1 (3 pts), ternaries 1 (2 pts) (nesting depth added 6). Of this number, 30 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body: 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.
hoist.selfCheck::checkNode (cognitive 30) packages/app-builder-lib/src/node-module-collector/hoist.ts:842— hoist.selfCheck::checkNode has cognitive complexity 30 (threshold 15). Drivers by points: if/else 9 (16 pts), ternaries 3 (10 pts), loops 3, boolean chains 1 (nesting depth added 14). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
WinPackager.signAndEditResources (cognitive 30) packages/app-builder-lib/src/winPackager.ts:238— WinPackager.signAndEditResources has cognitive complexity 30 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 9, ternaries 3 (5 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ConfigCodemod.ruleAsar (cognitive 30) packages/electron-builder/src/cli/migrate-schema-programmatic.ts:841— ConfigCodemod.ruleAsar has cognitive complexity 30 (threshold 15). Drivers by points: if/else 14 (18 pts), boolean chains 8, loops 2 (3 pts), ternaries 1 (nesting depth added 5). Of this number, 23 points are the body's own statements and 7 belong to 3 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
ConfigCodemod.rulePublish (cognitive 30) packages/electron-builder/src/cli/migrate-schema-programmatic.ts:1057— ConfigCodemod.rulePublish has cognitive complexity 30 (threshold 15). Drivers by points: if/else 9 (17 pts), ternaries 3 (10 pts), boolean chains 2, loops 1 (nesting depth added 15). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
migrate-schema.migratePlatformAsar (cognitive 30) REDACTED:1080— migrate-schema.migratePlatformAsar has cognitive complexity 30 (threshold 15). Drivers by points: if/else 11 (18 pts), ternaries 4 (7 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 11). 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.
migrate-schema.migrateElectronDownload (cognitive 30) REDACTED:1184— migrate-schema.migrateElectronDownload has cognitive complexity 30 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 8, ternaries 3 (4 pts), loops 2 (3 pts) (nesting depth added 7). Of this number, 29 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LinuxTargetHelper.computeDesktopEntry (cognitive 29) packages/app-builder-lib/src/targets/linux/LinuxTargetHelper.ts:278— LinuxTargetHelper.computeDesktopEntry has cognitive complexity 29 (threshold 15). Drivers by points: if/else 12 (19 pts), loops 6 (8 pts), boolean chains 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
migrate-schema.migrateCustomNsis (cognitive 29) REDACTED:933— migrate-schema.migrateCustomNsis has cognitive complexity 29 (threshold 15). Drivers by points: if/else 13 (27 pts), boolean chains 1, loops 1 (nesting depth added 14). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
MacPackager.checkForceCodeSigningAtBuildStart (cognitive 28) packages/app-builder-lib/src/macPackager.ts:127— MacPackager.checkForceCodeSigningAtBuildStart has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 6, loops 3 (4 pts), ternaries 1 (2 pts) (nesting depth added 8). Of this number, 27 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
dmgLicense.buildConventionLicenseConfig (cognitive 28) packages/dmg-builder/src/dmgLicense.ts:70— dmgLicense.buildConventionLicenseConfig has cognitive complexity 28 (threshold 15). Drivers by points: if/else 9 (22 pts), loops 2 (3 pts), ternaries 1 (3 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
dmgUtil.customizeDmg (cognitive 28) packages/dmg-builder/src/dmgUtil.ts:166— dmgUtil.customizeDmg has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 11, loops 1, ternaries 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NsisUpdater.doDownloadUpdate (cognitive 28) packages/electron-updater/src/NsisUpdater.ts:221— NsisUpdater.doDownloadUpdate has cognitive complexity 28 (threshold 15). Drivers by points: if/else 11 (15 pts), error handling 2 (7 pts), boolean chains 5, ternaries 1 (nesting depth added 9). Most of this is not in the body itself: 9 of the 28 points are its own statements and the rest belongs to one function literal inside it that branches (line 262). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
awsCredentials.parseAwsIni (cognitive 27) packages/electron-publish/src/s3/awsCredentials.ts:48— awsCredentials.parseAwsIni has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (21 pts), boolean chains 5, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
awsCredentials.planSsoRoleChain (cognitive 27) packages/electron-publish/src/s3/awsCredentials.ts:377— awsCredentials.planSsoRoleChain has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (21 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
model.compare (cognitive 27) website/src/changelog/model.ts:94— model.compare has cognitive complexity 27 (threshold 15). Drivers by points: if/else 6 (15 pts), boolean chains 6, loops 5 (6 pts) (nesting depth added 10). Most of this is not in the body itself: 7 of the 27 points are its own statements and the rest belongs to one function literal inside it that branches (line 102). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
NodeModulesCollector.markExcludedModules (cognitive 26) packages/app-builder-lib/src/node-module-collector/nodeModulesCollector.ts:289— NodeModulesCollector.markExcludedModules has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (19 pts), loops 4 (6 pts), boolean chains 1 (nesting depth added 12). 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.
windowsInstaller.createWindowsInstaller (cognitive 26) REDACTED:72— windowsInstaller.createWindowsInstaller has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 6, ternaries 3 (4 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
hoist.hoistTo (cognitive 25) packages/app-builder-lib/src/node-module-collector/hoist.ts:462— hoist.hoistTo has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 3 (4 pts), ternaries 2 (3 pts), boolean chains 2 (nesting depth added 11). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
PnpmNodeModulesCollector.extractProductionDependencyGraph (cognitive 25) packages/app-builder-lib/src/node-module-collector/pnpmNodeModulesCollector.ts:251— PnpmNodeModulesCollector.extractProductionDependencyGraph has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 5, loops 2, ternaries 2 (nesting depth added 6). Of this number, 21 points are the body's own statements and 4 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.
MacTargetHelper.buildSignOptions (cognitive 25) packages/app-builder-lib/src/targets/mac/MacTargetHelper.ts:293— MacTargetHelper.buildSignOptions has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 6, ternaries 4 (5 pts), error handling 1 (2 pts), loops 1 (2 pts) (nesting depth added 6). Of this number, 14 points are the body's own statements and 11 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PlatformPackager.doPack (cognitive 25) packages/app-builder-lib/src/platformPackager.ts:469— PlatformPackager.doPack has cognitive complexity 25 (threshold 15). Drivers by points: if/else 13 (14 pts), ternaries 4 (8 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 6). Of this number, 22 points are the body's own statements and 3 belong to one function item inside it that branches. 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.
PlatformPackager.copyAppFiles (cognitive 25) packages/app-builder-lib/src/platformPackager.ts:748— PlatformPackager.copyAppFiles has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (15 pts), ternaries 3 (5 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 10). Of this number, 15 points are the body's own statements and 10 belong to 4 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PublishManager.constructor (cognitive 25) packages/app-builder-lib/src/publish/PublishManager.ts:217— PublishManager.constructor has cognitive complexity 25 (threshold 15). Drivers by points: if/else 14 (20 pts), boolean chains 5 (nesting depth added 6). Most of this is not in the body itself: 10 of the 25 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 248, 286, 275). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
buildOutputVerifier.discover (cognitive 25) packages/app-builder-lib/src/util/buildOutputVerifier.ts:172— buildOutputVerifier.discover has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (15 pts), loops 2 (4 pts), boolean chains 3, ternaries 1 (3 pts) (nesting depth added 11). 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.
ModuleManager.downwardSearch (cognitive 24) packages/app-builder-lib/src/node-module-collector/moduleManager.ts:310— ModuleManager.downwardSearch has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (18 pts), loops 2 (3 pts), error handling 1 (2 pts), boolean chains 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
electronGet.downloadArtifactToFile (cognitive 24) packages/app-builder-lib/src/util/electronGet.ts:470— electronGet.downloadArtifactToFile has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 6, ternaries 3 (6 pts), error handling 1 (nesting depth added 5). Most of this is not in the body itself: 8 of the 24 points are its own statements and the rest belongs to one function literal inside it that branches (line 502). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
UninstallerReader.exec (cognitive 24) packages/app-builder-lib/src/targets/win/nsis/nsisUtil.ts:202— UninstallerReader.exec has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (17 pts), boolean chains 5, loops 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SnapCore24.buildSnap (cognitive 24) packages/app-builder-lib/src/targets/linux/snap/core24.ts:59— SnapCore24.buildSnap has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (19 pts), boolean chains 2, loops 1 (2 pts), error handling 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
fileMatcher.getMainFileMatchers (cognitive 24) packages/app-builder-lib/src/fileMatcher.ts:434— fileMatcher.getMainFileMatchers has cognitive complexity 24 (threshold 15). Drivers by points: if/else 13 (15 pts), boolean chains 6, loops 2, ternaries 1 (nesting depth added 2). 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.
ConfigCodemod.ruleMacSigning (cognitive 24) packages/electron-builder/src/cli/migrate-schema-programmatic.ts:1439— ConfigCodemod.ruleMacSigning has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 6, ternaries 2 (3 pts), loops 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
macCodeSign._findIdentity (cognitive 23) packages/app-builder-lib/src/codeSign/mac/macCodeSign.ts:327— macCodeSign._findIdentity has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (15 pts), loops 3 (6 pts), boolean chains 2 (nesting depth added 12). 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.
NsisTarget.configureDefines (cognitive 23) packages/app-builder-lib/src/targets/win/nsis/NsisTarget.ts:693— NsisTarget.configureDefines has cognitive complexity 23 (threshold 15). Drivers by points: if/else 17 (21 pts), boolean chains 2 (nesting depth added 4). 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.
updateInfoBuilder.createUpdateInfoTasks (cognitive 23) packages/app-builder-lib/src/publish/updateInfoBuilder.ts:114— updateInfoBuilder.createUpdateInfoTasks has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (16 pts), boolean chains 4, loops 2 (3 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SnapCoreLegacy.buildSnap (cognitive 23) packages/app-builder-lib/src/targets/linux/snap/coreLegacy.ts:217— SnapCoreLegacy.buildSnap has cognitive complexity 23 (threshold 15). Drivers by points: if/else 12 (15 pts), ternaries 3 (4 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 5). 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.
FileCopier.copy (cognitive 23) packages/builder-util/src/fs.ts:249— FileCopier.copy has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (18 pts), boolean chains 4, ternaries 1 (nesting depth added 9). Of this number, 20 points are the body's own statements and 3 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.
fs.copyOrLinkFile (cognitive 23) packages/builder-util/src/fs.ts:181— fs.copyOrLinkFile has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (19 pts), ternaries 1 (3 pts), boolean chains 1 (nesting depth added 11). Of this number, 13 points are the body's own statements and 10 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.
GitLabProvider.getLatestVersion (cognitive 23) packages/electron-updater/src/providers/GitLabProvider.ts:81— GitLabProvider.getLatestVersion has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 6, error handling 4, ternaries 1 (nesting depth added 2). Of this number, 15 points are the body's own statements and 8 belong to one function item inside it that branches. 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.
AppUpdater.executeDownload (cognitive 23) packages/electron-updater/src/AppUpdater.ts:1363— AppUpdater.executeDownload has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (12 pts), boolean chains 4, ternaries 4, error handling 2 (3 pts) (nesting depth added 2). Of this number, 13 points are the body's own statements and 10 belong to 3 function items inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
macroExpander.expandMacro (cognitive 22) packages/app-builder-lib/src/util/macroExpander.ts:5— macroExpander.expandMacro has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (18 pts), ternaries 1 (2 pts), boolean chains 1, match/switch 1 (nesting depth added 10). Most of this is not in the body itself: 1 of the 22 points is its own statement and the rest belongs to one function literal inside it that branches (line 18). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
index.findWorkspaceRoot (cognitive 22) packages/app-builder-lib/src/node-module-collector/index.ts:71— index.findWorkspaceRoot has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (12 pts), ternaries 2 (5 pts), boolean chains 2, loops 1 (2 pts), match/switch 1 (nesting depth added 8). Most of this is not in the body itself: 4 of the 22 points are its own statements and the rest belongs to one function literal inside it that branches (line 106). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
MacPackager.sign (cognitive 22) packages/app-builder-lib/src/macPackager.ts:674— MacPackager.sign has cognitive complexity 22 (threshold 15). Drivers by points: if/else 13 (17 pts), boolean chains 3, ternaries 2 (nesting depth added 4). 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.
manifestUploadCheck.warnAboutUpdateFilesBeforeUpload (cognitive 22) packages/app-builder-lib/src/publish/manifestUploadCheck.ts:118— manifestUploadCheck.warnAboutUpdateFilesBeforeUpload has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 4 (5 pts), error handling 1 (2 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
pathContainment.resolvePhysicalPath (cognitive 22) packages/builder-util/src/pathContainment.ts:37— pathContainment.resolvePhysicalPath has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (16 pts), error handling 2 (3 pts), boolean chains 1, loops 1, ternaries 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AsarPackager.processFileSets (cognitive 21) packages/app-builder-lib/src/asar/asarUtil.ts:187— AsarPackager.processFileSets has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (10 pts), loops 5 (7 pts), boolean chains 3, ternaries 1 (nesting depth added 6). Of this number, 13 points are the body's own statements and 8 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
electronGet.isLinkTargetInside (cognitive 21) packages/app-builder-lib/src/util/electronGet.ts:179— electronGet.isLinkTargetInside has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (13 pts), boolean chains 3, error handling 1 (3 pts), loops 1, ternaries 1 (nesting depth added 10). Of this number, 20 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
packageMetadata.findAppElectronUpdater (cognitive 21) packages/app-builder-lib/src/util/packageMetadata.ts:152— packageMetadata.findAppElectronUpdater has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (12 pts), ternaries 3 (6 pts), loops 2, error handling 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
certInfo.rc2CbcDecrypt (cognitive 21) packages/app-builder-lib/src/codeSign/certInfo.ts:132— certInfo.rc2CbcDecrypt has cognitive complexity 21 (threshold 15). Drivers by points: loops 8 (14 pts), if/else 4 (5 pts), boolean chains 2 (nesting depth added 7). Of this number, 17 points are the body's own statements and 4 belong to 2 function items inside it that branch. To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
certInfo.pkcs12PbeDeriveKey (cognitive 21) packages/app-builder-lib/src/codeSign/certInfo.ts:234— certInfo.pkcs12PbeDeriveKey has cognitive complexity 21 (threshold 15). Drivers by points: loops 7 (12 pts), if/else 3 (6 pts), ternaries 2, boolean chains 1 (nesting depth added 8). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
WinPackager.createTargets (cognitive 21) packages/app-builder-lib/src/winPackager.ts:68— WinPackager.createTargets has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (8 pts), error handling 1 (4 pts), match/switch 1 (3 pts), ternaries 1 (3 pts), boolean chains 2, loops 1 (nesting depth added 9). Most of this is not in the body itself: 8 of the 21 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 96, getCopyElevateHelper, getHelper, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
snapcraftBuilder.validateSnapcraftConfig (cognitive 21) REDACTED:59— snapcraftBuilder.validateSnapcraftConfig has cognitive complexity 21 (threshold 15). Drivers by points: if/else 14 (18 pts), boolean chains 3 (nesting depth added 4). Of this number, 18 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
arch.getArtifactArchName (cognitive 21) packages/builder-util/src/arch.ts:57— arch.getArtifactArchName has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 6 (nesting depth added 4). 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.
executables.validateExecutablesConfig (cognitive 21) packages/builder-util/src/executables.ts:212— executables.validateExecutablesConfig has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (8 pts), ternaries 2 (6 pts), boolean chains 4, loops 2 (3 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DmgTarget.signDmg (cognitive 21) packages/dmg-builder/src/dmg.ts:124— DmgTarget.signDmg has cognitive complexity 21 (threshold 15). Drivers by points: if/else 13 (20 pts), ternaries 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
migrate-schema.migrateIncludePdb (cognitive 21) REDACTED:849— migrate-schema.migrateIncludePdb has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (12 pts), ternaries 3 (6 pts), boolean chains 3 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
migrate-schema.migrateMacSigning (cognitive 21) REDACTED:986— migrate-schema.migrateMacSigning has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 5, ternaries 2 (3 pts), loops 2 (nesting depth added 4). 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.
downloadPlanBuilder.computeOperations (cognitive 21) packages/electron-updater/src/differentialDownloader/downloadPlanBuilder.ts:22— downloadPlanBuilder.computeOperations has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 3, ternaries 1 (2 pts), loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BaseUpdater.installPendingUpdate (cognitive 21) REDACTED:479— BaseUpdater.installPendingUpdate has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (13 pts), boolean chains 5, ternaries 1 (2 pts), error handling 1 (nesting depth added 2). 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.
differentialUpdateInfoBuilder.locateArchiveHeaderRegions (cognitive 20) packages/app-builder-lib/src/targets/differentialUpdateInfoBuilder.ts:137— differentialUpdateInfoBuilder.locateArchiveHeaderRegions has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (15 pts), boolean chains 2, ternaries 1 (2 pts), loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
config.getConfig (cognitive 20) packages/app-builder-lib/src/util/config/config.ts:51— config.getConfig has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (8 pts), boolean chains 6, error handling 1 (3 pts), ternaries 2 (3 pts) (nesting depth added 4). Of this number, 18 points are the body's own statements and 2 belong to one function literal inside it that branches. 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.
PublishManager.artifactCreatedWithoutExplicitPublishConfig (cognitive 20) packages/app-builder-lib/src/publish/PublishManager.ts:372— PublishManager.artifactCreatedWithoutExplicitPublishConfig has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 3, loops 1 (2 pts), ternaries 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
appimage.getAppImageTools (cognitive 20) packages/app-builder-lib/src/toolsets/appimage.ts:26— appimage.getAppImageTools has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 11 (17 pts), if/else 2, boolean chains 1 (nesting depth added 6). Of this number, 11 points are the body's own statements and 9 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
fileMatcher.getNodeModuleFileMatcher::addPatterns (cognitive 20) packages/app-builder-lib/src/fileMatcher.ts:546— fileMatcher.getNodeModuleFileMatcher::addPatterns has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 2 (5 pts), boolean chains 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
verify.verify (cognitive 20) packages/electron-builder/src/cli/verify.ts:47— verify.verify has cognitive complexity 20 (threshold 15). Drivers by points: if/else 12 (15 pts), boolean chains 4, loops 1 (nesting depth added 3). 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.
index.Changelog (cognitive 20) REDACTED:154— index.Changelog has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 11, ternaries 6, if/else 3. Of this number, 18 points are the body's own statements and 2 belong to 3 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
electronGet.downloadAndExtract (cognitive 19) packages/app-builder-lib/src/util/electronGet.ts:600— electronGet.downloadAndExtract has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (18 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
verbatimRange.findPreparedVerbatimRange (cognitive 19) packages/app-builder-lib/src/targets/blockmap/verbatimRange.ts:98— verbatimRange.findPreparedVerbatimRange has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 2 (3 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
differentialUpdateInfoBuilder.asarContentBoundaries (cognitive 19) packages/app-builder-lib/src/targets/differentialUpdateInfoBuilder.ts:217— differentialUpdateInfoBuilder.asarContentBoundaries has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (10 pts), error handling 2 (4 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 9). Most of this is not in the body itself: 7 of the 19 points are its own statements and the rest belongs to one function item inside it that branches (collect). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
iconConverter.buildSourceCandidates (cognitive 19) packages/app-builder-lib/src/util/iconConverter.ts:135— iconConverter.buildSourceCandidates has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (17 pts), loops 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MsixTarget.writeManifest (cognitive 19) packages/app-builder-lib/src/targets/win/MsixTarget.ts:152— MsixTarget.writeManifest has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 8, ternaries 3 (7 pts), if/else 2 (3 pts), match/switch 1 (nesting depth added 5). Most of this is not in the body itself: 3 of the 19 points are its own statements and the rest belongs to one function literal inside it that branches (line 166). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
SigntoolSignManager.computeWindowsSignArgs (cognitive 19) REDACTED:595— SigntoolSignManager.computeWindowsSignArgs has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (10 pts), boolean chains 5, ternaries 2 (4 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LinuxTargetHelper.getSnapCore (cognitive 19) packages/app-builder-lib/src/targets/linux/LinuxTargetHelper.ts:113— LinuxTargetHelper.getSnapCore has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (15 pts), boolean chains 2, match/switch 1 (2 pts) (nesting depth added 11). 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.
SquirrelWindowsTarget.computeEffectiveDistOptions (cognitive 19) packages/electron-builder-squirrel-windows/src/SquirrelWindowsTarget.ts:288— SquirrelWindowsTarget.computeEffectiveDistOptions has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 4, ternaries 3 (nesting depth added 3). 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.
ConfigCodemod.locateConfigObject (cognitive 19) packages/electron-builder/src/cli/migrate-schema-programmatic.ts:145— ConfigCodemod.locateConfigObject has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 2, loops 2 (nesting depth added 7). Of this number, 18 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BlockMapV3Fetcher.fetchRanges (cognitive 19) packages/electron-updater/src/differentialDownloader/blockMapV3Fetcher.ts:319— BlockMapV3Fetcher.fetchRanges has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 3 (5 pts), boolean chains 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BlockMapV3Fetcher.doRequest (cognitive 19) packages/electron-updater/src/differentialDownloader/blockMapV3Fetcher.ts:387— BlockMapV3Fetcher.doRequest has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (7 pts), ternaries 5 (7 pts), boolean chains 3, error handling 1 (2 pts) (nesting depth added 4). None of this is in the body itself: all 19 points belong to 4 function literals inside it that branch (lines 402, 447, 389, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
archCompatibility.collectSingleArchPackageNames (cognitive 18) packages/app-builder-lib/src/util/archCompatibility.ts:97— archCompatibility.collectSingleArchPackageNames has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (9 pts), error handling 2 (4 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NodeModulesCollector._getNodeModules (cognitive 18) packages/app-builder-lib/src/node-module-collector/nodeModulesCollector.ts:371— NodeModulesCollector._getNodeModules has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (14 pts), ternaries 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
cacheState.computeCacheMetadata (cognitive 18) packages/app-builder-lib/src/util/cacheState.ts:80— cacheState.computeCacheMetadata has cognitive complexity 18 (threshold 15). Drivers by points: if/else 3 (8 pts), error handling 2 (7 pts), loops 2 (3 pts) (nesting depth added 11). 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.
electronGet.extractArchive (cognitive 18) packages/app-builder-lib/src/util/electronGet.ts:288— electronGet.extractArchive has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 2, error handling 1 (2 pts), loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ArchiveTarget.build (cognitive 18) packages/app-builder-lib/src/targets/ArchiveTarget.ts:27— ArchiveTarget.build has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 1, ternaries 1 (nesting depth added 6). Most of this is not in the body itself: 2 of the 18 points are its own statements and the rest belongs to one function literal inside it that branches (line 42). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
AppXTarget.writeManifest (cognitive 18) packages/app-builder-lib/src/targets/win/AppxTarget.ts:54— AppXTarget.writeManifest has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 8, ternaries 3 (6 pts), if/else 2 (3 pts), match/switch 1 (nesting depth added 4). Most of this is not in the body itself: 4 of the 18 points are its own statements and the rest belongs to one function literal inside it that branches (line 68). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
snapcraftBuilder.executeSnapcraftBuild (cognitive 18) REDACTED:391— snapcraftBuilder.executeSnapcraftBuild has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (11 pts), ternaries 1 (3 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ConfigCodemod.run (cognitive 18) packages/electron-builder/src/cli/migrate-schema-programmatic.ts:360— ConfigCodemod.run has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (10 pts), loops 5, ternaries 1 (2 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GenericProvider.getLatestVersion (cognitive 18) packages/electron-updater/src/providers/GenericProvider.ts:28— GenericProvider.getLatestVersion has cognitive complexity 18 (threshold 15). Drivers by points: if/else 3 (8 pts), error handling 2 (7 pts), boolean chains 2, loops 1 (nesting depth added 10). Of this number, 13 points are the body's own statements and 5 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.
multipleRangeDownloader.doExecuteTasks (cognitive 18) packages/electron-updater/src/differentialDownloader/multipleRangeDownloader.ts:81— multipleRangeDownloader.doExecuteTasks has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 1, loops 1, ternaries 1 (nesting depth added 5). Most of this is not in the body itself: 4 of the 18 points are its own statements and the rest belongs to 6 function items inside it that branch (onResponse, w, a function literal at line 115, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
MacPackager.packMasTargets (cognitive 17) packages/app-builder-lib/src/macPackager.ts:522— MacPackager.packMasTargets has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 2, ternaries 1 (2 pts), loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MacPackager.applyCommonInfo (cognitive 17) packages/app-builder-lib/src/macPackager.ts:808— MacPackager.applyCommonInfo has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 6, loops 1 (nesting depth added 2). Of this number, 16 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body: 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.
SigntoolBaseSignManager.addCertificateArgs (cognitive 17) REDACTED:445— SigntoolBaseSignManager.addCertificateArgs has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 3, ternaries 1 (3 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PublishManager.createAppUpdateConfiguration (cognitive 17) packages/app-builder-lib/src/publish/PublishManager.ts:617— PublishManager.createAppUpdateConfiguration has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 5 (8 pts), if/else 6, boolean chains 3 (nesting depth added 3). 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.
snapPlugs.resolveCore24Plugs (cognitive 17) packages/app-builder-lib/src/targets/linux/snap/snapPlugs.ts:126— snapPlugs.resolveCore24Plugs has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (8 pts), loops 3 (4 pts), boolean chains 3, ternaries 2 (nesting depth added 4). 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.
index.build (cognitive 17) packages/app-builder-lib/src/index.ts:124— index.build has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (10 pts), loops 2 (5 pts), boolean chains 2 (nesting depth added 7). None of this is in the body itself: all 17 points belong to 2 function literals inside it that branch (lines 137, 177). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
buildOutputVerifier.verifyBuildOutput (cognitive 17) packages/app-builder-lib/src/util/buildOutputVerifier.ts:89— buildOutputVerifier.verifyBuildOutput has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (9 pts), loops 4 (5 pts), error handling 1 (2 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
buildOutputVerifier.verifyManifestSignature (cognitive 17) packages/app-builder-lib/src/util/buildOutputVerifier.ts:266— buildOutputVerifier.verifyManifestSignature has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (10 pts), ternaries 3 (5 pts), boolean chains 1, loops 1 (nesting depth added 5). Of this number, 14 points are the body's own statements and 3 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.
migrate-schema.migrateSchema (cognitive 17) REDACTED:1508— migrate-schema.migrateSchema has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (11 pts), loops 3, boolean chains 2, ternaries 1 (nesting depth added 2). 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.
R2Publisher.checkAndResolveOptions (cognitive 17) packages/electron-publish/src/s3/r2Publisher.ts:22— R2Publisher.checkAndResolveOptions has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 3, error handling 1 (2 pts) (nesting depth added 3). 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.
BlockMapV3Fetcher.fetch (cognitive 17) packages/electron-updater/src/differentialDownloader/blockMapV3Fetcher.ts:172— BlockMapV3Fetcher.fetch has cognitive complexity 17 (threshold 15). Drivers by points: if/else 13 (16 pts), boolean chains 1 (nesting depth added 3). Of this number, 15 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
remark-fix-anchors.remarkFixAnchors.<returned closure> (cognitive 17) website/src/remark/remark-fix-anchors.mjs:15— remark-fix-anchors.remarkFixAnchors.<returned closure> has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 2 (nesting depth added 4). None of this is in the body itself: all 17 points belong to 2 function literals inside it that branch (lines 32, 20). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
PkgTarget.buildComponentPackage (cognitive 16) packages/app-builder-lib/src/targets/mac/pkg.ts:233— PkgTarget.buildComponentPackage has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 2 (nesting depth added 5). Of this number, 13 points are the body's own statements and 3 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.
fileOptions.warnUnusedRemovals (cognitive 16) packages/app-builder-lib/src/util/config/fileOptions.ts:45— fileOptions.warnUnusedRemovals has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 5 (12 pts), boolean chains 3, loops 1 (nesting depth added 7). Of this number, 14 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MacTargetHelper.getNotarizeOptions (cognitive 16) packages/app-builder-lib/src/targets/mac/MacTargetHelper.ts:618— MacTargetHelper.getNotarizeOptions has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 3 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
wine.getWineToolset (cognitive 16) packages/app-builder-lib/src/toolsets/wine.ts:27— wine.getWineToolset has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6, boolean chains 5, ternaries 3 (5 pts) (nesting depth added 2). 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.
NsisTarget.executeMakensis (cognitive 16) packages/app-builder-lib/src/targets/win/nsis/NsisTarget.ts:829— NsisTarget.executeMakensis has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (9 pts), loops 3 (5 pts), boolean chains 1, ternaries 1 (nesting depth added 4). 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.
electronVersion.computeElectronVersion (cognitive 16) packages/app-builder-lib/src/electron/electronVersion.ts:44— electronVersion.computeElectronVersion has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (7 pts), ternaries 3 (6 pts), error handling 1 (2 pts), loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
fileMatcher.getFileMatchers (cognitive 16) packages/app-builder-lib/src/fileMatcher.ts:649— fileMatcher.getFileMatchers has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (11 pts), ternaries 2 (4 pts), loops 1 (nesting depth added 4). Most of this is not in the body itself: 5 of the 16 points are its own statements and the rest belongs to one function item inside it that branches (addPatterns). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
updateManifestSignature.splitPemBlocks (cognitive 16) packages/builder-util-runtime/src/updateManifestSignature.ts:277— updateManifestSignature.splitPemBlocks has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
HttpExecutor.doDownload (cognitive 16) REDACTED:441— HttpExecutor.doDownload has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (7 pts), ternaries 2 (4 pts), boolean chains 3, error handling 1 (2 pts) (nesting depth added 5). None of this is in the body itself: all 16 points belong to one function literal inside it that branches (line 445). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
httpExecutor.configurePipes (cognitive 16) REDACTED:811— httpExecutor.configurePipes has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (12 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 3). Of this number, 12 points are the body's own statements and 4 belong to 2 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
ConfigCodemod.publishEntries (cognitive 16) packages/electron-builder/src/cli/migrate-schema-programmatic.ts:635— ConfigCodemod.publishEntries has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 7, ternaries 3 (5 pts), if/else 2 (3 pts), loops 1 (nesting depth added 3). Of this number, 13 points are the body's own statements and 3 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.
ConfigCodemod.ruleSnap (cognitive 16) packages/electron-builder/src/cli/migrate-schema-programmatic.ts:1109— ConfigCodemod.ruleSnap has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 3, ternaries 2 (nesting depth added 2). 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.
ConfigCodemod.buildWinAzureSign (cognitive 16) packages/electron-builder/src/cli/migrate-schema-programmatic.ts:1390— ConfigCodemod.buildWinAzureSign has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (12 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
blockMapV3Fetcher.verifyBlockMapV3 (cognitive 16) packages/electron-updater/src/differentialDownloader/blockMapV3Fetcher.ts:637— blockMapV3Fetcher.verifyBlockMapV3 has cognitive complexity 16 (threshold 15). Drivers by points: if/else 13 (14 pts), loops 2 (nesting depth added 1). Of this number, 8 points are the body's own statements and 8 belong to 2 function literals inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AppUpdater.verifyManifestSignature (cognitive 16) packages/electron-updater/src/AppUpdater.ts:972— AppUpdater.verifyManifestSignature has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (7 pts), ternaries 3 (6 pts), error handling 1 (2 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AppUpdater.getBlockMapEnd (cognitive 16) packages/electron-updater/src/AppUpdater.ts:1764— AppUpdater.getBlockMapEnd has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (9 pts), boolean chains 4, loops 2 (3 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Duplication concentrated across 12 sibling directories (11 clone groups) packages/builder-util-runtime/src/ProgressCallbackTransform.ts:17— 11 duplicated blocks under packages/ have copies in at least two of the sibling directories app-builder-lib, builder-util, builder-util-runtime, dmg-builder, electron-builder, electron-builder-squirrel-windows (+6 more sibling(s) not listed) — 5 of them are reported below, and 6 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 11 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 11 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 11 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplicated block (54 lines × 2 locations) packages/app-builder-lib/src/targets/win/AppxTarget.ts:63— packages/app-builder-lib/src/targets/win/AppxTarget.ts:63 · packages/app-builder-lib/src/targets/win/MsixTarget.ts:161 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
R10 · Code Duplication· Duplicated block with local edits (46 matched lines × 2 locations) · ×1
Duplicated block with local edits (46 matched lines × 2 locations) packages/builder-util-runtime/src/ProgressCallbackTransform.ts:17— packages/builder-util-runtime/src/ProgressCallbackTransform.ts:17 · packages/electron-updater/src/differentialDownloader/ProgressDifferentialDownloadCallbackTransform.ts:30 — the two spans are one implementation copied and then locally edited — 278 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (29 matched lines × 2 locations) · ×1
Duplicated block with local edits (29 matched lines × 2 locations) packages/app-builder-lib/src/codeSign/win/authenticodeSignature.ts:210— packages/app-builder-lib/src/codeSign/win/authenticodeSignature.ts:210 · packages/electron-updater/src/windowsExecutableVersion.ts:17 — the two spans are one implementation copied and then locally edited — 218 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (22 lines × 2 locations) packages/app-builder-lib/src/targets/linux/appimage/AppImageTarget.ts:104— packages/app-builder-lib/src/targets/linux/appimage/AppImageTarget.ts:104 · packages/app-builder-lib/src/targets/linux/appimage/AppImageTarget.ts:137 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (18 matched lines × 2 locations) · ×1
Duplicated block with local edits (18 matched lines × 2 locations) packages/app-builder-lib/src/targets/linux/snap/core24.ts:477— packages/app-builder-lib/src/targets/linux/snap/core24.ts:477 · packages/app-builder-lib/src/targets/linux/snap/snapPlugs.ts:200 — the two spans are one implementation copied and then locally edited — 120 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (15 lines × 3 locations) packages/electron-updater/src/DebUpdater.ts:16— packages/electron-updater/src/DebUpdater.ts:16 · packages/electron-updater/src/PacmanUpdater.ts:14 · packages/electron-updater/src/RpmUpdater.ts:16 — the 3 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.
Duplicated block (15 lines × 2 locations) packages/electron-updater/src/providers/BitbucketProvider.ts:20— packages/electron-updater/src/providers/BitbucketProvider.ts:20 · packages/electron-updater/src/providers/KeygenProvider.ts:21 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (13 matched lines × 2 locations) · ×1
Duplicated block with local edits (13 matched lines × 2 locations) packages/electron-publish/src/gitlabPublisher.ts:237— packages/electron-publish/src/gitlabPublisher.ts:237 · packages/electron-publish/src/gitlabPublisher.ts:262 — the two spans are one implementation copied and then locally edited — 66 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (12 lines × 2 locations) packages/app-builder-lib/src/node-module-collector/hoist.ts:898— packages/app-builder-lib/src/node-module-collector/hoist.ts:898 · packages/app-builder-lib/src/node-module-collector/hoist.ts:924 — all 2 copies are in the same file, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases.
R10 · Code Duplication· Duplicated block with local edits (11 matched lines × 2 locations) · ×1
Duplicated block with local edits (11 matched lines × 2 locations) packages/electron-publish/src/bitbucketPublisher.ts:66— packages/electron-publish/src/bitbucketPublisher.ts:66 · packages/electron-publish/src/keygenPublisher.ts:256 — the two spans are one implementation copied and then locally edited — 82 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (10 lines × 4 locations) packages/electron-forge-maker-appimage/main.js:3— packages/electron-forge-maker-appimage/main.js:3 · packages/electron-forge-maker-nsis-web/main.js:3 · packages/electron-forge-maker-nsis/main.js:3 · packages/electron-forge-maker-snap/main.js:3 — the 4 copies are spread across 4 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (10 lines × 3 locations) packages/electron-updater/src/providers/GenericProvider.ts:17— packages/electron-updater/src/providers/GenericProvider.ts:17 · packages/electron-updater/src/providers/GitHubProvider.ts:50 · packages/electron-updater/src/providers/GitLabProvider.ts:70 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (9 matched lines × 2 locations) · ×1
Duplicated block with local edits (9 matched lines × 2 locations) packages/app-builder-lib/src/node-module-collector/npmNodeModulesCollector.ts:34— packages/app-builder-lib/src/node-module-collector/npmNodeModulesCollector.ts:34 · packages/app-builder-lib/src/node-module-collector/traversalNodeModulesCollector.ts:28 — the two spans are one implementation copied and then locally edited — 54 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (8 lines × 4 locations) packages/electron-updater/src/AppImageUpdater.ts:37— packages/electron-updater/src/AppImageUpdater.ts:37 · packages/electron-updater/src/DebUpdater.ts:16 · packages/electron-updater/src/PacmanUpdater.ts:14 · packages/electron-updater/src/RpmUpdater.ts:16 — the 4 copies are spread across 4 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (7 lines × 5 locations) packages/app-builder-lib/src/node-module-collector/moduleManager.ts:225— packages/app-builder-lib/src/node-module-collector/moduleManager.ts:225 · packages/app-builder-lib/src/node-module-collector/moduleManager.ts:286 · packages/app-builder-lib/src/node-module-collector/moduleManager.ts:372 · packages/app-builder-lib/src/node-module-collector/moduleManager.ts:381 · +1 more site(s) not listed — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (7 lines × 2 locations) packages/app-builder-lib/src/publish/PublishManager.ts:771— packages/app-builder-lib/src/publish/PublishManager.ts:771 · packages/builder-util/src/updateManifestSigner.ts:184 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Complex function migrateConfig (cyclomatic 110, cognitive 180) REDACTED:279— migrateConfig has cyclomatic complexity 110 and cognitive complexity 180; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 47, cognitive 94) packages/app-builder-lib/src/node-module-collector/hoist.ts:536— (anonymous) has cyclomatic complexity 47 and cognitive complexity 94; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function normalizeOptions (cyclomatic 37, cognitive 72) packages/electron-builder/src/builder.ts:33— normalizeOptions has cyclomatic complexity 37 and cognitive complexity 72; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function archive (cyclomatic 34, cognitive 61) packages/app-builder-lib/src/targets/archive.ts:259— archive has cyclomatic complexity 34 and cognitive complexity 61; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function compareListedFiles (cyclomatic 34, cognitive 60) packages/app-builder-lib/src/publish/updateManifestVerifier.ts:54— compareListedFiles has cyclomatic complexity 34 and cognitive complexity 60; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function ruleIncludePdb (cyclomatic 34, cognitive 35) packages/electron-builder/src/cli/migrate-schema-programmatic.ts:1583— ruleIncludePdb has cyclomatic complexity 34 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 34, cognitive 15) packages/app-builder-lib/src/targets/win/MsixTarget.ts:166— (anonymous) has cyclomatic complexity 34 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function validateSignedManifestShape (cyclomatic 33, cognitive 45) packages/builder-util-runtime/src/updateManifestSignature.ts:166— validateSignedManifestShape has cyclomatic complexity 33 and cognitive complexity 45; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function customizeDmg (cyclomatic 33, cognitive 38) packages/dmg-builder/src/dmgUtil.ts:166— customizeDmg has cyclomatic complexity 33 and cognitive complexity 38; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function rulePlatformAsar (cyclomatic 32, cognitive 35) packages/electron-builder/src/cli/migrate-schema-programmatic.ts:959— rulePlatformAsar has cyclomatic complexity 32 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 32, cognitive 13) packages/app-builder-lib/src/targets/win/AppxTarget.ts:68— (anonymous) has cyclomatic complexity 32 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function buildInstaller (cyclomatic 31, cognitive 39) packages/app-builder-lib/src/targets/win/nsis/NsisTarget.ts:339— buildInstaller has cyclomatic complexity 31 and cognitive complexity 39; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity· Complex function main (cyclomatic 31, cognitive 36) · ×1
Complex function main (cyclomatic 31, cognitive 36) scripts/aggregate-changesets.mjs:524— main has cyclomatic complexity 31 and cognitive complexity 36; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function compute7zCompressArgs (cyclomatic 30, cognitive 44) packages/app-builder-lib/src/targets/archive.ts:171— compute7zCompressArgs has cyclomatic complexity 30 and cognitive complexity 44; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function isInsecureFeedAllowed (cyclomatic 30, cognitive 28) REDACTED:44— isInsecureFeedAllowed has cyclomatic complexity 30 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function build (cyclomatic 29, cognitive 35) packages/app-builder-lib/src/targets/linux/FpmTarget.ts:143— build has cyclomatic complexity 29 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function check (cyclomatic 29, cognitive 34) scripts/checkDeps.js:23— check has cyclomatic complexity 29 and cognitive complexity 34; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 29, cognitive 31) packages/app-builder-lib/src/util/NodeModuleCopyHelper.ts:88— (anonymous) has cyclomatic complexity 29 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function hoistNodeDependencies (cyclomatic 28, cognitive 54) packages/app-builder-lib/src/node-module-collector/hoist.ts:687— hoistNodeDependencies has cyclomatic complexity 28 and cognitive complexity 54; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function differentialDownloadInstaller (cyclomatic 28, cognitive 49) packages/electron-updater/src/AppUpdater.ts:1526— differentialDownloadInstaller has cyclomatic complexity 28 and cognitive complexity 49; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function getResolvedPublishConfig (cyclomatic 28, cognitive 38) packages/app-builder-lib/src/publish/PublishManager.ts:1135— getResolvedPublishConfig has cyclomatic complexity 28 and cognitive complexity 38; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function parseDn (cyclomatic 27, cognitive 55) packages/builder-util-runtime/src/rfc2253Parser.ts:45— parseDn has cyclomatic complexity 27 and cognitive complexity 55; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function computeDesktopEntry (cyclomatic 27, cognitive 35) packages/app-builder-lib/src/targets/linux/LinuxTargetHelper.ts:278— computeDesktopEntry has cyclomatic complexity 27 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 26, cognitive 45) packages/app-builder-lib/src/targets/win/MsiTarget.ts:238— (anonymous) has cyclomatic complexity 26 and cognitive complexity 45; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function ruleWinSign (cyclomatic 26, cognitive 33) packages/electron-builder/src/cli/migrate-schema-programmatic.ts:1281— ruleWinSign has cyclomatic complexity 26 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function migrateElectronDownload (cyclomatic 26, cognitive 30) REDACTED:1184— migrateElectronDownload has cyclomatic complexity 26 and cognitive complexity 30; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function parseNativeBinaryHeader (cyclomatic 25, cognitive 31) packages/app-builder-lib/src/util/nativeBinaryVerifier.ts:49— parseNativeBinaryHeader has cyclomatic complexity 25 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function createMacApp (cyclomatic 24, cognitive 23) packages/app-builder-lib/src/electron/mac/electronMac.ts:28— createMacApp has cyclomatic complexity 24 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function ruleElectronDownload (cyclomatic 22, cognitive 34) packages/electron-builder/src/cli/migrate-schema-programmatic.ts:1741— ruleElectronDownload has cyclomatic complexity 22 and cognitive complexity 34; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function getMainFileMatchers (cyclomatic 22, cognitive 24) packages/app-builder-lib/src/fileMatcher.ts:434— getMainFileMatchers has cyclomatic complexity 22 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function ruleMacSigning (cyclomatic 22, cognitive 24) packages/electron-builder/src/cli/migrate-schema-programmatic.ts:1439— ruleMacSigning has cyclomatic complexity 22 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function installPendingUpdate (cyclomatic 22, cognitive 23) REDACTED:479— installPendingUpdate has cyclomatic complexity 22 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function getArtifactArchName (cyclomatic 22, cognitive 21) packages/builder-util/src/arch.ts:57— getArtifactArchName has cyclomatic complexity 22 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function ruleCustomNsis (cyclomatic 21, cognitive 44) packages/electron-builder/src/cli/migrate-schema-programmatic.ts:1223— ruleCustomNsis has cyclomatic complexity 21 and cognitive complexity 44; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function readCertInfo (cyclomatic 21, cognitive 32) packages/app-builder-lib/src/codeSign/certInfo.ts:375— readCertInfo has cyclomatic complexity 21 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function createWindowsInstaller (cyclomatic 21, cognitive 26) REDACTED:72— createWindowsInstaller has cyclomatic complexity 21 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function doPack (cyclomatic 21, cognitive 22) packages/app-builder-lib/src/platformPackager.ts:469— doPack has cyclomatic complexity 21 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function doConvertIcon (cyclomatic 20, cognitive 31) packages/app-builder-lib/src/util/iconConverter.ts:223— doConvertIcon has cyclomatic complexity 20 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function migratePlatformAsar (cyclomatic 20, cognitive 30) REDACTED:1080— migratePlatformAsar has cyclomatic complexity 20 and cognitive complexity 30; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function packAndCheck (cyclomatic 20, cognitive 30) test/src/helpers/packTester.ts:669— packAndCheck has cyclomatic complexity 20 and cognitive complexity 30; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files· packages/electron-builder/src/cli/migrate-schema-programmatic.ts · ×1
packages/electron-builder/src/cli/migrate-schema-programmatic.ts: 2012 lines of code packages/electron-builder/src/cli/migrate-schema-programmatic.ts:1— packages/electron-builder/src/cli/migrate-schema-programmatic.ts has 2012 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/electron-updater/src/AppUpdater.ts · ×1
packages/electron-updater/src/AppUpdater.ts: 1745 lines of code packages/electron-updater/src/AppUpdater.ts:1— packages/electron-updater/src/AppUpdater.ts has 1745 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
REDACTED: 1521 lines of code REDACTED:1— REDACTED has 1521 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/app-builder-lib/src/configuration.ts · ×1
packages/app-builder-lib/src/configuration.ts: 1180 lines of code packages/app-builder-lib/src/configuration.ts:1— packages/app-builder-lib/src/configuration.ts has 1180 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/app-builder-lib/src/publish/PublishManager.ts · ×1
packages/app-builder-lib/src/publish/PublishManager.ts: 1121 lines of code packages/app-builder-lib/src/publish/PublishManager.ts:1— packages/app-builder-lib/src/publish/PublishManager.ts has 1121 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/app-builder-lib/src/platformPackager.ts · ×1
packages/app-builder-lib/src/platformPackager.ts: 1070 lines of code packages/app-builder-lib/src/platformPackager.ts:1— packages/app-builder-lib/src/platformPackager.ts has 1070 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/app-builder-lib/src/node-module-collector/hoist.ts · ×1
packages/app-builder-lib/src/node-module-collector/hoist.ts: 1002 lines of code packages/app-builder-lib/src/node-module-collector/hoist.ts:1— packages/app-builder-lib/src/node-module-collector/hoist.ts has 1002 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/app-builder-lib/src/targets/win/nsis/NsisTarget.ts · ×1
packages/app-builder-lib/src/targets/win/nsis/NsisTarget.ts: 971 lines of code packages/app-builder-lib/src/targets/win/nsis/NsisTarget.ts:1— packages/app-builder-lib/src/targets/win/nsis/NsisTarget.ts has 971 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/app-builder-lib/src/util/electronGet.ts · ×1
packages/app-builder-lib/src/util/electronGet.ts: 957 lines of code packages/app-builder-lib/src/util/electronGet.ts:1— packages/app-builder-lib/src/util/electronGet.ts has 957 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
REDACTED: 903 lines of code REDACTED:1— REDACTED has 903 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
REDACTED: 893 lines of code REDACTED:1— REDACTED has 893 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/app-builder-lib/src/targets/mac/MacTargetHelper.ts · ×1
packages/app-builder-lib/src/targets/mac/MacTargetHelper.ts: 837 lines of code packages/app-builder-lib/src/targets/mac/MacTargetHelper.ts:1— packages/app-builder-lib/src/targets/mac/MacTargetHelper.ts has 837 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/app-builder-lib/src/macPackager.ts · ×1
packages/app-builder-lib/src/macPackager.ts: 807 lines of code packages/app-builder-lib/src/macPackager.ts:1— packages/app-builder-lib/src/macPackager.ts has 807 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/app-builder-lib/src/packager.ts · ×1
packages/app-builder-lib/src/packager.ts: 714 lines of code packages/app-builder-lib/src/packager.ts:1— packages/app-builder-lib/src/packager.ts has 714 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/electron-updater/src/differentialDownloader/blockMapV3Fetcher.ts · ×1
packages/electron-updater/src/differentialDownloader/blockMapV3Fetcher.ts: 713 lines of code packages/electron-updater/src/differentialDownloader/blockMapV3Fetcher.ts:1— packages/electron-updater/src/differentialDownloader/blockMapV3Fetcher.ts has 713 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/app-builder-lib/src/fileMatcher.ts · ×1
packages/app-builder-lib/src/fileMatcher.ts: 688 lines of code packages/app-builder-lib/src/fileMatcher.ts:1— packages/app-builder-lib/src/fileMatcher.ts has 688 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/builder-util-runtime/src/publishOptions.ts · ×1
packages/builder-util-runtime/src/publishOptions.ts: 677 lines of code packages/builder-util-runtime/src/publishOptions.ts:1— packages/builder-util-runtime/src/publishOptions.ts has 677 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
REDACTED: 614 lines of code REDACTED:1— REDACTED has 614 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/builder-util/src/util.ts · ×1
packages/builder-util/src/util.ts: 597 lines of code packages/builder-util/src/util.ts:1— packages/builder-util/src/util.ts has 597 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/electron-publish/src/s3/awsCredentials.ts · ×1
packages/electron-publish/src/s3/awsCredentials.ts: 522 lines of code packages/electron-publish/src/s3/awsCredentials.ts:1— packages/electron-publish/src/s3/awsCredentials.ts has 522 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/app-builder-lib/src/codeSign/certInfo.ts · ×1
packages/app-builder-lib/src/codeSign/certInfo.ts: 509 lines of code packages/app-builder-lib/src/codeSign/certInfo.ts:1— packages/app-builder-lib/src/codeSign/certInfo.ts has 509 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/electron-updater/src/NsisUpdater.ts · ×1
packages/electron-updater/src/NsisUpdater.ts: 505 lines of code packages/electron-updater/src/NsisUpdater.ts:1— packages/electron-updater/src/NsisUpdater.ts has 505 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/electron-builder/src/cli/sign-update-manifest.ts · ×1
packages/electron-builder/src/cli/sign-update-manifest.ts: 503 lines of code packages/electron-builder/src/cli/sign-update-manifest.ts:1— packages/electron-builder/src/cli/sign-update-manifest.ts has 503 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/builder-util-runtime/src/blockMapV3.ts · ×1
packages/builder-util-runtime/src/blockMapV3.ts: 500 lines of code packages/builder-util-runtime/src/blockMapV3.ts:1— packages/builder-util-runtime/src/blockMapV3.ts has 500 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/builder-util/src/fs.ts · ×1
packages/builder-util/src/fs.ts: 500 lines of code packages/builder-util/src/fs.ts:1— packages/builder-util/src/fs.ts has 500 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/app-builder-lib/src/targets/linux/snap/coreLegacy.ts · ×1
packages/app-builder-lib/src/targets/linux/snap/coreLegacy.ts: 489 lines of code packages/app-builder-lib/src/targets/linux/snap/coreLegacy.ts:1— packages/app-builder-lib/src/targets/linux/snap/coreLegacy.ts has 489 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
REDACTED: 489 lines of code REDACTED:1— REDACTED has 489 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/app-builder-lib/src/node-module-collector/pnpmNodeModulesCollector.ts · ×1
packages/app-builder-lib/src/node-module-collector/pnpmNodeModulesCollector.ts: 479 lines of code packages/app-builder-lib/src/node-module-collector/pnpmNodeModulesCollector.ts:1— packages/app-builder-lib/src/node-module-collector/pnpmNodeModulesCollector.ts has 479 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/electron-updater/src/LinuxUpdater.ts · ×1
packages/electron-updater/src/LinuxUpdater.ts: 476 lines of code packages/electron-updater/src/LinuxUpdater.ts:1— packages/electron-updater/src/LinuxUpdater.ts has 476 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/app-builder-lib/src/targets/win/winAppUtil.ts · ×1
packages/app-builder-lib/src/targets/win/winAppUtil.ts: 470 lines of code packages/app-builder-lib/src/targets/win/winAppUtil.ts:1— packages/app-builder-lib/src/targets/win/winAppUtil.ts has 470 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/app-builder-lib/src/util/appFileCopier.ts · ×1
packages/app-builder-lib/src/util/appFileCopier.ts: 464 lines of code packages/app-builder-lib/src/util/appFileCopier.ts:1— packages/app-builder-lib/src/util/appFileCopier.ts has 464 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/app-builder-lib/src/util/config/legacyOptions.ts · ×1
packages/app-builder-lib/src/util/config/legacyOptions.ts: 464 lines of code packages/app-builder-lib/src/util/config/legacyOptions.ts:1— packages/app-builder-lib/src/util/config/legacyOptions.ts has 464 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/app-builder-lib/src/targets/linux/FpmTarget.ts · ×1
packages/app-builder-lib/src/targets/linux/FpmTarget.ts: 463 lines of code packages/app-builder-lib/src/targets/linux/FpmTarget.ts:1— packages/app-builder-lib/src/targets/linux/FpmTarget.ts has 463 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/app-builder-lib/src/targets/linux/snap/core24.ts · ×1
packages/app-builder-lib/src/targets/linux/snap/core24.ts: 462 lines of code packages/app-builder-lib/src/targets/linux/snap/core24.ts:1— packages/app-builder-lib/src/targets/linux/snap/core24.ts has 462 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/app-builder-lib/src/options/PlatformSpecificBuildOptions.ts · ×1
packages/app-builder-lib/src/options/PlatformSpecificBuildOptions.ts: 461 lines of code packages/app-builder-lib/src/options/PlatformSpecificBuildOptions.ts:1— packages/app-builder-lib/src/options/PlatformSpecificBuildOptions.ts has 461 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/app-builder-lib/src/node-module-collector/nodeModulesCollector.ts · ×1
packages/app-builder-lib/src/node-module-collector/nodeModulesCollector.ts: 459 lines of code packages/app-builder-lib/src/node-module-collector/nodeModulesCollector.ts:1— packages/app-builder-lib/src/node-module-collector/nodeModulesCollector.ts has 459 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/app-builder-lib/src/util/buildOutputVerifier.ts · ×1
packages/app-builder-lib/src/util/buildOutputVerifier.ts: 459 lines of code packages/app-builder-lib/src/util/buildOutputVerifier.ts:1— packages/app-builder-lib/src/util/buildOutputVerifier.ts has 459 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/app-builder-lib/src/options/winOptions.ts · ×1
packages/app-builder-lib/src/options/winOptions.ts: 451 lines of code packages/app-builder-lib/src/options/winOptions.ts:1— packages/app-builder-lib/src/options/winOptions.ts has 451 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/app-builder-lib/src/targets/differentialUpdateInfoBuilder.ts · ×1
packages/app-builder-lib/src/targets/differentialUpdateInfoBuilder.ts: 439 lines of code packages/app-builder-lib/src/targets/differentialUpdateInfoBuilder.ts:1— packages/app-builder-lib/src/targets/differentialUpdateInfoBuilder.ts has 439 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/builder-util/src/executables.ts · ×1
packages/builder-util/src/executables.ts: 435 lines of code packages/builder-util/src/executables.ts:1— packages/builder-util/src/executables.ts has 435 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R4 · Test Coverage· No test reaches this file · ×1
No test reaches this file packages/app-builder-lib/helpers/remote-rebuild.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
Dead file (~92 LoC) scripts/generate-schema.ts— no import path from any entry point (70 application, 26 tooling, 403 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~42 LoC) scripts/renderer/src/typedoc2html.ts— no import path from any entry point (70 application, 26 tooling, 403 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~11 LoC) scripts/snap-exclude-list.js— no import path from any entry point (70 application, 26 tooling, 403 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Unlisted import 'electron' test/src/updater/updaterLoginChallengeTest.ts:3— Imported only as a TYPE and declared in no reachable REDACTED. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning REDACTED.
Unused dependency '@tsconfig/node22' REDACTED:50— Declared in the root REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'changesets-changelog-clean' REDACTED:55— Declared in the root REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'undici' packages/app-builder-lib/package.json:100— Declared in packages/app-builder-lib/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'temp-file' packages/dmg-builder/package.json:48— Declared in packages/dmg-builder/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'chalk' REDACTED:23— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'depcheck' REDACTED:25— Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
S1 · Web-Security Posture· Password key derivation is priced too cheaply · ×1
Password key derivation is priced too cheaply REDACTED:977— This code fixes scrypt at N=1,024 (r=8, p=1). A key-derivation function's only defence is the cost of ONE guess, and that cost is this number — the algorithm choice does not set it. Current OWASP guidance is 1,300,000 PBKDF2 iterations with HMAC-SHA1, 600,000 with SHA-256 and 210,000 with SHA-512; scrypt at N=2^17, r=8, p=1 (or an equivalent N·r·p product); Argon2id at 19 MiB of memory and 2 iterations (or an equivalent row); bcrypt at a work factor of at least 10. This figure divides the attacker's work by a factor of tens or hundreds against the same stolen hash, on hardware they already own. Where what is derived is short or low-entropy — a PIN, a numeric parental code, a four-character token — the whole keyspace falls in the time this parameter buys, and no salt or constant-time comparison changes that. Raise the count to the current published figure for the PRF you use, measure it on the slowest hardware that must run it (a target of roughly 100 ms per derivation is the usual budget), and read the value from configuration so a deployment can raise it again without a rebuild. Where the derived value must interoperate with a format someone else fixed, the count cannot move — derive a SEPARATE value for anything you own rather than inheriting the external format's price.
X2 · Cancellation propagation· Async function without AbortSignal · ×1
Async function without AbortSignal: getBucketLocation packages/electron-publish/src/s3/bucketLocation.ts:14— `getBucketLocation` awaits `https.request(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `https.request(url, { signal })`.
X29 · Per-element action decided by a fixed element· Per-element action decided by a fixed element · ×1
Per-element action decided by a fixed element packages/app-builder-lib/src/targets/linux/appimage/appLauncher.ts:31— This loop runs once per element of `icons`, and the statement it guards acts on the element it is on — `icon`. The test deciding whether that statement runs does not: `iconExtWithDot === ".svg"` reads `icons[0]`, a subscript that does not move, so whatever it answers for that one element it answers for ALL of them. One `if` names the same collection at two different subscripts — the fixed one at line 21, which is the contradiction: either the test was meant to be per-element, in which case every element that differs from the fixed one is handled wrongly and all in the same direction, or it really is one answer for the whole collection, in which case it is being re-asked on every pass and belongs above the loop. The `if` is in the wrong place under both readings. Give the test the loop variable, or hoist it out.
Disabled test test/src/ArtifactPublisherTest.ts:46— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test test/src/HoistedNodeModuleTest.ts:298— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test test/src/globTest.ts:117— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test test/src/linux/snapcraftParallels.e2e.ts:65— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test test/src/linux/snapcraftParallels.e2e.ts:75— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test test/src/linux/snapcraftParallels.e2e.ts:83— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test test/src/mac/dmg.e2e.ts:274— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test test/src/mac/macCodeSignTest.ts:25— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test test/src/mac/masTest.ts:25— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test test/src/updater/blackboxInstallTest.ts:64— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test test/src/updater/blackboxInstallTest.ts:74— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test test/src/updater/blackboxInstallTest.ts:84— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test test/src/updater/blackboxMsixTest.ts:138— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test test/src/updater/blackboxMsixTest.ts:196— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test test/src/updater/blackboxMsixTest.ts:255— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test test/src/updater/blackboxMsixTest.ts:325— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test test/src/updater/blackboxMsixTest.ts:377— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test test/src/updater/blackboxMsixTest.ts:458— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test test/src/updater/blackboxUpdateLinuxSuite.ts:113— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test test/src/updater/blackboxUpdateLinuxSuite.ts:117— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test test/src/updater/blackboxUpdateLinuxSuite.ts:132— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test test/src/updater/blackboxUpdateLinuxSuite.ts:138— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test test/src/updater/blackboxUpdateLinuxSuite.ts:149— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test test/src/updater/blackboxUpdateLinuxSuite.ts:154— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test test/src/updater/blackboxUpdateLinuxSuite.ts:164— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Duplicated predicate REDACTED:51— `!isOfflineModeEnabled() && (options.isNest || options.hash === "sha256")` appears character-identically in 2 files — REDACTED, REDACTED. 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 packages/app-builder-lib/src/fileMatcher.ts:471— `!matcher.isSpecifiedAsEmptyArray && (matcher.isEmpty() || matcher.containsOnlyIgnore())` appears character-identically in 2 files — packages/app-builder-lib/src/fileMatcher.ts, packages/app-builder-lib/src/util/AppFileWalker.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/app-builder-lib/src/asar/asarUtil.ts:310— `!stat.isFile() && !stat.isSymbolicLink()` appears character-identically in 2 files — packages/app-builder-lib/src/asar/asarUtil.ts, packages/builder-util/src/fs.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate REDACTED:240— `!this.app.isPackaged && !this.forceDevUpdateConfig` appears character-identically in 2 files — REDACTED, packages/electron-updater/src/NsisUpdater.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/app-builder-lib/src/targets/win/AppxTarget.ts:99— `appInfo.description || appInfo.productName` appears character-identically in 2 files — packages/app-builder-lib/src/targets/win/AppxTarget.ts, packages/app-builder-lib/src/targets/win/MsixTarget.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/app-builder-lib/src/asar/asarAlign.ts:45— `child.offset != null && !child.unpacked && child.link == null` appears character-identically in 2 files — packages/app-builder-lib/src/asar/asarAlign.ts, packages/app-builder-lib/src/targets/differentialUpdateInfoBuilder.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/app-builder-lib/src/packager.ts:393— `configFromOptions != null && typeof configFromOptions.extends === "string" && configFromOptions.extends.includes(".")` appears character-identically in 2 files — packages/app-builder-lib/src/packager.ts, packages/electron-builder/src/cli/sign-update-manifest.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/electron-updater/src/providers/BitbucketProvider.ts:40— `e instanceof Error && "code" in e && e.code === "ERR_HTTP_RESPONSE_TOO_LARGE"` appears character-identically in 3 files — packages/electron-updater/src/providers/BitbucketProvider.ts, packages/electron-updater/src/providers/KeygenProvider.ts, packages/electron-updater/src/providers/Provider.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/electron-updater/src/providers/GenericProvider.ts:35— `e instanceof HttpError && e.statusCode === 404` appears character-identically in 4 files — packages/electron-updater/src/providers/GenericProvider.ts, packages/electron-updater/src/providers/GitHubProvider.ts, packages/electron-updater/src/providers/GitLabProvider.ts, packages/electron-updater/src/providers/PrivateGitHubProvider.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/app-builder-lib/src/util/buildOutputVerifier.ts:232— `e.code === "ENOENT" || e.code === "ENOTDIR"` appears character-identically in 3 files — packages/app-builder-lib/src/util/buildOutputVerifier.ts, packages/app-builder-lib/src/util/cacheManager.ts, packages/builder-util/src/promise.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/app-builder-lib/src/util/NodeModuleCopyHelper.ts:126— `filter != null && !filter(filePath, stat)` appears character-identically in 2 files — packages/app-builder-lib/src/util/NodeModuleCopyHelper.ts, packages/builder-util/src/fs.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/app-builder-lib/src/targets/targetFactory.ts:136— `key === "mac" || key === "win" || key === "linux"` appears character-identically in 2 files — packages/app-builder-lib/src/targets/targetFactory.ts, packages/app-builder-lib/src/util/electronUpdaterCompatibility.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/app-builder-lib/src/asar/integrity.ts:52— `matcher.isEmpty() || matcher.containsOnlyIgnore()` appears character-identically in 2 files — packages/app-builder-lib/src/asar/integrity.ts, packages/app-builder-lib/src/fileMatcher.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/electron-publish/src/gitHubPublisher.ts:189— `mime.getType(fileName) || "application/octet-stream"` appears character-identically in 2 files — packages/electron-publish/src/gitHubPublisher.ts, packages/electron-publish/src/gitlabPublisher.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/electron-publish/src/s3/r2Publisher.ts:86— `options.channel == null && channelFromAppVersion != null` appears character-identically in 3 files — packages/electron-publish/src/s3/r2Publisher.ts, packages/electron-publish/src/s3/s3Publisher.ts, packages/electron-publish/src/s3/spacesPublisher.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/app-builder-lib/src/targets/win/AppxTarget.ts:58— `options.displayName || appInfo.productName` appears character-identically in 2 files — packages/app-builder-lib/src/targets/win/AppxTarget.ts, packages/app-builder-lib/src/targets/win/MsixTarget.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate REDACTED:37— `options.isNest || options.hash === "sha256"` appears character-identically in 3 files — REDACTED, REDACTED, REDACTED. 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 packages/app-builder-lib/src/targets/win/AppxTarget.ts:74— `options.publisherDisplayName || appInfo.companyName` appears character-identically in 2 files — packages/app-builder-lib/src/targets/win/AppxTarget.ts, packages/app-builder-lib/src/targets/win/MsixTarget.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/app-builder-lib/src/util/buildOutputVerifier.ts:244— `parsed == null || typeof parsed !== "object" || Array.isArray(parsed)` appears character-identically in 2 files — packages/app-builder-lib/src/util/buildOutputVerifier.ts, packages/builder-util/src/updateManifestSigner.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/app-builder-lib/src/targets/win/AppxTarget.ts:36— `process.platform !== "darwin" && (process.platform !== "win32" || isOldWin6())` appears character-identically in 2 files — packages/app-builder-lib/src/targets/win/AppxTarget.ts, packages/app-builder-lib/src/targets/win/MsixTarget.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/app-builder-lib/src/publish/PublishManager.ts:623— `publishConfigs == null || publishConfigs.length === 0` appears character-identically in 3 files — packages/app-builder-lib/src/publish/PublishManager.ts, packages/app-builder-lib/src/publish/updateInfoBuilder.ts, packages/app-builder-lib/src/targets/win/nsis/WebInstallerTarget.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/app-builder-lib/src/index.ts:151— `publishConfigurations == null || publishConfigurations.length === 0` appears character-identically in 2 files — packages/app-builder-lib/src/index.ts, packages/electron-builder/src/publish.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate REDACTED:475— `redirectOptions.protocol !== "http:" && redirectOptions.protocol !== "https:"` appears character-identically in 2 files — REDACTED, REDACTED. 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 packages/app-builder-lib/src/packager.ts:251— `result.length === 0 && currentIfNotSpecified` appears character-identically in 2 files — packages/app-builder-lib/src/packager.ts, packages/electron-builder/src/builder.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate REDACTED:39— `signing.rfc3161TimeStampServer || "http://timestamp.digicert.com"` appears character-identically in 2 files — REDACTED, REDACTED. 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 packages/app-builder-lib/src/targets/linux/appimage/appImageUtil.ts:54— "Write AppRun launcher and related files" repeats the code it sits on: 5 of its 6 words (write, app, launcher, related, files) are already in `await writeAppLauncherAndRelatedFiles(opts)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/app-builder-lib/src/targets/linux/flatpakBundle.ts:229— "the sdk has the version of the runtime" repeats the code it sits on: 3 of its 3 words (sdk, version, runtime) are already in `const refs: [FlatpakRefKind, string][] = [`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/electron-updater/src/providers/GitLabProvider.ts:271— "Get new version assets" repeats the code it sits on: 4 of its 4 words (get, new, version, assets) are already in `const newVersionAssets = await this.getVersionInfoForBlockMap(newVersion)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/electron-updater/src/providers/GitLabProvider.ts:277— "Get old version assets" repeats the code it sits on: 4 of its 4 words (get, old, version, assets) are already in `const oldVersionAssets = await this.getVersionInfoForBlockMap(oldVersion)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment test/fixtures/test-app-one/index.js:84— "Create the browser window." repeats the code it sits on: 3 of its 3 words (create, browser, window) are already in `mainWindow = new BrowserWindow({width: 800, height: 600, webPreferences: {nodeIntegration: true}});`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment test/fixtures/test-app-one/index.js:90— "Open the DevTools." repeats the code it sits on: 3 of its 3 words (open, dev, tools) are already in `mainWindow.webContents.openDevTools();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment test/fixtures/test-app-two-native-modules/app/index.js:29— "Create the browser window." repeats the code it sits on: 3 of its 3 words (create, browser, window) are already in `mainWindow = new BrowserWindow({width: 800, height: 600});`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment test/fixtures/test-app-two-native-modules/app/index.js:35— "Open the DevTools." repeats the code it sits on: 3 of its 3 words (open, dev, tools) are already in `mainWindow.webContents.openDevTools();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment test/fixtures/test-app-yarn-several-workspace/packages/test-app/index.js:29— "Create the browser window." repeats the code it sits on: 3 of its 3 words (create, browser, window) are already in `mainWindow = new BrowserWindow({width: 800, height: 600});`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment test/fixtures/test-app-yarn-several-workspace/packages/test-app/index.js:35— "Open the DevTools." repeats the code it sits on: 3 of its 3 words (open, dev, tools) are already in `mainWindow.webContents.openDevTools();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment test/fixtures/test-app-yarn-workspace-version-conflict/packages/test-app/index.js:29— "Create the browser window." repeats the code it sits on: 3 of its 3 words (create, browser, window) are already in `mainWindow = new BrowserWindow({width: 800, height: 600});`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment test/fixtures/test-app-yarn-workspace-version-conflict/packages/test-app/index.js:35— "Open the DevTools." repeats the code it sits on: 3 of its 3 words (open, dev, tools) are already in `mainWindow.webContents.openDevTools();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment test/fixtures/test-app-yarn-workspace/packages/test-app/index.js:29— "Create the browser window." repeats the code it sits on: 3 of its 3 words (create, browser, window) are already in `mainWindow = new BrowserWindow({width: 800, height: 600});`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment test/fixtures/test-app-yarn-workspace/packages/test-app/index.js:35— "Open the DevTools." repeats the code it sits on: 3 of its 3 words (open, dev, tools) are already in `mainWindow.webContents.openDevTools();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment test/fixtures/test-app/app/index.js:81— "autoUpdater._appUpdateConfigPath = _appUpdateConfigPath" repeats the code it sits on: 5 of its 6 words (auto, updater, update, config, path) are already in `autoUpdater.updateConfigPath = updateConfigPath`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment test/src/ArtifactPublisherTest.ts:163— "A missing token is a hard configuration error." repeats the code it sits on: 4 of its 5 words (missing, token, configuration, error) are already in `test("Bitbucket auth - missing token throws InvalidConfigurationError", ({ expect }) =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment test/src/archiveUtilTest.ts:407— "The decodable BCJ filter is applied to the executables…" repeats the code it sits on: 4 of its 5 words (decodable, bcj, filter, applied) are already in `expect(methods, "expected the decodable BCJ filter to be applied").toMatch(/\bBCJ\b/)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment test/src/certInfoTest.ts:333— "NO_EKU_PFX has exactly one cert and it has no EKU at all." repeats the code it sits on: 4 of its 5 words (no, eku, pfx, cert) are already in `await expect(readCertInfo(NO_EKU_PFX, "pw")).rejects.toThrow(/ExtKeyUsageCodeSigning/)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment test/src/filterTest.ts:331— "config.extraDistFiles is ignored for extraDistFiles" repeats the code it sits on: 4 of its 5 words (extra, dist, files, ignored) are already in `const result = getFileMatchers({ extraDistFiles: ["should-be-ignored.txt"] } as any, "extraDistFiles", "/out", customOpt …`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment test/src/httpExecutorTest.ts:1353— "the debug module builder-util-runtime itself loads" repeats the code it sits on: 5 of its 6 words (debug, module, builder, util, runtime) are already in `const runtimeDebug = createRequire(path.join(__dirname, "..", "..", "packages", "builder-util-runtime", "REDACTED")) …`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment test/src/packageManagerTest.ts:147— "yarn multi-package workspace" repeats the code it sits on: 4 of its 4 words (yarn, multi, package, workspace) are already in `test("yarn multi-package workspace", ({ expect }) =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment test/src/packageManagerTest.ts:168— "yarn berry multi-package workspace" repeats the code it sits on: 5 of its 5 words (yarn, berry, multi, package, workspace) are already in `test("yarn berry multi-package workspace", ({ expect }) =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment test/src/provider/bitbucketProviderTest.ts:128— "resolveFiles resolves YAML file URLs relative to the Bitbucket downloads base URL" repeats the code it sits on: 10 of its 12 words (resolve, files, resolves, file, ur, ls, relative, bitbucket, downloads, base) are already in `test("resolveFiles - constructs download URLs relative to Bitbucket base", async ({ expect }) =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment test/src/provider/githubProviderTest.ts:92— "allowPrerelease=true with stable current version: takes the newest available stable or prerelease version (prerelease in this case)" repeats the code it sits on: 8 of its 10 words (allow, prerelease, true, stable, current, newest, available, case) are already in `test("allowPrerelease=true with stable current - picks the newest available valid release (the beta release in this case …`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment test/src/provider/githubProviderTest.ts:115— "allowPrerelease=true with stable current version: takes the newest available stable or prerelease version (stable in this case)" repeats the code it sits on: 8 of its 10 words (allow, prerelease, true, stable, current, newest, available, case) are already in `test("allowPrerelease=true with stable current - picks the newest available valid release (the stable 5.1.0 release in t …`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
Orphaned file packages/electron-updater/src/differentialDownloader/downloadPlanBuilder.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/app-builder-lib/src/util/normalizePackageData.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/app-builder-lib/src/targets/win/AppxCapabilities.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/app-builder-lib/src/util/langs.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/app-builder-lib/src/appInfo.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/app-builder-lib/src/options/pkgOptions.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/electron-publish/src/progress.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/builder-util-runtime/src/uuid.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/app-builder-lib/src/asar/asar.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/app-builder-lib/src/options/AppXOptions.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/app-builder-lib/src/targets/win/nsis/nsisLang.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/app-builder-lib/src/targets/win/MsiWrappedTarget.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/app-builder-lib/src/fileTransformer.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/app-builder-lib/src/targets/win/nsis/progId.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/electron-updater/src/providerFactory.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/app-builder-lib/src/options/CommonWindowsInstallerConfiguration.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/builder-util-runtime/src/CancellationToken.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/app-builder-lib/src/util/repositoryInfo.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/app-builder-lib/src/util/filter.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/app-builder-lib/src/util/cacheManager.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/app-builder-lib/src/util/macroExpander.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Documentation: no build, run or usage example packages/app-builder-lib/README.md:1— `app-builder-lib` is a published package (`REDACTED` without `"private": true`) and neither `packages/app-builder-lib/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example packages/builder-util/readme.md:1— `builder-util` is a published package (`REDACTED` without `"private": true`) and neither `packages/builder-util/readme.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example packages/builder-util-runtime/readme.md:1— `builder-util-runtime` is a published package (`REDACTED` without `"private": true`) and neither `packages/builder-util-runtime/readme.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example packages/dmg-builder/readme.md:1— `dmg-builder` is a published package (`REDACTED` without `"private": true`) and neither `packages/dmg-builder/readme.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example packages/electron-builder-squirrel-windows/readme.md:1— `electron-builder-squirrel-windows` is a published package (`REDACTED` without `"private": true`) and neither `packages/electron-builder-squirrel-windows/readme.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example packages/electron-forge-maker-appimage/readme.md:1— `electron-forge-maker-appimage` is a published package (`REDACTED` without `"private": true`) and neither `packages/electron-forge-maker-appimage/readme.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example packages/electron-forge-maker-nsis/readme.md:1— `electron-forge-maker-nsis` is a published package (`REDACTED` without `"private": true`) and neither `packages/electron-forge-maker-nsis/readme.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example packages/electron-forge-maker-nsis-web/readme.md:1— `electron-forge-maker-nsis-web` is a published package (`REDACTED` without `"private": true`) and neither `packages/electron-forge-maker-nsis-web/readme.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example packages/electron-forge-maker-snap/readme.md:1— `electron-forge-maker-snap` is a published package (`REDACTED` without `"private": true`) and neither `packages/electron-forge-maker-snap/readme.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example packages/electron-publish/readme.md:1— `electron-publish` is a published package (`REDACTED` without `"private": true`) and neither `packages/electron-publish/readme.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example packages/electron-updater/README.md:1— `electron-updater` is a published package (`REDACTED` without `"private": true`) and neither `packages/electron-updater/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Mock-dominated test: aborts and logs error when cache dir resolves to filesystem root test/src/cliTest.ts:111— This test sets up 3 test doubles (for example `vi.mock/jest.mock of an imported module`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: closes readline interface even when user aborts test/src/cliTest.ts:118— This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: proceeds when user answers "${answer}" test/src/cliTest.ts:129— This test sets up 4 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: aborts when user answers "${answer}" test/src/cliTest.ts:140— This test sets up 5 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: the quota is per key, and shared by every level of that key test/src/loggerLimitTest.ts:26— This test sets up 4 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: emits Electron's login event with the request URL, and a handler cancels by calling the callback without credentials test/src/updater/updaterLoginChallengeTest.ts:288— This test sets up 4 test doubles (for example `vi.fn`) against 2 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
X23 · Unguarded diagnostic materialisation· Diagnostic log message is built whether or not it is wanted · ×5
Diagnostic log message is built whether or not it is wanted packages/electron-updater/src/differentialDownloader/DifferentialDownloader.ts:122— `debug` at line 122 is called with an argument built by `JSON.stringify(operations, null, 2)` (line 122), whose cost grows with the collection it walks. JavaScript 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 debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted packages/app-builder-lib/src/util/nativeBinaryVerifier.ts:365— `debug` at line 365 is called with an argument built by `describeNativeBinary(info)` (line 365), whose cost grows with the collection it walks. JavaScript 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 debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted packages/app-builder-lib/src/util/nativeBinaryVerifier.ts:377— `debug` at line 377 is called with an argument built by `describeNativeBinary(info)` (line 377), whose cost grows with the collection it walks. JavaScript 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 debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted packages/app-builder-lib/src/node-module-collector/index.ts:135— `debug` at line 135 is called with an argument built by `args.join(" ")` (line 135), whose cost grows with the collection it walks. JavaScript 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 debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted packages/app-builder-lib/src/asar/asarUtil.ts:103— `debug` at line 103 is called with an argument built by `join(", ")` (line 103), whose cost grows with the collection it walks. JavaScript 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 debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Silent fallback default in catch packages/app-builder-lib/src/util/nativeBinaryVerifier.ts:252— `listFiles` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch packages/app-builder-lib/src/util/installOrRebuild.ts:155— `getYarnBerryNpmAuthEnv` swallows every exception into `return {}` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch REDACTED:114— `read` swallows every exception into `return ""` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch test/src/updater/blackboxUpdateHelpers.ts:318— `embeddedCacheDirConfig` swallows every exception into `return {}` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch test/src/updater/blackboxInstallTest.ts:33— `determineEnvironment` swallows every exception into `return false` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Deprecated: @ungap/structured-clone REDACTED:4333— @ungap/structured-clone 1.3.0 is resolved in REDACTED and is marked deprecated by its publisher: "Potential CWE-502 - Update to 1.3.1 or higher". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: glob REDACTED:5888— glob 7.2.3 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: inflight REDACTED:6151— inflight 1.0.6 is resolved in REDACTED and is marked deprecated by its publisher: "This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Outdated (npm): dotenv-expand packages/app-builder-lib/package.json:81— dotenv-expand is pinned at 13.0.0; registry.npmjs.org publishes 1000.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): ejs packages/app-builder-lib/package.json:82— ejs is pinned at 3.1.10; registry.npmjs.org publishes 7.0.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): hosted-git-info packages/app-builder-lib/package.json:85— hosted-git-info is pinned at 4.1.0; registry.npmjs.org publishes 10.1.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
P2 · Observability· Console output used as the logging channel · ×3
Console output used as the logging channel packages/app-builder-lib/src/node-module-collector/hoist.ts:206— `packages/app-builder-lib/src/node-module-collector/hoist.ts` reports through `console.*` at line 206 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/app-builder-lib/src/node-module-collector/hoist.ts:218— `packages/app-builder-lib/src/node-module-collector/hoist.ts` reports through `console.*` at line 218 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/builder-util/src/promise.ts:4— `packages/builder-util/src/promise.ts` reports through `console.*` at line 4 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
D21 · Naming Consistency· `stopAtPackageJSON` spells `JSON` where 27 names in the project spell it `Json` · ×2
`stopAtPackageJSON` spells `JSON` where 27 names in the project spell it `Json` packages/app-builder-lib/src/electron/search-module.ts:4— 27 of 29 names in project @electron-builder/monorepo spell the token `Json` (27 of 29; unit: names in project @electron-builder/monorepo containing `Json`). Peers: AsarFilesystem.readJson (packages/app-builder-lib/src/asar/asar.ts:136); asar.readAsarJson (packages/app-builder-lib/src/asar/asar.ts:178); asarAlign.serializeHeader(headerJson) (packages/app-builder-lib/src/asar/asarAlign.ts:51); fileTransformer.cleanupPackageJson (packages/app-builder-lib/src/fileTransformer.ts:47); fileTransformer.modifyMainPackageJson (packages/app-builder-lib/src/fileTransformer.ts:79). Rename to `stopAtPackageJson`. [rule N6]
`stopAtPackageJSON` spells `JSON` where 27 names in the project spell it `Json` packages/app-builder-lib/src/electron/search-module.ts:16— 27 of 29 names in project @electron-builder/monorepo spell the token `Json` (27 of 29; unit: names in project @electron-builder/monorepo containing `Json`). Peers: AsarFilesystem.readJson (packages/app-builder-lib/src/asar/asar.ts:136); asar.readAsarJson (packages/app-builder-lib/src/asar/asar.ts:178); asarAlign.serializeHeader(headerJson) (packages/app-builder-lib/src/asar/asarAlign.ts:51); fileTransformer.cleanupPackageJson (packages/app-builder-lib/src/fileTransformer.ts:47); fileTransformer.modifyMainPackageJson (packages/app-builder-lib/src/fileTransformer.ts:79). Rename to `stopAtPackageJson`. [rule N6]
README/code drift website/docs/architecture.md:19— website/docs/architecture.md names Electron 43, but the manifest declares `electron` 42.11.16. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift website/docs/migration/v27-build-changes.md:34— website/docs/migration/v27-build-changes.md names Electron 44, but the manifest declares `electron` 42.11.16. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 12 significant file(s) lose their only recent owner: packages/app-builder-lib/src/util/flags.ts, packages/app-builder-lib/src/util/config/schemaValidator.ts, packages/app-builder-lib/src/node-module-collector/traversalNodeModulesCollector.ts, packages/app-builder-lib/src/util/removedEnvVars.ts, packages/app-builder-lib/src/electron/electronVersion.ts, packages/app-builder-lib/src/targets/linux/snap/SnapTarget.ts, packages/app-builder-lib/src/util/cacheState.ts, packages/electron-publish/src/bitbucketPublisher.ts (+4 more). Pair on, review, or document these before any departure.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 2 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (16 single-owned of 212 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 212 of the 310 production source files in this repository met that bar). They are anonymized user #2 (2 file(s)), anonymized user #3 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: packages/builder-util-runtime/src/xml.ts, packages/builder-util/src/asyncTaskManager.ts, packages/app-builder-lib/src/targets/blockmap/verbatimRange.ts.
No ADRs found packages/electron-builder/package.json:29— No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `packages/electron-builder/package.json` makes this repository a deployable product (line 29).
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion packages/app-builder-lib/package.json:1— `packages/app-builder-lib` (38150 LoC, 419 module-visible types across 26 directories) overshoots its size bounds. 1 of 15 build unit(s) (npm) overshoot their size bounds, lowering Project Cohesion to 8.7/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
REDACTED
D34 · Knowledge Freshness· Further orphaned files (smaller) · ×1
Further orphaned files (smaller) — 21 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: packages/electron-updater/src/differentialDownloader/downloadPlanBuilder.ts, packages/app-builder-lib/src/util/normalizePackageData.ts, packages/app-builder-lib/src/targets/win/AppxCapabilities.ts, packages/app-builder-lib/src/util/langs.ts, packages/app-builder-lib/src/appInfo.ts, packages/app-builder-lib/src/options/pkgOptions.ts, packages/electron-publish/src/progress.ts, packages/builder-util-runtime/src/uuid.ts (and 13 more) (22 orphaned of 213 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 213 of the 310 production source files in this repository met that bar). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
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.
No SAST REDACTED:27— No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 10 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
R7 · Dead Code· Unused export 'FIRST_ELECTRON_MAJOR_WITH_WER_HELPER' · ×1
Unused export 'FIRST_ELECTRON_MAJOR_WITH_WER_HELPER' packages/app-builder-lib/src/electron/ElectronFramework.ts:45— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'MetadataValue' · ×1
Unused export 'MetadataValue' packages/app-builder-lib/src/electron/electronVersion.ts:12— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'searchForModule' · ×1
Unused export 'searchForModule' packages/app-builder-lib/src/electron/search-module.ts:50— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'searchForNodeModules' · ×1
Unused export 'searchForNodeModules' packages/app-builder-lib/src/electron/search-module.ts:61— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export '_FuseOptionsV1Exhaustive' · ×1
Unused export '_FuseOptionsV1Exhaustive' packages/app-builder-lib/src/options/FuseOptionsV1.ts:151— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'getVendorPath' · ×1
Unused export 'getVendorPath' packages/app-builder-lib/src/util/pathManager.ts:9— Nothing imports this binding — it is safe to review for removal.
Unused export 'default' packages/electron-builder/assert-node-version.js:39— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'MAX_RANGES_PER_REQUEST' · ×1
Unused export 'MAX_RANGES_PER_REQUEST' packages/electron-updater/src/differentialDownloader/blockMapV3Fetcher.ts:51— Nothing imports THIS copy of 'MAX_RANGES_PER_REQUEST' — but packages/electron-updater/src/differentialDownloader/multipleRangeDownloader.ts:20 in the same directory exports that same name, and it is the copy every import site resolves to. Grepping the name therefore finds live callers that do not reach this binding: it is the dead half of a duplicated pair, left behind when the API moved. Delete it here and keep packages/electron-updater/src/differentialDownloader/multipleRangeDownloader.ts's, or, if this one is meant to be the survivor, repoint the importers before removing the other.
R8 · Dependency Hygiene· Type-only dependency '@electron/fuses' in production deps · ×1
Type-only dependency '@electron/fuses' in production deps packages/app-builder-lib/src/options/FuseOptionsV1.ts:1— Every import is type-only — move it to devDependencies.
R8 · Dependency Hygiene· Type-only dependency 'tiny-typed-emitter' in production deps · ×1
Type-only dependency 'tiny-typed-emitter' in production deps packages/electron-updater/src/AppUpdater.ts:43— Every import is type-only — move it to devDependencies.
No security response headers detected netlify.toml:1— None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `netlify.toml` configures this repository's static hosting, including its response headers, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.)
X2 · Cancellation propagation· Not all async functions that make a request accept an AbortSignal · ×1
Not all async functions that make a request accept an AbortSignal — Only 0/1 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
Null assertions (`!`) override strict null checking — ~2.0 `!` null assertions per 1k TypeScript source lines — 144 assertion(s) across the 71570 source line(s) of the 307 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: packages/app-builder-lib/src/packager.ts (12), packages/app-builder-lib/src/node-module-collector/hoist.ts (11), packages/app-builder-lib/src/asar/asar.ts (8). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
Skipped (documented): (unnamed test) test/src/buildOutputVerifierTest.ts:85— Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skipIf
Skipped (documented): (unnamed test) test/src/buildOutputVerifierTest.ts:98— Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skipIf
Skipped (documented): (unnamed test) test/src/buildOutputVerifierTest.ts:265— Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skipIf
Skipped (documented): (unnamed test) test/src/certInfoTest.ts:15— Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
Skipped (documented): (unnamed test) test/src/extractArchiveTest.ts:139— Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skipIf
Skipped (documented): (unnamed test) test/src/extractArchiveTest.ts:146— Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skipIf
Skipped (documented): (unnamed test) test/src/extractArchiveTest.ts:158— Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skipIf
Skipped (documented): (unnamed test) test/src/extractArchiveTest.ts:164— Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skipIf
Skipped (documented): (unnamed test) test/src/extractArchiveTest.ts:170— Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skipIf
Skipped (documented): (unnamed test) test/src/extractArchiveTest.ts:176— Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skipIf
Skipped (documented): (unnamed test) test/src/extractArchiveTest.ts:188— Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skipIf
Skipped (documented): (unnamed test) test/src/extractArchiveTest.ts:209— Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skipIf
Skipped (documented): (unnamed test) test/src/extractArchiveTest.ts:226— Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skipIf
Skipped (documented): (unnamed test) test/src/extractArchiveTest.ts:235— Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skipIf
Skipped (documented): (unnamed test) test/src/extractArchiveTest.ts:274— Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skipIf
Skipped (documented): (unnamed test) test/src/packageManagerTest.ts:269— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) test/src/packageManagerTest.ts:310— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) test/src/packageManagerTest.ts:353— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) test/src/packageManagerTest.ts:394— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) test/src/windows/squirrelWindowsInstallerTest.ts:375— Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skipIf
Skipped (documented): both readers report the subject Get-AuthenticodeSignature reports test/src/windows/updateInstallerPublisherTest.ts:331— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a this.skip()/t.skip() call
Skipped (documented): a matching publisherName passes and a wrong one fails test/src/windows/updateInstallerPublisherTest.ts:344— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a this.skip()/t.skip() call
Skipped (documented): (unnamed test) test/src/windows/winSignToolManagerTest.ts:877— Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skipIf
Skipped (documented): deb - compression: ${compression} - compressor: ${fpmCompression} test/src/updater/blackboxInstallTest.ts:62— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a this.skip()/t.skip() call
Skipped (documented): rpm - compression: ${compression} - compressor: ${fpmCompression} test/src/updater/blackboxInstallTest.ts:72— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a this.skip()/t.skip() call
Outdated (npm): @aws-sdk/credential-provider-ini — @aws-sdk/credential-provider-ini is pinned at 3.973.19; registry.npmjs.org publishes 3.973.30 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @aws-sdk/credential-provider-sso — @aws-sdk/credential-provider-sso is pinned at 3.973.18; registry.npmjs.org publishes 3.973.28 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @aws-sdk/nested-clients — @aws-sdk/nested-clients is pinned at 3.997.48; registry.npmjs.org publishes 3.998.3 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @docusaurus/core — @docusaurus/core is pinned at 3.10.1; registry.npmjs.org publishes 3.10.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @docusaurus/faster — @docusaurus/faster is pinned at 3.10.1; registry.npmjs.org publishes 3.10.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @docusaurus/plugin-client-redirects — @docusaurus/plugin-client-redirects is pinned at 3.10.1; registry.npmjs.org publishes 3.10.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @docusaurus/preset-classic — @docusaurus/preset-classic is pinned at 3.10.1; registry.npmjs.org publishes 3.10.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @electron/asar — @electron/asar is pinned at 4.3.1; registry.npmjs.org publishes 4.3.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @electron/notarize — @electron/notarize is pinned at 3.1.1; registry.npmjs.org publishes 3.1.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @electron/osx-sign — @electron/osx-sign is pinned at 2.7.0; registry.npmjs.org publishes 2.7.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @noble/hashes — @noble/hashes is pinned at 2.2.0; registry.npmjs.org publishes 2.4.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @peculiar/webcrypto — @peculiar/webcrypto is pinned at 1.7.1; registry.npmjs.org publishes 2.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @types/debug — @types/debug is pinned at 4.1.7; registry.npmjs.org publishes 4.1.13 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @types/fs-extra — @types/fs-extra is pinned at 9.0.13; registry.npmjs.org publishes 11.0.4 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): asn1js — asn1js is pinned at 3.0.10; registry.npmjs.org publishes 4.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): chalk — chalk is pinned at 4.1.2; registry.npmjs.org publishes 6.0.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): ci-info — ci-info is pinned at 4.3.1; registry.npmjs.org publishes 4.5.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): dotenv — dotenv is pinned at 17.4.2; registry.npmjs.org publishes 18.0.10 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): fs-extra — fs-extra is pinned at 11.3.5; registry.npmjs.org publishes 11.4.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): http-proxy-agent — http-proxy-agent is pinned at 7.0.2; registry.npmjs.org publishes 9.1.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): https-proxy-agent — https-proxy-agent is pinned at 7.0.6; registry.npmjs.org publishes 9.1.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): isbinaryfile — isbinaryfile is pinned at 5.0.4; registry.npmjs.org publishes 6.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): jiti — jiti is pinned at 2.4.2; registry.npmjs.org publishes 2.7.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): js-yaml — js-yaml is pinned at 4.3.2; registry.npmjs.org publishes 5.5.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): marked — marked is pinned at 16.4.2; registry.npmjs.org publishes 18.2.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
doc comments repeat the names packages/app-builder-lib/src/node-module-collector/hoist.ts:163— 2 of 49 documented parameters and 9 of 1236 summaries in `app-builder-lib` only repeat the member or parameter name (e.g. "Debug level" for `debugLevel`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names packages/builder-util-runtime/src/publishOptions.ts:22— 0 of 1 documented parameters and 12 of 198 summaries in `builder-util-runtime` only repeat the member or parameter name (e.g. "The provider." for `provider`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names packages/electron-updater/src/AppUpdater.ts:454— 0 of 7 documented parameters and 1 of 270 summaries in `electron-updater` only repeat the member or parameter name (e.g. "The request headers." for `requestHeaders`). 2 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 3 file(s) — `packages/app-builder-lib/src/forge-maker.ts`, `packages/app-builder-lib/src/platformPackager.ts`, `website/docusaurus.config.ts` — 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 01a1e762-c302-7dfc-adde-049f99476c0f · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 64 · Warnings: 670 · Recommendations: 191 · Info: 119 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 17-11-2026 @ 02:42 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.