Public report of decaporg/decap-cms, published 15 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive 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, 15 November 2026, 04:13 UTC · Survey ID cd_c622f0825de6428f8009eeca95a5408d
decaporg/decap-cms
Measured 15 November 2026, 04:12 UTC, at code version 61ceb6e
CAI scoreAt riskDown 1 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A medium codebase: 76,545 lines of product code in 47 projects, tests not counted · Estimated rebuild effort: about 0.8 person-years · Weakest lens: Code Health, 42
Findings by how serious they are
66 critical478 serious514 minor
10 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
15 November 2026, 04:12 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.
A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.
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 ▸
73of 73 dimensions measured by tools.
972of 1058 findings point to an exact file and line, so you can open each one in the code. The other 86 concern the repository as a whole, such as missing documentation.
73dimensions across 6 lenses, read from 76,545 lines of product code in 47 projects.
decaporg/decap-cms is rated At risk because critical security findings are open, most of them in the build pipeline. It scores 50 out of 100, which the At risk rating leaves unchanged.
Code Health, at 42, is the weakest lens and counts most in the score. The best first step is simplifying the most tangled methods, worth about 4 points. Writing log messages as searchable templates would lift Code Health itself, also worth about 4. Raising Code Health to 70 would lift the score to about 57.
Twenty-eight pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Eleven known security holes in the packages the code depends on can be used by attackers, and five secrets can leak from the build pipeline. Pinning each tool to an exact version, updating the vulnerable packages and limiting each secret to its own step would close these risks. The four places where the code runs text as code or as a command need a direct call instead. The three passwords or keys in the code's history need replacing, with the old ones switched off. The three inner parts of the code that depend on an outer part need turning around so they point inward.
The product code is 76,545 lines, about €110,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
We compare every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 213 findings
These 213 critical or serious findings were in the previous survey, on 29 October 2026, and are gone from this one. The first 100 are listed here.
€37,000 to €190,000, for 624 to 1,980 hours of work, about 0.8 person-years for 1 to 2 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.7 at a score of 50. 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: 76,545 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
Bring the 35 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with S3Widget.S3Widget (cyclomatic 43), entryDraft.entryDraftReducer (cyclomatic 42), config.applyDefaults (cyclomatic 40).
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 €110,000 to build again, about 0.8 person-years of work. Its weakest lens is Code Health, at 42 (Weak). Code Health is about how easy the code is to read and change safely, and code that is hard to read is slow and risky to change, so every future change costs more than it should. Because the weakest lens counts most in the score, work on Code Health also moves the score most.
Based on: the rebuild estimate · the Code Health grade · how much each lens counts
What to do: Start with the Code Health actions in Top priorities.
If you do one thing first · First action
Bring the 35 bodies over 15 down to 15 or less in Cyclomatic Complexity. Of all the actions in this report, it raises the score most for the work it takes: about 4 points for high effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
265 modules, with 208 dependencies between them. 2 loops run through 6 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 225 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.
decap-cms-lib-util.src.API uses decap-cms-lib-util.src, so a change to decap-cms-lib-util.src can break decap-cms-lib-util.src.API, while a change to decap-cms-lib-util.src.API can't break decap-cms-lib-util.src.
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.
10→11 decap-cms-lib-util.src.implementation uses decap-cms-core.src.types.reduxpart of a loop✕
Connections
1 pair of types, where a type in decap-cms-lib-util.src.implementation uses a type in decap-cms-core.src.types.redux.
decap-cms-lib-util.src.implementation uses decap-cms-core.src.types.redux, so a change to decap-cms-core.src.types.redux can break decap-cms-lib-util.src.implementation, while a change to decap-cms-lib-util.src.implementation can't break decap-cms-core.src.types.redux.
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.
decap-cms-core.src.types.redux uses decap-cms-lib-util.src.implementation, so a change to decap-cms-lib-util.src.implementation can break decap-cms-core.src.types.redux, while a change to decap-cms-core.src.types.redux can't break decap-cms-lib-util.src.implementation.
Position
Below the diagonal: decap-cms-core.src.types.redux uses a module listed above it, which is the healthy direction.
decap-cms-lib-util.src.Cursor uses decap-cms-lib-util.src.implementation, so a change to decap-cms-lib-util.src.implementation can break decap-cms-lib-util.src.Cursor, while a change to decap-cms-lib-util.src.Cursor can't break decap-cms-lib-util.src.implementation.
Position
Below the diagonal: decap-cms-lib-util.src.Cursor uses a module listed above it, which is the healthy direction.
decap-cms-lib-util.src.notesPolling uses decap-cms-lib-util.src.implementation, so a change to decap-cms-lib-util.src.implementation can break decap-cms-lib-util.src.notesPolling, while a change to decap-cms-lib-util.src.notesPolling can't break decap-cms-lib-util.src.implementation.
Position
Below the diagonal: decap-cms-lib-util.src.notesPolling uses a module listed above it, which is the healthy direction.
decap-cms-backend-gitlab.src.notesApi uses decap-cms-lib-util.src.implementation, so a change to decap-cms-lib-util.src.implementation can break decap-cms-backend-gitlab.src.notesApi, while a change to decap-cms-backend-gitlab.src.notesApi can't break decap-cms-lib-util.src.implementation.
Position
Below the diagonal: decap-cms-backend-gitlab.src.notesApi uses a module listed above it, which is the healthy direction.
decap-cms-backend-gitlab.src.notesApi uses decap-cms-lib-util.src.notesPolling, so a change to decap-cms-lib-util.src.notesPolling can break decap-cms-backend-gitlab.src.notesApi, while a change to decap-cms-backend-gitlab.src.notesApi can't break decap-cms-lib-util.src.notesPolling.
Position
Below the diagonal: decap-cms-backend-gitlab.src.notesApi uses a module listed above it, which is the healthy direction.
decap-cms-core.src uses decap-cms-core.src.valueObjects.Entry, so a change to decap-cms-core.src.valueObjects.Entry can break decap-cms-core.src, while a change to decap-cms-core.src can't break decap-cms-core.src.valueObjects.Entry.
Position
Below the diagonal: decap-cms-core.src uses a module listed above it, which is the healthy direction.
decap-cms-core.src uses decap-cms-core.src.types.redux, so a change to decap-cms-core.src.types.redux can break decap-cms-core.src, while a change to decap-cms-core.src can't break decap-cms-core.src.types.redux.
Position
Below the diagonal: decap-cms-core.src uses a module listed above it, which is the healthy direction.
decap-cms-core.src.backend uses decap-cms-core.src.valueObjects.AssetProxy, so a change to decap-cms-core.src.valueObjects.AssetProxy can break decap-cms-core.src.backend, while a change to decap-cms-core.src.backend can't break decap-cms-core.src.valueObjects.AssetProxy.
Position
Below the diagonal: decap-cms-core.src.backend uses a module listed above it, which is the healthy direction.
decap-cms-core.src.backend uses decap-cms-core.src.valueObjects.Entry, so a change to decap-cms-core.src.valueObjects.Entry can break decap-cms-core.src.backend, while a change to decap-cms-core.src.backend can't break decap-cms-core.src.valueObjects.Entry.
Position
Below the diagonal: decap-cms-core.src.backend uses a module listed above it, which is the healthy direction.
decap-cms-core.src.backend uses decap-cms-lib-util.src.implementation, so a change to decap-cms-lib-util.src.implementation can break decap-cms-core.src.backend, while a change to decap-cms-core.src.backend can't break decap-cms-lib-util.src.implementation.
Position
Below the diagonal: decap-cms-core.src.backend uses a module listed above it, which is the healthy direction.
decap-cms-core.src.backend uses decap-cms-core.src.types.redux, so a change to decap-cms-core.src.types.redux can break decap-cms-core.src.backend, while a change to decap-cms-core.src.backend can't break decap-cms-core.src.types.redux.
Position
Below the diagonal: decap-cms-core.src.backend uses a module listed above it, which is the healthy direction.
decap-cms-core.src.backend uses decap-cms-lib-util.src.Cursor, so a change to decap-cms-lib-util.src.Cursor can break decap-cms-core.src.backend, while a change to decap-cms-core.src.backend can't break decap-cms-lib-util.src.Cursor.
Position
Below the diagonal: decap-cms-core.src.backend uses a module listed above it, which is the healthy direction.
16→18 decap-cms-core.src.backend uses decap-cms-lib-util.srcpart of a loop✕
Connections
2 pairs of types, where a type in decap-cms-core.src.backend uses a type in decap-cms-lib-util.src.
decap-cms-core.src.backend uses decap-cms-lib-util.src, so a change to decap-cms-lib-util.src can break decap-cms-core.src.backend, while a change to decap-cms-core.src.backend can't break decap-cms-lib-util.src.
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.
decap-cms-core.src.reducers uses decap-cms-lib-util.src.implementation, so a change to decap-cms-lib-util.src.implementation can break decap-cms-core.src.reducers, while a change to decap-cms-core.src.reducers can't break decap-cms-lib-util.src.implementation.
Position
Below the diagonal: decap-cms-core.src.reducers uses a module listed above it, which is the healthy direction.
decap-cms-core.src.reducers uses decap-cms-core.src.types.redux, so a change to decap-cms-core.src.types.redux can break decap-cms-core.src.reducers, while a change to decap-cms-core.src.reducers can't break decap-cms-core.src.types.redux.
Position
Below the diagonal: decap-cms-core.src.reducers uses a module listed above it, which is the healthy direction.
decap-cms-core.src.reducers uses decap-cms-core.src.backend, so a change to decap-cms-core.src.backend can break decap-cms-core.src.reducers, while a change to decap-cms-core.src.reducers can't break decap-cms-core.src.backend.
Position
Below the diagonal: decap-cms-core.src.reducers uses a module listed above it, which is the healthy direction.
decap-cms-lib-util.src uses decap-cms-lib-util.src.API, so a change to decap-cms-lib-util.src.API can break decap-cms-lib-util.src, while a change to decap-cms-lib-util.src can't break decap-cms-lib-util.src.API.
Position
Below the diagonal: decap-cms-lib-util.src uses a module listed above it, which is the healthy direction.
decap-cms-lib-util.src uses decap-cms-lib-util.src.implementation, so a change to decap-cms-lib-util.src.implementation can break decap-cms-lib-util.src, while a change to decap-cms-lib-util.src can't break decap-cms-lib-util.src.implementation.
Position
Below the diagonal: decap-cms-lib-util.src uses a module listed above it, which is the healthy direction.
decap-cms-lib-util.src uses decap-cms-core.src.types.redux, so a change to decap-cms-core.src.types.redux can break decap-cms-lib-util.src, while a change to decap-cms-lib-util.src can't break decap-cms-core.src.types.redux.
Position
Below the diagonal: decap-cms-lib-util.src uses a module listed above it, which is the healthy direction.
decap-cms-lib-util.src uses decap-cms-core.src.backend, so a change to decap-cms-core.src.backend can break decap-cms-lib-util.src, while a change to decap-cms-lib-util.src can't break decap-cms-core.src.backend.
Position
Below the diagonal: decap-cms-lib-util.src uses a module listed above it, which is the healthy direction.
18→19 decap-cms-lib-util.src uses decap-cms-backend-azure.src.APIpart of a loop✕
Connections
1 pair of types, where a type in decap-cms-lib-util.src uses a type in decap-cms-backend-azure.src.API.
decap-cms-lib-util.src uses decap-cms-backend-azure.src.API, so a change to decap-cms-backend-azure.src.API can break decap-cms-lib-util.src, while a change to decap-cms-lib-util.src can't break decap-cms-backend-azure.src.API.
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.
decap-cms-backend-azure.src.API uses decap-cms-lib-util.src.API, so a change to decap-cms-lib-util.src.API can break decap-cms-backend-azure.src.API, while a change to decap-cms-backend-azure.src.API can't break decap-cms-lib-util.src.API.
Position
Below the diagonal: decap-cms-backend-azure.src.API uses a module listed above it, which is the healthy direction.
decap-cms-backend-azure.src.API uses decap-cms-lib-util.src.implementation, so a change to decap-cms-lib-util.src.implementation can break decap-cms-backend-azure.src.API, while a change to decap-cms-backend-azure.src.API can't break decap-cms-lib-util.src.implementation.
Position
Below the diagonal: decap-cms-backend-azure.src.API uses a module listed above it, which is the healthy direction.
decap-cms-backend-azure.src.API uses decap-cms-lib-util.src, so a change to decap-cms-lib-util.src can break decap-cms-backend-azure.src.API, while a change to decap-cms-backend-azure.src.API can't break decap-cms-lib-util.src.
Position
Below the diagonal: decap-cms-backend-azure.src.API uses a module listed above it, which is the healthy direction.
decap-cms-backend-bitbucket.src.API uses decap-cms-lib-util.src.API, so a change to decap-cms-lib-util.src.API can break decap-cms-backend-bitbucket.src.API, while a change to decap-cms-backend-bitbucket.src.API can't break decap-cms-lib-util.src.API.
Position
Below the diagonal: decap-cms-backend-bitbucket.src.API uses a module listed above it, which is the healthy direction.
decap-cms-backend-bitbucket.src.API uses decap-cms-lib-util.src.Cursor, so a change to decap-cms-lib-util.src.Cursor can break decap-cms-backend-bitbucket.src.API, while a change to decap-cms-backend-bitbucket.src.API can't break decap-cms-lib-util.src.Cursor.
Position
Below the diagonal: decap-cms-backend-bitbucket.src.API uses a module listed above it, which is the healthy direction.
decap-cms-backend-bitbucket.src.API uses decap-cms-lib-util.src, so a change to decap-cms-lib-util.src can break decap-cms-backend-bitbucket.src.API, while a change to decap-cms-backend-bitbucket.src.API can't break decap-cms-lib-util.src.
Position
Below the diagonal: decap-cms-backend-bitbucket.src.API uses a module listed above it, which is the healthy direction.
decap-cms-core.src.actions uses decap-cms-backend-turbo-github.src.deployWatcher, so a change to decap-cms-backend-turbo-github.src.deployWatcher can break decap-cms-core.src.actions, while a change to decap-cms-core.src.actions can't break decap-cms-backend-turbo-github.src.deployWatcher.
Position
Below the diagonal: decap-cms-core.src.actions uses a module listed above it, which is the healthy direction.
decap-cms-core.src.actions uses decap-cms-core.src.valueObjects.AssetProxy, so a change to decap-cms-core.src.valueObjects.AssetProxy can break decap-cms-core.src.actions, while a change to decap-cms-core.src.actions can't break decap-cms-core.src.valueObjects.AssetProxy.
Position
Below the diagonal: decap-cms-core.src.actions uses a module listed above it, which is the healthy direction.
decap-cms-core.src.actions uses decap-cms-core.src.valueObjects.Entry, so a change to decap-cms-core.src.valueObjects.Entry can break decap-cms-core.src.actions, while a change to decap-cms-core.src.actions can't break decap-cms-core.src.valueObjects.Entry.
Position
Below the diagonal: decap-cms-core.src.actions uses a module listed above it, which is the healthy direction.
decap-cms-core.src.actions uses decap-cms-lib-util.src.implementation, so a change to decap-cms-lib-util.src.implementation can break decap-cms-core.src.actions, while a change to decap-cms-core.src.actions can't break decap-cms-lib-util.src.implementation.
Position
Below the diagonal: decap-cms-core.src.actions uses a module listed above it, which is the healthy direction.
26 pairs of types, where a type in decap-cms-core.src.actions uses a type in decap-cms-core.src.types.redux. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
decap-cms-core.src.actions uses decap-cms-core.src.types.redux, so a change to decap-cms-core.src.types.redux can break decap-cms-core.src.actions, while a change to decap-cms-core.src.actions can't break decap-cms-core.src.types.redux.
Position
Below the diagonal: decap-cms-core.src.actions uses a module listed above it, which is the healthy direction.
decap-cms-core.src.actions uses decap-cms-lib-util.src.Cursor, so a change to decap-cms-lib-util.src.Cursor can break decap-cms-core.src.actions, while a change to decap-cms-core.src.actions can't break decap-cms-lib-util.src.Cursor.
Position
Below the diagonal: decap-cms-core.src.actions uses a module listed above it, which is the healthy direction.
decap-cms-core.src.actions uses decap-cms-core.src.backend, so a change to decap-cms-core.src.backend can break decap-cms-core.src.actions, while a change to decap-cms-core.src.actions can't break decap-cms-core.src.backend.
Position
Below the diagonal: decap-cms-core.src.actions uses a module listed above it, which is the healthy direction.
decap-cms-core.src.actions uses decap-cms-lib-util.src, so a change to decap-cms-lib-util.src can break decap-cms-core.src.actions, while a change to decap-cms-core.src.actions can't break decap-cms-lib-util.src.
Position
Below the diagonal: decap-cms-core.src.actions uses a module listed above it, which is the healthy direction.
decap-cms-core.src.lib uses decap-cms-core.src.valueObjects.Entry, so a change to decap-cms-core.src.valueObjects.Entry can break decap-cms-core.src.lib, while a change to decap-cms-core.src.lib can't break decap-cms-core.src.valueObjects.Entry.
Position
Below the diagonal: decap-cms-core.src.lib uses a module listed above it, which is the healthy direction.
decap-cms-core.src.lib uses decap-cms-lib-util.src.implementation, so a change to decap-cms-lib-util.src.implementation can break decap-cms-core.src.lib, while a change to decap-cms-core.src.lib can't break decap-cms-lib-util.src.implementation.
Position
Below the diagonal: decap-cms-core.src.lib uses a module listed above it, which is the healthy direction.
decap-cms-core.src.lib uses decap-cms-core.src.types.redux, so a change to decap-cms-core.src.types.redux can break decap-cms-core.src.lib, while a change to decap-cms-core.src.lib can't break decap-cms-core.src.types.redux.
Position
Below the diagonal: decap-cms-core.src.lib uses a module listed above it, which is the healthy direction.
decap-cms-core.src.lib uses decap-cms-lib-util.src, so a change to decap-cms-lib-util.src can break decap-cms-core.src.lib, while a change to decap-cms-core.src.lib can't break decap-cms-lib-util.src.
Position
Below the diagonal: decap-cms-core.src.lib uses a module listed above it, which is the healthy direction.
decap-cms-lib-turbo.src.session uses decap-cms-lib-util.src, so a change to decap-cms-lib-util.src can break decap-cms-lib-turbo.src.session, while a change to decap-cms-lib-turbo.src.session can't break decap-cms-lib-util.src.
Position
Below the diagonal: decap-cms-lib-turbo.src.session uses a module listed above it, which is the healthy direction.
decap.src uses decap-cms-core.src.valueObjects.Entry, so a change to decap-cms-core.src.valueObjects.Entry can break decap.src, while a change to decap.src can't break decap-cms-core.src.valueObjects.Entry.
Position
Below the diagonal: decap.src uses a module listed above it, which is the healthy direction.
decap.src uses decap-turbo-api.src, so a change to decap-turbo-api.src can break decap.src, while a change to decap.src can't break decap-turbo-api.src.
Position
Below the diagonal: decap.src uses a module listed above it, which is the healthy direction.
decap.src uses decap-cms-lib-util.src, so a change to decap-cms-lib-util.src can break decap.src, while a change to decap.src can't break decap-cms-lib-util.src.
Position
Below the diagonal: decap.src uses a module listed above it, which is the healthy direction.
decap-cms-backend-azure.src.implementation uses decap-cms-core.src.valueObjects.AssetProxy, so a change to decap-cms-core.src.valueObjects.AssetProxy can break decap-cms-backend-azure.src.implementation, while a change to decap-cms-backend-azure.src.implementation can't break decap-cms-core.src.valueObjects.AssetProxy.
Position
Below the diagonal: decap-cms-backend-azure.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-azure.src.implementation uses decap-cms-lib-util.src.implementation, so a change to decap-cms-lib-util.src.implementation can break decap-cms-backend-azure.src.implementation, while a change to decap-cms-backend-azure.src.implementation can't break decap-cms-lib-util.src.implementation.
Position
Below the diagonal: decap-cms-backend-azure.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-azure.src.implementation uses decap-cms-core.src.types.redux, so a change to decap-cms-core.src.types.redux can break decap-cms-backend-azure.src.implementation, while a change to decap-cms-backend-azure.src.implementation can't break decap-cms-core.src.types.redux.
Position
Below the diagonal: decap-cms-backend-azure.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-azure.src.implementation uses decap-cms-lib-util.src, so a change to decap-cms-lib-util.src can break decap-cms-backend-azure.src.implementation, while a change to decap-cms-backend-azure.src.implementation can't break decap-cms-lib-util.src.
Position
Below the diagonal: decap-cms-backend-azure.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-azure.src.implementation uses decap-cms-backend-azure.src.API, so a change to decap-cms-backend-azure.src.API can break decap-cms-backend-azure.src.implementation, while a change to decap-cms-backend-azure.src.implementation can't break decap-cms-backend-azure.src.API.
Position
Below the diagonal: decap-cms-backend-azure.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-azure.src.implementation uses decap-cms-backend-bitbucket.src.API, so a change to decap-cms-backend-bitbucket.src.API can break decap-cms-backend-azure.src.implementation, while a change to decap-cms-backend-azure.src.implementation can't break decap-cms-backend-bitbucket.src.API.
Position
Below the diagonal: decap-cms-backend-azure.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-bitbucket.src.implementation uses decap-cms-core.src.valueObjects.AssetProxy, so a change to decap-cms-core.src.valueObjects.AssetProxy can break decap-cms-backend-bitbucket.src.implementation, while a change to decap-cms-backend-bitbucket.src.implementation can't break decap-cms-core.src.valueObjects.AssetProxy.
Position
Below the diagonal: decap-cms-backend-bitbucket.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-bitbucket.src.implementation uses decap-cms-lib-util.src.API, so a change to decap-cms-lib-util.src.API can break decap-cms-backend-bitbucket.src.implementation, while a change to decap-cms-backend-bitbucket.src.implementation can't break decap-cms-lib-util.src.API.
Position
Below the diagonal: decap-cms-backend-bitbucket.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-bitbucket.src.implementation uses decap-cms-lib-util.src.implementation, so a change to decap-cms-lib-util.src.implementation can break decap-cms-backend-bitbucket.src.implementation, while a change to decap-cms-backend-bitbucket.src.implementation can't break decap-cms-lib-util.src.implementation.
Position
Below the diagonal: decap-cms-backend-bitbucket.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-bitbucket.src.implementation uses decap-cms-core.src.types.redux, so a change to decap-cms-core.src.types.redux can break decap-cms-backend-bitbucket.src.implementation, while a change to decap-cms-backend-bitbucket.src.implementation can't break decap-cms-core.src.types.redux.
Position
Below the diagonal: decap-cms-backend-bitbucket.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-bitbucket.src.implementation uses decap-cms-lib-util.src.Cursor, so a change to decap-cms-lib-util.src.Cursor can break decap-cms-backend-bitbucket.src.implementation, while a change to decap-cms-backend-bitbucket.src.implementation can't break decap-cms-lib-util.src.Cursor.
Position
Below the diagonal: decap-cms-backend-bitbucket.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-bitbucket.src.implementation uses decap-cms-lib-util.src, so a change to decap-cms-lib-util.src can break decap-cms-backend-bitbucket.src.implementation, while a change to decap-cms-backend-bitbucket.src.implementation can't break decap-cms-lib-util.src.
Position
Below the diagonal: decap-cms-backend-bitbucket.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-bitbucket.src.implementation uses decap-cms-backend-bitbucket.src.API, so a change to decap-cms-backend-bitbucket.src.API can break decap-cms-backend-bitbucket.src.implementation, while a change to decap-cms-backend-bitbucket.src.implementation can't break decap-cms-backend-bitbucket.src.API.
Position
Below the diagonal: decap-cms-backend-bitbucket.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-forgejo.src.API uses decap-cms-core.src.valueObjects.Entry, so a change to decap-cms-core.src.valueObjects.Entry can break decap-cms-backend-forgejo.src.API, while a change to decap-cms-backend-forgejo.src.API can't break decap-cms-core.src.valueObjects.Entry.
Position
Below the diagonal: decap-cms-backend-forgejo.src.API uses a module listed above it, which is the healthy direction.
decap-cms-backend-forgejo.src.API uses decap-cms-lib-util.src.API, so a change to decap-cms-lib-util.src.API can break decap-cms-backend-forgejo.src.API, while a change to decap-cms-backend-forgejo.src.API can't break decap-cms-lib-util.src.API.
Position
Below the diagonal: decap-cms-backend-forgejo.src.API uses a module listed above it, which is the healthy direction.
decap-cms-backend-forgejo.src.API uses decap-cms-lib-util.src, so a change to decap-cms-lib-util.src can break decap-cms-backend-forgejo.src.API, while a change to decap-cms-backend-forgejo.src.API can't break decap-cms-lib-util.src.
Position
Below the diagonal: decap-cms-backend-forgejo.src.API uses a module listed above it, which is the healthy direction.
decap-cms-backend-forgejo.src.API uses decap-cms-backend-bitbucket.src.API, so a change to decap-cms-backend-bitbucket.src.API can break decap-cms-backend-forgejo.src.API, while a change to decap-cms-backend-forgejo.src.API can't break decap-cms-backend-bitbucket.src.API.
Position
Below the diagonal: decap-cms-backend-forgejo.src.API uses a module listed above it, which is the healthy direction.
decap-cms-backend-forgejo.src.implementation uses decap-cms-core.src.valueObjects.AssetProxy, so a change to decap-cms-core.src.valueObjects.AssetProxy can break decap-cms-backend-forgejo.src.implementation, while a change to decap-cms-backend-forgejo.src.implementation can't break decap-cms-core.src.valueObjects.AssetProxy.
Position
Below the diagonal: decap-cms-backend-forgejo.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-forgejo.src.implementation uses decap-cms-lib-util.src.implementation, so a change to decap-cms-lib-util.src.implementation can break decap-cms-backend-forgejo.src.implementation, while a change to decap-cms-backend-forgejo.src.implementation can't break decap-cms-lib-util.src.implementation.
Position
Below the diagonal: decap-cms-backend-forgejo.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-forgejo.src.implementation uses decap-cms-core.src.types.redux, so a change to decap-cms-core.src.types.redux can break decap-cms-backend-forgejo.src.implementation, while a change to decap-cms-backend-forgejo.src.implementation can't break decap-cms-core.src.types.redux.
Position
Below the diagonal: decap-cms-backend-forgejo.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-forgejo.src.implementation uses decap-cms-lib-util.src.Cursor, so a change to decap-cms-lib-util.src.Cursor can break decap-cms-backend-forgejo.src.implementation, while a change to decap-cms-backend-forgejo.src.implementation can't break decap-cms-lib-util.src.Cursor.
Position
Below the diagonal: decap-cms-backend-forgejo.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-forgejo.src.implementation uses decap-cms-lib-util.src, so a change to decap-cms-lib-util.src can break decap-cms-backend-forgejo.src.implementation, while a change to decap-cms-backend-forgejo.src.implementation can't break decap-cms-lib-util.src.
Position
Below the diagonal: decap-cms-backend-forgejo.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-forgejo.src.implementation uses decap-cms-backend-bitbucket.src.API, so a change to decap-cms-backend-bitbucket.src.API can break decap-cms-backend-forgejo.src.implementation, while a change to decap-cms-backend-forgejo.src.implementation can't break decap-cms-backend-bitbucket.src.API.
Position
Below the diagonal: decap-cms-backend-forgejo.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-git-gateway.src.implementation uses decap-cms-core.src.valueObjects.AssetProxy, so a change to decap-cms-core.src.valueObjects.AssetProxy can break decap-cms-backend-git-gateway.src.implementation, while a change to decap-cms-backend-git-gateway.src.implementation can't break decap-cms-core.src.valueObjects.AssetProxy.
Position
Below the diagonal: decap-cms-backend-git-gateway.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-git-gateway.src.implementation uses decap-cms-lib-util.src.API, so a change to decap-cms-lib-util.src.API can break decap-cms-backend-git-gateway.src.implementation, while a change to decap-cms-backend-git-gateway.src.implementation can't break decap-cms-lib-util.src.API.
Position
Below the diagonal: decap-cms-backend-git-gateway.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-git-gateway.src.implementation uses decap-cms-lib-util.src.implementation, so a change to decap-cms-lib-util.src.implementation can break decap-cms-backend-git-gateway.src.implementation, while a change to decap-cms-backend-git-gateway.src.implementation can't break decap-cms-lib-util.src.implementation.
Position
Below the diagonal: decap-cms-backend-git-gateway.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-git-gateway.src.implementation uses decap-cms-core.src.types.redux, so a change to decap-cms-core.src.types.redux can break decap-cms-backend-git-gateway.src.implementation, while a change to decap-cms-backend-git-gateway.src.implementation can't break decap-cms-core.src.types.redux.
Position
Below the diagonal: decap-cms-backend-git-gateway.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-git-gateway.src.implementation uses decap-cms-lib-util.src.Cursor, so a change to decap-cms-lib-util.src.Cursor can break decap-cms-backend-git-gateway.src.implementation, while a change to decap-cms-backend-git-gateway.src.implementation can't break decap-cms-lib-util.src.Cursor.
Position
Below the diagonal: decap-cms-backend-git-gateway.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-git-gateway.src.implementation uses decap-cms-lib-util.src, so a change to decap-cms-lib-util.src can break decap-cms-backend-git-gateway.src.implementation, while a change to decap-cms-backend-git-gateway.src.implementation can't break decap-cms-lib-util.src.
Position
Below the diagonal: decap-cms-backend-git-gateway.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-git-gateway.src.implementation uses decap-cms-backend-bitbucket.src.API, so a change to decap-cms-backend-bitbucket.src.API can break decap-cms-backend-git-gateway.src.implementation, while a change to decap-cms-backend-git-gateway.src.implementation can't break decap-cms-backend-bitbucket.src.API.
Position
Below the diagonal: decap-cms-backend-git-gateway.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-gitea.src.implementation uses decap-cms-core.src.valueObjects.AssetProxy, so a change to decap-cms-core.src.valueObjects.AssetProxy can break decap-cms-backend-gitea.src.implementation, while a change to decap-cms-backend-gitea.src.implementation can't break decap-cms-core.src.valueObjects.AssetProxy.
Position
Below the diagonal: decap-cms-backend-gitea.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-gitea.src.implementation uses decap-cms-lib-util.src.implementation, so a change to decap-cms-lib-util.src.implementation can break decap-cms-backend-gitea.src.implementation, while a change to decap-cms-backend-gitea.src.implementation can't break decap-cms-lib-util.src.implementation.
Position
Below the diagonal: decap-cms-backend-gitea.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-gitea.src.implementation uses decap-cms-core.src.types.redux, so a change to decap-cms-core.src.types.redux can break decap-cms-backend-gitea.src.implementation, while a change to decap-cms-backend-gitea.src.implementation can't break decap-cms-core.src.types.redux.
Position
Below the diagonal: decap-cms-backend-gitea.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-gitea.src.implementation uses decap-cms-lib-util.src.Cursor, so a change to decap-cms-lib-util.src.Cursor can break decap-cms-backend-gitea.src.implementation, while a change to decap-cms-backend-gitea.src.implementation can't break decap-cms-lib-util.src.Cursor.
Position
Below the diagonal: decap-cms-backend-gitea.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-gitea.src.implementation uses decap-cms-lib-util.src, so a change to decap-cms-lib-util.src can break decap-cms-backend-gitea.src.implementation, while a change to decap-cms-backend-gitea.src.implementation can't break decap-cms-lib-util.src.
Position
Below the diagonal: decap-cms-backend-gitea.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-gitea.src.implementation uses decap-cms-backend-bitbucket.src.API, so a change to decap-cms-backend-bitbucket.src.API can break decap-cms-backend-gitea.src.implementation, while a change to decap-cms-backend-gitea.src.implementation can't break decap-cms-backend-bitbucket.src.API.
Position
Below the diagonal: decap-cms-backend-gitea.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-github.src.implementation uses decap-cms-core.src.valueObjects.AssetProxy, so a change to decap-cms-core.src.valueObjects.AssetProxy can break decap-cms-backend-github.src.implementation, while a change to decap-cms-backend-github.src.implementation can't break decap-cms-core.src.valueObjects.AssetProxy.
Position
Below the diagonal: decap-cms-backend-github.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-github.src.implementation uses decap-cms-lib-util.src.implementation, so a change to decap-cms-lib-util.src.implementation can break decap-cms-backend-github.src.implementation, while a change to decap-cms-backend-github.src.implementation can't break decap-cms-lib-util.src.implementation.
Position
Below the diagonal: decap-cms-backend-github.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-github.src.implementation uses decap-cms-core.src.types.redux, so a change to decap-cms-core.src.types.redux can break decap-cms-backend-github.src.implementation, while a change to decap-cms-backend-github.src.implementation can't break decap-cms-core.src.types.redux.
Position
Below the diagonal: decap-cms-backend-github.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-github.src.implementation uses decap-cms-lib-util.src.Cursor, so a change to decap-cms-lib-util.src.Cursor can break decap-cms-backend-github.src.implementation, while a change to decap-cms-backend-github.src.implementation can't break decap-cms-lib-util.src.Cursor.
Position
Below the diagonal: decap-cms-backend-github.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-github.src.implementation uses decap-cms-lib-util.src.notesPolling, so a change to decap-cms-lib-util.src.notesPolling can break decap-cms-backend-github.src.implementation, while a change to decap-cms-backend-github.src.implementation can't break decap-cms-lib-util.src.notesPolling.
Position
Below the diagonal: decap-cms-backend-github.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-github.src.implementation uses decap-cms-lib-util.src, so a change to decap-cms-lib-util.src can break decap-cms-backend-github.src.implementation, while a change to decap-cms-backend-github.src.implementation can't break decap-cms-lib-util.src.
Position
Below the diagonal: decap-cms-backend-github.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-github.src.implementation uses decap-cms-backend-bitbucket.src.API, so a change to decap-cms-backend-bitbucket.src.API can break decap-cms-backend-github.src.implementation, while a change to decap-cms-backend-github.src.implementation can't break decap-cms-backend-bitbucket.src.API.
Position
Below the diagonal: decap-cms-backend-github.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-gitlab.src.API uses decap-cms-lib-util.src.API, so a change to decap-cms-lib-util.src.API can break decap-cms-backend-gitlab.src.API, while a change to decap-cms-backend-gitlab.src.API can't break decap-cms-lib-util.src.API.
Position
Below the diagonal: decap-cms-backend-gitlab.src.API uses a module listed above it, which is the healthy direction.
decap-cms-backend-gitlab.src.API uses decap-cms-lib-util.src.Cursor, so a change to decap-cms-lib-util.src.Cursor can break decap-cms-backend-gitlab.src.API, while a change to decap-cms-backend-gitlab.src.API can't break decap-cms-lib-util.src.Cursor.
Position
Below the diagonal: decap-cms-backend-gitlab.src.API uses a module listed above it, which is the healthy direction.
decap-cms-backend-gitlab.src.API uses decap-cms-lib-util.src, so a change to decap-cms-lib-util.src can break decap-cms-backend-gitlab.src.API, while a change to decap-cms-backend-gitlab.src.API can't break decap-cms-lib-util.src.
Position
Below the diagonal: decap-cms-backend-gitlab.src.API uses a module listed above it, which is the healthy direction.
decap-cms-backend-gitlab.src.API uses decap-cms-backend-bitbucket.src.API, so a change to decap-cms-backend-bitbucket.src.API can break decap-cms-backend-gitlab.src.API, while a change to decap-cms-backend-gitlab.src.API can't break decap-cms-backend-bitbucket.src.API.
Position
Below the diagonal: decap-cms-backend-gitlab.src.API uses a module listed above it, which is the healthy direction.
decap-cms-backend-gitlab.src.implementation uses decap-cms-core.src.valueObjects.AssetProxy, so a change to decap-cms-core.src.valueObjects.AssetProxy can break decap-cms-backend-gitlab.src.implementation, while a change to decap-cms-backend-gitlab.src.implementation can't break decap-cms-core.src.valueObjects.AssetProxy.
Position
Below the diagonal: decap-cms-backend-gitlab.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-gitlab.src.implementation uses decap-cms-lib-util.src.API, so a change to decap-cms-lib-util.src.API can break decap-cms-backend-gitlab.src.implementation, while a change to decap-cms-backend-gitlab.src.implementation can't break decap-cms-lib-util.src.API.
Position
Below the diagonal: decap-cms-backend-gitlab.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-gitlab.src.implementation uses decap-cms-lib-util.src.implementation, so a change to decap-cms-lib-util.src.implementation can break decap-cms-backend-gitlab.src.implementation, while a change to decap-cms-backend-gitlab.src.implementation can't break decap-cms-lib-util.src.implementation.
Position
Below the diagonal: decap-cms-backend-gitlab.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-gitlab.src.implementation uses decap-cms-core.src.types.redux, so a change to decap-cms-core.src.types.redux can break decap-cms-backend-gitlab.src.implementation, while a change to decap-cms-backend-gitlab.src.implementation can't break decap-cms-core.src.types.redux.
Position
Below the diagonal: decap-cms-backend-gitlab.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-gitlab.src.implementation uses decap-cms-lib-util.src.Cursor, so a change to decap-cms-lib-util.src.Cursor can break decap-cms-backend-gitlab.src.implementation, while a change to decap-cms-backend-gitlab.src.implementation can't break decap-cms-lib-util.src.Cursor.
Position
Below the diagonal: decap-cms-backend-gitlab.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-gitlab.src.implementation uses decap-cms-lib-util.src.notesPolling, so a change to decap-cms-lib-util.src.notesPolling can break decap-cms-backend-gitlab.src.implementation, while a change to decap-cms-backend-gitlab.src.implementation can't break decap-cms-lib-util.src.notesPolling.
Position
Below the diagonal: decap-cms-backend-gitlab.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-gitlab.src.implementation uses decap-cms-backend-gitlab.src.notesApi, so a change to decap-cms-backend-gitlab.src.notesApi can break decap-cms-backend-gitlab.src.implementation, while a change to decap-cms-backend-gitlab.src.implementation can't break decap-cms-backend-gitlab.src.notesApi.
Position
Below the diagonal: decap-cms-backend-gitlab.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-gitlab.src.implementation uses decap-cms-lib-util.src, so a change to decap-cms-lib-util.src can break decap-cms-backend-gitlab.src.implementation, while a change to decap-cms-backend-gitlab.src.implementation can't break decap-cms-lib-util.src.
Position
Below the diagonal: decap-cms-backend-gitlab.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-gitlab.src.implementation uses decap-cms-backend-bitbucket.src.API, so a change to decap-cms-backend-bitbucket.src.API can break decap-cms-backend-gitlab.src.implementation, while a change to decap-cms-backend-gitlab.src.implementation can't break decap-cms-backend-bitbucket.src.API.
Position
Below the diagonal: decap-cms-backend-gitlab.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-proxy.src.implementation uses decap-cms-core.src.valueObjects.AssetProxy, so a change to decap-cms-core.src.valueObjects.AssetProxy can break decap-cms-backend-proxy.src.implementation, while a change to decap-cms-backend-proxy.src.implementation can't break decap-cms-core.src.valueObjects.AssetProxy.
Position
Below the diagonal: decap-cms-backend-proxy.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-proxy.src.implementation uses decap-cms-lib-util.src.implementation, so a change to decap-cms-lib-util.src.implementation can break decap-cms-backend-proxy.src.implementation, while a change to decap-cms-backend-proxy.src.implementation can't break decap-cms-lib-util.src.implementation.
Position
Below the diagonal: decap-cms-backend-proxy.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-proxy.src.implementation uses decap-cms-lib-util.src, so a change to decap-cms-lib-util.src can break decap-cms-backend-proxy.src.implementation, while a change to decap-cms-backend-proxy.src.implementation can't break decap-cms-lib-util.src.
Position
Below the diagonal: decap-cms-backend-proxy.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-proxy.src.implementation uses decap-cms-backend-bitbucket.src.API, so a change to decap-cms-backend-bitbucket.src.API can break decap-cms-backend-proxy.src.implementation, while a change to decap-cms-backend-proxy.src.implementation can't break decap-cms-backend-bitbucket.src.API.
Position
Below the diagonal: decap-cms-backend-proxy.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-turbo-github.src.implementation uses decap-cms-backend-turbo-github.src.deployWatcher, so a change to decap-cms-backend-turbo-github.src.deployWatcher can break decap-cms-backend-turbo-github.src.implementation, while a change to decap-cms-backend-turbo-github.src.implementation can't break decap-cms-backend-turbo-github.src.deployWatcher.
Position
Below the diagonal: decap-cms-backend-turbo-github.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-turbo-github.src.implementation uses decap-cms-lib-turbo.src.editorAttach, so a change to decap-cms-lib-turbo.src.editorAttach can break decap-cms-backend-turbo-github.src.implementation, while a change to decap-cms-backend-turbo-github.src.implementation can't break decap-cms-lib-turbo.src.editorAttach.
Position
Below the diagonal: decap-cms-backend-turbo-github.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-turbo-github.src.implementation uses decap-cms-lib-turbo.src.requestCoalescer, so a change to decap-cms-lib-turbo.src.requestCoalescer can break decap-cms-backend-turbo-github.src.implementation, while a change to decap-cms-backend-turbo-github.src.implementation can't break decap-cms-lib-turbo.src.requestCoalescer.
Position
Below the diagonal: decap-cms-backend-turbo-github.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-turbo-github.src.implementation uses decap-cms-lib-turbo.src.saveEvent, so a change to decap-cms-lib-turbo.src.saveEvent can break decap-cms-backend-turbo-github.src.implementation, while a change to decap-cms-backend-turbo-github.src.implementation can't break decap-cms-lib-turbo.src.saveEvent.
Position
Below the diagonal: decap-cms-backend-turbo-github.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-turbo-github.src.implementation uses decap-cms-lib-util.src.implementation, so a change to decap-cms-lib-util.src.implementation can break decap-cms-backend-turbo-github.src.implementation, while a change to decap-cms-backend-turbo-github.src.implementation can't break decap-cms-lib-util.src.implementation.
Position
Below the diagonal: decap-cms-backend-turbo-github.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-turbo-github.src.implementation uses decap-cms-lib-util.src, so a change to decap-cms-lib-util.src can break decap-cms-backend-turbo-github.src.implementation, while a change to decap-cms-backend-turbo-github.src.implementation can't break decap-cms-lib-util.src.
Position
Below the diagonal: decap-cms-backend-turbo-github.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-turbo-github.src.implementation uses decap-cms-backend-bitbucket.src.API, so a change to decap-cms-backend-bitbucket.src.API can break decap-cms-backend-turbo-github.src.implementation, while a change to decap-cms-backend-turbo-github.src.implementation can't break decap-cms-backend-bitbucket.src.API.
Position
Below the diagonal: decap-cms-backend-turbo-github.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-turbo-github.src.implementation uses decap-cms-lib-turbo.src.session, so a change to decap-cms-lib-turbo.src.session can break decap-cms-backend-turbo-github.src.implementation, while a change to decap-cms-backend-turbo-github.src.implementation can't break decap-cms-lib-turbo.src.session.
Position
Below the diagonal: decap-cms-backend-turbo-github.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-turbo-gitlab.src.implementation uses decap-cms-lib-turbo.src.editorAttach, so a change to decap-cms-lib-turbo.src.editorAttach can break decap-cms-backend-turbo-gitlab.src.implementation, while a change to decap-cms-backend-turbo-gitlab.src.implementation can't break decap-cms-lib-turbo.src.editorAttach.
Position
Below the diagonal: decap-cms-backend-turbo-gitlab.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-turbo-gitlab.src.implementation uses decap-cms-lib-turbo.src.requestCoalescer, so a change to decap-cms-lib-turbo.src.requestCoalescer can break decap-cms-backend-turbo-gitlab.src.implementation, while a change to decap-cms-backend-turbo-gitlab.src.implementation can't break decap-cms-lib-turbo.src.requestCoalescer.
Position
Below the diagonal: decap-cms-backend-turbo-gitlab.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-turbo-gitlab.src.implementation uses decap-cms-lib-turbo.src.saveEvent, so a change to decap-cms-lib-turbo.src.saveEvent can break decap-cms-backend-turbo-gitlab.src.implementation, while a change to decap-cms-backend-turbo-gitlab.src.implementation can't break decap-cms-lib-turbo.src.saveEvent.
Position
Below the diagonal: decap-cms-backend-turbo-gitlab.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-turbo-gitlab.src.implementation uses decap-cms-lib-util.src, so a change to decap-cms-lib-util.src can break decap-cms-backend-turbo-gitlab.src.implementation, while a change to decap-cms-backend-turbo-gitlab.src.implementation can't break decap-cms-lib-util.src.
Position
Below the diagonal: decap-cms-backend-turbo-gitlab.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-turbo-gitlab.src.implementation uses decap-cms-backend-bitbucket.src.API, so a change to decap-cms-backend-bitbucket.src.API can break decap-cms-backend-turbo-gitlab.src.implementation, while a change to decap-cms-backend-turbo-gitlab.src.implementation can't break decap-cms-backend-bitbucket.src.API.
Position
Below the diagonal: decap-cms-backend-turbo-gitlab.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-backend-turbo-gitlab.src.implementation uses decap-cms-lib-turbo.src.session, so a change to decap-cms-lib-turbo.src.session can break decap-cms-backend-turbo-gitlab.src.implementation, while a change to decap-cms-backend-turbo-gitlab.src.implementation can't break decap-cms-lib-turbo.src.session.
Position
Below the diagonal: decap-cms-backend-turbo-gitlab.src.implementation uses a module listed above it, which is the healthy direction.
decap-cms-lib-turbo.src uses decap-cms-lib-turbo.src.editorAttach, so a change to decap-cms-lib-turbo.src.editorAttach can break decap-cms-lib-turbo.src, while a change to decap-cms-lib-turbo.src can't break decap-cms-lib-turbo.src.editorAttach.
Position
Below the diagonal: decap-cms-lib-turbo.src uses a module listed above it, which is the healthy direction.
decap-cms-lib-turbo.src uses decap-cms-lib-turbo.src.requestCoalescer, so a change to decap-cms-lib-turbo.src.requestCoalescer can break decap-cms-lib-turbo.src, while a change to decap-cms-lib-turbo.src can't break decap-cms-lib-turbo.src.requestCoalescer.
Position
Below the diagonal: decap-cms-lib-turbo.src uses a module listed above it, which is the healthy direction.
decap-cms-lib-turbo.src uses decap-cms-lib-turbo.src.saveEvent, so a change to decap-cms-lib-turbo.src.saveEvent can break decap-cms-lib-turbo.src, while a change to decap-cms-lib-turbo.src can't break decap-cms-lib-turbo.src.saveEvent.
Position
Below the diagonal: decap-cms-lib-turbo.src uses a module listed above it, which is the healthy direction.
decap-cms-lib-turbo.src uses decap-cms-backend-bitbucket.src.API, so a change to decap-cms-backend-bitbucket.src.API can break decap-cms-lib-turbo.src, while a change to decap-cms-lib-turbo.src can't break decap-cms-backend-bitbucket.src.API.
Position
Below the diagonal: decap-cms-lib-turbo.src uses a module listed above it, which is the healthy direction.
decap-cms-backend-gitea.src.API uses decap-cms-core.src.valueObjects.Entry, so a change to decap-cms-core.src.valueObjects.Entry can break decap-cms-backend-gitea.src.API, while a change to decap-cms-backend-gitea.src.API can't break decap-cms-core.src.valueObjects.Entry.
Position
Below the diagonal: decap-cms-backend-gitea.src.API uses a module listed above it, which is the healthy direction.
decap-cms-backend-gitea.src.API uses decap-cms-lib-util.src.API, so a change to decap-cms-lib-util.src.API can break decap-cms-backend-gitea.src.API, while a change to decap-cms-backend-gitea.src.API can't break decap-cms-lib-util.src.API.
Position
Below the diagonal: decap-cms-backend-gitea.src.API uses a module listed above it, which is the healthy direction.
decap-cms-backend-gitea.src.API uses decap-cms-lib-util.src, so a change to decap-cms-lib-util.src can break decap-cms-backend-gitea.src.API, while a change to decap-cms-backend-gitea.src.API can't break decap-cms-lib-util.src.
Position
Below the diagonal: decap-cms-backend-gitea.src.API uses a module listed above it, which is the healthy direction.
decap-cms-backend-gitea.src.API uses decap-cms-backend-bitbucket.src.API, so a change to decap-cms-backend-bitbucket.src.API can break decap-cms-backend-gitea.src.API, while a change to decap-cms-backend-gitea.src.API can't break decap-cms-backend-bitbucket.src.API.
Position
Below the diagonal: decap-cms-backend-gitea.src.API uses a module listed above it, which is the healthy direction.
decap-cms-backend-gitea.src.API uses decap-cms-backend-forgejo.src.API, so a change to decap-cms-backend-forgejo.src.API can break decap-cms-backend-gitea.src.API, while a change to decap-cms-backend-gitea.src.API can't break decap-cms-backend-forgejo.src.API.
Position
Below the diagonal: decap-cms-backend-gitea.src.API uses a module listed above it, which is the healthy direction.
decap-cms-backend-github.src.API uses decap-cms-core.src.valueObjects.Entry, so a change to decap-cms-core.src.valueObjects.Entry can break decap-cms-backend-github.src.API, while a change to decap-cms-backend-github.src.API can't break decap-cms-core.src.valueObjects.Entry.
Position
Below the diagonal: decap-cms-backend-github.src.API uses a module listed above it, which is the healthy direction.
decap-cms-backend-github.src.API uses decap-cms-lib-util.src.API, so a change to decap-cms-lib-util.src.API can break decap-cms-backend-github.src.API, while a change to decap-cms-backend-github.src.API can't break decap-cms-lib-util.src.API.
Position
Below the diagonal: decap-cms-backend-github.src.API uses a module listed above it, which is the healthy direction.
decap-cms-backend-github.src.API uses decap-cms-lib-util.src.implementation, so a change to decap-cms-lib-util.src.implementation can break decap-cms-backend-github.src.API, while a change to decap-cms-backend-github.src.API can't break decap-cms-lib-util.src.implementation.
Position
Below the diagonal: decap-cms-backend-github.src.API uses a module listed above it, which is the healthy direction.
decap-cms-backend-github.src.API uses decap-cms-lib-util.src, so a change to decap-cms-lib-util.src can break decap-cms-backend-github.src.API, while a change to decap-cms-backend-github.src.API can't break decap-cms-lib-util.src.
Position
Below the diagonal: decap-cms-backend-github.src.API uses a module listed above it, which is the healthy direction.
decap-cms-backend-github.src.API uses decap-cms-backend-bitbucket.src.API, so a change to decap-cms-backend-bitbucket.src.API can break decap-cms-backend-github.src.API, while a change to decap-cms-backend-github.src.API can't break decap-cms-backend-bitbucket.src.API.
Position
Below the diagonal: decap-cms-backend-github.src.API uses a module listed above it, which is the healthy direction.
decap-cms-backend-github.src.API uses decap-cms-backend-forgejo.src.API, so a change to decap-cms-backend-forgejo.src.API can break decap-cms-backend-github.src.API, while a change to decap-cms-backend-github.src.API can't break decap-cms-backend-forgejo.src.API.
Position
Below the diagonal: decap-cms-backend-github.src.API uses a module listed above it, which is the healthy direction.
decap-cms-backend-github.src.GraphQLAPI uses decap-cms-backend-azure.src.API, so a change to decap-cms-backend-azure.src.API can break decap-cms-backend-github.src.GraphQLAPI, while a change to decap-cms-backend-github.src.GraphQLAPI can't break decap-cms-backend-azure.src.API.
Position
Below the diagonal: decap-cms-backend-github.src.GraphQLAPI uses a module listed above it, which is the healthy direction.
decap-cms-backend-github.src.GraphQLAPI uses decap-cms-backend-bitbucket.src.API, so a change to decap-cms-backend-bitbucket.src.API can break decap-cms-backend-github.src.GraphQLAPI, while a change to decap-cms-backend-github.src.GraphQLAPI can't break decap-cms-backend-bitbucket.src.API.
Position
Below the diagonal: decap-cms-backend-github.src.GraphQLAPI uses a module listed above it, which is the healthy direction.
decap-cms-backend-github.src.GraphQLAPI uses decap-cms-backend-forgejo.src.API, so a change to decap-cms-backend-forgejo.src.API can break decap-cms-backend-github.src.GraphQLAPI, while a change to decap-cms-backend-github.src.GraphQLAPI can't break decap-cms-backend-forgejo.src.API.
Position
Below the diagonal: decap-cms-backend-github.src.GraphQLAPI uses a module listed above it, which is the healthy direction.
decap-cms-backend-github.src.GraphQLAPI uses decap-cms-backend-github.src.API, so a change to decap-cms-backend-github.src.API can break decap-cms-backend-github.src.GraphQLAPI, while a change to decap-cms-backend-github.src.GraphQLAPI can't break decap-cms-backend-github.src.API.
Position
Below the diagonal: decap-cms-backend-github.src.GraphQLAPI uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 42% · Weak · gated by R1, X4 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
62
High / Critical
A03:2025 — Software Supply Chain Failures
46
High / Critical
A07:2025 — Authentication Failures
4
High / Critical
Roadmap
Top priorities: Bring the 35 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with S3Widget.S3Widget (cyclomatic 43), entryDraft.entryDraftReducer (cyclomatic 42), config.applyDefaults (cyclomatic 40); Interpolated log message defeats structured logging; Resolve the 36 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (36).
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Bring the 35 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with S3Widget.S3Widget (cyclomatic 43), entryDraft.entryDraftReducer (cyclomatic 42), config.applyDefaults (cyclomatic 40).
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.
Bound every outbound call: pass `signal: AbortSignal.timeout(ms)` to `fetch`, set `timeout` on the axios instance (`axios.create({ timeout })`), and add retries with back-off (`axios-retry`, `p-retry`) and a breaker (`opossum`, `cockatiel`) around dependencies that fail.
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 — 66
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 — 478
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 — 514
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 10
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 73 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 — 73 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, 972 of 1058 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 the repository root could not reach github.com, which the analyzer sandbox's egress allowlist does not carry (Error: Error when performing the request to https://registry.npmjs.org/pnpm/-/pnpm-11.12.0.tgz; for troubleshooting help, see https://github.com/nodejs/corepack…), 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 the repository root could not reach github.com, which the analyzer sandbox's egress allowlist does not carry (Error: Error when performing the request to https://registry.npmjs.org/pnpm/-/pnpm-11.12.0.tgz; for troubleshooting help, see https://github.com/nodejs/corepack…), 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 jest suite in the repository root was NOT MEASURED: the dependency install for the repository root could not reach github.com, which the analyzer sandbox's egress allowlist does not carry (Error: Error when performing the request to https://registry.npmjs.org/pnpm/-/pnpm-11.12.0.tgz; for troubleshooting help, see https://github.com/nodejs/corepack…), 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.
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 jest suite in packages/decap/ was NOT MEASURED: the dependency install for packages/decap/ could not reach github.com, which the analyzer sandbox's egress allowlist does not carry (Error: Error when performing the request to https://registry.npmjs.org/pnpm/-/pnpm-11.12.0.tgz; for troubleshooting help, see https://github.com/nodejs/corepack…), 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.
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 jest suite in packages/decap-cms-media-library-s3/ was NOT MEASURED: the dependency install for packages/decap-cms-media-library-s3/ could not reach github.com, which the analyzer sandbox's egress allowlist does not carry (Error: Error when performing the request to https://registry.npmjs.org/pnpm/-/pnpm-11.12.0.tgz; for troubleshooting help, see https://github.com/nodejs/corepack…), 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.
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 on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. 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/decap-turbo-api/src/index.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.
AXB2 Runtime readiness — 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. A program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. (rule: missing-tool). The renderer reported: the dev server (`npm run start`) exited before it served a page. Likely cause (our sandbox): a program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. Last output: "> start / > pnpm run develop / sh: 1: pnpm: not found" No runtime evidence was gathered.
AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (start). the dev server (`npm run start`) exited before it served a page. Likely cause (our sandbox): a program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. Last output: "> start / > pnpm run develop / sh: 1: pnpm: not found" No runtime evidence was gathered.
C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'localforage' is imported (packages/decap-cms-lib-util/src/localForage.ts:1), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'localforage' is imported (packages/decap-cms-lib-util/src/localForage.ts:1), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'localforage' is imported (packages/decap-cms-lib-util/src/localForage.ts:1), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'localforage' is imported (packages/decap-cms-lib-util/src/localForage.ts:1), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
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. 115 further occurrence(s) are not listed individually; the score already reflects all 155.
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. 38 further occurrence(s) are not listed individually; the score already reflects all 78.
R4 Test Coverage — 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. 58 further occurrence(s) are not listed individually; the score already reflects all 98.
X10 Duplicated predicate — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 8 further occurrence(s) are not listed individually; the score already reflects all 48.
Repo exclusion declarations: 12 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
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.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
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.
47 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was S3Widget.S3Widget at 43. A further 5 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 renderers.Element at 22 — they are counted neither in the figure above nor in this dimension's score. 5 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: packages/decap-cms-widget-markdown/src/MarkdownControl/renderers.js (Element at 22), packages/decap-cms-widget-markdown/src/MarkdownControl/renderers.js (renderers.Element at 22), REDACTED (entries.entries at 21), packages/decap-cms-backend-turbo-github/src/implementation.tsx (DecapTurboGitHubBackend.setScopedApiRequestBuilder at 20), packages/decap-cms-widget-markdown/src/MarkdownControl/plugins/lists/withLists.js (withLists.withLists at 17). 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.
+ 28 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 35 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with S3Widget.S3Widget (cyclomatic 43), entryDraft.entryDraftReducer (cyclomatic 42), config.applyDefaults (cyclomatic 40). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 35 together lifts Cyclomatic Complexity from 6.9 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
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.
+ 42 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 7 bodies over 30 down to 30 or less in Cognitive Complexity — start with config.applyDefaults (cognitive 69), index.validateInput (cognitive 63), S3Widget.S3Widget (cognitive 51). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 7 together lifts Cognitive Complexity from 6.4 to about 7.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes7.6 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 15 FileTooLong finding(s) in God Classes — start with API.ts (5), REDACTED (2), implementation.ts (2). — One of this dimension's main actionable groups (15 warning-level).
Resolve the 14 FunctionTooLong finding(s) in God Classes — start with index.ts (3), slateRemark.js (2), VisualEditor.js (2). — One of this dimension's main actionable groups (14 warning-level).
Resolve the 13 TooManyMethods finding(s) in God Classes — start with API.ts (5), implementation.ts (3), implementation.tsx (2). — One of this dimension's main actionable groups (13 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling8.6 / 10Strong✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
47 production modules (npm), 0 dependency cycle(s), 4 unstable depended-on module(s). Read from the build's own module declarations; 3 module(s) off the main sequence, with abstractness counted on 18 of the 47 (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).
Resolve the 3 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 1 Unstable project decap-cms-app finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Unstable project decap-cms-backend-aws-cognito-github-proxy finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 3 Low cohesion finding(s) in Cohesion (LCOM4) — start with implementation.ts, GitHubAPI.ts, EditorControlPane.js. — 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 Quality10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
0 skipped, 113 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 2301 tests (1 harness-style project(s) excluded from the assertion penalty).
No direct assertions: successfully loads · ×113cypress/e2e/editorial_workflow_spec_test_backend.js:57
Mock-dominated test: backs off quietly when the server refuses · ×24packages/decap-cms-lib-turbo/src/__tests__/editorBridge.spec.ts:173
✓ On the Gold path — maintain.
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.
79 outdated direct production npm dependency(ies) of 138 graded, 0 pinning defect(s), across 39 package.json (39 of them the product) and 1 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 12 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 36 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (36). — One of this dimension's main actionable groups (36 recommendation-level).
Resolve the 24 Outdated (npm) finding(s) in Dependency Hygiene — start with package.json (24). — One of this dimension's main actionable groups (24 recommendation-level).
Resolve the 13 Deprecated finding(s) in Dependency Hygiene — start with package.json (13). — One of this dimension's main actionable groups (13 warning-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 953 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 953 package(s) this repository's committed lockfile installs for a consumer — its 138 production, optional and peer dependency(ies), across 39 product package.json manifest(s), and everything those install in turn. Its 145 `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. 2 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. 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 (14×21=294); packages/decap-cms-core/src/reducers/editorialWorkflow.ts (9×25=225); packages/decap/src/index.ts (5×27=135) Repeated repair below the complexity floor: packages/decap-cms-core/src/actions/editorialWorkflow.ts (6 of 10 changes were fixes); packages/decap-cms-widget-relation/src/RelationControl.js (6 of 7 changes were fixes); packages/decap/src/login.ts (4 of 4 changes were fixes)
Resolve the 10 Hotspot finding(s) in Churn × Complexity Hotspots — start with REDACTED, editorialWorkflow.ts, index.ts. — One of this dimension's main actionable groups (10 warning-level).
Resolve the 3 Repeated repair finding(s) in Churn × Complexity Hotspots — start with editorialWorkflow.ts, RelationControl.js, login.ts. — One of this dimension's main actionable groups (3 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 Factor8.0 / 10Strong✓ 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.
48 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is packages/decap-turbo-api/src/index.ts. Counted over 239 of the 581 production source files in this repository: 340 are under the ~2,400-byte size floor this dimension measures over, and the remaining 2 have no attributable history left to measure.
Off-boarding risk: anonymized user #1
Further sole-owners (lower concentration)
What to do
Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
15 deducted task-comment markers across 35039 LoC (0.0/KLoC) → score 9.9. 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.
TodoComment · ×15REDACTED:893
What to do
Resolve the 15 TodoComment finding(s) in Explicit Debt — start with media.spec.ts (6), implementation.ts (3), REDACTED (2). — One of this dimension's main actionable groups (15 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. 47 document(s) read across 48 unit(s).
Documentation: no build, run or usage example · ×33packages/decap-cms/README.md:1
What to do
Resolve the 33 Documentation finding(s) in Documentation Quality — start with README.md (33). — One of this dimension's main actionable groups (33 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.
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with package.json. — 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 58 declarations measured against a convention their peers follow.
`appID` spells `ID` where 68 names in the project spell it `Id`packages/decap-cms-backend-gitlab/src/implementation.ts:86
`controlID` spells `ID` where 68 names in the project spell it `Id`packages/decap-cms-core/src/actions/mediaLibrary.ts:138
What to do
Resolve the 1 `appID` spells `ID` where 68 names in the project spell it `Id` finding(s) in Naming Consistency — start with implementation.ts. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 `controlID` spells `ID` where 68 names in the project spell it `Id` finding(s) in Naming Consistency — start with mediaLibrary.ts. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d21_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether 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.
1 domain type(s) cross context boundaries across 43 contexts; they are measured and withheld (not published, not scored). Contexts: decap, decap-cms-app, decap-cms-backend-aws-cognito-github-proxy, decap-cms-backend-azure, decap-cms-backend-bitbucket, decap-cms-backend-forgejo, decap-cms-backend-git-gateway, decap-cms-backend-gitea, decap-cms-backend-github, decap-cms-backend-gitlab, decap-cms-backend-proxy, decap-cms-backend-test and 31 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.
14 of 1179 judged comments only repeat the code they sit on (1.2 %). 25 comment(s) in another language or script were not judged.
redundant comment · ×14cypress/utils/steps.js:580
doc comments repeat the names · ×3packages/decap-cms-backend-github/src/API.ts:1856
What to do
Resolve the 14 redundant comment finding(s) in Comment Value — start with API.ts (2), API.spec.js (2), steps.js. — One of this dimension's main actionable groups (14 recommendation-level).
Detailed fixes: d24_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.
43 % of calls cross a namespace and 0 % go through an interface, but 64 % of collaborators are co-located — so following a call takes several hops. 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.
3 finding(s): 0 critical, 3 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 3 REDACTED finding(s) in Secrets (history) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 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).
62 finding(s): 0 critical, 43 high, 18 medium, 1 low. 28 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 43 file(s) — `cypress/fixtures/Git Gateway (GitHub) Backend Editorial Workflow__can change status on and publish multiple entries.json`, `cypress/fixtures/Git Gateway (GitHub) Backend Editorial Workflow__can change workflow status.json`, `cypress/fixtures/Git Gateway (GitHub) Backend Editorial Workflow__can create an entry.json`, `cypress/fixtures/Git Gateway (GitHub) Backend Editorial Workflow__can delete an entry.json`, `cypress/fixtures/Git Gateway (GitHub) Backend Editorial Workflow__can publish an editorial workflow entry.json`, … (+38 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
+ 11 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED. — One of this dimension's main actionable groups (5 issue-level).
Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED. — One of this dimension's main actionable groups (4 issue-level).
No action in Static Analysis (SAST) — all 28 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (28 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether 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 22 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (22). — One of this dimension's main actionable groups (22 warning-level).
Resolve the 10 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (10). — One of this dimension's main actionable groups (10 issue-level).
Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d30_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.
101 of 241 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is packages/decap-cms-locales/src/th/index.js. Counted over 241 of the 581 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Resolve the 99 Orphaned file finding(s) in Knowledge Freshness — start with REDACTED (34), AuthenticationPage.js (4), Toolbar.js (2). — One of this dimension's main actionable groups (99 recommendation-level).
Resolve the 2 Orphaned knowledge finding(s) in Knowledge Freshness — start with REDACTED, implementation.ts. — One of this dimension's main actionable groups (2 issue-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.
Resolve the 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with implementation.ts. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
+ 3 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.
Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.
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 15 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.
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.
`decap-cms-app` is a Application project but references `decap-cms-ui-auth`, a Web project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one. — packages/decap-cms-app/package.json:55
`decap-cms-app` is a Application project but references `decap-cms-ui-default`, a Web project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one. — packages/decap-cms-app/package.json:56
`decap-cms-core` is a Domain project but references `decap-cms-ui-default`, a Web project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one. — packages/decap-cms-core/package.json:87
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.
`StaticallyTypedRecord` declares 19 required operations: `get`, `set`, `has`, `delete`, `getIn`, `getIn`, `getIn`, `setIn`, `setIn`, `toJS`, `isEmpty`, `some`, `mapKeys`, `find`, `filter`, `valueSeq`, `map`, `keySeq`, `withMutations`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. Those 19 declarations carry 16 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 16 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — packages/decap-cms-core/src/types/immutable.ts:11
`Implementation` declares 22 required operations: `authComponent`, `restoreUser`, `authenticate`, `logout`, `getToken`, `getEntry`, `entriesByFolder`, `entriesByFiles`, `getMedia`, `getMediaFile`, `persistEntry`, `persistMedia`, `deleteFiles`, `unpublishedEntries`, `unpublishedEntry`, `unpublishedEntryDataFile`, `unpublishedEntryMediaFile`, `updateUnpublishedEntryStatus`, `publishUnpublishedEntry`, `deleteUnpublishedEntry`, `getDeployPreview`, `status`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — packages/decap-cms-lib-util/src/implementation.ts:202
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
Do you agree with this assessment?
C2 · Access Controls7.0 / 10Strong✓ Tool-verified
Other · Security — Whether access is authorized by default — a framework authorization attribute/decorator or policy, or imperative guard methods (throw-on-violation) called from handlers.
Method: Roslyn scan: [Authorize] usage and authorization policies, plus imperative throw-on-violation guard methods detected via syntax. Deterministic.
Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect. — functions/publish.js:80
What to do
Name the access rules — roles/permissions declared once (a @Roles/@Permissions decorator with its guard, a CASL ability, a casbin model, or Supabase CREATE POLICY) and consulted where access is checked, so the rule set is reviewable and testable on its own.
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.
`doVerify` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/decap-cms-backend-bitbucket/src/git-lfs-client.ts:74
`unpublishedContentKeys` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — REDACTED:1247
Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition. — packages/decap-cms-core/src/components/Editor/EditorNotesPane/NoteItem.js:9
`onValidateObject` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it. — packages/decap-cms-widget-richtext/src/RichtextControl/components/Element/ShortcodeElement.js:102
`registerMiddleware` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/decap/src/dev/middlewares/localFs/index.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. (×4) — cypress/e2e/editorial_workflow_spec_proxy_git_backend.js:8, cypress/e2e/richtext_widget_enter_spec.js:90, packages/decap-cms-widget-markdown/src/serializers/__tests__/commonmark.spec.js:68, …
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.
What to do
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
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.
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 · Observability5.5 / 10Adequate✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 1/2 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `packages/decap-server`.
`packages/decap/src/login.ts` reports through `console.*` at line 54 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/decap/src/login.ts:54
`packages/decap/src/login.ts` reports through `console.*` at line 55 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/decap/src/login.ts:55
`packages/decap/src/login.ts` reports through `console.*` at line 56 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/decap/src/login.ts:56
`packages/decap/src/login.ts` reports through `console.*` at line 88 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/decap/src/login.ts:88
`packages/decap/src/login.ts` reports through `console.*` at line 100 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/decap/src/login.ts:100
`packages/decap/src/login.ts` reports through `console.*` at line 130 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/decap/src/login.ts:130
`packages/decap/src/login.ts` reports through `console.*` at line 133 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/decap/src/login.ts:133
`packages/decap/src/mcp.ts` reports through `console.*` at line 23 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/decap/src/mcp.ts:23
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
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 5 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:3
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 · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.
Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.
`fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×2) — packages/decap/src/api.ts:68, packages/decap/src/api.ts:117
What to do
Bound every outbound call: pass `signal: AbortSignal.timeout(ms)` to `fetch`, set `timeout` on the axios instance (`axios.create({ timeout })`), and add retries with back-off (`axios-retry`, `p-retry`) and a breaker (`opossum`, `cockatiel`) around dependencies that fail.
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.
Do you agree with this assessment?
R1 · Type Safety2.7 / 10Weak✓ 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.
211 typed · 573 plain JS — the untyped files are __mocks__/cleanStackMock.js, __mocks__/fileMock.js, __mocks__/styleMock.js, cypress/e2e/common/editorial_workflow.js, cypress/e2e/common/entries.js, cypress/e2e/common/i18n.js (+567 more). 0 production file(s) opt out entirely with @ts-nocheck · 11 @ts-ignore suppression(s).
Do you agree with this assessment?
R10 · Code Duplication4.2 / 10Weak✓ Tool-verified
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.
98 duplicated blocks under packages/ have copies in at least two of the sibling directories decap, decap-cms, decap-cms-app, decap-cms-backend-aws-cognito-github-proxy, decap-cms-backend-azure, decap-cms-backend-bitbucket (+27 more sibling(s) not listed) — 79 of them are reported below, and 19 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 98 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 98 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 98 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/decap-cms-backend-forgejo/src/API.ts:56
10 duplicated blocks under packages/decap-cms-core/src/components/ have copies in at least two of the sibling directories App, Collection, Deploys, Editor, MediaLibrary, UI (+1 more sibling(s) not listed) — 1 of them are reported below, and 9 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 10 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 10 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 10 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/decap-cms-core/src/components/Collection/Entries/EntryCard.js:232
6 duplicated blocks under packages/decap-cms-widget-markdown/src/MarkdownControl/plugins/ have copies in at least two of the sibling directories blocks, inlines, lists, shortcodes — 3 of them are reported below, and 3 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 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/decap-cms-widget-markdown/src/MarkdownControl/plugins/blocks/events/keyDown.js:10
packages/decap-cms-backend-forgejo/src/API.ts:56 · packages/decap-cms-backend-gitea/src/API.ts:40 — the two spans are one implementation copied and then locally edited — 2148 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/decap-cms-backend-forgejo/src/API.ts:56
packages/decap-cms-backend-bitbucket/src/implementation.ts:93 · packages/decap-cms-backend-gitlab/src/implementation.ts:91 — the two spans are one implementation copied and then locally edited — 2043 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/decap-cms-backend-bitbucket/src/implementation.ts:93
packages/decap-cms-widget-markdown/src/serializers/slateRemark.js:1 · packages/decap-cms-widget-richtext/src/serializers/slateRemark.js:1 — these 2 files are line-for-line copies of one another — 198 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages/decap-cms-widget-markdown/src/serializers/slateRemark.js:1
packages/decap-cms-backend-turbo-github/src/implementation.tsx:126 · packages/decap-cms-backend-turbo-gitlab/src/implementation.tsx:109 — the two spans are one implementation copied and then locally edited — 1115 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/decap-cms-backend-turbo-github/src/implementation.tsx:126
packages/decap-cms-backend-azure/src/implementation.ts:108 · packages/decap-cms-backend-gitlab/src/implementation.ts:138 — the two spans are one implementation copied and then locally edited — 998 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/decap-cms-backend-azure/src/implementation.ts:108
packages/decap-cms-widget-markdown/src/serializers/remarkSlate.js:1 · packages/decap-cms-widget-richtext/src/serializers/remarkSlate.js:1 — these 2 files are line-for-line copies of one another — 163 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages/decap-cms-widget-markdown/src/serializers/remarkSlate.js:1
packages/decap-cms-backend-github/src/implementation.tsx:647 · packages/decap-cms-backend-gitlab/src/implementation.ts:503 — the two spans are one implementation copied and then locally edited — 1089 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/decap-cms-backend-github/src/implementation.tsx:647
packages/decap-cms-backend-azure/src/API.ts:517 · packages/decap-cms-backend-gitlab/src/API.ts:640 — the two spans are one implementation copied and then locally edited — 639 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/decap-cms-backend-azure/src/API.ts:517
packages/decap-cms-widget-markdown/src/regexHelper.js:32 · packages/decap-cms-widget-richtext/src/serializers/regexHelper.js:32 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/decap-cms-widget-markdown/src/regexHelper.js:32
packages/decap-cms-backend-forgejo/src/implementation.tsx:95 · packages/decap-cms-backend-github/src/implementation.tsx:115 — the two spans are one implementation copied and then locally edited — 631 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/decap-cms-backend-forgejo/src/implementation.tsx:95
packages/decap-cms-backend-gitea/src/implementation.tsx:306 · packages/decap-cms-backend-github/src/implementation.tsx:520 — 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/decap-cms-backend-gitea/src/implementation.tsx:306
packages/decap-cms-widget-markdown/src/serializers/index.js:1 · packages/decap-cms-widget-richtext/src/serializers/index.js:1 — these 2 files are line-for-line copies of one another — 91 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages/decap-cms-widget-markdown/src/serializers/index.js:1
packages/decap-cms-backend-forgejo/src/implementation.tsx:351 · packages/decap-cms-backend-gitea/src/implementation.tsx:193 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/decap-cms-backend-forgejo/src/implementation.tsx:351
packages/decap-cms-backend-forgejo/src/types.ts:182 · packages/decap-cms-backend-gitea/src/types.ts:182 — the 2 copies are spread across 2 files, 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/decap-cms-backend-forgejo/src/types.ts:182
packages/decap-cms-widget-markdown/src/MarkdownControl/index.js:25 · packages/decap-cms-widget-richtext/src/RichtextControl.js:12 — the two spans are one implementation copied and then locally edited — 422 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/decap-cms-widget-markdown/src/MarkdownControl/index.js:25
packages/decap-cms-widget-markdown/src/serializers/remarkEscapeMarkdownEntities.js:11 · packages/decap-cms-widget-richtext/src/serializers/remarkEscapeMarkdownEntities.js:11 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/decap-cms-widget-markdown/src/serializers/remarkEscapeMarkdownEntities.js:11
packages/decap-cms-backend-forgejo/src/AuthenticationPage.js:7 · packages/decap-cms-backend-github/src/AuthenticationPage.js:7 — the two spans are one implementation copied and then locally edited — 309 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/decap-cms-backend-forgejo/src/AuthenticationPage.js:7
packages/decap-cms-core/src/actions/editorialWorkflow.ts:367 · packages/decap-cms-core/src/actions/entries.ts:977 — the two spans are one implementation copied and then locally edited — 318 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/decap-cms-core/src/actions/editorialWorkflow.ts:367
packages/decap-cms-widget-markdown/src/serializers/remarkPaddedLinks.js:20 · packages/decap-cms-widget-richtext/src/serializers/remarkPaddedLinks.js:20 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/decap-cms-widget-markdown/src/serializers/remarkPaddedLinks.js:20
packages/decap-cms-backend-forgejo/src/implementation.tsx:537 · packages/decap-cms-backend-gitea/src/implementation.tsx:370 · packages/decap-cms-backend-github/src/implementation.tsx:584 — the 3 copies are spread across 3 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. 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/decap-cms-backend-forgejo/src/implementation.tsx:537
packages/decap-cms-backend-forgejo/src/types.ts:36 · packages/decap-cms-backend-gitea/src/types.ts:36 — the 2 copies are spread across 2 files, 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/decap-cms-backend-forgejo/src/types.ts:36
packages/decap-cms-widget-markdown/src/serializers/remarkAllowHtmlEntities.js:1 · packages/decap-cms-widget-richtext/src/serializers/remarkAllowHtmlEntities.js:1 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/decap-cms-widget-markdown/src/serializers/remarkAllowHtmlEntities.js:1
REDACTED:28 · packages/decap-cms-widget-richtext/src/serializers/remarkShortcodes.js:13 — the two spans are one implementation copied and then locally edited — 214 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:28
packages/decap-cms-widget-markdown/src/schema.js:1 · packages/decap-cms-widget-richtext/src/schema.js:1 — the 2 copies are spread across 2 files, 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/decap-cms-widget-markdown/src/schema.js:1
packages/decap-cms-core/src/actions/entries.ts:247 · packages/decap-cms-core/src/actions/entries.ts:286 — 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/decap-cms-core/src/actions/entries.ts:247
packages/decap-cms-backend-bitbucket/src/implementation.ts:136 · packages/decap-cms-backend-github/src/implementation.tsx:145 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/decap-cms-backend-bitbucket/src/implementation.ts:136
packages/decap-cms-core/src/components/Editor/EditorToolbar.js:454 · packages/decap-cms-core/src/components/Editor/EditorToolbar.js:556 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/decap-cms-core/src/components/Editor/EditorToolbar.js:454
packages/decap-cms-backend-aws-cognito-github-proxy/src/AuthenticationPage.js:55 · packages/decap-cms-backend-bitbucket/src/AuthenticationPage.js:73 · packages/decap-cms-ui-auth/src/PKCEAuthenticationPage.js:125 — the 3 copies are spread across 3 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. 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/decap-cms-backend-aws-cognito-github-proxy/src/AuthenticationPage.js:55
packages/decap-cms-backend-forgejo/src/AuthenticationPage.js:163 · packages/decap-cms-backend-github/src/AuthenticationPage.js:117 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/decap-cms-backend-forgejo/src/AuthenticationPage.js:163
packages/decap-cms-widget-markdown/src/serializers/remarkSquashReferences.js:28 · packages/decap-cms-widget-richtext/src/serializers/remarkSquashReferences.js:31 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/decap-cms-widget-markdown/src/serializers/remarkSquashReferences.js:28
packages/decap-cms-widget-markdown/src/MarkdownControl/VisualEditor.js:53 · packages/decap-cms-widget-richtext/src/RichtextControl/mergeMediaConfig.js:1 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/decap-cms-widget-markdown/src/MarkdownControl/VisualEditor.js:53
packages/decap-cms-widget-markdown/src/MarkdownControl/Toolbar.js:194 · packages/decap-cms-widget-richtext/src/RichtextControl/components/Toolbar/HeadingToolbarButton.js:66 — 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/decap-cms-widget-markdown/src/MarkdownControl/Toolbar.js:194
packages/decap-cms-widget-markdown/src/MarkdownControl/ToolbarButton.js:12 · packages/decap-cms-widget-richtext/src/RichtextControl/components/Toolbar/ToolbarButton.js:13 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/decap-cms-widget-markdown/src/MarkdownControl/ToolbarButton.js:12
packages/decap-cms-widget-markdown/src/serializers/remarkRehypeShortcodes.js:61 · packages/decap-cms-widget-richtext/src/serializers/remarkRehypeShortcodes.js:58 — 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/decap-cms-widget-markdown/src/serializers/remarkRehypeShortcodes.js:61
packages/decap-cms-backend-forgejo/src/implementation.tsx:154 · packages/decap-cms-backend-gitea/src/implementation.tsx:128 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/decap-cms-backend-forgejo/src/implementation.tsx:154
packages/decap-cms-core/src/integrations/providers/algolia/implementation.js:44 · packages/decap-cms-core/src/integrations/providers/assetStore/implementation.js:18 — 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/decap-cms-core/src/integrations/providers/algolia/implementation.js:44
REDACTED:703 · REDACTED:731 — 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:703
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/decap-cms-core/src/components/App/__tests__/Header.spec.js:10 reaches past another workspace package's public entry into its internals with a relative path (../../../../../decap-cms-locales/src/en) — 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. — packages/decap-cms-core/src/components/App/__tests__/Header.spec.js:10
packages/decap-cms-core/src/components/Deploys/__tests__/Deploys.spec.js:8 reaches past another workspace package's public entry into its internals with a relative path (../../../../../decap-cms-locales/src/en) — 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. — packages/decap-cms-core/src/components/Deploys/__tests__/Deploys.spec.js:8
packages/decap-cms-core/src/components/UI/Notifications.tsx:3 imports react-toastify/dist/inject-style, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/decap-cms-core/src/components/UI/Notifications.tsx:3
packages/decap-cms-core/src/constants/configSchema.js:2 imports ajv-keywords/dist/keywords, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/decap-cms-core/src/constants/configSchema.js:2
packages/decap-cms-widget-richtext/src/RichtextControl/__tests__/VisualEditor.spec.js:4 reaches past another workspace package's public entry into its internals with a relative path (../../../../decap-cms-editor-component-image/src) — 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. — packages/decap-cms-widget-richtext/src/RichtextControl/__tests__/VisualEditor.spec.js:4
packages/decap-cms-widget-richtext/src/__tests__/renderer.spec.js:5 reaches past another workspace package's public entry into its internals with a relative path (../../../decap-cms-editor-component-image/src) — 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. — packages/decap-cms-widget-richtext/src/__tests__/renderer.spec.js:5
packages/decap/src/api.ts:1 imports packages/decap-turbo-api/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/decap/src/api.ts:1
packages/decap/src/commands.ts:7 imports packages/decap-turbo-api/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/decap/src/commands.ts:7
packages/decap/src/mcp.ts:4 imports packages/decap-turbo-api/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/decap/src/mcp.ts:4
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 (6 rows); move the shared test helper into a source directory production code may depend on (3 rows).
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.
(anonymous) has cyclomatic complexity 40 and cognitive complexity 69; 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/decap-cms-core/src/actions/config.ts:233
validateInput has cyclomatic complexity 40 and cognitive complexity 65; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/decap-turbo-api/src/index.ts:877
(anonymous) has cyclomatic complexity 31 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/decap/src/dev/middlewares/localGit/index.ts:179
mediaLibrary has cyclomatic complexity 30 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 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/decap-cms-core/src/reducers/mediaLibrary.ts:62
convertNode has cyclomatic complexity 28 and cognitive complexity 11; 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/decap-cms-widget-markdown/src/serializers/remarkSlate.js:235
main has cyclomatic complexity 27 and cognitive complexity 41; 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/decap/src/index.ts:63
applyFieldPatch has cyclomatic complexity 27 and cognitive complexity 37; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/decap-cms-core/src/lib/editorApi.ts:142
convertNode has cyclomatic complexity 26 and cognitive complexity 9; 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/decap-cms-widget-richtext/src/serializers/remarkSlate.js:234
convertBlockNode has cyclomatic complexity 26 and cognitive complexity 9; 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/decap-cms-widget-richtext/src/serializers/slateRemark.js:327
convertBlockNode has cyclomatic complexity 25 and cognitive complexity 9; 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/decap-cms-widget-markdown/src/serializers/slateRemark.js:328
renderWorkflowControls has cyclomatic complexity 22 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/decap-cms-core/src/components/Editor/EditorToolbar.js:600
persistEntry has cyclomatic complexity 21 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:1383
MediaLibraryModal has cyclomatic complexity 20 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/decap-cms-core/src/components/MediaLibrary/MediaLibraryModal.js:67
promotePrereleaseOnlyLatest has cyclomatic complexity 19 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:201
formatResult has cyclomatic complexity 19 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/decap/src/commands.ts:187
constructor has cyclomatic complexity 18 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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/decap-cms-backend-github/src/implementation.tsx:99
preloadConfig has cyclomatic complexity 18 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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/decap-cms-lib-turbo/src/preloadConfig.ts:10
constructor has cyclomatic complexity 18 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/decap-cms-backend-gitlab/src/implementation.ts:93
compareVersions has cyclomatic complexity 17 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:158
checkValue has cyclomatic complexity 17 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/decap-cms-core/src/lib/editorApi.ts:117
render has cyclomatic complexity 17 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/decap-cms-widget-markdown/src/MarkdownControl/Toolbar.js:105
requestWithBackoff has cyclomatic complexity 16 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/decap-cms-lib-util/src/API.ts:63
deserialize has cyclomatic complexity 16 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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/decap-cms-widget-markdown/src/MarkdownControl/plugins/html/withHtml.js:83
checkPackage has cyclomatic complexity 16 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — scripts/verify-published-packages.mjs:230
(anonymous) has cyclomatic complexity 16 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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/decap-cms-ui-auth/src/PKCEAuthenticationPage.js:19
call has cyclomatic complexity 16 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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/decap/src/api.ts:35
constructor has cyclomatic complexity 16 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/decap-cms-backend-bitbucket/src/implementation.ts:95
insertShortcode has cyclomatic complexity 15 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. — packages/decap-cms-widget-markdown/src/MarkdownControl/plugins/shortcodes/insertShortcode.js:5
main has cyclomatic complexity 15 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:327
main has cyclomatic complexity 15 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — scripts/verify-published-packages.mjs:316
getCypressArgs has cyclomatic complexity 15 and cognitive complexity 20; 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. — cypress/run.mjs:27
constructor has cyclomatic complexity 15 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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/decap-cms-backend-forgejo/src/implementation.tsx:73
getFormat has cyclomatic complexity 15 and cognitive complexity 14; 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/decap-cms-widget-datetime/src/DateTimeControl.js:88
persistFiles has cyclomatic complexity 15 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/decap-cms-backend-turbo-github/src/API.ts:149
match has cyclomatic complexity 15 and cognitive complexity 12; 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/decap-cms-widget-markdown/src/MarkdownControl/plugins/matchers/matchedAncestors.js:5
checkCurrentIssue has cyclomatic complexity 14 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:315
mutate has cyclomatic complexity 14 and cognitive complexity 20; 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/decap-cms-backend-github/src/GraphQLAPI.ts:156
responseBodySanitizer has cyclomatic complexity 14 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 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. — cypress/plugins/github.js:338
(anonymous) has cyclomatic complexity 14 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 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/decap-cms-backend-git-gateway/src/implementation.ts:296
detectProxyServer has cyclomatic complexity 14 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/decap-cms-core/src/actions/config.ts:508
Do you agree with this assessment?
R3 · Large Files7.0 / 10Adequate✓ Tool-verified
React / JS · Code Health — How many source files exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
packages/decap-cms-backend-github/src/API.ts has 1801 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/decap-cms-backend-github/src/API.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/decap-cms-core/src/actions/entries.ts has 1389 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/decap-cms-core/src/actions/entries.ts:1
packages/decap-cms-backend-forgejo/src/API.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/decap-cms-backend-forgejo/src/API.ts:1
packages/decap-cms-backend-gitlab/src/API.ts has 940 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/decap-cms-backend-gitlab/src/API.ts:1
packages/decap-turbo-api/src/index.ts has 883 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/decap-turbo-api/src/index.ts:1
packages/decap-cms-backend-github/src/implementation.tsx has 851 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/decap-cms-backend-github/src/implementation.tsx:1
packages/decap-cms-core/src/types/redux.ts has 795 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/decap-cms-core/src/types/redux.ts:1
packages/decap-cms-backend-bitbucket/src/API.ts has 759 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/decap-cms-backend-bitbucket/src/API.ts:1
REDACTED has 757 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/decap-cms-backend-turbo-github/src/deployWatcher.ts has 750 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/decap-cms-backend-turbo-github/src/deployWatcher.ts:1
REDACTED has 740 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/decap-cms-backend-azure/src/API.ts has 719 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/decap-cms-backend-azure/src/API.ts:1
packages/decap-cms-backend-gitlab/src/implementation.ts has 682 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/decap-cms-backend-gitlab/src/implementation.ts:1
packages/decap-cms-core/src/components/Editor/EditorToolbar.js has 657 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/decap-cms-core/src/components/Editor/EditorToolbar.js:1
packages/decap-cms-backend-github/src/GraphQLAPI.ts has 645 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/decap-cms-backend-github/src/GraphQLAPI.ts:1
packages/decap-cms-lib-util/src/implementation.ts has 626 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/decap-cms-lib-util/src/implementation.ts:1
packages/decap-cms-backend-git-gateway/src/implementation.ts has 609 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/decap-cms-backend-git-gateway/src/implementation.ts:1
packages/decap-cms-core/src/actions/mediaLibrary.ts has 602 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/decap-cms-core/src/actions/mediaLibrary.ts:1
packages/decap-cms-backend-forgejo/src/implementation.tsx has 581 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/decap-cms-backend-forgejo/src/implementation.tsx:1
packages/decap-cms-backend-bitbucket/src/implementation.ts has 580 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/decap-cms-backend-bitbucket/src/implementation.ts:1
packages/decap-cms-lib-turbo/src/session.ts has 577 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/decap-cms-lib-turbo/src/session.ts:1
packages/decap-cms-backend-turbo-github/src/implementation.tsx has 572 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/decap-cms-backend-turbo-github/src/implementation.tsx:1
packages/decap-cms-core/src/actions/config.ts has 551 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/decap-cms-core/src/actions/config.ts:1
packages/decap-cms-core/src/actions/editorialWorkflow.ts has 550 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/decap-cms-core/src/actions/editorialWorkflow.ts:1
packages/decap-cms-core/src/components/Editor/EditorControlPane/EditorControl.js has 521 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/decap-cms-core/src/components/Editor/EditorControlPane/EditorControl.js:1
packages/decap-cms-core/src/components/Editor/Editor.js has 520 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/decap-cms-core/src/components/Editor/Editor.js:1
packages/decap-cms-ui-default/src/styles.js has 510 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/decap-cms-ui-default/src/styles.js:1
packages/decap-cms-core/src/components/Editor/EditorInterface.js has 496 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/decap-cms-core/src/components/Editor/EditorInterface.js:1
packages/decap-cms-widget-relation/src/RelationControl.js has 475 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/decap-cms-widget-relation/src/RelationControl.js:1
packages/decap-cms-core/src/constants/configSchema.js has 468 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/decap-cms-core/src/constants/configSchema.js:1
packages/decap-cms-core/src/reducers/collections.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/decap-cms-core/src/reducers/collections.ts:1
packages/decap-cms-backend-test/src/implementation.ts has 457 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/decap-cms-backend-test/src/implementation.ts:1
packages/decap/src/dev/middlewares/localGit/index.ts has 452 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/decap/src/dev/middlewares/localGit/index.ts:1
REDACTED has 444 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/decap-cms-widget-file/src/withFileControl.js has 444 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/decap-cms-widget-file/src/withFileControl.js:1
packages/decap-cms-widget-markdown/src/serializers/slateRemark.js has 436 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/decap-cms-widget-markdown/src/serializers/slateRemark.js:1
packages/decap-cms-core/src/lib/i18n.ts has 430 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/decap-cms-core/src/lib/i18n.ts:1
packages/decap-cms-widget-richtext/src/serializers/slateRemark.js has 425 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/decap-cms-widget-richtext/src/serializers/slateRemark.js:1
packages/decap-cms-backend-gitea/src/API.ts has 417 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/decap-cms-backend-gitea/src/API.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 Coverage8.1 / 10Strong✓ 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.
cypress/run.mjs:7 imports './e2e/', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — cypress/run.mjs:7
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. (×39) — packages/decap-cms-widget-file/src/withFileControl.js:1, packages/decap-cms-backend-azure/src/implementation.ts:1, packages/decap-cms-widget-code/src/CodeControl.js:1, …
What to do
Add tests that import the unreached modules (directly or through their public entry).
Do you agree with this assessment?
R6 · Tooling10.0 / 10Exemplary✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.
This repository declares test tooling, and the ✓ above records that declaration — but cypress/run.mjs cannot be loaded at all: it imports a module that names no file in this repository, so the runner throws while collecting it and none of its cases execute. The wiring is present and the suite it points at does not run as written, which is why the tooling tick must not be read as a statement that the tests pass. Fix the unloadable file(s) — each one is reported with its failing import under Test Coverage — then the declared script exercises what it claims to. — cypress/run.mjs:7
Do you agree with this assessment?
R7 · Dead Code8.8 / 10Strong✓ 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 150 application, 73 tooling and 254 test entry point(s) detected in this repo. Gate removals on `pnpm run build` — an undetected custom entry would make these reachable.
no import path from any entry point (150 application, 73 tooling, 254 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 (×5) — functions/publish.js, packages/decap-cms-backend-aws-cognito-github-proxy/src/AuthenticationPage.js, jest.resolver.js, …
Nothing imports this binding — it is safe to review for removal. (×21) — packages/decap-cms-backend-github/src/fragments.ts:72, packages/decap-cms-core/src/actions/collections.ts:12, packages/decap-cms-core/src/actions/entries.ts:1319, …
Nothing imports THIS copy of 'selectEntries' — but REDACTED:432 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 REDACTED's, or, if this one is meant to be the survivor, repoint the importers before removing the other. — packages/decap-cms-core/src/reducers/index.ts:53
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 only as a TYPE and declared in no reachable package.json. 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 package.json. — packages/decap-cms-core/index.d.ts:5
Declared in the root 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. (×9)
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/decap-cms-core/src/actions/config.ts → REDACTED → packages/decap-cms-core/src/lib/formatters.ts → packages/decap-cms-core/src/reducers/collections.ts → packages/decap-cms-core/src/actions/config.ts (one verified cycle inside a mutually-dependent group of 32 files) — packages/decap-cms-core/src/actions/config.ts:13
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. Its Node HTTP listeners were read for HTTPS enforcement alone — TLS served, a redirect to https:// or HSTS, or a TLS-terminating proxy configuration committed beside the server — each judged per server package.
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.
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
`app.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.) — packages/decap/src/dev/server.ts:108
What to do
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.
Enforce HTTPS on each listed server: serve TLS itself, or redirect plain requests to `https://` and send `Strict-Transport-Security` (`helmet()` does by default) behind the TLS-terminating proxy — and commit that proxy's configuration beside the service. A server only this machine reaches should bind `127.0.0.1`.
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 · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a 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 3/41 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.
`listObjects` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — packages/decap-cms-media-library-s3/src/api/client.ts:160
`uploadFile` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — packages/decap-cms-media-library-s3/src/api/client.ts:200
`deleteFile` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — packages/decap-cms-media-library-s3/src/api/client.ts:216
`rpc` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — packages/decap-cms-lib-turbo/src/editorBridge.ts:244
`preloadConfig` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — packages/decap-cms-lib-turbo/src/preloadConfig.ts:10
`setActiveSiteAndRefresh` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — packages/decap-cms-lib-turbo/src/session.ts:323
`fetchPermissions` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — packages/decap-cms-lib-turbo/src/session.ts:371
`fetchRefreshedTokens` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — packages/decap-cms-lib-turbo/src/session.ts:444
`fetchDbPaginated` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — packages/decap-cms-lib-turbo/src/supabase.ts:58
`exchangeCodeForCredentials` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — packages/decap-cms-lib-turbo/src/AuthenticationPage.js:123
`_loadOidcConfig` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — packages/decap-cms-lib-auth/src/pkce-oauth.js:79
`_requestToken` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — packages/decap-cms-lib-auth/src/pkce-oauth.js:208
`persistLocalDraftBackup` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — REDACTED:1036
`toBase64` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — packages/decap-cms-core/src/valueObjects/AssetProxy.ts:27
`getConfigYaml` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — packages/decap-cms-core/src/actions/config.ts:418
`detectProxyServer` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — packages/decap-cms-core/src/actions/config.ts:508
`queryDeployments` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — packages/decap-cms-backend-turbo-github/src/deployWatcher.ts:715
`listCommits` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — packages/decap-cms-backend-turbo-github/src/deployWatcher.ts:783
`getIssueWithETag` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — packages/decap-cms-backend-github/src/API.ts:1658
`status` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. (×3) — packages/decap-cms-backend-github/src/implementation.tsx:145, packages/decap-cms-backend-git-gateway/src/implementation.ts:207, packages/decap-cms-backend-bitbucket/src/implementation.ts:136
`pollUntilForkExists` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. (×2) — packages/decap-cms-backend-github/src/implementation.tsx:194, packages/decap-cms-backend-forgejo/src/implementation.tsx:178
`currentUser` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. (×4) — packages/decap-cms-backend-github/src/implementation.tsx:218, packages/decap-cms-backend-gitea/src/implementation.tsx:117, packages/decap-cms-backend-forgejo/src/implementation.tsx:143, …
`userIsOriginMaintainer` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. (×3) — packages/decap-cms-backend-github/src/implementation.tsx:236, packages/decap-cms-backend-gitea/src/implementation.tsx:128, packages/decap-cms-backend-forgejo/src/implementation.tsx:154
`forkExists` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — packages/decap-cms-backend-github/src/implementation.tsx:260
`authenticateWithFork` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — packages/decap-cms-backend-github/src/implementation.tsx:284
`authenticate` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. (×2) — packages/decap-cms-backend-github/src/implementation.tsx:334, packages/decap-cms-backend-bitbucket/src/implementation.ts:195
`apiGet` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — packages/decap-cms-backend-git-gateway/src/implementation.ts:131
`call` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — packages/decap/src/api.ts:35
`assertCliApi` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — packages/decap/src/api.ts:113
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.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped4.6 / 10Weak✓ 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.
`toRender` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` 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. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×2) — packages/decap-cms-widget-markdown/src/MarkdownPreview.js:65, REDACTED:101
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 element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×11) — packages/decap-cms-ui-auth/src/PKCEAuthenticationPage.js:105, packages/decap-cms-ui-auth/src/PKCEAuthenticationPage.js:113, packages/decap-cms-media-library-s3/src/api/client.ts:149, …
`.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. — packages/decap-cms-lib-turbo/src/telemetry.ts:23
`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. — packages/decap-cms-backend-github/src/API.ts:644
`.catch(ignore)` 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/decap/src/login.ts:196
Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.
Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.
`info` at line 76 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/decap/src/dev/server.ts:76
`warn` at line 78 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.warn({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.warn('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/decap/src/dev/server.ts:78
`info` at line 100 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/decap/src/dev/server.ts:100
`error` at line 454 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/decap/src/dev/middlewares/localGit/index.ts:454
`info` at line 476 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/decap/src/dev/middlewares/localGit/index.ts:476
`error` at line 135 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/decap/src/dev/middlewares/localFs/index.ts:135
`info` at line 159 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — packages/decap/src/dev/middlewares/localFs/index.ts:159
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.
~11.9 `!` null assertions per 1k TypeScript source lines — 467 assertion(s) across the 39096 source line(s) of the 160 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/decap-cms-backend-github/src/implementation.tsx (52), packages/decap-cms-backend-forgejo/src/implementation.tsx (49), packages/decap-cms-backend-gitlab/src/implementation.ts (47). 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 — 40 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 — 4 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
C3 Audit Trail — Not assessed: this repository stores data through 'localforage' (packages/decap-cms-lib-util/src/localForage.ts:1) but declares no persisted model this check reads (TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entities, Mongoose schemas, Sequelize or Drizzle tables, Knex migrations, Prisma models). Personal data may be written through raw SQL or a hosted backend, so whether its changes need an audit trail could not be established, and the trail's absence is not scored.
C4 Data Retention — Not assessed: this repository stores data through 'localforage' (packages/decap-cms-lib-util/src/localForage.ts:1) but declares no persisted model this check reads (TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entities, Mongoose schemas, Sequelize or Drizzle tables, Knex migrations, Prisma models). Personal data may be written through raw SQL or a hosted backend, so whether a retention limit applies here could not be established, and its absence is not scored.
C5 Data-Subject Rights — Not assessed: this repository stores data through 'localforage' (packages/decap-cms-lib-util/src/localForage.ts:1) but declares no persisted model this check reads (TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entities, Mongoose schemas, Sequelize or Drizzle tables, Knex migrations, Prisma models). Personal data may be written through raw SQL or a hosted backend, so whether data-subject rights apply here could not be established, and their absence is not scored.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 50 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 (11 DOM element(s) < 25) — too little surface to assess accessibility.
AC2 Forms & labels — Frontend below the scale floor (11 DOM element(s) < 25) — too little surface to assess accessibility.
AC3 Page structure — Frontend below the scale floor (11 DOM element(s) < 25) — too little surface to assess accessibility.
AC4 Keyboard semantics — Frontend below the scale floor (11 DOM element(s) < 25) — too little surface to assess accessibility.
AC5 ARIA correctness — Frontend below the scale floor (11 DOM element(s) < 25) — too little surface to assess accessibility.
AC6 Visual & motion safety — Frontend below the scale floor (11 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 (our sandbox): a program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. Last output: "> start / > pnpm run develop / sh: 1: pnpm: not found" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — Not assessed: this repository stores data through 'localforage' (packages/decap-cms-lib-util/src/localForage.ts:1) but declares no persisted model this check reads (TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entities, Mongoose schemas, Sequelize or Drizzle tables, Knex migrations, Prisma models). Personal data may be written through raw SQL or a hosted backend, so the absence of a personal-data field here is not evidence that none is stored, and encryption at rest is not scored over a subject that could not be established.
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# only; the exposed TypeScript surface was not measured.
D25 ADR Conformance — no ADRs to check
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
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 only 1 of the 3 signals this lens looks for (a Domain/Aggregates/ValueObjects layer)
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
R5 Dependency Freshness — uses a pnpm lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
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.
X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X32 Type resolved by simple name across every loaded assembly — 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.
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.
Dependency-rule violation: decap-cms-app (Application) → decap-cms-ui-auth (Web) packages/decap-cms-app/package.json:55— `decap-cms-app` is a Application project but references `decap-cms-ui-auth`, a Web project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one.
Dependency-rule violation: decap-cms-app (Application) → decap-cms-ui-default (Web) packages/decap-cms-app/package.json:56— `decap-cms-app` is a Application project but references `decap-cms-ui-default`, a Web project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one.
Dependency-rule violation: decap-cms-core (Domain) → decap-cms-ui-default (Web) packages/decap-cms-core/package.json:87— `decap-cms-core` is a Domain project but references `decap-cms-ui-default`, a Web project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one.
Orphaned knowledge packages/decap-cms-locales/src/th/index.js: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.
Orphaned knowledge packages/decap-cms-backend-bitbucket/src/implementation.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.
Boundary-crossing change coupling: implementation.ts ↔ REDACTED packages/decap-cms-backend-test/src/implementation.ts:1— `packages/decap-cms-backend-test/src/implementation.ts` (context decap-cms-backend-test) and `REDACTED` (context decap-cms-core) sit in DIFFERENT parts of the tree yet change together 50% of the time (7 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `03d6446d` Feature: Collaborative Notes Pane for the Editor screen (#7563); `a50edc70` feat: add backend status down indicator (#3889) (at that commit the files were still `packages/netlify-cms-backend-test/src/implementation.ts` and `packages/netlify-cms-core/src/backend.ts`); `285c9405` fix: handle token expiry (#3847) (at that commit the files were still `packages/netlify-cms-backend-test/src/implementation.ts` and `packages/netlify-cms-core/src/backend.ts`) — run `git show` on any of them.
R4 · Test Coverage· No test reaches this file · ×39
No test reaches this file packages/decap-cms-widget-file/src/withFileControl.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.
No test reaches this file packages/decap-cms-backend-azure/src/implementation.ts: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.
No test reaches this file packages/decap-cms-widget-code/src/CodeControl.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.
No test reaches this file packages/decap-cms-widget-richtext/src/RichtextControl/VisualEditor.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.
No test reaches this file packages/decap/src/index.ts: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.
No test reaches this file packages/decap-cms-widget-richtext/src/RichtextControl/components/Toolbar/Toolbar.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.
No test reaches this file packages/decap-cms-widget-colorstring/src/ColorControl.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.
No test reaches this file packages/decap-cms-ui-auth/src/PKCEAuthenticationPage.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.
No test reaches this file packages/decap-cms-widget-richtext/src/RichtextControl.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.
No test reaches this file packages/decap-cms-widget-code/src/SettingsPane.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.
No test reaches this file packages/decap-cms-widget-map/src/withMapControl.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.
No test reaches this file packages/decap-cms-widget-richtext/src/RichtextControl/components/Toolbar/HeadingToolbarButton.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.
No test reaches this file packages/decap/src/mcp.ts: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.
No test reaches this file packages/decap-cms-widget-richtext/src/RichtextControl/RawEditor.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.
No test reaches this file packages/decap-cms-widget-richtext/src/RichtextControl/components/Toolbar/EditorComponentsToolbarButton.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.
No test reaches this file packages/decap-cms-backend-azure/src/AuthenticationPage.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.
No test reaches this file functions/publish.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.
No test reaches this file packages/decap-cms-backend-aws-cognito-github-proxy/src/AuthenticationPage.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.
No test reaches this file packages/decap-cms-app/src/extensions.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.
No test reaches this file packages/decap-cms-lib-auth/src/implicit-oauth.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.
No test reaches this file packages/decap-cms-backend-proxy/src/AuthenticationPage.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.
No test reaches this file packages/decap-cms-widget-string/src/StringControl.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.
No test reaches this file packages/decap-cms-widget-image/src/ImagePreview.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.
No test reaches this file packages/decap-cms-backend-aws-cognito-github-proxy/src/implementation.tsx: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.
No test reaches this file packages/decap-cms-widget-text/src/TextControl.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.
+ 14 more in this group — see findings.md.
X2 · Cancellation propagation· Async function without AbortSignal · ×38
Async function without AbortSignal: listObjects packages/decap-cms-media-library-s3/src/api/client.ts:160— `listObjects` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: uploadFile packages/decap-cms-media-library-s3/src/api/client.ts:200— `uploadFile` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: deleteFile packages/decap-cms-media-library-s3/src/api/client.ts:216— `deleteFile` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: rpc packages/decap-cms-lib-turbo/src/editorBridge.ts:244— `rpc` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: preloadConfig packages/decap-cms-lib-turbo/src/preloadConfig.ts:10— `preloadConfig` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: setActiveSiteAndRefresh packages/decap-cms-lib-turbo/src/session.ts:323— `setActiveSiteAndRefresh` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: fetchPermissions packages/decap-cms-lib-turbo/src/session.ts:371— `fetchPermissions` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: fetchRefreshedTokens packages/decap-cms-lib-turbo/src/session.ts:444— `fetchRefreshedTokens` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: fetchDbPaginated packages/decap-cms-lib-turbo/src/supabase.ts:58— `fetchDbPaginated` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: exchangeCodeForCredentials packages/decap-cms-lib-turbo/src/AuthenticationPage.js:123— `exchangeCodeForCredentials` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: _loadOidcConfig packages/decap-cms-lib-auth/src/pkce-oauth.js:79— `_loadOidcConfig` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: _requestToken packages/decap-cms-lib-auth/src/pkce-oauth.js:208— `_requestToken` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: persistLocalDraftBackup REDACTED:1036— `persistLocalDraftBackup` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: toBase64 packages/decap-cms-core/src/valueObjects/AssetProxy.ts:27— `toBase64` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: getConfigYaml packages/decap-cms-core/src/actions/config.ts:418— `getConfigYaml` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: detectProxyServer packages/decap-cms-core/src/actions/config.ts:508— `detectProxyServer` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: queryDeployments packages/decap-cms-backend-turbo-github/src/deployWatcher.ts:715— `queryDeployments` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: listCommits packages/decap-cms-backend-turbo-github/src/deployWatcher.ts:783— `listCommits` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: getIssueWithETag packages/decap-cms-backend-github/src/API.ts:1658— `getIssueWithETag` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: status packages/decap-cms-backend-github/src/implementation.tsx:145— `status` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: pollUntilForkExists packages/decap-cms-backend-github/src/implementation.tsx:194— `pollUntilForkExists` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: currentUser packages/decap-cms-backend-github/src/implementation.tsx:218— `currentUser` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: userIsOriginMaintainer packages/decap-cms-backend-github/src/implementation.tsx:236— `userIsOriginMaintainer` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: forkExists packages/decap-cms-backend-github/src/implementation.tsx:260— `forkExists` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: authenticateWithFork packages/decap-cms-backend-github/src/implementation.tsx:284— `authenticateWithFork` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
+ 13 more in this group — see findings.md.
D30 · Dependency Vulnerabilities· Medium CVE · ×22
TodoComment REDACTED:893— // TODO: pass search fields in as an argument — 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 REDACTED:984— // TODO: stop assuming all cursors are for collections — 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/decap-cms-core/src/types/redux.ts:510— // TODO: type properly — 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/decap-cms-core/src/actions/config.ts:373— // TODO remove fromJS when Immutable is removed from the collections state slice — 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/decap-cms-core/src/actions/__tests__/media.spec.ts:45— // TODO change to proper payload when immutable is removed — 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/decap-cms-core/src/actions/__tests__/media.spec.ts:72— // TODO change to proper payload when immutable is removed — 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/decap-cms-core/src/actions/__tests__/media.spec.ts:102— // TODO change to proper payload when immutable is removed — 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/decap-cms-core/src/actions/__tests__/media.spec.ts:125— // TODO change to proper payload when immutable is removed — 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/decap-cms-core/src/actions/__tests__/media.spec.ts:155— // TODO change to proper payload when immutable is removed — 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/decap-cms-core/src/actions/__tests__/media.spec.ts:59— // TODO change to proper store data when immutable is removed — 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/decap-cms-backend-test/src/implementation.ts:212— // TODO: stop assuming cursors are for collections — 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/decap-cms-backend-git-gateway/src/implementation.ts:415— // TODO: remove after https://github.com/netlify/gotrue-js/pull/83 is merged
TodoComment packages/decap-cms-backend-git-gateway/src/implementation.ts:617— // TODO: get Netlify API Token and use it to access private logs — 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/decap-cms-backend-git-gateway/src/netlify-lfs-client.ts:51— // TODO: what kind of error to throw here? APIError doesn't seem — 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/decap-cms-backend-bitbucket/src/API.ts:754— // TODO: get real id — 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.
FileTooLong: src/API.ts packages/decap-cms-backend-github/src/API.ts— FileTooLong — 1306 significant lines (blank, comment-only and punctuation-only lines excluded), about 86% of them inside a single declaration: API (232-2000). The bar is 500 significant lines; this is 806 over it, 2.61× 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 — 1119 significant lines (blank, comment-only and punctuation-only lines excluded), about 71% of them inside a single declaration: Backend (430-1699). The bar is 500 significant lines; this is 619 over it, 2.24× 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: actions/entries.ts packages/decap-cms-core/src/actions/entries.ts— FileTooLong — 1004 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 504 over it, 2.01× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/API.ts packages/decap-cms-backend-gitlab/src/API.ts— FileTooLong — 738 significant lines (blank, comment-only and punctuation-only lines excluded), about 78% of them inside a single declaration: API (211-1043). The bar is 500 significant lines; this is 238 over it, 1.48× 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/API.ts packages/decap-cms-backend-forgejo/src/API.ts— FileTooLong — 713 significant lines (blank, comment-only and punctuation-only lines excluded), about 87% of them inside a single declaration: API (113-1081). The bar is 500 significant lines; this is 213 over it, 1.43× 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/index.ts packages/decap-turbo-api/src/index.ts— FileTooLong — 695 significant lines (blank, comment-only and punctuation-only lines excluded), about 67% of them inside a single declaration: operations (105-672). The bar is 500 significant lines; this is 195 over it, 1.39× 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: types/redux.ts packages/decap-cms-core/src/types/redux.ts— FileTooLong — 671 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 171 over it, 1.34× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/implementation.tsx packages/decap-cms-backend-github/src/implementation.tsx— FileTooLong — 633 significant lines (blank, comment-only and punctuation-only lines excluded), about 91% of them inside a single declaration: GitHub (65-955). The bar is 500 significant lines; this is 133 over it, 1.27× 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 — 603 significant lines (blank, comment-only and punctuation-only lines excluded; the length bar is tripled for a single-responsibility module of 4 or fewer top-level units), about 79% of them inside a single declaration: ListControl (175-850). The bar is 500 significant lines; this is 103 over it, 1.21× 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 — 581 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 81 over it, 1.16× 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: Editor/EditorToolbar.js packages/decap-cms-core/src/components/Editor/EditorToolbar.js— FileTooLong — 574 significant lines (blank, comment-only and punctuation-only lines excluded), about 64% of them inside a single declaration: EditorToolbar (267-732). The bar is 500 significant lines; this is 74 over it, 1.15× 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/API.ts packages/decap-cms-backend-bitbucket/src/API.ts— FileTooLong — 573 significant lines (blank, comment-only and punctuation-only lines excluded), about 76% of them inside a single declaration: API (186-846). The bar is 500 significant lines; this is 73 over it, 1.15× 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/API.ts packages/decap-cms-backend-azure/src/API.ts— FileTooLong — 554 significant lines (blank, comment-only and punctuation-only lines excluded), about 71% of them inside a single declaration: API (228-813). The bar is 500 significant lines; this is 54 over it, 1.11× 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/implementation.ts packages/decap-cms-backend-gitlab/src/implementation.ts— FileTooLong — 543 significant lines (blank, comment-only and punctuation-only lines excluded), about 90% of them inside a single declaration: GitLab (57-771). The bar is 500 significant lines; this is 43 over it, 1.09× 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/implementation.ts packages/decap-cms-lib-util/src/implementation.ts— FileTooLong — 528 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 28 over it, 1.06× 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.
FunctionTooLong: index.localGitMiddleware packages/decap/src/dev/middlewares/localGit/index.ts:173— FunctionTooLong — localGitMiddleware runs 228 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 128 over it, 2.28× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: index.localGitMiddleware.<returned closure> packages/decap/src/dev/middlewares/localGit/index.ts:179— FunctionTooLong — localGitMiddleware.<returned closure> runs 225 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 125 over it, 2.25× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: S3Widget.S3Widget packages/decap-cms-media-library-s3/src/components/S3Widget.tsx:57— FunctionTooLong — S3Widget runs 223 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 123 over it, 2.23× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: slateRemark.slateToRemark packages/decap-cms-widget-markdown/src/serializers/slateRemark.js:71— FunctionTooLong — slateToRemark runs 206 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 106 over it, 2.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.
FunctionTooLong: slateRemark.slateToRemark packages/decap-cms-widget-richtext/src/serializers/slateRemark.js:72— FunctionTooLong — slateToRemark runs 200 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 100 over it, 2.00× 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: withFileControl.withFileControl packages/decap-cms-widget-file/src/withFileControl.js:240— FunctionTooLong — withFileControl runs 182 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 82 over it, 1.82× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: configSchema.getConfigSchema packages/decap-cms-core/src/constants/configSchema.js:158— FunctionTooLong — getConfigSchema runs 173 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 73 over it, 1.73× 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: entryDraft.entryDraftReducer packages/decap-cms-core/src/reducers/entryDraft.js:74— FunctionTooLong — entryDraftReducer runs 144 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 44 over it, 1.44× 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: VisualEditor.Editor packages/decap-cms-widget-markdown/src/MarkdownControl/VisualEditor.js:85— FunctionTooLong — Editor runs 144 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 44 over it, 1.44× 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: mediaLibrary.mediaLibrary packages/decap-cms-core/src/reducers/mediaLibrary.ts:62— FunctionTooLong — mediaLibrary runs 143 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 43 over it, 1.43× 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: index.defaultSchema packages/decap/src/dev/middlewares/joi/index.ts:33— FunctionTooLong — defaultSchema runs 138 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 38 over it, 1.38× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: remarkSlate.remarkToSlate packages/decap-cms-widget-markdown/src/serializers/remarkSlate.js:82— FunctionTooLong — remarkToSlate runs 129 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 29 over it, 1.29× 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: remarkSlate.remarkToSlate packages/decap-cms-widget-richtext/src/serializers/remarkSlate.js:81— FunctionTooLong — remarkToSlate runs 122 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 22 over it, 1.22× 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: VisualEditor.VisualEditor packages/decap-cms-widget-richtext/src/RichtextControl/VisualEditor.js:56— FunctionTooLong — VisualEditor 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.
Deprecated: @stylelint/postcss-css-in-js package.json:75— @stylelint/postcss-css-in-js 0.37.3, declared in package.json, is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: @types/js-base64 package.json:81— @types/js-base64 3.3.1, declared in package.json, is marked deprecated by its publisher: "This is a stub types definition. js-base64 provides its own type definitions, so you do not need this installed.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: babel-eslint package.json:95— babel-eslint 11.0.0-beta.2, declared in package.json, is marked deprecated by its publisher: "babel-eslint is now @babel/eslint-parser. This package will no longer receive updates.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint package.json:115— eslint 8.57.1, declared in package.json, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: gitlab package.json:124— gitlab 14.2.2, declared in package.json, is marked deprecated by its publisher: "This package has found a new home in the @gitbeaker organization. For the latest GitLab API library for node, browser, and deno usage, check out @gitbeaker/rest. A full list of the features can be found here: https://github.com/jdalrymple/gitbeaker#readme". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: rimraf package.json:147— rimraf 3.0.2, declared in package.json, is marked deprecated by its publisher: "Rimraf versions prior to v4 are no longer supported". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: start-server-and-test package.json:149— start-server-and-test 1.15.5, declared in package.json, is marked deprecated by its publisher: "this package has been deprecated". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint-import-resolver-exports package.json:165— eslint-import-resolver-exports 1.0.0-beta.5, declared in package.json, is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: uuid packages/decap-cms-app/package.json:78— uuid 8.3.2, declared in packages/decap-cms-app/package.json, is marked deprecated by its publisher: "uuid@10 and below is no longer supported. For ESM codebases, update to uuid@latest. For CommonJS codebases, use uuid@11 (but be aware this version will likely be deprecated in 2028).". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: react-waypoint packages/decap-cms-core/package.json:66— react-waypoint 10.3.0, declared in packages/decap-cms-core/package.json, is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: redux-devtools-extension packages/decap-cms-core/package.json:69— redux-devtools-extension 2.13.9, declared in packages/decap-cms-core/package.json, is marked deprecated by its publisher: "Package moved to @redux-devtools/extension.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: uuid packages/decap-cms-default-exports/package.json:28— uuid 8.3.2, declared in packages/decap-cms-default-exports/package.json, is marked deprecated by its publisher: "uuid@10 and below is no longer supported. For ESM codebases, update to uuid@latest. For CommonJS codebases, use uuid@11 (but be aware this version will likely be deprecated in 2028).". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: @hapi/joi packages/decap/package.json:37— @hapi/joi 17.1.1, declared in packages/decap/package.json, is marked deprecated by its publisher: "Switch to 'npm install joi'". Replace it with the package or version that message names, or record why this one must stay.
TooManyMethods: API packages/decap-cms-backend-github/src/API.ts:232— TooManyMethods — 94 methods. The bar is 30 methods; this is 64 over it, 3.13× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Backend REDACTED:430— TooManyMethods — 64 methods. The bar is 30 methods; this is 34 over it, 2.13× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: API packages/decap-cms-backend-forgejo/src/API.ts:113— TooManyMethods — 59 methods. The bar is 30 methods; this is 29 over it, 1.97× 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: API packages/decap-cms-backend-gitlab/src/API.ts:211— TooManyMethods — 50 methods. The bar is 30 methods; this is 20 over it, 1.67× 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: GitLab packages/decap-cms-backend-gitlab/src/implementation.ts:57— TooManyMethods — 49 methods. The bar is 30 methods; this is 19 over it, 1.63× 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: GitHub packages/decap-cms-backend-github/src/implementation.tsx:65— TooManyMethods — 46 methods. The bar is 30 methods; this is 16 over it, 1.53× 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: API packages/decap-cms-backend-bitbucket/src/API.ts:186— TooManyMethods — 44 methods. The bar is 30 methods; this is 14 over it, 1.47× 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: API packages/decap-cms-backend-azure/src/API.ts:228— TooManyMethods — 37 methods. The bar is 30 methods; this is 7 over it, 1.23× 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: BitbucketBackend packages/decap-cms-backend-bitbucket/src/implementation.ts:66— TooManyMethods — 36 methods. The bar is 30 methods; this is 6 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.
TooManyMethods: GraphQLAPI packages/decap-cms-backend-github/src/GraphQLAPI.ts:101— TooManyMethods — 35 methods. The bar is 30 methods; this is 5 over it, 1.17× 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: Forgejo packages/decap-cms-backend-forgejo/src/implementation.tsx:47— TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: GitGateway packages/decap-cms-backend-git-gateway/src/implementation.ts:137— TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ListControl REDACTED:175— 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.
Swallowed exception (empty catch) packages/decap-cms-ui-auth/src/PKCEAuthenticationPage.js:105— 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/decap-cms-ui-auth/src/PKCEAuthenticationPage.js:113— 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/decap-cms-media-library-s3/src/api/client.ts: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/decap-cms-lib-util/src/notesFormat.ts:138— 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/decap-cms-lib-turbo/src/editorBridge.ts:323— 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/decap-cms-lib-turbo/src/scopedFetch.ts:33— 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/decap-cms-lib-turbo/src/telemetry.ts:23— `.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/decap-cms-core/src/actions/editorialWorkflow.ts:274— 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/decap-cms-backend-git-gateway/src/implementation.ts:634— 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/decap/src/api.ts:83— 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/decap/src/api.ts:136— 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/decap/src/login.ts:196— `.catch(ignore)` 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/decap/src/login.ts:238— 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.
Hotspot: REDACTED REDACTED:1383— REDACTED changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in Backend.persistEntry at line 1383. 7 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-07-30..2026-10-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-30 14:41:31 +01:00' --until='2026-10-28 14:41:31 +01: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/decap-cms-core/src/reducers/editorialWorkflow.ts packages/decap-cms-core/src/reducers/editorialWorkflow.ts:34— packages/decap-cms-core/src/reducers/editorialWorkflow.ts changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in editorialWorkflow.unpublishedEntries at line 34. 6 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-07-30..2026-10-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-30 14:41:31 +01:00' --until='2026-10-28 14:41:31 +01:00' --full-history --no-merges -- packages/decap-cms-core/src/reducers/editorialWorkflow.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/decap/src/index.ts packages/decap/src/index.ts:63— packages/decap/src/index.ts changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in index.main at line 63. 3 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-07-30..2026-10-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-30 14:41:31 +01:00' --until='2026-10-28 14:41:31 +01:00' --full-history --no-merges -- packages/decap/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.
Hotspot: packages/decap-cms-core/src/reducers/entryDraft.js packages/decap-cms-core/src/reducers/entryDraft.js:74— packages/decap-cms-core/src/reducers/entryDraft.js changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 42 in entryDraft.entryDraftReducer at line 74. 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-07-30..2026-10-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-30 14:41:31 +01:00' --until='2026-10-28 14:41:31 +01:00' --full-history --no-merges -- packages/decap-cms-core/src/reducers/entryDraft.js`: 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/decap-cms-core/src/reducers/mediaLibrary.ts packages/decap-cms-core/src/reducers/mediaLibrary.ts:62— packages/decap-cms-core/src/reducers/mediaLibrary.ts changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 37 in mediaLibrary.mediaLibrary at line 62. 1 of those changes was a fix/bug commit, and the other 2 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-07-30..2026-10-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-30 14:41:31 +01:00' --until='2026-10-28 14:41:31 +01:00' --full-history --no-merges -- packages/decap-cms-core/src/reducers/mediaLibrary.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/decap-cms-core/src/components/Editor/EditorControlPane/EditorControl.js packages/decap-cms-core/src/components/Editor/EditorControlPane/EditorControl.js:256— packages/decap-cms-core/src/components/Editor/EditorControlPane/EditorControl.js changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in EditorControl.render at line 256. 2 of those changes were fix/bug commits, and the other 4 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-30..2026-10-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-30 14:41:31 +01:00' --until='2026-10-28 14:41:31 +01:00' --full-history --no-merges -- packages/decap-cms-core/src/components/Editor/EditorControlPane/EditorControl.js`: 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:201— REDACTED changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in publish-packages.promotePrereleaseOnlyLatest at line 201. 1 of those changes was a fix/bug commit, and the other 2 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-07-30..2026-10-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-30 14:41:31 +01:00' --until='2026-10-28 14:41:31 +01: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/decap-cms-lib-turbo/src/preloadConfig.ts packages/decap-cms-lib-turbo/src/preloadConfig.ts:10— packages/decap-cms-lib-turbo/src/preloadConfig.ts changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in preloadConfig.createPreloadConfig.preloadConfig at line 10. 2 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-07-30..2026-10-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-30 14:41:31 +01:00' --until='2026-10-28 14:41:31 +01:00' --full-history --no-merges -- packages/decap-cms-lib-turbo/src/preloadConfig.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: scripts/verify-published-packages.mjs scripts/verify-published-packages.mjs:230— scripts/verify-published-packages.mjs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in verify-published-packages.checkPackage at line 230. 1 of those changes was a fix/bug commit, and the other 2 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-07-30..2026-10-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-30 14:41:31 +01:00' --until='2026-10-28 14:41:31 +01:00' --full-history --no-merges -- scripts/verify-published-packages.mjs`: 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/decap-cms-widget-markdown/src/serializers/remarkRehypeShortcodes.js packages/decap-cms-widget-markdown/src/serializers/remarkRehypeShortcodes.js:12— packages/decap-cms-widget-markdown/src/serializers/remarkRehypeShortcodes.js changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in remarkRehypeShortcodes.remarkToRehypeShortcodes at line 12. 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-07-30..2026-10-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-30 14:41:31 +01:00' --until='2026-10-28 14:41:31 +01:00' --full-history --no-merges -- packages/decap-cms-widget-markdown/src/serializers/remarkRehypeShortcodes.js`: 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-cross-package-internals] packages/decap-cms-core/src/components/App/__tests__/Header.spec.js:10— packages/decap-cms-core/src/components/App/__tests__/Header.spec.js:10 reaches past another workspace package's public entry into its internals with a relative path (../../../../../decap-cms-locales/src/en) — 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] packages/decap-cms-core/src/components/Deploys/__tests__/Deploys.spec.js:8— packages/decap-cms-core/src/components/Deploys/__tests__/Deploys.spec.js:8 reaches past another workspace package's public entry into its internals with a relative path (../../../../../decap-cms-locales/src/en) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:third-party-deep-import] packages/decap-cms-core/src/components/UI/Notifications.tsx:3— packages/decap-cms-core/src/components/UI/Notifications.tsx:3 imports react-toastify/dist/inject-style, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] packages/decap-cms-core/src/constants/configSchema.js:2— packages/decap-cms-core/src/constants/configSchema.js:2 imports ajv-keywords/dist/keywords, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:test-cross-package-internals] packages/decap-cms-widget-richtext/src/RichtextControl/__tests__/VisualEditor.spec.js:4— packages/decap-cms-widget-richtext/src/RichtextControl/__tests__/VisualEditor.spec.js:4 reaches past another workspace package's public entry into its internals with a relative path (../../../../decap-cms-editor-component-image/src) — 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] packages/decap-cms-widget-richtext/src/__tests__/renderer.spec.js:5— packages/decap-cms-widget-richtext/src/__tests__/renderer.spec.js:5 reaches past another workspace package's public entry into its internals with a relative path (../../../decap-cms-editor-component-image/src) — 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-suite-dependency] packages/decap/src/api.ts:1— packages/decap/src/api.ts:1 imports packages/decap-turbo-api/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:test-suite-dependency] packages/decap/src/commands.ts:7— packages/decap/src/commands.ts:7 imports packages/decap-turbo-api/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:test-suite-dependency] packages/decap/src/mcp.ts:4— packages/decap/src/mcp.ts:4 imports packages/decap-turbo-api/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.
MethodTooLong: EditorInterface.render packages/decap-cms-core/src/components/Editor/EditorInterface.js:259— MethodTooLong — render runs 221 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 121 over it, 2.21× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: EditorControl.render packages/decap-cms-core/src/components/Editor/EditorControlPane/EditorControl.js:256— MethodTooLong — render runs 189 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 89 over it, 1.89× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Toolbar.render packages/decap-cms-widget-markdown/src/MarkdownControl/Toolbar.js:105— MethodTooLong — render runs 172 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 72 over it, 1.72× 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: App.render packages/decap-cms-core/src/components/App/App.js:178— MethodTooLong — render runs 104 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 4 over it, 1.04× 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: Widget.render REDACTED:285— MethodTooLong — render runs 102 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 2 over it, 1.02× 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.
ClassTooLong: Backend REDACTED:430— ClassTooLong — 799 significant lines (blank, comment-only and punctuation-only lines excluded), 64 methods. The bar is 400 significant lines; this is 399 over it, 2.00× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: API packages/decap-cms-backend-forgejo/src/API.ts:113— ClassTooLong — 622 significant lines (blank, comment-only and punctuation-only lines excluded), 59 methods. The bar is 400 significant lines; this is 222 over it, 1.56× 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: GitHub packages/decap-cms-backend-github/src/implementation.tsx:65— ClassTooLong — 578 significant lines (blank, comment-only and punctuation-only lines excluded), 46 methods. The bar is 400 significant lines; this is 178 over it, 1.45× 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: GitLab packages/decap-cms-backend-gitlab/src/implementation.ts:57— ClassTooLong — 491 significant lines (blank, comment-only and punctuation-only lines excluded), 49 methods. The bar is 400 significant lines; this is 91 over it, 1.23× 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: Forgejo packages/decap-cms-backend-forgejo/src/implementation.tsx:47— ClassTooLong — 415 significant lines (blank, comment-only and punctuation-only lines excluded), 33 methods. The bar is 400 significant lines; this is 15 over it, 1.04× 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.
Repeated repair: packages/decap-cms-core/src/actions/editorialWorkflow.ts packages/decap-cms-core/src/actions/editorialWorkflow.ts:255— packages/decap-cms-core/src/actions/editorialWorkflow.ts 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 9 (its worst body is editorialWorkflow.loadUnpublishedEntry.<returned closure> at line 255), 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(core): search body only on backends that search it, and other GA fixes”; “fix(core): stop a failed workflow load from retrying on every render”; “Revert the e2e triage probes”; “fix(core): key a new workflow entry on the slug the backend committed”. 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-07-30..2026-10-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-30 14:41:31 +01:00' --until='2026-10-28 14:41:31 +01:00' --full-history --no-merges -- packages/decap-cms-core/src/actions/editorialWorkflow.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/decap-cms-widget-relation/src/RelationControl.js packages/decap-cms-widget-relation/src/RelationControl.js:291— packages/decap-cms-widget-relation/src/RelationControl.js changed 7 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 7 (its worst body is RelationControl.loadInitialOptions at line 291), 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(relation): match filters against multiple-value fields (#8006)”; “Revert "fix(relation): retry menu options after a failed query" and its follow-up”; “fix(relation): guard shouldComponentUpdate when nextState is missing”; “fix(relation): retry menu options after a failed query and cache only success”. 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-07-30..2026-10-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-30 14:41:31 +01:00' --until='2026-10-28 14:41:31 +01:00' --full-history --no-merges -- packages/decap-cms-widget-relation/src/RelationControl.js`: 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/decap/src/login.ts packages/decap/src/login.ts:137— packages/decap/src/login.ts changed 4 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 8 (its worst body is login.listenForCallback 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(decap): fail fast when the instance has no CLI API”; “fix(decap): revoke the token a new login replaces”; “fix(decap): open the login link on Windows without a shell”; “fix(decap): forget the stored token even when revoking it fails”. 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-07-30..2026-10-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-30 14:41:31 +01:00' --until='2026-10-28 14:41:31 +01:00' --full-history --no-merges -- packages/decap/src/login.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.
Off the main sequence: @decap/cli — @decap/cli: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: decap-cms-lib-widgets — decap-cms-lib-widgets: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 6 project(s), so it's rigid to change.
Off the main sequence: decap-cms-lib-util — decap-cms-lib-util: abstractness 0.24, instability 0.00, distance 0.76 — zone of pain — concrete and depended on by 18 project(s), so it's rigid to change.
Low cohesion: TestBackend (LCOM4 15) packages/decap-cms-backend-test/src/implementation.ts:152— TestBackend's methods fall into 15 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 15 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: API (LCOM4 5) packages/decap-cms-backend-git-gateway/src/GitHubAPI.ts:15— API's methods fall into 5 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 5 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: ControlPane (LCOM4 4) packages/decap-cms-core/src/components/Editor/EditorControlPane/EditorControlPane.js:99— ControlPane'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.
Fake-async — async method never awaits packages/decap-cms-backend-bitbucket/src/git-lfs-client.ts:74— `doVerify` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits REDACTED:1247— `unpublishedContentKeys` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/decap/src/dev/middlewares/localFs/index.ts:154— `registerMiddleware` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Duplicated block (23 lines × 2 locations) packages/decap-cms-backend-forgejo/src/implementation.tsx:154— packages/decap-cms-backend-forgejo/src/implementation.tsx:154 · packages/decap-cms-backend-gitea/src/implementation.tsx:128 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (23 lines × 2 locations) packages/decap-cms-core/src/integrations/providers/algolia/implementation.js:44— packages/decap-cms-core/src/integrations/providers/algolia/implementation.js:44 · packages/decap-cms-core/src/integrations/providers/assetStore/implementation.js:18 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (23 lines × 2 locations) REDACTED:703— REDACTED:703 · REDACTED:731 — 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.
remarkSlate.remarkToSlate::convertNode (cyclomatic 28) packages/decap-cms-widget-markdown/src/serializers/remarkSlate.js:235— remarkSlate.remarkToSlate::convertNode has cyclomatic complexity 28 (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.
remarkSlate.remarkToSlate::convertNode (cyclomatic 26) packages/decap-cms-widget-richtext/src/serializers/remarkSlate.js:234— remarkSlate.remarkToSlate::convertNode has cyclomatic complexity 26 (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.
slateRemark.slateToRemark::convertBlockNode (cyclomatic 26) packages/decap-cms-widget-richtext/src/serializers/slateRemark.js:327— slateRemark.slateToRemark::convertBlockNode has cyclomatic complexity 26 (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.
slateRemark.slateToRemark::convertBlockNode (cyclomatic 25) packages/decap-cms-widget-markdown/src/serializers/slateRemark.js:328— slateRemark.slateToRemark::convertBlockNode has cyclomatic complexity 25 (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.
slateRemark.slateToRemark::convertInlineAndTextChildren (cognitive 16) packages/decap-cms-widget-markdown/src/serializers/slateRemark.js:263— slateRemark.slateToRemark::convertInlineAndTextChildren has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 2, 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.
slateRemark.slateToRemark::convertInlineAndTextChildren (cognitive 16) packages/decap-cms-widget-richtext/src/serializers/slateRemark.js:262— slateRemark.slateToRemark::convertInlineAndTextChildren has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 2, 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.
Outbound HTTP without resilience packages/decap/src/api.ts:68— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience packages/decap/src/api.ts:117— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Duplicated block (32 lines × 2 locations) packages/decap-cms-backend-bitbucket/src/implementation.ts:136— packages/decap-cms-backend-bitbucket/src/implementation.ts:136 · packages/decap-cms-backend-github/src/implementation.tsx:145 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (32 lines × 2 locations) packages/decap-cms-core/src/components/Editor/EditorToolbar.js:454— packages/decap-cms-core/src/components/Editor/EditorToolbar.js:454 · packages/decap-cms-core/src/components/Editor/EditorToolbar.js:556 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (27 lines × 2 locations) packages/decap-cms-backend-forgejo/src/AuthenticationPage.js:163— packages/decap-cms-backend-forgejo/src/AuthenticationPage.js:163 · packages/decap-cms-backend-github/src/AuthenticationPage.js:117 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (27 lines × 2 locations) packages/decap-cms-widget-markdown/src/serializers/remarkSquashReferences.js:28— packages/decap-cms-widget-markdown/src/serializers/remarkSquashReferences.js:28 · packages/decap-cms-widget-richtext/src/serializers/remarkSquashReferences.js:31 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (24 lines × 2 locations) packages/decap-cms-widget-markdown/src/MarkdownControl/ToolbarButton.js:12— packages/decap-cms-widget-markdown/src/MarkdownControl/ToolbarButton.js:12 · packages/decap-cms-widget-richtext/src/RichtextControl/components/Toolbar/ToolbarButton.js:13 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (24 lines × 2 locations) packages/decap-cms-widget-markdown/src/serializers/remarkRehypeShortcodes.js:61— packages/decap-cms-widget-markdown/src/serializers/remarkRehypeShortcodes.js:61 · packages/decap-cms-widget-richtext/src/serializers/remarkRehypeShortcodes.js:58 — 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.
Dead file (~18 LoC) jest.resolver.js— no import path from any entry point (150 application, 73 tooling, 254 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 (~18 LoC) setupTestFramework.js— no import path from any entry point (150 application, 73 tooling, 254 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
X24 · Document value interpolated into markup unescaped· Untrusted text written into markup unescaped · ×2
Untrusted text written into markup unescaped packages/decap-cms-widget-markdown/src/MarkdownPreview.js:65— `toRender` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` 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. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped REDACTED:101— `toRender` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` 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. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
S3Widget.S3Widget (cyclomatic 43) packages/decap-cms-media-library-s3/src/components/S3Widget.tsx:57— S3Widget.S3Widget has cyclomatic complexity 43 (threshold 15). Most of this is not in the body itself: 9 of the 43 points are its own statements and the rest belongs to 12 function items inside it that branch (a function literal at line 82, handleUpload, a function literal at line 128, …). 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.
entryDraft.entryDraftReducer (cyclomatic 42) packages/decap-cms-core/src/reducers/entryDraft.js:74— entryDraft.entryDraftReducer has cyclomatic complexity 42 (threshold 15). Of this number, 33 points are the body's own statements and 9 belong to 5 function literals inside it that branch. 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.
config.applyDefaults (cyclomatic 40) packages/decap-cms-core/src/actions/config.ts:232— config.applyDefaults has cyclomatic complexity 40 (threshold 15). Most of this is not in the body itself: 1 of the 40 points is its own statement and the rest belongs to one function literal inside it that branches (line 233). 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.validateInput (cyclomatic 39) packages/decap-turbo-api/src/index.ts:877— index.validateInput has cyclomatic complexity 39 (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.
mediaLibrary.mediaLibrary (cyclomatic 37) packages/decap-cms-core/src/reducers/mediaLibrary.ts:62— mediaLibrary.mediaLibrary has cyclomatic complexity 37 (threshold 15). Of this number, 30 points are the body's own statements and 7 belong to 4 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.
index.localGitMiddleware.<returned closure> (cyclomatic 36) packages/decap/src/dev/middlewares/localGit/index.ts:179— index.localGitMiddleware.<returned closure> has cyclomatic complexity 36 (threshold 15). Of this number, 31 points are the body's own statements and 5 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
withFileControl.withFileControl (cyclomatic 29) packages/decap-cms-widget-file/src/withFileControl.js:240— withFileControl.withFileControl has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 11 of the 29 points are its own statements and the rest belongs to 10 function literals inside it that branch (lines 454, 388, 397, …). 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.
index.main (cyclomatic 27) packages/decap/src/index.ts:63— index.main has cyclomatic complexity 27 (threshold 15). Of this number, 26 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.
editorApi.applyFieldPatch (cyclomatic 26) packages/decap-cms-core/src/lib/editorApi.ts:142— editorApi.applyFieldPatch 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.
editorialWorkflow.unpublishedEntries (cyclomatic 25) packages/decap-cms-core/src/reducers/editorialWorkflow.ts:34— editorialWorkflow.unpublishedEntries has cyclomatic complexity 25 (threshold 15). Of this number, 21 points are the body's own statements and 4 belong to 2 function literals inside it that branch. 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.
GitGateway.authenticate (cyclomatic 22) packages/decap-cms-backend-git-gateway/src/implementation.ts:279— GitGateway.authenticate has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 2 of the 22 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 296, 307, 283, …). 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.
formatters.commitMessageFormatter (cyclomatic 22) packages/decap-cms-core/src/lib/formatters.ts:51— formatters.commitMessageFormatter has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 6 of the 22 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 70, 92). 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.
EditorToolbar.renderWorkflowControls (cyclomatic 22) packages/decap-cms-core/src/components/Editor/EditorToolbar.js:600— EditorToolbar.renderWorkflowControls has cyclomatic complexity 22 (threshold 15). Of this number, 21 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
renderWorkflowStatusControls::renderWorkflowControls (cyclomatic 22) packages/decap-cms-core/src/components/Editor/EditorToolbar.js:600— renderWorkflowStatusControls::renderWorkflowControls has cyclomatic complexity 22 (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.
Backend.persistEntry (cyclomatic 21) REDACTED:1383— Backend.persistEntry 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.
MediaLibraryModal.MediaLibraryModal (cyclomatic 20) packages/decap-cms-core/src/components/MediaLibrary/MediaLibraryModal.js:67— MediaLibraryModal.MediaLibraryModal has cyclomatic complexity 20 (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.
Toolbar.render (cyclomatic 20) packages/decap-cms-widget-markdown/src/MarkdownControl/Toolbar.js:105— Toolbar.render has cyclomatic complexity 20 (threshold 15). Of this number, 19 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
createInlineShortcodeTokenizer (cyclomatic 20) REDACTED:88— createInlineShortcodeTokenizer has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 1 of the 20 points is its own statement and the rest belongs to 5 function items inside it that branch (a function literal at line 151, tokenizeInlineShortcode, a function literal at line 89, …). 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.
commands.formatResult (cyclomatic 19) packages/decap/src/commands.ts:187— commands.formatResult 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.
GitHub.constructor (cyclomatic 18) packages/decap-cms-backend-github/src/implementation.tsx:99— GitHub.constructor 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.
GitLab.constructor (cyclomatic 18) packages/decap-cms-backend-gitlab/src/implementation.ts:93— GitLab.constructor 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.
EditorControl.render (cyclomatic 18) packages/decap-cms-core/src/components/Editor/EditorControlPane/EditorControl.js:256— EditorControl.render has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 4 of the 18 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 312, 347). 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.
editorApi.checkValue (cyclomatic 17) packages/decap-cms-core/src/lib/editorApi.ts:117— editorApi.checkValue has cyclomatic complexity 17 (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.
preloadConfig.createPreloadConfig.preloadConfig (cyclomatic 17) packages/decap-cms-lib-turbo/src/preloadConfig.ts:10— preloadConfig.createPreloadConfig.preloadConfig 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.
InlineShortcode.InlineShortcode (cyclomatic 17) packages/decap-cms-widget-markdown/src/MarkdownControl/components/InlineShortcode.js:9— InlineShortcode.InlineShortcode has cyclomatic complexity 17 (threshold 15). Of this number, 12 points are the body's own statements and 5 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.
withLists (cyclomatic 17) packages/decap-cms-widget-markdown/src/MarkdownControl/plugins/lists/withLists.js:7— withLists has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 2 of the 17 points are its own statements and the rest belongs to 5 function items inside it that branch (normalizeNode, isListItem::match, isListItem, …). 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.
BitbucketBackend.constructor (cyclomatic 16) packages/decap-cms-backend-bitbucket/src/implementation.ts:95— BitbucketBackend.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.
PKCEAuthenticationPage.normalizeClaimsToUser.<returned closure> (cyclomatic 16) packages/decap-cms-ui-auth/src/PKCEAuthenticationPage.js:19— PKCEAuthenticationPage.normalizeClaimsToUser.<returned closure> 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.
remarkRehypeShortcodes.remarkToRehypeShortcodes (cyclomatic 16) packages/decap-cms-widget-markdown/src/serializers/remarkRehypeShortcodes.js:12— remarkRehypeShortcodes.remarkToRehypeShortcodes 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 items inside it that branch (a function literal at line 79, getPreview, transform::walk, …). 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.
withHtml.deserialize (cyclomatic 16) packages/decap-cms-widget-markdown/src/MarkdownControl/plugins/html/withHtml.js:83— withHtml.deserialize 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.
normalizeClaimsToUser (cyclomatic 16) packages/decap-cms-ui-auth/src/PKCEAuthenticationPage.js:12— normalizeClaimsToUser 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 one function literal inside it that branches (line 19). 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.
config.applyDefaults (cognitive 69) packages/decap-cms-core/src/actions/config.ts:232— config.applyDefaults has cognitive complexity 69 (threshold 15). Drivers by points: if/else 25 (51 pts), boolean chains 14, loops 2 (4 pts) (nesting depth added 28). None of this is in the body itself: all 69 points belong to one function literal inside it that branches (line 233). 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.validateInput (cognitive 63) packages/decap-turbo-api/src/index.ts:877— index.validateInput has cognitive complexity 63 (threshold 15). Drivers by points: if/else 18 (42 pts), boolean chains 13, ternaries 2 (5 pts), loops 3 (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.
S3Widget.S3Widget (cognitive 51) packages/decap-cms-media-library-s3/src/components/S3Widget.tsx:57— S3Widget.S3Widget has cognitive complexity 51 (threshold 15). Drivers by points: if/else 22 (24 pts), ternaries 8 (14 pts), boolean chains 7, error handling 5, loops 1 (nesting depth added 8). Most of this is not in the body itself: 9 of the 51 points are its own statements and the rest belongs to 12 function items inside it that branch (a function literal at line 82, handleUpload, a function literal at line 128, …). 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.
index.main (cognitive 41) packages/decap/src/index.ts:63— index.main has cognitive complexity 41 (threshold 15). Drivers by points: if/else 14 (24 pts), ternaries 5 (10 pts), boolean chains 3, loops 1 (3 pts), match/switch 1 (nesting depth added 17). Of this number, 40 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.
index.localGitMiddleware.<returned closure> (cognitive 36) packages/decap/src/dev/middlewares/localGit/index.ts:179— index.localGitMiddleware.<returned closure> has cognitive complexity 36 (threshold 15). Drivers by points: if/else 11 (19 pts), ternaries 3 (9 pts), boolean chains 6, error handling 1, match/switch 1 (nesting depth added 14). Of this number, 23 points are the body's own statements and 13 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.
mediaLibrary.mediaLibrary (cognitive 35) packages/decap-cms-core/src/reducers/mediaLibrary.ts:62— mediaLibrary.mediaLibrary has cognitive complexity 35 (threshold 15). Drivers by points: if/else 12 (22 pts), boolean chains 6, ternaries 3 (6 pts), match/switch 1 (nesting depth added 13). Of this number, 24 points are the body's own statements and 11 belong to 4 function literals inside it that branch. The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
editorApi.applyFieldPatch (cognitive 35) packages/decap-cms-core/src/lib/editorApi.ts:142— editorApi.applyFieldPatch has cognitive complexity 35 (threshold 15). Drivers by points: if/else 10 (17 pts), boolean chains 7, ternaries 3 (6 pts), loops 3 (5 pts) (nesting depth added 12). Of this number, 32 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.
createInlineShortcodeTokenizer (cognitive 30) REDACTED:88— createInlineShortcodeTokenizer has cognitive complexity 30 (threshold 15). Drivers by points: if/else 12 (19 pts), boolean chains 5, ternaries 2 (4 pts), error handling 1 (2 pts) (nesting depth added 10). None of this is in the body itself: all 30 points belong to 5 function items inside it that branch (a function literal at line 151, tokenizeInlineShortcode, a function literal at line 89, …). 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.
withFileControl.withFileControl (cognitive 29) packages/decap-cms-widget-file/src/withFileControl.js:240— withFileControl.withFileControl has cognitive complexity 29 (threshold 15). Drivers by points: ternaries 11 (12 pts), if/else 10, boolean chains 7 (nesting depth added 1). Most of this is not in the body itself: 10 of the 29 points are its own statements and the rest belongs to 10 function literals inside it that branch (lines 454, 388, 397, …). 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.
GitGateway.authenticate (cognitive 26) packages/decap-cms-backend-git-gateway/src/implementation.ts:279— GitGateway.authenticate has cognitive complexity 26 (threshold 15). Drivers by points: if/else 14 (18 pts), boolean chains 4, ternaries 2 (4 pts) (nesting depth added 6). Most of this is not in the body itself: 2 of the 26 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 296, 307, 283, …). 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.
API.uploadFiles (cognitive 25) packages/decap-cms-backend-bitbucket/src/API.ts:426— API.uploadFiles has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (11 pts), ternaries 2 (7 pts), loops 2 (4 pts), boolean chains 2, error handling 1 (nesting depth added 9). Of this number, 22 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.
NotesPollingManager.checkCurrentIssue (cognitive 23) REDACTED:315— NotesPollingManager.checkCurrentIssue has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (20 pts), boolean chains 2, 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.
insertShortcode.insertShortcode (cognitive 23) packages/decap-cms-widget-markdown/src/MarkdownControl/plugins/shortcodes/insertShortcode.js:5— insertShortcode.insertShortcode has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (12 pts), ternaries 3 (5 pts), boolean chains 3, error handling 1 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
API.requestWithBackoff (cognitive 22) packages/decap-cms-lib-util/src/API.ts:63— API.requestWithBackoff has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (11 pts), ternaries 2 (7 pts), boolean chains 3, error handling 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.
remarkSlate.remarkToSlate (cognitive 22) packages/decap-cms-widget-markdown/src/serializers/remarkSlate.js:82— remarkSlate.remarkToSlate has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 9 (14 pts), if/else 4, boolean chains 2, match/switch 2 (nesting depth added 5). None of this is in the body itself: all 22 points belong to 9 function items inside it that branch (convertNode, transformNode, createBlock, …). 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.
entryDraft.entryDraftReducer (cognitive 21) packages/decap-cms-core/src/reducers/entryDraft.js:74— entryDraft.entryDraftReducer has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 2 (4 pts), boolean chains 3, ternaries 1 (2 pts), match/switch 1 (nesting depth added 8). Most of this is not in the body itself: 4 of the 21 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 133, 163, 173, …). 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.
args.parseCliArgs (cognitive 21) packages/decap/src/args.ts:24— args.parseCliArgs has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (18 pts), boolean chains 2, loops 1 (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.
GraphQLAPI.mutate (cognitive 20) packages/decap-cms-backend-github/src/GraphQLAPI.ts:156— GraphQLAPI.mutate has cognitive complexity 20 (threshold 15). Drivers by points: if/else 4 (9 pts), boolean chains 6, error handling 2 (5 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.
configSchema.validateConfig (cognitive 20) packages/decap-cms-core/src/constants/configSchema.js:424— configSchema.validateConfig has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 3, match/switch 1 (2 pts) (nesting depth added 8). Most of this is not in the body itself: 2 of the 20 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 434, 470, 473). 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.
entries.evaluateFolder (cognitive 20) REDACTED:669— entries.evaluateFolder has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (20 pts) (nesting depth added 11). 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.
Backend.persistEntry (cognitive 20) REDACTED:1383— Backend.persistEntry has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 8, 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.
remarkSlate.remarkToSlate (cognitive 20) packages/decap-cms-widget-richtext/src/serializers/remarkSlate.js:81— remarkSlate.remarkToSlate has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 8 (12 pts), if/else 4, boolean chains 2, match/switch 2 (nesting depth added 4). None of this is in the body itself: all 20 points belong to 9 function items inside it that branch (convertNode, transformNode, createBlock, …). 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.
commands.formatResult (cognitive 20) packages/decap/src/commands.ts:187— commands.formatResult has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 5, ternaries 2 (4 pts), loops 1 (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.
InlineShortcode.InlineShortcode (cognitive 19) packages/decap-cms-widget-markdown/src/MarkdownControl/components/InlineShortcode.js:9— InlineShortcode.InlineShortcode has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 8, if/else 5 (6 pts), ternaries 3, error handling 1 (2 pts) (nesting depth added 2). Of this number, 12 points are the body's own statements and 7 belong to one function item inside it that branches. 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.
withHtml.deserialize (cognitive 19) packages/decap-cms-widget-markdown/src/MarkdownControl/plugins/html/withHtml.js:83— withHtml.deserialize has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12 (16 pts), loops 1 (2 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.
render (cognitive 19) packages/decap-cms-widget-markdown/src/MarkdownControl/Toolbar.js:105— render has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 15, ternaries 4. Of this number, 16 points are the body's own statements and 3 belong to 14 function items 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.
API.listFiles (cognitive 18) packages/decap-cms-backend-forgejo/src/API.ts:384— API.listFiles has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (10 pts), boolean chains 4, ternaries 3, error handling 1 (nesting depth added 4). Most of this is not in the body itself: 7 of the 18 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 407, 425). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
GitHub.constructor (cognitive 18) packages/decap-cms-backend-github/src/implementation.tsx:99— GitHub.constructor has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 13, if/else 4 (5 pts) (nesting depth added 1). 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.
formatters.commitMessageFormatter (cognitive 18) packages/decap-cms-core/src/lib/formatters.ts:51— formatters.commitMessageFormatter has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 8, if/else 5 (6 pts), match/switch 2, ternaries 1 (2 pts) (nesting depth added 2). Most of this is not in the body itself: 7 of the 18 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 70, 92). 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.
mediaLibrary.persistMedia.<returned closure> (cognitive 18) packages/decap-cms-core/src/actions/mediaLibrary.ts:268— mediaLibrary.persistMedia.<returned closure> has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (12 pts), error handling 2 (3 pts), boolean chains 2, 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.
entries.createEmptyDraftData (cognitive 18) packages/decap-cms-core/src/actions/entries.ts:868— entries.createEmptyDraftData has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (9 pts), ternaries 2 (6 pts), boolean chains 3 (nesting depth added 7). None of this is in the body itself: all 18 points belong to one function literal inside it that branches (line 873). 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.
EditorToolbar.renderWorkflowControls (cognitive 18) packages/decap-cms-core/src/components/Editor/EditorToolbar.js:600— EditorToolbar.renderWorkflowControls has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 11, ternaries 5 (7 pts) (nesting depth added 2). Of this number, 17 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
renderWorkflowStatusControls::renderWorkflowControls (cognitive 18) packages/decap-cms-core/src/components/Editor/EditorToolbar.js:600— renderWorkflowStatusControls::renderWorkflowControls has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 12, ternaries 5, other 1. 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.
MediaLibraryModal (cognitive 18) packages/decap-cms-core/src/components/MediaLibrary/MediaLibraryModal.js:67— MediaLibraryModal has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 15, ternaries 3. 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.
withLists (cognitive 18) packages/decap-cms-widget-markdown/src/MarkdownControl/plugins/lists/withLists.js:7— withLists has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 7, loops 1 (2 pts) (nesting depth added 4). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 5 function items inside it that branch (normalizeNode, isListItem, isListItem::match, …). 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.
API.hasWriteAccess (cognitive 17) packages/decap-cms-backend-gitlab/src/API.ts:324— API.hasWriteAccess has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (10 pts), boolean chains 4, error handling 1 (3 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.
preloadConfig.createPreloadConfig.preloadConfig (cognitive 17) packages/decap-cms-lib-turbo/src/preloadConfig.ts:10— preloadConfig.createPreloadConfig.preloadConfig has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 7, if/else 5, loops 1 (2 pts), ternaries 2, error handling 1 (nesting depth added 1). 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.
CodeControl.handleChangeCodeMirrorProps (cognitive 17) packages/decap-cms-widget-code/src/CodeControl.js:204— CodeControl.handleChangeCodeMirrorProps has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (10 pts), error handling 1 (4 pts), boolean chains 2, 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.
remarkRehypeShortcodes.remarkToRehypeShortcodes (cognitive 17) packages/decap-cms-widget-markdown/src/serializers/remarkRehypeShortcodes.js:12— remarkRehypeShortcodes.remarkToRehypeShortcodes has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 3, ternaries 2 (3 pts) (nesting depth added 3). None of this is in the body itself: all 17 points belong to 4 function items inside it that branch (a function literal at line 79, transform::walk, processShortcodes, …). 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.
Forgejo.constructor (cognitive 16) packages/decap-cms-backend-forgejo/src/implementation.tsx:73— Forgejo.constructor has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 10, if/else 5 (6 pts) (nesting depth added 1). 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.
API.updateUnpublishedEntryStatus (cognitive 16) packages/decap-cms-backend-github/src/API.ts:1204— API.updateUnpublishedEntryStatus has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 3 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GitLab.constructor (cognitive 16) packages/decap-cms-backend-gitlab/src/implementation.ts:93— GitLab.constructor has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 15, if/else 1. 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.
EditorControl.render (cognitive 16) packages/decap-cms-core/src/components/Editor/EditorControlPane/EditorControl.js:256— EditorControl.render has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 16. Most of this is not in the body itself: 3 of the 16 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 312, 347). 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.
PKCEAuthenticationPage.normalizeClaimsToUser.<returned closure> (cognitive 16) packages/decap-cms-ui-auth/src/PKCEAuthenticationPage.js:19— PKCEAuthenticationPage.normalizeClaimsToUser.<returned closure> has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 5 (nesting depth added 3). 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.
server.runDevServer (cognitive 16) packages/decap/src/dev/server.ts:44— server.runDevServer has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 3, error handling 1, loops 1 (nesting depth added 3). 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.
normalizeClaimsToUser (cognitive 16) packages/decap-cms-ui-auth/src/PKCEAuthenticationPage.js:12— normalizeClaimsToUser has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 5 (nesting depth added 3). None of this is in the body itself: all 16 points belong to one function literal inside it that branches (line 19). 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.
Unstable project decap-cms-core — decap-cms-core has instability 0.83 with 1 dependents.
IC1 · Incompleteness & stubs· Both branches are identical · ×1
Both branches are identical — the condition decides nothing packages/decap-cms-core/src/components/Editor/EditorNotesPane/NoteItem.js:9— Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition.
IC1 · Incompleteness & stubs· Markup wires an event to an empty handler · ×1
Markup wires an event to an empty handler packages/decap-cms-widget-richtext/src/RichtextControl/components/Element/ShortcodeElement.js:102— `onValidateObject` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
Duplication concentrated across 33 sibling directories (98 clone groups) packages/decap-cms-backend-forgejo/src/API.ts:56— 98 duplicated blocks under packages/ have copies in at least two of the sibling directories decap, decap-cms, decap-cms-app, decap-cms-backend-aws-cognito-github-proxy, decap-cms-backend-azure, decap-cms-backend-bitbucket (+27 more sibling(s) not listed) — 79 of them are reported below, and 19 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 98 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 98 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 98 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 7 sibling directories (10 clone groups) packages/decap-cms-core/src/components/Collection/Entries/EntryCard.js:232— 10 duplicated blocks under packages/decap-cms-core/src/components/ have copies in at least two of the sibling directories App, Collection, Deploys, Editor, MediaLibrary, UI (+1 more sibling(s) not listed) — 1 of them are reported below, and 9 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 10 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 10 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 10 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 4 sibling directories (6 clone groups) packages/decap-cms-widget-markdown/src/MarkdownControl/plugins/blocks/events/keyDown.js:10— 6 duplicated blocks under packages/decap-cms-widget-markdown/src/MarkdownControl/plugins/ have copies in at least two of the sibling directories blocks, inlines, lists, shortcodes — 3 of them are reported below, and 3 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 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication· Duplicated block with local edits (350 matched lines × 2 locations) · ×1
Duplicated block with local edits (350 matched lines × 2 locations) packages/decap-cms-backend-forgejo/src/API.ts:56— packages/decap-cms-backend-forgejo/src/API.ts:56 · packages/decap-cms-backend-gitea/src/API.ts:40 — the two spans are one implementation copied and then locally edited — 2148 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 (333 matched lines × 2 locations) · ×1
Duplicated block with local edits (333 matched lines × 2 locations) packages/decap-cms-backend-bitbucket/src/implementation.ts:93— packages/decap-cms-backend-bitbucket/src/implementation.ts:93 · packages/decap-cms-backend-gitlab/src/implementation.ts:91 — the two spans are one implementation copied and then locally edited — 2043 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.
Wholesale file copy (198 identical lines × 2 files) packages/decap-cms-widget-markdown/src/serializers/slateRemark.js:1— packages/decap-cms-widget-markdown/src/serializers/slateRemark.js:1 · packages/decap-cms-widget-richtext/src/serializers/slateRemark.js:1 — these 2 files are line-for-line copies of one another — 198 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication· Duplicated block with local edits (181 matched lines × 2 locations) · ×1
Duplicated block with local edits (181 matched lines × 2 locations) packages/decap-cms-backend-turbo-github/src/implementation.tsx:126— packages/decap-cms-backend-turbo-github/src/implementation.tsx:126 · packages/decap-cms-backend-turbo-gitlab/src/implementation.tsx:109 — the two spans are one implementation copied and then locally edited — 1115 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 (164 matched lines × 2 locations) · ×1
Duplicated block with local edits (164 matched lines × 2 locations) packages/decap-cms-backend-azure/src/implementation.ts:108— packages/decap-cms-backend-azure/src/implementation.ts:108 · packages/decap-cms-backend-gitlab/src/implementation.ts:138 — the two spans are one implementation copied and then locally edited — 998 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.
Wholesale file copy (163 identical lines × 2 files) packages/decap-cms-widget-markdown/src/serializers/remarkSlate.js:1— packages/decap-cms-widget-markdown/src/serializers/remarkSlate.js:1 · packages/decap-cms-widget-richtext/src/serializers/remarkSlate.js:1 — these 2 files are line-for-line copies of one another — 163 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication· Duplicated block with local edits (162 matched lines × 2 locations) · ×1
Duplicated block with local edits (162 matched lines × 2 locations) packages/decap-cms-backend-github/src/implementation.tsx:647— packages/decap-cms-backend-github/src/implementation.tsx:647 · packages/decap-cms-backend-gitlab/src/implementation.ts:503 — the two spans are one implementation copied and then locally edited — 1089 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 (106 matched lines × 2 locations) · ×1
Duplicated block with local edits (106 matched lines × 2 locations) packages/decap-cms-backend-azure/src/API.ts:517— packages/decap-cms-backend-azure/src/API.ts:517 · packages/decap-cms-backend-gitlab/src/API.ts:640 — the two spans are one implementation copied and then locally edited — 639 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 (106 lines × 2 locations) packages/decap-cms-widget-markdown/src/regexHelper.js:32— packages/decap-cms-widget-markdown/src/regexHelper.js:32 · packages/decap-cms-widget-richtext/src/serializers/regexHelper.js:32 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R10 · Code Duplication· Duplicated block with local edits (101 matched lines × 2 locations) · ×1
Duplicated block with local edits (101 matched lines × 2 locations) packages/decap-cms-backend-forgejo/src/implementation.tsx:95— packages/decap-cms-backend-forgejo/src/implementation.tsx:95 · packages/decap-cms-backend-github/src/implementation.tsx:115 — the two spans are one implementation copied and then locally edited — 631 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 (97 lines × 2 locations) packages/decap-cms-backend-gitea/src/implementation.tsx:306— packages/decap-cms-backend-gitea/src/implementation.tsx:306 · packages/decap-cms-backend-github/src/implementation.tsx:520 — 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.
Wholesale file copy (91 identical lines × 2 files) packages/decap-cms-widget-markdown/src/serializers/index.js:1— packages/decap-cms-widget-markdown/src/serializers/index.js:1 · packages/decap-cms-widget-richtext/src/serializers/index.js:1 — these 2 files are line-for-line copies of one another — 91 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Duplicated block (73 lines × 2 locations) packages/decap-cms-backend-forgejo/src/implementation.tsx:351— packages/decap-cms-backend-forgejo/src/implementation.tsx:351 · packages/decap-cms-backend-gitea/src/implementation.tsx:193 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (71 lines × 2 locations) packages/decap-cms-backend-forgejo/src/types.ts:182— packages/decap-cms-backend-forgejo/src/types.ts:182 · packages/decap-cms-backend-gitea/src/types.ts:182 — the 2 copies are spread across 2 files, 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 (69 matched lines × 2 locations) · ×1
Duplicated block with local edits (69 matched lines × 2 locations) packages/decap-cms-widget-markdown/src/MarkdownControl/index.js:25— packages/decap-cms-widget-markdown/src/MarkdownControl/index.js:25 · packages/decap-cms-widget-richtext/src/RichtextControl.js:12 — the two spans are one implementation copied and then locally edited — 422 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 (67 lines × 2 locations) packages/decap-cms-widget-markdown/src/serializers/remarkEscapeMarkdownEntities.js:11— packages/decap-cms-widget-markdown/src/serializers/remarkEscapeMarkdownEntities.js:11 · packages/decap-cms-widget-richtext/src/serializers/remarkEscapeMarkdownEntities.js:11 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R10 · Code Duplication· Duplicated block with local edits (59 matched lines × 2 locations) · ×1
Duplicated block with local edits (59 matched lines × 2 locations) packages/decap-cms-backend-forgejo/src/AuthenticationPage.js:7— packages/decap-cms-backend-forgejo/src/AuthenticationPage.js:7 · packages/decap-cms-backend-github/src/AuthenticationPage.js:7 — the two spans are one implementation copied and then locally edited — 309 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 (58 matched lines × 2 locations) · ×1
Duplicated block with local edits (58 matched lines × 2 locations) packages/decap-cms-core/src/actions/editorialWorkflow.ts:367— packages/decap-cms-core/src/actions/editorialWorkflow.ts:367 · packages/decap-cms-core/src/actions/entries.ts:977 — the two spans are one implementation copied and then locally edited — 318 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 (48 lines × 2 locations) packages/decap-cms-widget-markdown/src/serializers/remarkPaddedLinks.js:20— packages/decap-cms-widget-markdown/src/serializers/remarkPaddedLinks.js:20 · packages/decap-cms-widget-richtext/src/serializers/remarkPaddedLinks.js:20 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (45 lines × 3 locations) packages/decap-cms-backend-forgejo/src/implementation.tsx:537— packages/decap-cms-backend-forgejo/src/implementation.tsx:537 · packages/decap-cms-backend-gitea/src/implementation.tsx:370 · packages/decap-cms-backend-github/src/implementation.tsx:584 — the 3 copies are spread across 3 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. 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 (43 lines × 2 locations) packages/decap-cms-backend-forgejo/src/types.ts:36— packages/decap-cms-backend-forgejo/src/types.ts:36 · packages/decap-cms-backend-gitea/src/types.ts:36 — the 2 copies are spread across 2 files, 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.
Duplicated block (42 lines × 2 locations) packages/decap-cms-widget-markdown/src/serializers/remarkAllowHtmlEntities.js:1— packages/decap-cms-widget-markdown/src/serializers/remarkAllowHtmlEntities.js:1 · packages/decap-cms-widget-richtext/src/serializers/remarkAllowHtmlEntities.js:1 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R10 · Code Duplication· Duplicated block with local edits (42 matched lines × 2 locations) · ×1
Duplicated block with local edits (42 matched lines × 2 locations) REDACTED:28— REDACTED:28 · packages/decap-cms-widget-richtext/src/serializers/remarkShortcodes.js:13 — the two spans are one implementation copied and then locally edited — 214 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 (36 lines × 2 locations) packages/decap-cms-widget-markdown/src/schema.js:1— packages/decap-cms-widget-markdown/src/schema.js:1 · packages/decap-cms-widget-richtext/src/schema.js:1 — the 2 copies are spread across 2 files, 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.
Duplicated block (35 lines × 2 locations) packages/decap-cms-core/src/actions/entries.ts:247— packages/decap-cms-core/src/actions/entries.ts:247 · packages/decap-cms-core/src/actions/entries.ts:286 — 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 (28 lines × 3 locations) packages/decap-cms-backend-aws-cognito-github-proxy/src/AuthenticationPage.js:55— packages/decap-cms-backend-aws-cognito-github-proxy/src/AuthenticationPage.js:55 · packages/decap-cms-backend-bitbucket/src/AuthenticationPage.js:73 · packages/decap-cms-ui-auth/src/PKCEAuthenticationPage.js:125 — the 3 copies are spread across 3 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. 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 (26 lines × 2 locations) packages/decap-cms-widget-markdown/src/MarkdownControl/VisualEditor.js:53— packages/decap-cms-widget-markdown/src/MarkdownControl/VisualEditor.js:53 · packages/decap-cms-widget-richtext/src/RichtextControl/mergeMediaConfig.js:1 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (25 lines × 2 locations) packages/decap-cms-widget-markdown/src/MarkdownControl/Toolbar.js:194— packages/decap-cms-widget-markdown/src/MarkdownControl/Toolbar.js:194 · packages/decap-cms-widget-richtext/src/RichtextControl/components/Toolbar/HeadingToolbarButton.js:66 — 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 (anonymous) (cyclomatic 40, cognitive 69) packages/decap-cms-core/src/actions/config.ts:233— (anonymous) has cyclomatic complexity 40 and cognitive complexity 69; 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 validateInput (cyclomatic 40, cognitive 65) packages/decap-turbo-api/src/index.ts:877— validateInput has cyclomatic complexity 40 and cognitive complexity 65; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 31, cognitive 23) packages/decap/src/dev/middlewares/localGit/index.ts:179— (anonymous) has cyclomatic complexity 31 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 mediaLibrary (cyclomatic 30, cognitive 24) packages/decap-cms-core/src/reducers/mediaLibrary.ts:62— mediaLibrary has cyclomatic complexity 30 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 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 convertNode (cyclomatic 28, cognitive 11) packages/decap-cms-widget-markdown/src/serializers/remarkSlate.js:235— convertNode has cyclomatic complexity 28 and cognitive complexity 11; 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.
R2 · Cyclomatic Complexity· Complex function main (cyclomatic 27, cognitive 41) · ×1
Complex function main (cyclomatic 27, cognitive 41) packages/decap/src/index.ts:63— main has cyclomatic complexity 27 and cognitive complexity 41; 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 applyFieldPatch (cyclomatic 27, cognitive 37) packages/decap-cms-core/src/lib/editorApi.ts:142— applyFieldPatch has cyclomatic complexity 27 and cognitive complexity 37; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function convertNode (cyclomatic 26, cognitive 9) packages/decap-cms-widget-richtext/src/serializers/remarkSlate.js:234— convertNode has cyclomatic complexity 26 and cognitive complexity 9; 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 convertBlockNode (cyclomatic 26, cognitive 9) packages/decap-cms-widget-richtext/src/serializers/slateRemark.js:327— convertBlockNode has cyclomatic complexity 26 and cognitive complexity 9; 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 convertBlockNode (cyclomatic 25, cognitive 9) packages/decap-cms-widget-markdown/src/serializers/slateRemark.js:328— convertBlockNode has cyclomatic complexity 25 and cognitive complexity 9; 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 renderWorkflowControls (cyclomatic 22, cognitive 18) packages/decap-cms-core/src/components/Editor/EditorToolbar.js:600— renderWorkflowControls has cyclomatic complexity 22 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function persistEntry (cyclomatic 21, cognitive 25) REDACTED:1383— persistEntry has cyclomatic complexity 21 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function MediaLibraryModal (cyclomatic 20, cognitive 18) packages/decap-cms-core/src/components/MediaLibrary/MediaLibraryModal.js:67— MediaLibraryModal has cyclomatic complexity 20 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function promotePrereleaseOnlyLatest (cyclomatic 19, cognitive 26) REDACTED:201— promotePrereleaseOnlyLatest has cyclomatic complexity 19 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 formatResult (cyclomatic 19, cognitive 21) packages/decap/src/commands.ts:187— formatResult has cyclomatic complexity 19 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function constructor (cyclomatic 18, cognitive 19) packages/decap-cms-backend-github/src/implementation.tsx:99— constructor has cyclomatic complexity 18 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 preloadConfig (cyclomatic 18, cognitive 19) packages/decap-cms-lib-turbo/src/preloadConfig.ts:10— preloadConfig has cyclomatic complexity 18 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 constructor (cyclomatic 18, cognitive 17) packages/decap-cms-backend-gitlab/src/implementation.ts:93— constructor has cyclomatic complexity 18 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function compareVersions (cyclomatic 17, cognitive 27) REDACTED:158— compareVersions has cyclomatic complexity 17 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function checkValue (cyclomatic 17, cognitive 16) packages/decap-cms-core/src/lib/editorApi.ts:117— checkValue has cyclomatic complexity 17 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function render (cyclomatic 17, cognitive 16) packages/decap-cms-widget-markdown/src/MarkdownControl/Toolbar.js:105— render has cyclomatic complexity 17 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function requestWithBackoff (cyclomatic 16, cognitive 27) packages/decap-cms-lib-util/src/API.ts:63— requestWithBackoff has cyclomatic complexity 16 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function deserialize (cyclomatic 16, cognitive 19) packages/decap-cms-widget-markdown/src/MarkdownControl/plugins/html/withHtml.js:83— deserialize has cyclomatic complexity 16 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 checkPackage (cyclomatic 16, cognitive 18) scripts/verify-published-packages.mjs:230— checkPackage has cyclomatic complexity 16 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 16, cognitive 16) packages/decap-cms-ui-auth/src/PKCEAuthenticationPage.js:19— (anonymous) has cyclomatic complexity 16 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 call (cyclomatic 16, cognitive 16) packages/decap/src/api.ts:35— call has cyclomatic complexity 16 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 constructor (cyclomatic 16, cognitive 15) packages/decap-cms-backend-bitbucket/src/implementation.ts:95— constructor has cyclomatic complexity 16 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 insertShortcode (cyclomatic 15, cognitive 23) packages/decap-cms-widget-markdown/src/MarkdownControl/plugins/shortcodes/insertShortcode.js:5— insertShortcode has cyclomatic complexity 15 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.
R2 · Cyclomatic Complexity· Complex function main (cyclomatic 15, cognitive 23) · ×1
Complex function main (cyclomatic 15, cognitive 23) REDACTED:327— main has cyclomatic complexity 15 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.
R2 · Cyclomatic Complexity· Complex function main (cyclomatic 15, cognitive 21) · ×1
Complex function main (cyclomatic 15, cognitive 21) scripts/verify-published-packages.mjs:316— main has cyclomatic complexity 15 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function getCypressArgs (cyclomatic 15, cognitive 20) cypress/run.mjs:27— getCypressArgs has cyclomatic complexity 15 and cognitive complexity 20; 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 constructor (cyclomatic 15, cognitive 16) packages/decap-cms-backend-forgejo/src/implementation.tsx:73— constructor has cyclomatic complexity 15 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 getFormat (cyclomatic 15, cognitive 14) packages/decap-cms-widget-datetime/src/DateTimeControl.js:88— getFormat has cyclomatic complexity 15 and cognitive complexity 14; 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 persistFiles (cyclomatic 15, cognitive 13) packages/decap-cms-backend-turbo-github/src/API.ts:149— persistFiles has cyclomatic complexity 15 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.
R2 · Cyclomatic Complexity· Complex function match (cyclomatic 15, cognitive 12) · ×1
Complex function match (cyclomatic 15, cognitive 12) packages/decap-cms-widget-markdown/src/MarkdownControl/plugins/matchers/matchedAncestors.js:5— match has cyclomatic complexity 15 and cognitive complexity 12; 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 checkCurrentIssue (cyclomatic 14, cognitive 23) REDACTED:315— checkCurrentIssue has cyclomatic complexity 14 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 mutate (cyclomatic 14, cognitive 20) packages/decap-cms-backend-github/src/GraphQLAPI.ts:156— mutate has cyclomatic complexity 14 and cognitive complexity 20; 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 responseBodySanitizer (cyclomatic 14, cognitive 15) cypress/plugins/github.js:338— responseBodySanitizer has cyclomatic complexity 14 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 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 14, cognitive 15) packages/decap-cms-backend-git-gateway/src/implementation.ts:296— (anonymous) has cyclomatic complexity 14 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 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 detectProxyServer (cyclomatic 14, cognitive 13) packages/decap-cms-core/src/actions/config.ts:508— detectProxyServer has cyclomatic complexity 14 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.
R3 · Large Files· packages/decap-cms-backend-github/src/API.ts · ×1
packages/decap-cms-backend-github/src/API.ts: 1801 lines of code packages/decap-cms-backend-github/src/API.ts:1— packages/decap-cms-backend-github/src/API.ts has 1801 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/decap-cms-core/src/actions/entries.ts · ×1
packages/decap-cms-core/src/actions/entries.ts: 1389 lines of code packages/decap-cms-core/src/actions/entries.ts:1— packages/decap-cms-core/src/actions/entries.ts has 1389 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/decap-cms-backend-forgejo/src/API.ts · ×1
packages/decap-cms-backend-forgejo/src/API.ts: 957 lines of code packages/decap-cms-backend-forgejo/src/API.ts:1— packages/decap-cms-backend-forgejo/src/API.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.
R3 · Large Files· packages/decap-cms-backend-gitlab/src/API.ts · ×1
packages/decap-cms-backend-gitlab/src/API.ts: 940 lines of code packages/decap-cms-backend-gitlab/src/API.ts:1— packages/decap-cms-backend-gitlab/src/API.ts has 940 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/decap-turbo-api/src/index.ts · ×1
packages/decap-turbo-api/src/index.ts: 883 lines of code packages/decap-turbo-api/src/index.ts:1— packages/decap-turbo-api/src/index.ts has 883 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/decap-cms-backend-github/src/implementation.tsx · ×1
packages/decap-cms-backend-github/src/implementation.tsx: 851 lines of code packages/decap-cms-backend-github/src/implementation.tsx:1— packages/decap-cms-backend-github/src/implementation.tsx has 851 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/decap-cms-core/src/types/redux.ts · ×1
packages/decap-cms-core/src/types/redux.ts: 795 lines of code packages/decap-cms-core/src/types/redux.ts:1— packages/decap-cms-core/src/types/redux.ts has 795 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/decap-cms-backend-bitbucket/src/API.ts · ×1
packages/decap-cms-backend-bitbucket/src/API.ts: 759 lines of code packages/decap-cms-backend-bitbucket/src/API.ts:1— packages/decap-cms-backend-bitbucket/src/API.ts has 759 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: 757 lines of code REDACTED:1— REDACTED has 757 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/decap-cms-backend-turbo-github/src/deployWatcher.ts · ×1
packages/decap-cms-backend-turbo-github/src/deployWatcher.ts: 750 lines of code packages/decap-cms-backend-turbo-github/src/deployWatcher.ts:1— packages/decap-cms-backend-turbo-github/src/deployWatcher.ts has 750 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: 740 lines of code REDACTED:1— REDACTED has 740 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/decap-cms-backend-azure/src/API.ts · ×1
packages/decap-cms-backend-azure/src/API.ts: 719 lines of code packages/decap-cms-backend-azure/src/API.ts:1— packages/decap-cms-backend-azure/src/API.ts has 719 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/decap-cms-backend-gitlab/src/implementation.ts · ×1
packages/decap-cms-backend-gitlab/src/implementation.ts: 682 lines of code packages/decap-cms-backend-gitlab/src/implementation.ts:1— packages/decap-cms-backend-gitlab/src/implementation.ts has 682 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/decap-cms-core/src/components/Editor/EditorToolbar.js · ×1
packages/decap-cms-core/src/components/Editor/EditorToolbar.js: 657 lines of code packages/decap-cms-core/src/components/Editor/EditorToolbar.js:1— packages/decap-cms-core/src/components/Editor/EditorToolbar.js has 657 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/decap-cms-backend-github/src/GraphQLAPI.ts · ×1
packages/decap-cms-backend-github/src/GraphQLAPI.ts: 645 lines of code packages/decap-cms-backend-github/src/GraphQLAPI.ts:1— packages/decap-cms-backend-github/src/GraphQLAPI.ts has 645 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/decap-cms-lib-util/src/implementation.ts · ×1
packages/decap-cms-lib-util/src/implementation.ts: 626 lines of code packages/decap-cms-lib-util/src/implementation.ts:1— packages/decap-cms-lib-util/src/implementation.ts has 626 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/decap-cms-backend-git-gateway/src/implementation.ts · ×1
packages/decap-cms-backend-git-gateway/src/implementation.ts: 609 lines of code packages/decap-cms-backend-git-gateway/src/implementation.ts:1— packages/decap-cms-backend-git-gateway/src/implementation.ts has 609 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/decap-cms-core/src/actions/mediaLibrary.ts · ×1
packages/decap-cms-core/src/actions/mediaLibrary.ts: 602 lines of code packages/decap-cms-core/src/actions/mediaLibrary.ts:1— packages/decap-cms-core/src/actions/mediaLibrary.ts has 602 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/decap-cms-backend-forgejo/src/implementation.tsx · ×1
packages/decap-cms-backend-forgejo/src/implementation.tsx: 581 lines of code packages/decap-cms-backend-forgejo/src/implementation.tsx:1— packages/decap-cms-backend-forgejo/src/implementation.tsx has 581 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/decap-cms-backend-bitbucket/src/implementation.ts · ×1
packages/decap-cms-backend-bitbucket/src/implementation.ts: 580 lines of code packages/decap-cms-backend-bitbucket/src/implementation.ts:1— packages/decap-cms-backend-bitbucket/src/implementation.ts has 580 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/decap-cms-lib-turbo/src/session.ts · ×1
packages/decap-cms-lib-turbo/src/session.ts: 577 lines of code packages/decap-cms-lib-turbo/src/session.ts:1— packages/decap-cms-lib-turbo/src/session.ts has 577 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/decap-cms-backend-turbo-github/src/implementation.tsx · ×1
packages/decap-cms-backend-turbo-github/src/implementation.tsx: 572 lines of code packages/decap-cms-backend-turbo-github/src/implementation.tsx:1— packages/decap-cms-backend-turbo-github/src/implementation.tsx has 572 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/decap-cms-core/src/actions/config.ts · ×1
packages/decap-cms-core/src/actions/config.ts: 551 lines of code packages/decap-cms-core/src/actions/config.ts:1— packages/decap-cms-core/src/actions/config.ts has 551 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/decap-cms-core/src/actions/editorialWorkflow.ts · ×1
packages/decap-cms-core/src/actions/editorialWorkflow.ts: 550 lines of code packages/decap-cms-core/src/actions/editorialWorkflow.ts:1— packages/decap-cms-core/src/actions/editorialWorkflow.ts has 550 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/decap-cms-core/src/components/Editor/EditorControlPane/EditorControl.js · ×1
packages/decap-cms-core/src/components/Editor/EditorControlPane/EditorControl.js: 521 lines of code packages/decap-cms-core/src/components/Editor/EditorControlPane/EditorControl.js:1— packages/decap-cms-core/src/components/Editor/EditorControlPane/EditorControl.js has 521 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/decap-cms-core/src/components/Editor/Editor.js · ×1
packages/decap-cms-core/src/components/Editor/Editor.js: 520 lines of code packages/decap-cms-core/src/components/Editor/Editor.js:1— packages/decap-cms-core/src/components/Editor/Editor.js has 520 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/decap-cms-ui-default/src/styles.js · ×1
packages/decap-cms-ui-default/src/styles.js: 510 lines of code packages/decap-cms-ui-default/src/styles.js:1— packages/decap-cms-ui-default/src/styles.js has 510 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/decap-cms-core/src/components/Editor/EditorInterface.js · ×1
packages/decap-cms-core/src/components/Editor/EditorInterface.js: 496 lines of code packages/decap-cms-core/src/components/Editor/EditorInterface.js:1— packages/decap-cms-core/src/components/Editor/EditorInterface.js has 496 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/decap-cms-widget-relation/src/RelationControl.js · ×1
packages/decap-cms-widget-relation/src/RelationControl.js: 475 lines of code packages/decap-cms-widget-relation/src/RelationControl.js:1— packages/decap-cms-widget-relation/src/RelationControl.js has 475 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/decap-cms-core/src/constants/configSchema.js · ×1
packages/decap-cms-core/src/constants/configSchema.js: 468 lines of code packages/decap-cms-core/src/constants/configSchema.js:1— packages/decap-cms-core/src/constants/configSchema.js has 468 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/decap-cms-core/src/reducers/collections.ts · ×1
packages/decap-cms-core/src/reducers/collections.ts: 463 lines of code packages/decap-cms-core/src/reducers/collections.ts:1— packages/decap-cms-core/src/reducers/collections.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/decap-cms-backend-test/src/implementation.ts · ×1
packages/decap-cms-backend-test/src/implementation.ts: 457 lines of code packages/decap-cms-backend-test/src/implementation.ts:1— packages/decap-cms-backend-test/src/implementation.ts has 457 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/decap/src/dev/middlewares/localGit/index.ts · ×1
packages/decap/src/dev/middlewares/localGit/index.ts: 452 lines of code packages/decap/src/dev/middlewares/localGit/index.ts:1— packages/decap/src/dev/middlewares/localGit/index.ts has 452 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: 444 lines of code REDACTED:1— REDACTED has 444 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/decap-cms-widget-file/src/withFileControl.js · ×1
packages/decap-cms-widget-file/src/withFileControl.js: 444 lines of code packages/decap-cms-widget-file/src/withFileControl.js:1— packages/decap-cms-widget-file/src/withFileControl.js has 444 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/decap-cms-widget-markdown/src/serializers/slateRemark.js · ×1
packages/decap-cms-widget-markdown/src/serializers/slateRemark.js: 436 lines of code packages/decap-cms-widget-markdown/src/serializers/slateRemark.js:1— packages/decap-cms-widget-markdown/src/serializers/slateRemark.js has 436 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/decap-cms-core/src/lib/i18n.ts · ×1
packages/decap-cms-core/src/lib/i18n.ts: 430 lines of code packages/decap-cms-core/src/lib/i18n.ts:1— packages/decap-cms-core/src/lib/i18n.ts has 430 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/decap-cms-widget-richtext/src/serializers/slateRemark.js · ×1
packages/decap-cms-widget-richtext/src/serializers/slateRemark.js: 425 lines of code packages/decap-cms-widget-richtext/src/serializers/slateRemark.js:1— packages/decap-cms-widget-richtext/src/serializers/slateRemark.js has 425 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/decap-cms-backend-gitea/src/API.ts · ×1
packages/decap-cms-backend-gitea/src/API.ts: 417 lines of code packages/decap-cms-backend-gitea/src/API.ts:1— packages/decap-cms-backend-gitea/src/API.ts has 417 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· This test file cannot be loaded · ×1
This test file cannot be loaded cypress/run.mjs:7— cypress/run.mjs:7 imports './e2e/', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
R6 · Tooling· The declared test suite includes a file that cannot be loaded · ×1
The declared test suite includes a file that cannot be loaded cypress/run.mjs:7— This repository declares test tooling, and the ✓ above records that declaration — but cypress/run.mjs cannot be loaded at all: it imports a module that names no file in this repository, so the runner throws while collecting it and none of its cases execute. The wiring is present and the suite it points at does not run as written, which is why the tooling tick must not be read as a statement that the tests pass. Fix the unloadable file(s) — each one is reported with its failing import under Test Coverage — then the declared script exercises what it claims to.
Dead file (~84 LoC) functions/publish.js— no import path from any entry point (150 application, 73 tooling, 254 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 (~83 LoC) packages/decap-cms-backend-aws-cognito-github-proxy/src/AuthenticationPage.js— no import path from any entry point (150 application, 73 tooling, 254 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 (~15 LoC) scripts/cache.js— no import path from any entry point (150 application, 73 tooling, 254 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 'unified' packages/decap-cms-core/index.d.ts:5— Imported only as a TYPE and declared in no reachable package.json. 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 package.json.
Unused dependency 'all-contributors-cli' — Declared in the root 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 'axios' — Declared in the root 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 'browserify' — Declared in the root 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 'globby' — Declared in the root 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 'js-yaml' — Declared in the root 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 'lodash-es' — Declared in the root 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 'start-server-and-test' — Declared in the root 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 'stylelint-config-styled-components' — Declared in the root 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 'stylelint-processor-styled-components' — Declared in the root 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.
Swallowed exception (caught, then discarded) packages/decap-cms-backend-github/src/API.ts:644— `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.
No direct assertions: successfully loads cypress/e2e/editorial_workflow_spec_test_backend.js:57— No conventional assertion call was detected, and 113 of 161 tests in `the repository root` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: can publish an editorial workflow entry cypress/e2e/editorial_workflow_spec_test_backend.js:76— No conventional assertion call was detected, and 113 of 161 tests in `the repository root` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: can change workflow status cypress/e2e/editorial_workflow_spec_test_backend.js:105— No conventional assertion call was detected, and 113 of 161 tests in `the repository root` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: can change status on and publish multiple entries cypress/e2e/editorial_workflow_spec_test_backend.js:116— No conventional assertion call was detected, and 113 of 161 tests in `the repository root` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: can update workflow status from within the editor cypress/e2e/editorial_workflow_spec_test_backend.js:140— No conventional assertion call was detected, and 113 of 161 tests in `the repository root` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: can unpublish an existing entry cypress/e2e/editorial_workflow_spec_test_backend.js:153— No conventional assertion call was detected, and 113 of 161 tests in `the repository root` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: can navigate to nested entry cypress/e2e/editorial_workflow_spec_test_backend.js:231— No conventional assertion call was detected, and 113 of 161 tests in `the repository root` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: sets non-default block to default when empty cypress/e2e/markdown_widget_backspace_spec.js:21— No conventional assertion call was detected, and 113 of 161 tests in `the repository root` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: moves to previous block when no character left to delete cypress/e2e/markdown_widget_backspace_spec.js:29— No conventional assertion call was detected, and 113 of 161 tests in `the repository root` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: does nothing at start of first block in document when non-empty and non-default cypress/e2e/markdown_widget_backspace_spec.js:40— No conventional assertion call was detected, and 113 of 161 tests in `the repository root` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: deletes individual characters in middle of non-empty non-default block in document cypress/e2e/markdown_widget_backspace_spec.js:50— No conventional assertion call was detected, and 113 of 161 tests in `the repository root` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: at beginning of non-first block, moves default block content to previous block cypress/e2e/markdown_widget_backspace_spec.js:60— No conventional assertion call was detected, and 113 of 161 tests in `the repository root` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: at beginning of non-first block, moves non-default block content to previous block cypress/e2e/markdown_widget_backspace_spec.js:72— No conventional assertion call was detected, and 113 of 161 tests in `the repository root` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: outputs code cypress/e2e/markdown_widget_code_block_spec.js:19— No conventional assertion call was detected, and 113 of 161 tests in `the repository root` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: creates new default block from empty block cypress/e2e/markdown_widget_enter_spec.js:20— No conventional assertion call was detected, and 113 of 161 tests in `the repository root` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: creates new default block when selection collapsed at end of block cypress/e2e/markdown_widget_enter_spec.js:28— No conventional assertion call was detected, and 113 of 161 tests in `the repository root` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: creates new default block when selection collapsed at end of non-default block cypress/e2e/markdown_widget_enter_spec.js:37— No conventional assertion call was detected, and 113 of 161 tests in `the repository root` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: creates new default block when selection collapsed in empty non-default block cypress/e2e/markdown_widget_enter_spec.js:46— No conventional assertion call was detected, and 113 of 161 tests in `the repository root` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: splits block into two same-type blocks when collapsed selection at block start cypress/e2e/markdown_widget_enter_spec.js:54— No conventional assertion call was detected, and 113 of 161 tests in `the repository root` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: splits block into two same-type blocks when collapsed in middle of selection at block start cypress/e2e/markdown_widget_enter_spec.js:64— No conventional assertion call was detected, and 113 of 161 tests in `the repository root` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: deletes selected content and splits to same-type block when selection is expanded cypress/e2e/markdown_widget_enter_spec.js:74— No conventional assertion call was detected, and 113 of 161 tests in `the repository root` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: creates line break cypress/e2e/markdown_widget_enter_spec.js:87— No conventional assertion call was detected, and 113 of 161 tests in `the repository root` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: creates consecutive line break cypress/e2e/markdown_widget_enter_spec.js:96— No conventional assertion call was detected, and 113 of 161 tests in `the repository root` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: pressing mod+b bolds the text cypress/e2e/markdown_widget_hotkeys_spec.js:29— No conventional assertion call was detected, and 113 of 161 tests in `the repository root` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: pressing mod+i italicizes the text cypress/e2e/markdown_widget_hotkeys_spec.js:42— No conventional assertion call was detected, and 113 of 161 tests in `the repository root` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
Orphaned file packages/decap-cms-locales/src/ru/index.js: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/decap-cms-locales/src/mk/index.js: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/decap-cms-locales/src/fa/index.js: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/decap-cms-locales/src/ua/index.js: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/decap-cms-locales/src/bg/index.js: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/decap-cms-locales/src/uk/index.js: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/decap-cms-widget-richtext/src/serializers/slateRemark.js: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/decap-cms-locales/src/he/index.js: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/decap-cms-locales/src/ja/index.js: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/decap-cms-locales/src/gr/index.js: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/decap-cms-locales/src/de/index.js: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/decap-cms-backend-gitea/src/API.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/decap-cms-locales/src/ko/index.js: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/decap-cms-widget-richtext/src/serializers/remarkSlate.js: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/decap-cms-locales/src/it/index.js: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/decap-cms-locales/src/fr/index.js: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/decap-cms-locales/src/cs/index.js: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/decap-cms-locales/src/tr/index.js: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/decap-cms-locales/src/pl/index.js: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/decap-cms-locales/src/da/index.js: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/decap-cms-locales/src/pt/index.js: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/decap-cms-backend-gitea/src/implementation.tsx: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/decap-cms-locales/src/ro/index.js: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/decap-cms-locales/src/lt/index.js: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/decap-cms-locales/src/sv/index.js: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.
Duplicated predicate packages/decap-cms-widget-markdown/src/MarkdownControl/plugins/lists/locations/isCursorInListItem.js:18— `!!match && match[0].type === 'list-item'` appears character-identically in 2 files — packages/decap-cms-widget-markdown/src/MarkdownControl/plugins/lists/locations/isCursorInListItem.js, packages/decap-cms-widget-markdown/src/MarkdownControl/plugins/lists/withLists.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/decap-cms-widget-markdown/src/MarkdownControl/Toolbar.js:90— `!List.isList(buttons) || buttons.includes(button)` appears character-identically in 2 files — packages/decap-cms-widget-markdown/src/MarkdownControl/Toolbar.js, packages/decap-cms-widget-richtext/src/RichtextControl/components/Toolbar/Toolbar.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/decap-cms-widget-relation/src/RelationControl.js:497— `!field.get('required', true) || isMultiple` appears character-identically in 2 files — packages/decap-cms-widget-relation/src/RelationControl.js, packages/decap-cms-widget-select/src/SelectControl.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/decap-cms-widget-markdown/src/serializers/remarkPaddedLinks.js:62— `!leadingWhitespaceNode && !trailingWhitespaceNode` appears character-identically in 2 files — packages/decap-cms-widget-markdown/src/serializers/remarkPaddedLinks.js, packages/decap-cms-widget-richtext/src/serializers/remarkPaddedLinks.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/decap-cms-widget-markdown/src/serializers/slateRemark.js:281— `!markType && markNodes.length === 1 && isNodeInline(nextNode)` appears character-identically in 2 files — packages/decap-cms-widget-markdown/src/serializers/slateRemark.js, packages/decap-cms-widget-richtext/src/serializers/slateRemark.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/decap-cms-widget-relation/src/RelationControl.js:162— `!selectedOptions || !Array.isArray(selectedOptions)` appears character-identically in 2 files — packages/decap-cms-widget-relation/src/RelationControl.js, packages/decap-cms-widget-select/src/SelectControl.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/decap-cms-backend-bitbucket/src/implementation.ts:105— `!this.options.proxied && (config.backend.repo === null || config.backend.repo === undefined)` appears character-identically in 5 files — packages/decap-cms-backend-bitbucket/src/implementation.ts, packages/decap-cms-backend-forgejo/src/implementation.tsx, packages/decap-cms-backend-gitea/src/implementation.tsx, packages/decap-cms-backend-github/src/implementation.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/decap-cms-core/src/lib/editorApi.ts:173— `(i18n && getDataPath(i18n.currentLocale, i18n.defaultLocale)) || ['data']` appears character-identically in 2 files — packages/decap-cms-core/src/lib/editorApi.ts, packages/decap-cms-core/src/reducers/entryDraft.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/decap-cms-widget-file/src/FilePreview.js:38— `Array.isArray(value) || List.isList(value)` appears character-identically in 3 files — packages/decap-cms-widget-file/src/FilePreview.js, packages/decap-cms-widget-file/src/withFileControl.js, packages/decap-cms-widget-image/src/ImagePreview.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/decap-cms-widget-markdown/src/serializers/remarkEscapeMarkdownEntities.js:256— `['text', 'html'].includes(node.type) && node.value` appears character-identically in 2 files — packages/decap-cms-widget-markdown/src/serializers/remarkEscapeMarkdownEntities.js, packages/decap-cms-widget-richtext/src/serializers/remarkEscapeMarkdownEntities.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/decap-cms-widget-markdown/src/MarkdownControl/VisualEditor.js:112— `codeBlockComponent || editorComponents.has('code-block')` appears character-identically in 2 files — packages/decap-cms-widget-markdown/src/MarkdownControl/VisualEditor.js, packages/decap-cms-widget-richtext/src/RichtextControl/VisualEditor.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/decap-cms-core/src/components/App/Header.js:282— `collection.get('label_singular') || collection.get('label')` appears character-identically in 2 files — packages/decap-cms-core/src/components/App/Header.js, packages/decap-cms-core/src/lib/formatters.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/decap-cms-backend-azure/src/API.ts:342— `commit.author.name || commit.author.email` appears character-identically in 3 files — packages/decap-cms-backend-azure/src/API.ts, packages/decap-cms-backend-forgejo/src/API.ts, packages/decap-cms-backend-gitea/src/API.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/decap-cms-backend-git-gateway/src/implementation.ts:170— `config.backend.branch?.trim() || 'master'` appears character-identically in 3 files — packages/decap-cms-backend-git-gateway/src/implementation.ts, packages/decap-cms-backend-gitea/src/implementation.tsx, packages/decap-cms-backend-github/src/implementation.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/decap-cms-backend-turbo-github/src/implementation.tsx:114— `config.backend.supabase_anon_key || config.backend.supabase_app_id || ''` appears character-identically in 2 files — packages/decap-cms-backend-turbo-github/src/implementation.tsx, packages/decap-cms-backend-turbo-gitlab/src/implementation.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/decap-cms-backend-forgejo/src/API.ts:224— `contentType && contentType.match(/json/)` appears character-identically in 6 files — packages/decap-cms-backend-forgejo/src/API.ts, packages/decap-cms-backend-gitea/src/API.ts, packages/decap-cms-backend-github/src/API.ts, packages/decap-cms-core/src/integrations/providers/algolia/implementation.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/decap-cms-backend-forgejo/src/API.ts:935— `diff.commits[0]?.commit?.message || API.DEFAULT_COMMIT_MESSAGE` appears character-identically in 2 files — packages/decap-cms-backend-forgejo/src/API.ts, packages/decap-cms-backend-github/src/API.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/decap-cms-core/src/components/Editor/EditorNotesPane/AddNoteForm.js:98— `e.key === 'Enter' && (e.ctrlKey || e.metaKey)` appears character-identically in 2 files — packages/decap-cms-core/src/components/Editor/EditorNotesPane/AddNoteForm.js, packages/decap-cms-core/src/components/Editor/EditorNotesPane/NoteItem.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/decap-cms-widget-markdown/src/serializers/remarkPaddedLinks.js:60— `endsWith(text, ' ') && getEdgeTextChild(node, true)` appears character-identically in 2 files — packages/decap-cms-widget-markdown/src/serializers/remarkPaddedLinks.js, packages/decap-cms-widget-richtext/src/serializers/remarkPaddedLinks.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/decap-cms-backend-azure/src/API.ts:631— `error instanceof APIError && error.status === 404` appears character-identically in 2 files — packages/decap-cms-backend-azure/src/API.ts, packages/decap-cms-backend-gitlab/src/API.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/decap-cms-core/src/actions/editorialWorkflow.ts:304— `error.name === EDITORIAL_WORKFLOW_ERROR && error.notUnderEditorialWorkflow` appears character-identically in 2 files — packages/decap-cms-core/src/actions/editorialWorkflow.ts, 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/decap-cms-core/src/actions/editorialWorkflow.ts:372— `error.type && error.type === ValidationErrorTypes.PRESENCE` appears character-identically in 2 files — packages/decap-cms-core/src/actions/editorialWorkflow.ts, packages/decap-cms-core/src/actions/entries.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/decap-cms-widget-markdown/src/MarkdownControl/VisualEditor.js:71— `field.has('media_folder') && !f.has('media_folder')` appears character-identically in 2 files — packages/decap-cms-widget-markdown/src/MarkdownControl/VisualEditor.js, packages/decap-cms-widget-richtext/src/RichtextControl/mergeMediaConfig.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/decap-cms-widget-markdown/src/MarkdownControl/VisualEditor.js:75— `field.has('public_folder') && !f.has('public_folder')` appears character-identically in 2 files — packages/decap-cms-widget-markdown/src/MarkdownControl/VisualEditor.js, packages/decap-cms-widget-richtext/src/RichtextControl/mergeMediaConfig.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/decap-cms-widget-markdown/src/serializers/slateRemark.js:185— `firstGroupMarks[0] === 'code' && firstGroupMarks.length > 1` appears character-identically in 2 files — packages/decap-cms-widget-markdown/src/serializers/slateRemark.js, packages/decap-cms-widget-richtext/src/serializers/slateRemark.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Deprecated: @hapi/address REDACTED:4239— @hapi/address 4.1.0 is resolved in REDACTED and is marked deprecated by its publisher: "Moved to 'npm install @sideway/address'". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @hapi/formula REDACTED:4243— @hapi/formula 2.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "Moved to 'npm install @sideway/formula'". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @humanwhocodes/config-array REDACTED:4266— @humanwhocodes/config-array 0.13.0 is resolved in REDACTED and is marked deprecated by its publisher: "Use @eslint/config-array instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @humanwhocodes/object-schema REDACTED:4275— @humanwhocodes/object-schema 2.0.3 is resolved in REDACTED and is marked deprecated by its publisher: "Use @eslint/object-schema instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @types/vfile-message REDACTED:5612— @types/vfile-message 2.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "This is a stub types definition. vfile-message provides its own type definitions, so you do not need this installed.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @ungap/structured-clone REDACTED:5747— @ungap/structured-clone 1.2.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: abab REDACTED:5873— abab 2.0.6 is resolved in REDACTED and is marked deprecated by its publisher: "Use your platform's native atob() and btoa() methods instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: conventional-changelog-core REDACTED:6958— conventional-changelog-core 5.0.1 is resolved in REDACTED and is marked deprecated by its publisher: "Deprecated and no longer maintained. Please use conventional-changelog instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: core-js REDACTED:7028— core-js 2.6.12 is resolved in REDACTED and is marked deprecated by its publisher: "core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: domexception REDACTED:7450— domexception 2.0.1 is resolved in REDACTED and is marked deprecated by its publisher: "Use your platform's native DOMException instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: git-raw-commits REDACTED:8238— git-raw-commits 2.0.11 is resolved in REDACTED and is marked deprecated by its publisher: "Deprecated and no longer maintained. Use @conventional-changelog/git-client instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: git-raw-commits REDACTED:8244— git-raw-commits 3.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "Deprecated and no longer maintained. Use @conventional-changelog/git-client instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: git-semver-tags REDACTED:8254— git-semver-tags 5.0.1 is resolved in REDACTED and is marked deprecated by its publisher: "Deprecated and no longer maintained. Use @conventional-changelog/git-client instead.". 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:8289— glob 11.1.0 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: glob REDACTED:8299— 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: glob REDACTED:8303— glob 8.0.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:8694— 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.
Deprecated: is-accessor-descriptor REDACTED:8765— is-accessor-descriptor 0.1.6 is resolved in REDACTED and is marked deprecated by its publisher: "Please upgrade to v0.1.7". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: is-accessor-descriptor REDACTED:8770— is-accessor-descriptor 1.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "Please upgrade to v1.0.1". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: is-data-descriptor REDACTED:8835— is-data-descriptor 0.1.4 is resolved in REDACTED and is marked deprecated by its publisher: "Please upgrade to v0.1.5". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: is-data-descriptor REDACTED:8840— is-data-descriptor 1.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "Please upgrade to v1.0.1". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: lodash.get REDACTED:9609— lodash.get 4.4.2 is resolved in REDACTED and is marked deprecated by its publisher: "This package is deprecated. Use the optional chaining (?.) operator instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: q REDACTED:11060— q 1.5.1 is resolved in REDACTED and is marked deprecated by its publisher: "You or someone you depend on is using Q, the JavaScript Promise library that gave JavaScript developers strong feelings about promises. They can almost certainly migrate to the native JavaScript promise now. Thank you literally everyone for joining me in this bet against the odds. Be excellent to each other. (For a CapTP with native promises, see @endo/eventual-send and @endo/captp)". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: q REDACTED:11068— q 2.0.3 is resolved in REDACTED and is marked deprecated by its publisher: "You or someone you depend on is using Q, the JavaScript Promise library that gave JavaScript developers strong feelings about promises. They can almost certainly migrate to the native JavaScript promise now. Thank you literally everyone for joining me in this bet against the odds. Be excellent to each other. (For a CapTP with native promises, see @endo/eventual-send and @endo/captp)". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: resolve-url REDACTED:11533— resolve-url 0.2.1 is resolved in REDACTED and is marked deprecated by its publisher: "https://github.com/lydell/resolve-url#deprecated". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Documentation: no build, run or usage example packages/decap-cms/README.md:1— `decap-cms` is a published package (`package.json` without `"private": true`) and neither `packages/decap-cms/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/decap-cms-backend-aws-cognito-github-proxy/README.md:1— `decap-cms-backend-aws-cognito-github-proxy` is a published package (`package.json` without `"private": true`) and neither `packages/decap-cms-backend-aws-cognito-github-proxy/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/decap-cms-backend-azure/README.md:1— `decap-cms-backend-azure` is a published package (`package.json` without `"private": true`) and neither `packages/decap-cms-backend-azure/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/decap-cms-backend-bitbucket/README.md:1— `decap-cms-backend-bitbucket` is a published package (`package.json` without `"private": true`) and neither `packages/decap-cms-backend-bitbucket/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/decap-cms-backend-github/README.md:1— `decap-cms-backend-github` is a published package (`package.json` without `"private": true`) and neither `packages/decap-cms-backend-github/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/decap-cms-backend-gitlab/README.md:1— `decap-cms-backend-gitlab` is a published package (`package.json` without `"private": true`) and neither `packages/decap-cms-backend-gitlab/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/decap-cms-backend-proxy/README.md:1— `decap-cms-backend-proxy` is a published package (`package.json` without `"private": true`) and neither `packages/decap-cms-backend-proxy/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/decap-cms-core/README.md:1— `decap-cms-core` is a published package (`package.json` without `"private": true`) and neither `packages/decap-cms-core/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/decap-cms-editor-component-image/README.md:1— `decap-cms-editor-component-image` is a published package (`package.json` without `"private": true`) and neither `packages/decap-cms-editor-component-image/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/decap-cms-lib-auth/README.md:1— `decap-cms-lib-auth` is a published package (`package.json` without `"private": true`) and neither `packages/decap-cms-lib-auth/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/decap-cms-lib-util/README.md:1— `decap-cms-lib-util` is a published package (`package.json` without `"private": true`) and neither `packages/decap-cms-lib-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/decap-cms-lib-widgets/README.md:1— `decap-cms-lib-widgets` is a published package (`package.json` without `"private": true`) and neither `packages/decap-cms-lib-widgets/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/decap-cms-media-library-cloudinary/README.md:1— `decap-cms-media-library-cloudinary` is a published package (`package.json` without `"private": true`) and neither `packages/decap-cms-media-library-cloudinary/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/decap-cms-media-library-uploadcare/README.md:1— `decap-cms-media-library-uploadcare` is a published package (`package.json` without `"private": true`) and neither `packages/decap-cms-media-library-uploadcare/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/decap-cms-ui-auth/README.md:1— `decap-cms-ui-auth` is a published package (`package.json` without `"private": true`) and neither `packages/decap-cms-ui-auth/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/decap-cms-ui-default/README.md:1— `decap-cms-ui-default` is a published package (`package.json` without `"private": true`) and neither `packages/decap-cms-ui-default/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/decap-cms-widget-boolean/README.md:1— `decap-cms-widget-boolean` is a published package (`package.json` without `"private": true`) and neither `packages/decap-cms-widget-boolean/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/decap-cms-widget-code/README.md:1— `decap-cms-widget-code` is a published package (`package.json` without `"private": true`) and neither `packages/decap-cms-widget-code/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/decap-cms-widget-colorstring/README.md:1— `decap-cms-widget-colorstring` is a published package (`package.json` without `"private": true`) and neither `packages/decap-cms-widget-colorstring/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/decap-cms-widget-datetime/README.md:1— `decap-cms-widget-datetime` is a published package (`package.json` without `"private": true`) and neither `packages/decap-cms-widget-datetime/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/decap-cms-widget-file/README.md:1— `decap-cms-widget-file` is a published package (`package.json` without `"private": true`) and neither `packages/decap-cms-widget-file/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/decap-cms-widget-image/README.md:1— `decap-cms-widget-image` is a published package (`package.json` without `"private": true`) and neither `packages/decap-cms-widget-image/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/decap-cms-widget-list/README.md:1— `decap-cms-widget-list` is a published package (`package.json` without `"private": true`) and neither `packages/decap-cms-widget-list/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/decap-cms-widget-map/README.md:1— `decap-cms-widget-map` is a published package (`package.json` without `"private": true`) and neither `packages/decap-cms-widget-map/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/decap-cms-widget-markdown/README.md:1— `decap-cms-widget-markdown` is a published package (`package.json` without `"private": true`) and neither `packages/decap-cms-widget-markdown/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: backs off quietly when the server refuses packages/decap-cms-lib-turbo/src/__tests__/editorBridge.spec.ts:173— This test sets up 3 test doubles (for example `jest.spyOn`) 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: retries once the user arrives, when a backend actually exists packages/decap-cms-core/src/components/App/__tests__/App.spec.js:47— This test sets up 10 test doubles (for example `jest.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: does not re-subscribe on every unrelated render packages/decap-cms-core/src/components/App/__tests__/App.spec.js:79— This test sets up 6 test doubles (for example `jest.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: keeps a draft this session saved when a later listing predates the commit packages/decap-cms-core/src/actions/__tests__/editorialWorkflow.spec.js:163— This test sets up 3 test doubles (for example `jest.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: should update the draft with the new entry returned by preSave event packages/decap-cms-core/src/__tests__/backend.spec.js:425— This test sets up 5 test doubles (for example `jest.fn`) against 1 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: should update the draft with the new data returned by preSave event packages/decap-cms-core/src/__tests__/backend.spec.js:461— This test sets up 5 test doubles (for example `jest.fn`) against 1 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: should pass hasSubfolders=true when subfolders is true (default) packages/decap-cms-core/src/__tests__/backend.spec.js:1634— This test sets up 7 test doubles (for example `jest.fn`) against 1 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: should pass hasSubfolders=false when subfolders is false packages/decap-cms-core/src/__tests__/backend.spec.js:1684— This test sets up 7 test doubles (for example `jest.fn`) against 1 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: should default to hasSubfolders=true when subfolders is not specified packages/decap-cms-core/src/__tests__/backend.spec.js:1734— This test sets up 7 test doubles (for example `jest.fn`) against 1 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: finishes an incomplete workflow save over REST without committing again packages/decap-cms-backend-turbo-github/src/__tests__/API.spec.ts:188— This test sets up 4 test doubles (for example `jest
.spyOn`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: opens the pull request too when the server could not packages/decap-cms-backend-turbo-github/src/__tests__/API.spec.ts:216— This test sets up 4 test doubles (for example `jest
.spyOn`) 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: should migrate to pull request labels when no version packages/decap-cms-backend-github/src/__tests__/API.spec.js:447— This test sets up 3 test doubles (for example `jest.fn`) against 1 real object(s) of its own, and its only verification is 6 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: should migrate to pull request labels when version is 1 packages/decap-cms-backend-github/src/__tests__/API.spec.js:481— This test sets up 3 test doubles (for example `jest.fn`) against 1 real object(s) of its own, and its only verification is 5 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: should not start polling if already watching same entry packages/decap-cms-backend-github/src/__tests__/implementation.spec.js:766— This test sets up 3 test doubles (for example `jest.fn`) against 1 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: should handle polling manager error gracefully packages/decap-cms-backend-github/src/__tests__/implementation.spec.js:872— This test sets up 3 test doubles (for example `jest.fn`) against 2 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: should create PR with correct branch when publishing with editorial workflow packages/decap-cms-backend-forgejo/src/__tests__/API.spec.js:75— This test sets up 6 test doubles (for example `jest.fn`) against 2 real object(s) of its own, and its only verification is 6 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: should not create branch if it already exists packages/decap-cms-backend-forgejo/src/__tests__/API.spec.js:110— This test sets up 6 test doubles (for example `jest.fn`) against 1 real object(s) of its own, and its only verification is 4 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should not create PR for open authoring (branch-only draft) packages/decap-cms-backend-forgejo/src/__tests__/API.spec.js:138— This test sets up 6 test doubles (for example `jest.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.
Mock-dominated test: should create PR from mock PR when OA entry moves to pending_review packages/decap-cms-backend-forgejo/src/__tests__/API.spec.js:1029— This test sets up 3 test doubles (for example `jest.fn`) against 1 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: should delete unpublished entry by closing PR and deleting branch packages/decap-cms-backend-forgejo/src/__tests__/API.spec.js:1054— This test sets up 3 test doubles (for example `jest.fn`) against 1 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: should delete branch even if PR does not exist packages/decap-cms-backend-forgejo/src/__tests__/API.spec.js:1069— This test sets up 3 test doubles (for example `jest
.fn`) against 2 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: should publish unpublished entry by merging PR and deleting branch packages/decap-cms-backend-forgejo/src/__tests__/API.spec.js:1086— This test sets up 3 test doubles (for example `jest.fn`) against 1 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: should return error when default branch doesn't exist packages/decap/src/dev/middlewares/localGit/index.spec.ts:166— This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 4 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should send error on invalid schema packages/decap/src/dev/middlewares/joi/index.spec.ts:595— This test sets up 3 test doubles (for example `jest.fn`) against 0 real object(s) of its own, and its only verification is 5 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.
Outdated (npm): @dnd-kit/modifiers packages/decap-cms-widget-file/package.json:26— @dnd-kit/modifiers is pinned at 6.0.1; registry.npmjs.org publishes 9.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): @dnd-kit/sortable packages/decap-cms-widget-file/package.json:27— @dnd-kit/sortable is pinned at 7.0.2; registry.npmjs.org publishes 10.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): @platejs/basic-nodes packages/decap-cms-widget-richtext/package.json:24— @platejs/basic-nodes is pinned at 49.0.0; registry.npmjs.org publishes 53.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): @platejs/link packages/decap-cms-widget-richtext/package.json:25— @platejs/link is pinned at 50.3.2; registry.npmjs.org publishes 53.3.5 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): @platejs/list-classic packages/decap-cms-widget-richtext/package.json:26— @platejs/list-classic is pinned at 49.1.0; registry.npmjs.org publishes 53.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): globby package.json:188— globby is pinned at 12.2.0; registry.npmjs.org publishes 16.2.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): ini packages/decap-cms-backend-git-gateway/package.json:24— ini is pinned at 2.0.0; registry.npmjs.org publishes 7.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): mdast-util-definitions packages/decap-cms-widget-markdown/package.json:28— mdast-util-definitions is pinned at 1.2.5; 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): minimatch packages/decap-cms-backend-bitbucket/package.json:24— minimatch is pinned at 7.4.9; registry.npmjs.org publishes 11.0.8 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): ol packages/decap-cms-widget-map/package.json:33— ol is pinned at 6.15.1; registry.npmjs.org publishes 10.11.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): platejs packages/decap-cms-widget-richtext/package.json:30— platejs is pinned at 49.2.21; registry.npmjs.org publishes 53.5.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): react-is packages/decap-cms-core/package.json:55— react-is is pinned at 16.13.1; registry.npmjs.org publishes 19.3.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): react-markdown packages/decap-cms-core/package.json:56— react-markdown is pinned at 6.0.3; registry.npmjs.org publishes 10.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): react-split-pane packages/decap-cms-core/package.json:62— react-split-pane is pinned at 0.1.92; registry.npmjs.org publishes 3.3.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): rehype-parse packages/decap-cms-widget-markdown/package.json:30— rehype-parse is pinned at 6.0.2; registry.npmjs.org publishes 9.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): rehype-stringify packages/decap-cms-widget-markdown/package.json:33— rehype-stringify is pinned at 7.0.0; registry.npmjs.org publishes 10.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): remark-gfm packages/decap-cms-core/package.json:71— remark-gfm is pinned at 1.0.0; registry.npmjs.org publishes 4.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): remark-parse packages/decap-cms-widget-markdown/package.json:34— remark-parse is pinned at 6.0.3; registry.npmjs.org publishes 11.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): remark-rehype packages/decap-cms-widget-markdown/package.json:35— remark-rehype is pinned at 4.0.1; registry.npmjs.org publishes 11.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): remark-stringify packages/decap-cms-widget-markdown/package.json:37— remark-stringify is pinned at 6.0.4; registry.npmjs.org publishes 11.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): unist-builder packages/decap-cms-widget-markdown/package.json:45— unist-builder is pinned at 1.0.4; 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): unist-util-visit-parents packages/decap-cms-widget-markdown/package.json:46— unist-util-visit-parents is pinned at 2.1.2; registry.npmjs.org publishes 6.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): uuid packages/decap-cms-app/package.json:78— uuid is pinned at 8.3.2; registry.npmjs.org publishes 14.0.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): vfile-location packages/decap-cms-widget-markdown/package.json:47— vfile-location is pinned at 2.0.6; registry.npmjs.org publishes 5.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.
redundant comment cypress/utils/steps.js:580— "assert on list controls" repeats the code it sits on: 3 of its 3 words (assert, list, controls) are already in `assertListControlErrorStatus([colorError, colorError], '@hotelLocationsListControl');`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/decap-cms-backend-forgejo/src/API.ts:779— "Get or create the new status label" repeats the code it sits on: 4 of its 5 words (get, create, new, label) are already in `const label = await this.getOrCreateLabel(newLabel);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/decap-cms-backend-forgejo/src/__tests__/API.spec.js:749— "Mock getOpenAuthoringBranches" repeats the code it sits on: 5 of its 5 words (mock, get, open, authoring, branches) are already in `api.getOpenAuthoringBranches = jest`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/decap-cms-backend-forgejo/src/__tests__/API.spec.js:757— "Mock filterOpenAuthoringBranches to allow all" repeats the code it sits on: 5 of its 6 words (mock, filter, open, authoring, branches) are already in `api.filterOpenAuthoringBranches = jest`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/decap-cms-backend-github/src/API.ts:1132— "create a new commit from the updated tree" repeats the code it sits on: 4 of its 5 words (create, new, commit, tree) are already in `const newCommit = await this.createCommit(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/decap-cms-core/src/actions/config.ts:254— "Use media_folder as default public_folder." repeats the code it sits on: 4 of its 5 words (media, folder, default, public) are already in `const defaultPublicFolder = `/${trimStart(config.media_folder, '/')}`;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/decap-cms-core/src/actions/editorialWorkflow.ts:366— "load unpublishedEntries" repeats the code it sits on: 3 of its 3 words (load, unpublished, entries) are already in `!entriesLoaded && dispatch(loadUnpublishedEntries(state.collections));`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/decap-cms-core/src/actions/entries.ts:1199— "Set entrySlug for all notes" repeats the code it sits on: 4 of its 4 words (set, entry, slug, notes) are already in `const notesWithSlug = notes.map(note => ({ ...note, entrySlug: slug }));`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/decap-cms-core/src/actions/mediaLibrary.ts:634— "load display url" repeats the code it sits on: 3 of its 3 words (load, display, url) are already in `dispatch(loadMediaDisplayURL(file));`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/decap-cms-core/src/components/Editor/EditorPreviewPane/EditorPreviewPane.js:178— "Variable Type lists" repeats the code it sits on: 3 of its 3 words (variable, type, lists) are already in `if (List.isList(value) && variableTypes)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment REDACTED:514— "Stop current watch" repeats the code it sits on: 3 of its 3 words (stop, current, watch) are already in `this.stopCurrentWatch();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/decap-cms-widget-markdown/src/MarkdownControl/plugins/lists/transforms/convertParagraphToListItem.js:8— "wrap the paragraph in a list item" repeats the code it sits on: 4 of its 4 words (wrap, paragraph, list, item) are already in `wrapFirstMatchedParent(editor, 'paragraph', {`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/decap-cms-widget-markdown/src/MarkdownControl/plugins/lists/transforms/splitListItem.js:22— "wrap the paragraph in a list item" repeats the code it sits on: 4 of its 4 words (wrap, paragraph, list, item) are already in `wrapFirstMatchedParent(editor, 'paragraph', {`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/decap-cms-widget-markdown/src/MarkdownControl/plugins/lists/transforms/splitToNestedList.js:21— "wrap the paragraph in a list item" repeats the code it sits on: 4 of its 4 words (wrap, paragraph, list, item) are already in `wrapFirstMatchedParent(editor, 'paragraph', {`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
P2 · Observability· Console output used as the logging channel · ×8
Console output used as the logging channel packages/decap/src/login.ts:54— `packages/decap/src/login.ts` reports through `console.*` at line 54 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/decap/src/login.ts:55— `packages/decap/src/login.ts` reports through `console.*` at line 55 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/decap/src/login.ts:56— `packages/decap/src/login.ts` reports through `console.*` at line 56 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/decap/src/login.ts:88— `packages/decap/src/login.ts` reports through `console.*` at line 88 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/decap/src/login.ts:100— `packages/decap/src/login.ts` reports through `console.*` at line 100 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/decap/src/login.ts:130— `packages/decap/src/login.ts` reports through `console.*` at line 130 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/decap/src/login.ts:133— `packages/decap/src/login.ts` reports through `console.*` at line 133 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/decap/src/mcp.ts:23— `packages/decap/src/mcp.ts` reports through `console.*` at line 23 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Interpolated log message defeats structured logging packages/decap/src/dev/server.ts:76— `info` at line 76 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging packages/decap/src/dev/server.ts:78— `warn` at line 78 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.warn({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.warn('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging packages/decap/src/dev/server.ts:100— `info` at line 100 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging packages/decap/src/dev/middlewares/localGit/index.ts:454— `error` at line 454 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging packages/decap/src/dev/middlewares/localGit/index.ts:476— `info` at line 476 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging packages/decap/src/dev/middlewares/localFs/index.ts:135— `error` at line 135 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging packages/decap/src/dev/middlewares/localFs/index.ts:159— `info` at line 159 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Silent fallback default in catch packages/decap-cms-backend-turbo-github/src/deployWatcher.ts:240— `createLocalStorageLedger.load` 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/decap-cms-lib-turbo/src/scopedFetch.ts:53— `peekBody` 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/decap-cms-media-library-s3/src/components/FileGrid.tsx:144— `formatDate` 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/decap/src/dev/middlewares/utils/fs.ts:26— `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 scripts/webpack.js:111— `reactDomServerAlias` 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.
Disabled test cypress/e2e/editorial_workflow_spec_proxy_git_backend.js:8— 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 cypress/e2e/richtext_widget_enter_spec.js:90— 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 packages/decap-cms-widget-markdown/src/serializers/__tests__/commonmark.spec.js:68— 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 packages/decap-cms-widget-richtext/src/serializers/__tests__/commonmark.spec.js:68— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Fat interface: StaticallyTypedRecord (19 required operations) packages/decap-cms-core/src/types/immutable.ts:11— `StaticallyTypedRecord` declares 19 required operations: `get`, `set`, `has`, `delete`, `getIn`, `getIn`, `getIn`, `setIn`, `setIn`, `toJS`, `isEmpty`, `some`, `mapKeys`, `find`, `filter`, `valueSeq`, `map`, `keySeq`, `withMutations`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. Those 19 declarations carry 16 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 16 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: Implementation (22 required operations) packages/decap-cms-lib-util/src/implementation.ts:202— `Implementation` declares 22 required operations: `authComponent`, `restoreUser`, `authenticate`, `logout`, `getToken`, `getEntry`, `entriesByFolder`, `entriesByFiles`, `getMedia`, `getMediaFile`, `persistEntry`, `persistMedia`, `deleteFiles`, `unpublishedEntries`, `unpublishedEntry`, `unpublishedEntryDataFile`, `unpublishedEntryMediaFile`, `updateUnpublishedEntryStatus`, `publishUnpublishedEntry`, `deleteUnpublishedEntry`, `getDeployPreview`, `status`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
C2 · Access Controls· No named authorization policies · ×1
No named authorization policies functions/publish.js:80— Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 39 significant file(s) lose their only recent owner: packages/decap-turbo-api/src/index.ts, packages/decap-cms-backend-turbo-github/src/deployWatcher.ts, packages/decap-cms-backend-turbo-github/src/implementation.tsx, packages/decap-cms-core/src/actions/editorialWorkflow.ts, packages/decap-cms-backend-gitlab/src/notesApi.ts, packages/decap-cms-backend-turbo-gitlab/src/implementation.tsx, packages/decap-cms-core/src/components/MediaLibrary/MediaLibrary.js, packages/decap-cms-lib-turbo/src/editorBridge.ts (+31 more). Pair on, review, or document these before any departure.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 7 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 (48 single-owned of 239 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; 239 of the 581 production source files in this repository met that bar). They are anonymized user #2 (2 file(s)), anonymized user #3 (2 file(s)), anonymized user #4 (1 file(s)), anonymized user #5 (1 file(s)), anonymized user #6 (1 file(s)), anonymized user #7 (1 file(s)) (+1 more) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: packages/decap-cms-locales/src/sr_Cyrl/index.js, packages/decap-cms-locales/src/hr/index.js, packages/decap-cms-ui-default/src/Dropdown.js, packages/decap-cms-ui-default/src/DropDown/useDropDownCoords.js, REDACTED, packages/decap-cms-core/src/actions/media.ts, packages/decap-cms-widget-richtext/src/serializers/remarkRehypeShortcodes.js, packages/decap-cms-widget-markdown/src/MarkdownControl/RawEditor.js (+1 more).
No ADRs found package.json:3— 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 `package.json` makes this repository a deployable product (line 3).
D21 · Naming Consistency· `appID` spells `ID` where 68 names in the project spell it `Id` · ×1
`appID` spells `ID` where 68 names in the project spell it `Id` packages/decap-cms-backend-gitlab/src/implementation.ts:86— 68 of 70 names in project repository spell the token `Id` (68 of 70; unit: names in project repository containing `Id`). Peers: AzureGitChange.changeId (packages/decap-cms-backend-azure/src/API.ts:140); AzureGitChangeItem.objectId (packages/decap-cms-backend-azure/src/API.ts:148); AzureGitChangeItem.originalObjectId (packages/decap-cms-backend-azure/src/API.ts:149); AzureGitChangeItem.commitId (packages/decap-cms-backend-azure/src/API.ts:151); API.getFileId (packages/decap-cms-backend-bitbucket/src/API.ts:288). Rename to `appId`. [rule N6]
D21 · Naming Consistency· `controlID` spells `ID` where 68 names in the project spell it `Id` · ×1
`controlID` spells `ID` where 68 names in the project spell it `Id` packages/decap-cms-core/src/actions/mediaLibrary.ts:138— 68 of 70 names in project repository spell the token `Id` (68 of 70; unit: names in project repository containing `Id`). Peers: AzureGitChange.changeId (packages/decap-cms-backend-azure/src/API.ts:140); AzureGitChangeItem.objectId (packages/decap-cms-backend-azure/src/API.ts:148); AzureGitChangeItem.originalObjectId (packages/decap-cms-backend-azure/src/API.ts:149); AzureGitChangeItem.commitId (packages/decap-cms-backend-azure/src/API.ts:151); API.getFileId (packages/decap-cms-backend-bitbucket/src/API.ts:288). Rename to `controlId`. [rule N6]
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 1 of 47 project(s) overshoot their size bounds, lowering Project Cohesion to 9.6/10. The most over is `packages/decap-cms-core` (22466 LoC, 230 module-visible types across 25 directories). 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
D34 · Knowledge Freshness· Further orphaned files (smaller) · ×1
Further orphaned files (smaller) — 99 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/decap-cms-locales/src/ru/index.js, packages/decap-cms-locales/src/mk/index.js, packages/decap-cms-locales/src/fa/index.js, packages/decap-cms-locales/src/ua/index.js, packages/decap-cms-locales/src/bg/index.js, packages/decap-cms-locales/src/uk/index.js, packages/decap-cms-widget-richtext/src/serializers/slateRemark.js, packages/decap-cms-locales/src/he/index.js (and 91 more) (101 orphaned of 241 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; 241 of the 581 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.
Logging is not universal — Only 1/2 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `packages/decap-server`.
No SAST REDACTED:3— 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 5 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.
Unused export 'treeEntry' packages/decap-cms-backend-github/src/fragments.ts:72— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'showCollection' · ×1
Unused export 'showCollection' packages/decap-cms-core/src/actions/collections.ts:12— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'refreshNotesNow' · ×1
Unused export 'refreshNotesNow' packages/decap-cms-core/src/actions/entries.ts:1319— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'toggleNoteResolutionPersist' · ×1
Unused export 'toggleNoteResolutionPersist' packages/decap-cms-core/src/actions/entries.ts:1470— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'statusDescriptions' · ×1
Unused export 'statusDescriptions' packages/decap-cms-core/src/constants/publishModes.ts:16— Nothing imports this binding — it is safe to review for removal.
Unused export 'getFormatter' packages/decap-cms-core/src/lib/registry.js:351— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'selectEntries' · ×1
Unused export 'selectEntries' packages/decap-cms-core/src/reducers/index.ts:53— Nothing imports THIS copy of 'selectEntries' — but REDACTED:432 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 REDACTED's, or, if this one is meant to be the survivor, repoint the importers before removing the other.
R7 · Dead Code· Unused export 'LoadNotesPayload' · ×1
Unused export 'LoadNotesPayload' packages/decap-cms-core/src/types/redux.ts:327— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'AddNotePayload' · ×1
Unused export 'AddNotePayload' packages/decap-cms-core/src/types/redux.ts:331— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'UpdateNotePayload' · ×1
Unused export 'UpdateNotePayload' packages/decap-cms-core/src/types/redux.ts:335— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'DeleteNotePayload' · ×1
Unused export 'DeleteNotePayload' packages/decap-cms-core/src/types/redux.ts:340— Nothing imports this binding — it is safe to review for removal.
Unused export 'Hook' packages/decap-cms-core/src/types/redux.ts:798— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'EntriesMoveSuccessPayload' · ×1
Unused export 'EntriesMoveSuccessPayload' packages/decap-cms-core/src/types/redux.ts:896— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'endpointConstants' · ×1
Unused export 'endpointConstants' packages/decap-cms-lib-util/src/API.ts:158— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'DeleteOptions' · ×1
Unused export 'DeleteOptions' packages/decap-cms-lib-util/src/implementation.ts:141— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'NOTES_POLLING_START' · ×1
Unused export 'NOTES_POLLING_START' REDACTED:58— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'NOTES_POLLING_STOP' · ×1
Unused export 'NOTES_POLLING_STOP' REDACTED:59— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'NOTES_POLLING_UPDATE' · ×1
Unused export 'NOTES_POLLING_UPDATE' REDACTED:60— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'NOTES_CHANGE_DETECTED' · ×1
Unused export 'NOTES_CHANGE_DETECTED' REDACTED:61— Nothing imports this binding — it is safe to review for removal.
Unused export 'default' REDACTED:523— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'resolveFunctionForTypedField' · ×1
Unused export 'resolveFunctionForTypedField' packages/decap-cms-widget-list/src/typedListHelpers.js:12— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'renderInline__DEPRECATED' · ×1
Unused export 'renderInline__DEPRECATED' packages/decap-cms-widget-markdown/src/MarkdownControl/renderers.js:285— Nothing imports this binding — it is safe to review for removal.
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.)
No app-layer HTTPS enforcement detected packages/decap/src/dev/server.ts:108— `app.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−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 3/41 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 — ~11.9 `!` null assertions per 1k TypeScript source lines — 467 assertion(s) across the 39096 source line(s) of the 160 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/decap-cms-backend-github/src/implementation.tsx (52), packages/decap-cms-backend-forgejo/src/implementation.tsx (49), packages/decap-cms-backend-gitlab/src/implementation.ts (47). 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.
Outdated (npm): @modelcontextprotocol/sdk — @modelcontextprotocol/sdk is pinned at 1.32.1; registry.npmjs.org publishes 1.32.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): @reduxjs/toolkit — @reduxjs/toolkit is pinned at 1.9.7; registry.npmjs.org publishes 2.14.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): @vercel/stega — @vercel/stega is pinned at 0.1.2; registry.npmjs.org publishes 1.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): async-mutex — async-mutex is pinned at 0.3.2; registry.npmjs.org publishes 0.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): codemirror — codemirror is pinned at 5.65.20; registry.npmjs.org publishes 6.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): cors — cors is pinned at 2.8.5; registry.npmjs.org publishes 2.8.6 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): dayjs — dayjs is pinned at 1.11.18; registry.npmjs.org publishes 1.11.23 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): detab — detab is pinned at 2.0.4; registry.npmjs.org publishes 3.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): dompurify — dompurify is pinned at 3.4.17; registry.npmjs.org publishes 3.4.18 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): dotenv — dotenv is pinned at 16.4.7; 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): eslint-config-prettier — eslint-config-prettier is pinned at 8.10.0; registry.npmjs.org publishes 10.1.8 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): express — express is pinned at 4.22.3; registry.npmjs.org publishes 5.3.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): gotrue-js — gotrue-js is pinned at 0.9.29; registry.npmjs.org publishes 1.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): graphql — graphql is pinned at 15.10.1; registry.npmjs.org publishes 17.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): graphql-tag — graphql-tag is pinned at 2.12.6; registry.npmjs.org publishes 2.12.7 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): history — history is pinned at 4.10.1; registry.npmjs.org publishes 5.3.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): immer — immer is pinned at 9.0.21; registry.npmjs.org publishes 11.2.10 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): immutable — immutable is pinned at 4.3.9; registry.npmjs.org publishes 5.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.
Outdated (npm): imports-loader — imports-loader is pinned at 4.0.1; registry.npmjs.org publishes 5.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): is-hotkey — is-hotkey is pinned at 0.2.0; registry.npmjs.org publishes 0.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.
Outdated (npm): js-base64 — js-base64 is pinned at 3.7.5; registry.npmjs.org publishes 3.9.6 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-sha256 — js-sha256 is pinned at 0.9.0; registry.npmjs.org publishes 1.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): jwt-decode — jwt-decode is pinned at 3.1.2; 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): mdast-util-to-string — mdast-util-to-string is pinned at 2.0.0; 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): react — react is pinned at 19.2.0; registry.npmjs.org publishes 19.3.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
doc comments repeat the names packages/decap-cms-backend-github/src/API.ts:1856— 0 of 0 documented parameters and 2 of 27 summaries in `decap-cms-backend-github` only repeat the member or parameter name (e.g. "Get all notes for an entry" for `getEntryNotes`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names packages/decap-cms-core/src/lib/registry.js:87— 0 of 0 documented parameters and 3 of 161 summaries in `decap-cms-core` only repeat the member or parameter name (e.g. "Preview Templates" for `registerPreviewTemplate`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names REDACTED:240— 0 of 3 documented parameters and 0 of 1 summaries in `decap-cms-lib-widgets` only repeat the member or parameter name (e.g. "" for `entryPath`). 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.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 1 file(s) — `packages/decap-turbo-api/src/index.ts` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
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 01a1dd68-6b36-7abd-8208-7afbabfe2810 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 66 · Warnings: 478 · Recommendations: 456 · Info: 58 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 15-11-2026 @ 04:12 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.