decap-cms — Watchdog Audit

Executive summary

⚠ A critical security finding caps this grade — resolve it before relying on the score below; see the Security lens.

The system holds a 61% health score, indicating a workable asset carrying significant structural risk. While performance is flawless, the underlying code architecture and maintainability are fragile. This standing suggests that while the business can continue to operate, the cost of change is artificially inflated, and the risk of unexpected outages or security gaps is higher than it should be for a system of this size.

The application is a medium-sized asset with roughly 65,000 lines of production code. Rebuilding it from scratch would cost approximately €110,000 and take less than a year for a small team. However, the true cost lies in the daily friction of maintaining it. The code quality signals suggest a hidden tax on every change, where modifications in weaker areas plausibly cost 2–5% more effort than in clean code. This inefficiency compounds annually, draining engineering capacity that could otherwise be spent on new features.

The primary risk is architectural fragility. The system lacks clear boundaries, leading to tight coupling where changes in one area ripple unpredictably into others. This structure makes the system brittle; as the business grows, the cost of adapting the software will rise disproportionately. Without decoupling these components, the team will face increasing delays and a higher likelihood of defects when introducing new functionality.

A secondary concern is technical debt accumulation. The codebase contains cycles and shared logic that are difficult to isolate. This creates a maintenance burden that pays a high annual interest in the form of slowed delivery speeds. While the documentation and maturity levels are decent, the lack of modern tooling in some areas means new engineers will face a steeper learning curve, further slowing onboarding and initial productivity.

The system’s greatest strength is its operational stability. Performance metrics are perfect, and the core logic is robust enough to handle current loads without degradation. This reliability provides a solid foundation for improvement, ensuring that refactoring efforts do not introduce immediate instability.

Focus first on breaking architectural cycles by extracting shared logic into independent modules. This single action offers the highest return on investment, paying for itself within months by reducing the annual drag on engineering velocity. Addressing this structural issue will immediately lower the cost of change and improve the system’s long-term resilience.

Code Health 59% Adequate · gated by D3, R1 Architecture 59% Adequate · gated by R9 Maturity 68% Adequate · gated by M2 Readiness 60% Adequate · gated by R8, P3 Security 67% Adequate · gated by D29, D30, D36 Performance 100% ★ Exemplary

How the score is built — each lens's share of the headline Width is the lens's weight in the worst-heaviest fold (the weakest area pulls hardest); colour is that lens's own band. A lens fixes the score in proportion to its width.

Architecture 59% · 46% weightCode Health 59% · 25% weightReadiness 60% · 14% weightSecurity 67% · 8% weightMaturity 68% · 4% weightPerformance 100% · 2% weight

No single dominant problem — the weakest areas are close, so progress on any of them moves the score.

Code composition — where the lines go

Tests 100%

New since the last scan (31+)

31 finding(s) are new versus the previous scan (2026-09-16) — surfaced by this scheduled scan itself, no pull request required.

D2 · NotesPollingManager.checkCurrentIssue (cognitive 23) REDACTED
D3 · ClassTooLong: GitLab packages/decap-cms-backend-gitlab/src/implementation.ts
D3 · FileTooLong: src/implementation.ts packages/decap-cms-backend-gitlab/src/implementation.ts
D3 · MethodTooLong: Widget.render packages/decap-cms-core/src/components/Editor/EditorControlPane/Widget.js
D5 · Unstable project decap-cms-app
D5 · Unstable project decap-cms-backend-aws-cognito-github-proxy
D5 · Unstable project decap-cms-backend-git-gateway
D5 · Unstable project decap-cms-core
D5 · Off the main sequence: decap-cms-lib-widgets
D5 · Off the main sequence: decap-cms-lib-util
D6 · Low cohesion: TestBackend (LCOM4 15) packages/decap-cms-backend-test/src/implementation.ts
D6 · Low cohesion: API (LCOM4 5) REDACTED
D6 · Low cohesion: ControlPane (LCOM4 4) packages/decap-cms-core/src/components/Editor/EditorControlPane/EditorControlPane.js
D29 · REDACTED
D29 · REDACTED
D30 · REDACTED
D30 · REDACTED
D30 · REDACTED
D30 · REDACTED
D30 · REDACTED
D30 · REDACTED
D30 · REDACTED
D30 · REDACTED
D30 · REDACTED
R10 · Duplicated block with local edits (333 matched lines × 2 locations) packages/decap-cms-backend-bitbucket/src/implementation.ts
R10 · Duplicated block with local edits (164 matched lines × 2 locations) packages/decap-cms-backend-azure/src/implementation.ts
R10 · Duplicated block with local edits (162 matched lines × 2 locations) packages/decap-cms-backend-github/src/implementation.tsx
R2 · Complex function constructor (cyclomatic 16, cognitive 15) packages/decap-cms-backend-bitbucket/src/implementation.ts
AX4 · Dependency-rule violation: decap-cms-app (Application) → decap-cms-ui-auth (Web)
AX4 · Dependency-rule violation: decap-cms-app (Application) → decap-cms-ui-default (Web)
AX4 · Dependency-rule violation: decap-cms-core (Domain) → decap-cms-ui-default (Web)

A full-fidelity diff against the previous run's complete recorded findings — line-move tolerant: a finding that only shifted line counts as unchanged, only genuinely new titles/files surface here.

Rebuild cost & value ~ Modeled — €36,000–€180,000

Cost to rebuild	€36,000–€180,000 (0.4–1.1 person-years (602–1,909 h), ~1–2 engineers)
Domain complexity	Standard — harder problems cost more per line
Quality factor	0.8× (at 61% quality) — the last 20% of quality is most of the work
Size & shape	Medium · effort split not classified (source measured from disk; the effort-tier breakdown is a C#-only syntax walk)

This codebase represents roughly ~0.7 person-years of build effort (about ~€110,000 to rebuild). Its weakest lens is Architecture at 59% — the part of that asset most exposed by the findings below.

How we model this: boilerplate at a scaffolding rate + logic × domain Standard (×1.0) — standard service × a 0.8× quality factor, at €60–95/h; indicative, ±~30% · size measured directly from source · effort from total production LoC as straight-line logic (the tier split is a C#-only syntax walk), a conservative lower bound. Indicative only — most sensitive to the hourly rate and the domain tier (both tunable in config).

Top priorities

The highest-leverage moves; the full ranked list is in the Roadmap below.

Break each cycle by extracting the shared piece into a module both sides can import.

+2.8 pts · Medium effort · Circular Imports

Keep dependencies pointing inward: domain/application define interfaces, infrastructure/web implement them (Dependency Inversion).

+2.7 pts · Medium effort · Dependency direction

Resolve the 1 No ADRs found finding(s) in ADR Quality.

+1.3 pts · Low effort · ADR Quality

Diagnosis — what's actually going on

The top fix pays for itself · High · Economics

The top-ranked fix costs roughly 3–10 engineer-days once. Not doing it costs about 14.9–99 engineer-days every year, paid as drag on the ~297,146 lines this team changes annually — a bill that arrives whether or not anyone books it. On those figures the fix breaks even in roughly 1–8 months and is free after that. Method, stated so this is not read as a quotation: debt from the ranked task's effort band; interest = annual changed lines (measured, annualised from the 90-day window) ÷ an ASSUMED 150–400 lines per engineer-day × the 2–5% drag implied by the code-quality signals; breaking point = debt ÷ annual interest. A modelled planning range built from measured inputs and one named assumption — not a quotation, a valuation, or a certified figure.

Evidence: D15 churn: 73,269 line(s) changed over a 90-day window ⇒ ~297,146/year · D1/D2/D6 code quality: averaging 7.3/10 ⇒ a 2–5% drag on each change · top-ranked remediation: Medium effort ⇒ about 3–10 engineer-day(s)

→ Do the top-ranked fix now if this code will still be yours in 8 months.

Value concentrated against a weak lens · Medium · Value at risk

This is a Medium asset (~0.7 person-years to rebuild), and its weakest lens is Architecture at 59%. The operational and business risk on an asset this size concentrates there — that's where remediation buys the most protection.

Evidence: valuation: Medium, ~0.7 person-years rebuild (65,652 LoC) · weakest lens: Architecture 59%

→ Direct remediation budget at Architecture first — highest risk-reduction per euro on an asset this size.

Highest-leverage move · Medium · Leverage

Of everything flagged, the best return on effort is: Break each cycle by extracting the shared piece into a module both sides can import. The rest can wait behind it.

Evidence: priority ranking: top of 5 ranked by impact/effort

→ Break each cycle by extracting the shared piece into a module both sides can import.

A velocity tax on every change · Medium · Economics

The code-quality signals (complexity, duplication, cohesion) average 7.3/10, which acts as a tax on every change in the weaker areas: modifications there plausibly cost on the order of 2–5% more than in clean code, and the tax compounds as the codebase grows. (A modelled estimate, not a measured fact.)

Evidence: D1/D2/D6 code quality: averaging 7.3/10 across the code-quality signals actually measured

→ Pay it down where churn is highest — the hotspots — not everywhere; that's where the tax is actually paid.

Architecture — module dependency graph

Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways — a layering smell or cycle. A clean layered graph has none.

Architecture — module dependency matrix

Rows and columns are the same modules, ordered so that a module only depends on ones above it. A cell means the row depends on the column, and its number is how many type pairs create that dependency. Read one thing: is anything above the diagonal? A mark there is a dependency cycle. (A cycle is all this shows — an unusual but cycle-free dependency sits below the diagonal like any other.)

227 modules, 143 dependencies. 1 dependency cycle across 2 modules, marked above the diagonal.

Showing the 40 most-connected modules; 187 more are not drawn.

Module dependency matrix. The row depends on the column; the number is how many type pairs create the dependency. A cell above the diagonal is part of a dependency cycle.
depends on →	1 decap-cms-core.src.components.Collection.Collection	2 decap-cms-core.src.components.Collection.Entries	3 decap-cms-core.src.valueObjects.AssetProxy	4 decap-cms-core.src.valueObjects.Entry	5 decap-cms-lib-util.src.API	6 decap-cms-lib-util.src.git-lfs	7 decap-cms-backend-bitbucket.src.git-lfs-client	8 decap-cms-core.src.actions.media	9 decap-cms-core.src.types.redux	13 decap-cms-lib-util.src.implementation	14 decap-cms-backend-azure.src.API	16 decap-cms-lib-util.src.Cursor	17 decap-cms-lib-util.src.notesPolling	18 decap-cms-backend-bitbucket.src.API	19 decap-cms-backend-gitlab.src.notesApi	20 decap-cms-core.src.backend	23 decap-cms-backend-forgejo.src.API	39 decap-cms-backend-github.src.API
1 decap-cms-core.src.components.Collection.Collection
2 decap-cms-core.src.components.Collection.Entries
3 decap-cms-core.src.valueObjects.AssetProxy
4 decap-cms-core.src.valueObjects.Entry
5 decap-cms-lib-util.src.API
6 decap-cms-lib-util.src.git-lfs
7 decap-cms-backend-bitbucket.src.git-lfs-client						1
8 decap-cms-core.src.actions.media	1
9 decap-cms-core.src.types.redux		1								2
10 decap-cms-core.src	1			1					1
11 decap-cms-core.src.components.UI									1
12 decap-cms-core.src.formats	1								1
13 decap-cms-lib-util.src.implementation									1
14 decap-cms-backend-azure.src.API					1					1
15 decap-cms-core.src.lib	2			2					3	1
16 decap-cms-lib-util.src.Cursor										1
17 decap-cms-lib-util.src.notesPolling										4
18 decap-cms-backend-bitbucket.src.API					1							1
19 decap-cms-backend-gitlab.src.notesApi										2			1
20 decap-cms-core.src.backend	2		1	1					6	4		1
21 decap-cms-backend-azure.src.implementation			1						1	3	1			1
22 decap-cms-backend-bitbucket.src.implementation			1		1		1		1	1		1		1
23 decap-cms-backend-forgejo.src.API				1	2									1
24 decap-cms-backend-forgejo.src.implementation			1						1	1		1		1
25 decap-cms-backend-git-gateway.src.GitLabAPI					1									1
26 decap-cms-backend-git-gateway.src.implementation			1		1				1	1		1		1
27 decap-cms-backend-gitea.src.implementation			1						1	1		1		1
28 decap-cms-backend-github.src.implementation			1						1	4		1	1	1
29 decap-cms-backend-gitlab.src										2					2
30 decap-cms-backend-gitlab.src.API					1							1		2
31 decap-cms-backend-gitlab.src.implementation			1		1				1	3		1	1	1	1
32 decap-cms-backend-proxy.src			1													1
33 decap-cms-backend-proxy.src.implementation			1							2				1
34 decap-cms-backend-test.src.implementation			1							2		1		1
35 decap-cms-core.src.actions	4		1	1				1	11	4		1				2
36 decap-cms-core.src.reducers	2	1							7							1
37 decap-cms-lib-util.src					2	1			1	3	1					1
38 decap-cms-backend-gitea.src.API				1	2									1			3
39 decap-cms-backend-github.src.API				1	2					3				1			3
40 decap-cms-backend-github.src.GraphQLAPI											1			1			1	1

Dependency, pointing down the layeringAbove the diagonal — part of a cycleThe module itself

At a glance — Code Health · 59% · Adequate · gated by D3, R1 ·

The Good

D17 · JavaScript Explicit Debt 9.9 R10 · React / TS Code Duplication 9.0 R2 · React / TS Cyclomatic Complexity 8.9 R3 · React / TS Large Files 7.1 R7 · React / TS Dead Code 9.2 X25 · Repo Inert configuration knob 10.0 X29 · Repo Per-element action decided by a fixed element 10.0

The Bad

D1 · JavaScript Cyclomatic Complexity 6.3 D2 · JavaScript Cognitive Complexity 6.4

The Ugly

D3 · JavaScript God Classes 3.6 R1 · React / TS Type Safety 2.0

At a glance — Architecture · 59% · Adequate · gated by R9 ·

The Good

D5 · JavaScript Coupling 8.6 D6 · JavaScript Cohesion (LCOM4) 9.2 D26 · JavaScript Project Cohesion 9.5 D35 · JavaScript Change Coupling 9.9 AX10 · Repo Code composition 9.0 AX3 · Repo Project dependency cycles 10.0 R11 · React / TS Import Boundaries 9.4

The Bad

AX4 · Repo Dependency direction 6.0

The Ugly

R9 · React / TS Circular Imports 1.6

At a glance — Maturity · 68% · Adequate · gated by M2 ·

The Good

D15 · JavaScript Churn × Complexity Hotspots 9.9 D16 · JavaScript Bus Factor 9.4 D21 · JavaScript Naming Consistency 10.0 M1 · Repo Documentation (README) 9.2 M3 · Repo Folder & project structure 10.0 M4 · Repo Documentation accuracy 10.0

The Bad

D19 · JavaScript Documentation Quality 6.6 D34 · JavaScript Knowledge Freshness 5.6

The Ugly

D20 · JavaScript ADR Quality 0.0 M2 · Repo Architecture documentation 2.0

At a glance — Readiness · 60% · Adequate · gated by R8, P3 ·

The Good

D9 · JavaScript Test Distribution 8.7 D10 · JavaScript Test Quality 10.0 D12 · JavaScript Dependency Hygiene 8.0 D13 · JavaScript REDACTED Scanning 10.0 D14 · JavaScript License Compliance 10.0 P1 · Repo CI/CD gates 10.0 P10 · Repo Library API & versioning 10.0 P2 · Repo Observability 7.0 P4 · Repo Deployment & Rollback 10.0 P6 · Repo Release Hygiene 10.0 R4 · React / TS Test Coverage 7.5 R6 · React / TS Tooling 10.0

The Ugly

P3 · Repo Security & performance tooling 3.0 R8 · React / TS Dependency Hygiene 3.5

At a glance — Security · 67% · Adequate · gated by D29, D30, D36 ·

The Good

D28 · JavaScript Secrets (history) 7.0 D37 · JavaScript Vulnerability-disclosure Policy 10.0 D43 · JavaScript Malicious Dependencies 10.0 D44 · JavaScript Platform End-of-Life 10.0 S1 · Repo Web-Security Posture 8.0 X24 · Repo Document value interpolated into markup unescaped 10.0

The Ugly

D29 · JavaScript Static Analysis (SAST) 1.0 D30 · JavaScript Dependency Vulnerabilities 0.0 D36 · JavaScript Supply-chain Provenance & Signing 2.5

At a glance — Performance · 100% · Exemplary ·

The Good

PF3 · Repo Async & latency hygiene 10.0

Security & Compliance — OWASP Top-10 mapping

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
A06:2021 — Vulnerable & Outdated Components	94	High / Critical
A03:2021 — Injection	48	High / Critical
A02:2021 — Cryptographic Failures	4	High / Critical

Roadmap

First, resolve circular imports by extracting shared logic into separate modules and enforce inward dependency direction to maintain clean architecture. Next, migrate remaining JavaScript files to TypeScript to improve type safety and reduce runtime errors. Finally, integrate static analysis into the CI pipeline to catch security regressions early and clean up unused dependencies to streamline the project.

Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.

Do this	Helps	Effort	Dimension
Break each cycle by extracting the shared piece into a module both sides can import.	+2.8 pts	Medium	Circular Imports
Keep dependencies pointing inward: domain/application define interfaces, infrastructure/web implement them (Dependency Inversion).	+2.7 pts	Medium	Dependency direction
Resolve the 1 No ADRs found finding(s) in ADR Quality.	+1.3 pts	Low	ADR Quality
Migrate the remaining .js/.jsx files to TypeScript.	+2.6 pts	Medium	Type Safety
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.	+2.4 pts	Medium	Security & performance tooling
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.	+2.4 pts	Medium	Dependency Hygiene
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.	+2.1 pts	Medium	Large Files
Consider OpenTelemetry tracing/metrics (@opentelemetry/sdk-node) and a health-check endpoint (@godaddy/terminus or a /health route) for operability.	+2.0 pts	Medium	Observability

File quality

Per-file score 0–10 — a quality signature. Of 95 files carrying findings, judged against the Production bar: 3% slop · 55% mixed · 42% near-clean.

File	Score	Band	Worst signal
REDACTED	0.0	Slop	Dependency Vulnerabilities: Critical CVE: REDACTED
REDACTED	2.7	Slop	Static Analysis (SAST): High: REDACTED
REDACTED	2.7	Slop	Static Analysis (SAST): High: REDACTED
REDACTED	4.4	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	4.4	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	4.6	Mixed	Static Analysis (SAST): Medium: REDACTED
packages/decap-cms-backend-test/src/implementation.ts	4.7	Mixed	Change Coupling: Boundary-crossing change coupling: implementation.ts ↔ backend.ts
REDACTED	4.8	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	5.1	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	5.7	Mixed	Static Analysis (SAST): High: REDACTED
packages/decap-cms-core/src/actions/config.ts	6.0	Mixed	Explicit Debt: TodoComment
packages/decap-cms-backend-git-gateway/src/implementation.ts	6.0	Mixed	Explicit Debt: TodoComment
packages/decap-cms-core/src/backend.ts	6.0	Mixed	Explicit Debt: TodoComment
packages/decap-cms-backend-bitbucket/src/API.ts	6.0	Mixed	Explicit Debt: TodoComment
REDACTED	6.4	Mixed	Static Analysis (SAST): Medium: REDACTED
REDACTED	6.4	Mixed	Static Analysis (SAST): Medium: REDACTED
packages/decap-cms-core/src/actions/__tests__/media.spec.ts	6.5	Mixed	Explicit Debt: TodoComment
packages/decap-cms-core/src/types/redux.ts	6.7	Mixed	Explicit Debt: TodoComment
packages/decap-cms-widget-markdown/src/serializers/slateRemark.js	7.1	Mixed	Cyclomatic Complexity: slateRemark.slateToRemark (cyclomatic 73)
packages/decap-cms-widget-richtext/src/serializers/slateRemark.js	7.1	Mixed	Cyclomatic Complexity: slateRemark.slateToRemark (cyclomatic 71)

How the grades work

Every finding carries one of four grades. Three say how serious it is. The fourth says this survey could not settle it — and it is a grade, not a gap.

Critical — 110

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 — 309

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 — 265

Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.

Could not be resolved — 32

Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.

Methodology & how to trust this report

Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 50 of 54 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 4 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.

Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.

What we checked — 54 dimensions across the health lenses

D1D2D3D5D6D9D10D12D13D14D15D16D17D19D20D21D26D28D29D30D34D35D36D37D43D44AX10AX3AX4M1M2M3M4P1P10P2P3P4P6PF3R1R10R11R2R3R4R6R7R8R9S1X24X25X29

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, 573 of 684 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.

This report answers yes to all three. That's the bar to hold any assessment to.

Tools & methods

The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.

Method	Backs	Version	Evaluator
Roslyn static analysis	Complexity, cohesion, coupling, dead code, API surface, layering	5.3.0	✓ deterministic
Native secret scanner	Hardcoded secrets / credentials	1.0.0	✓ deterministic
Watchdog duplication detector (in-process)	Code duplication	1.0.0	✓ deterministic
Coverage (coverlet / dotnet-coverage)	Line & branch coverage	10.0.400	✓ deterministic
NuGet / dotnet	Outdated, vulnerable & deprecated dependencies	10.0.400	✓ deterministic
git / LibGit2Sharp	Churn hotspots, knowledge concentration, history	2.43.0 · 0.31.0	✓ deterministic
gitleaks · semgrep · trivy	Secrets in history, SAST, CVEs, IaC & container, PII / GDPR	1.86.0 · 0.69.3	✓ deterministic
LLM (sampled · advisory)	Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement	Local LLM	◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 01a0f8e4-25e6-7a29-949e-a76661745970.

The exact command behind every deep-scan dimension — tool, version, invocation and retained raw output — is in Appendix B — Reproduction & audit trail.

Run transparency — what happened this run

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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the dependency install for packages/decap-server/ failed in the analyzer sandbox (throw new Error(), 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. In the meantime, commit (or publish into the working tree) the lcov/Cobertura report your CI produces and the real number is read on the next scan. You can widen what we reach: optional: commit the lcov/Cobertura report your CI produces, and the real number is read on the next scan.
D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT MEASURED: the JavaScript/TypeScript suite could not be re-run in the analyzer sandbox — the dependency install for packages/decap-server/ failed in the analyzer sandbox (throw new Error(), 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the jest suite in packages/decap-server/ was NOT MEASURED: the dependency install for packages/decap-server/ failed in the analyzer sandbox (throw new Error(), 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.
D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: it declares a published package (packages/decap-cms-app/package.json), but no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
AX6 Interface segregation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
C2 Access Controls — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
C3 Audit Trail — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
C4 Data Retention — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
C5 Data-Subject Rights — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
ED5 Idempotency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds retry-prone mutations by walking the repository's declared types, and NONE was loaded on this run, so it had nothing to look at. That is a limit of the analyzer's reach — it reads .NET projects — not a finding that this repository has no command handlers or message consumers.
GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
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 — Watchdog measured this, but not all of it. What it 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. 104 further occurrence(s) are not listed individually; the score already reflects all 144.
R4 Test Coverage — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. 77 further occurrence(s) are not listed individually; the score already reflects all 117.
X1 Async correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X12 Unreachable branch — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X13 Undrained process stream — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X14 Bypassable address classification — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X15 Unvalidated length from an untrusted reader — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X16 Unfloored truncation loop — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X17 Uncapped recursion over a caller-supplied document — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X18 Disposal-pattern correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X19 Unrestored process-global state — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X2 Cancellation propagation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X20 Mistyped argument guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X21 Side-effecting pattern guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X22 Contradicted release guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X23 Unguarded diagnostic materialisation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X27 Collection changed while being enumerated — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java and Rust source only, and no C# was loaded and no Java or Rust was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X28 Index access outside its own emptiness guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Scala source only, and no C# was loaded and no Scala was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X3 Exception handling — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X30 Support guard that admits what it rejects — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Scala source only, and no C# was loaded and no Scala was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X4 Structured logging — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X5 Nullable reference types — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.

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

Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.

Per-dimension blind spots

For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.

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.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
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 is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
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: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

The LLM boundary

LLM-set scores this run (4): D19, D21, D26, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score; each names its own sample and method on its card. They are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.

Dimensions

D1 · Cyclomatic Complexity6.3 / 10Adequate✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 6.3 / 10 · rule-coverage 100% · ceiling Prevented

40 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was slateRemark.slateToRemark at 73. 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), packages/decap-cms-core/src/reducers/entries.ts (entries.entries at 21), packages/decap-cms-core/src/reducers/editorialWorkflow.ts (editorialWorkflow.unpublishedEntries 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.

remarkToSlate::convertNode (cyclomatic 28) · ×2packages/decap-cms-widget-markdown/src/serializers/remarkSlate.js:235

slateToRemark::convertBlockNode (cyclomatic 26) · ×2packages/decap-cms-widget-richtext/src/serializers/slateRemark.js:322

slateRemark.slateToRemark (cyclomatic 73)packages/decap-cms-widget-markdown/src/serializers/slateRemark.js:71

slateRemark.slateToRemark (cyclomatic 71)packages/decap-cms-widget-richtext/src/serializers/slateRemark.js:67

remarkSlate.remarkToSlate (cyclomatic 46)packages/decap-cms-widget-markdown/src/serializers/remarkSlate.js:82

+ 23 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

Resolve the 2 remarkToSlate finding(s) in Cyclomatic Complexity — start with remarkSlate.js (2). — One of this dimension's main actionable groups (2 warning-level).
Resolve the 2 slateToRemark finding(s) in Cyclomatic Complexity — start with slateRemark.js (2). — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 slateRemark.slateToRemark (cyclomatic 73) finding(s) in Cyclomatic Complexity — start with slateRemark.js. — One of this dimension's main actionable groups (1 warning-level).
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D2 · Cognitive Complexity6.4 / 10Adequate✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 6.4 / 10 · rule-coverage 100% · ceiling Prevented

56 method(s) exceeded the cognitive complexity threshold of 15; the worst was config.applyDefaults at 69.

slateRemark.slateToRemark (cognitive 62) · ×2packages/decap-cms-widget-markdown/src/serializers/slateRemark.js:71

slateToRemark::convertInlineAndTextChildren (cognitive 16) · ×2packages/decap-cms-widget-markdown/src/serializers/slateRemark.js:263

config.applyDefaults (cognitive 69)packages/decap-cms-core/src/actions/config.ts:231

index.localGitMiddleware (cognitive 36)packages/decap-server/src/middlewares/localGit/index.ts:173

mediaLibrary.mediaLibrary (cognitive 35)packages/decap-cms-core/src/reducers/mediaLibrary.ts:62

+ 36 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

Resolve the 2 slateRemark.slateToRemark (cognitive 62) finding(s) in Cognitive Complexity — start with slateRemark.js (2). — One of this dimension's main actionable groups (2 warning-level).
Resolve the 2 slateToRemark finding(s) in Cognitive Complexity — start with slateRemark.js (2). — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 config.applyDefaults (cognitive 69) finding(s) in Cognitive Complexity — start with config.ts. — One of this dimension's main actionable groups (1 warning-level).
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D3 · God Classes3.6 / 10Weak✓ 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.

Maturity: Documented → Verified → Prevented · effective 3.6 / 10 · rule-coverage 100% · ceiling Prevented

49 god class(es) detected.

FileTooLong: src/API.ts · ×14packages/decap-cms-backend-github/src/API.ts

TooManyMethods: API · ×13packages/decap-cms-backend-github/src/API.ts:232

FunctionTooLong: index.localGitMiddleware · ×12packages/decap-server/src/middlewares/localGit/index.ts:173

MethodTooLong: EditorInterface.render · ×5packages/decap-cms-core/src/components/Editor/EditorInterface.js:259

ClassTooLong: Backend · ×5packages/decap-cms-core/src/backend.ts:362

What to do

Resolve the 14 FileTooLong finding(s) in God Classes — start with API.ts (5), entries.ts (2), implementation.ts (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).
Resolve the 12 FunctionTooLong finding(s) in God Classes — start with index.ts (2), slateRemark.js (2), VisualEditor.js (2). — One of this dimension's main actionable groups (12 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.

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.

Maturity: Documented → Verified → Prevented · effective 8.6 / 10 · rule-coverage 100% · ceiling Prevented

41 production modules (npm), 0 dependency cycle(s), 4 unstable depended-on module(s). Read from the build's own module declarations; 2 module(s) off the main sequence, with abstractness counted on 13 of the 41 (the rest declare no modelled class or interface, export only macros, or have no source directory of their own).

Off the main sequence: decap-cms-lib-widgets · ×2

Unstable project decap-cms-app

Unstable project decap-cms-backend-aws-cognito-github-proxy

Unstable project decap-cms-backend-git-gateway

Unstable project decap-cms-core

What to do

Resolve the 2 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (2 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).
Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D6 · Cohesion (LCOM4)9.2 / 10Stronggated by 3 serious findings✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 9.2 / 10 · rule-coverage 100% · ceiling Verified

3 of 48 classes have LCOM4 above 3.

Low cohesion: TestBackend (LCOM4 15) · ×3packages/decap-cms-backend-test/src/implementation.ts:152

What to do

Resolve the 3 Low cohesion finding(s) in Cohesion (LCOM4) — start with implementation.ts, REDACTED, EditorControlPane.js. — One of this dimension's main actionable groups (3 warning-level).
Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D9 · Test Distribution8.7 / 10Strong✓ Tool-verified

What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.

Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.

Maturity: Documented → Verified → Prevented · effective 8.7 / 10 · rule-coverage 100% · ceiling Documented

1600 test methods: 1439 unit, 0 integration, 0 BDD, 161 e2e. The JavaScript/TypeScript suite contributes 1600 `it`/`test` case(s) across 147 test file(s) declaring at least one; its tier split is read from package names and paths only.

What to do

Improve Test Distribution — currently 8.7/10. — 1600 test methods: 1439 unit, 0 integration, 0 BDD, 161 e2e. The JavaScript/TypeScript suite contributes 1600 `it`/`test` case(s) across 147 test file(s) declaring at least one; its tier split is read from package names and paths only.

Detailed fixes: d9_recommendation.md.

Do you agree with this assessment?

D10 · Test Quality10.0 / 10Stronggated by 3 serious findings✓ Tool-verified

What it measures: Whether the tests truly assert behaviour rather than just running the code.

Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

0 skipped, 135 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 1600 tests (1 harness-style project(s) excluded from the assertion penalty).

No assertions: should convert inline-shortcode between Slate and MDAST · ×3packages/decap-cms-widget-markdown/src/serializers/__tests__/slate.spec.js:343

No direct assertions: successfully loads · ×132cypress/e2e/simple_workflow_spec_test_backend.js:42

What to do

Resolve the 132 No direct assertions finding(s) in Test Quality — start with markdown_widget_list_spec.js (20), markdown_widget_quote_spec.js (13), editorial_workflow_spec_test_backend.js (11). — One of this dimension's main actionable groups (132 recommendation-level).
Resolve the 3 No assertions finding(s) in Test Quality — start with remarkShortcodes.spec.js (2), slate.spec.js. — One of this dimension's main actionable groups (3 warning-level).
Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D12 · Dependency Hygiene8.0 / 10Strong✓ Tool-verified

What it measures: Whether dependencies are current, secure, and not bloated.

Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.

Maturity: Documented → Verified → Prevented · effective 8.0 / 10 · rule-coverage 100% · ceiling Verified

82 outdated direct production npm dependency(ies) of 142 graded, 0 pinning defect(s), across 34 package.json (34 of them the product) and 1 committed lockfile(s). Development dependencies are deliberately not graded: this dimension grades what SHIPS. Whether any of these packages is DEPRECATED or UNMAINTAINED is not graded — registry.npmjs.org's latest-version answer carries neither, and release age does not stand in for a maintenance status. 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.

Outdated (npm): @dnd-kit/modifiers · ×82

What to do

Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D13 · REDACTED Scanning10.0 / 10Exemplary○ Nothing flagged

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

REDACTED scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

Do you agree with this assessment?

D14 · License Compliance10.0 / 10Exemplary○ Nothing flagged

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 of 142 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 142 production dependency(ies) this repository's committed lockfile resolves, across 34 product package.json manifest(s). Its 143 `devDependencies` declaration(s) are excluded: a consumer installs none of them. ★ DEPTH: this is the DIRECT production set the lockfile resolves, NOT the transitive closure — only one of the four lock dialects this pass reads states a full graph, so a banned licence pulled in only by a dependency's OWN dependencies is outside this verdict, exactly as the JVM arm's declaration-site verdict is. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. 1 of them publish no licence this pass can read on registry.npmjs.org — an absent field, `UNLICENSED`, or a `SEE LICENSE IN <file>` pointer into a tarball this pass does not download; that is missing data, not a violation, and none of them is charged. This repository publishes itself under MIT, which is its own choice and is not judged here.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

Do you agree with this assessment?

D15 · Churn × Complexity Hotspots9.9 / 10Stronggated by 5 serious findings✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 9.9 / 10 · rule-coverage 100% · ceiling Documented

Top hotspots: packages/decap-cms-core/src/reducers/mediaLibrary.ts (3×37=111); packages/decap-cms-core/src/components/Editor/EditorToolbar.js (2×22=44); packages/decap-cms-core/src/reducers/editorialWorkflow.ts (2×20=40) Repeated repair below the complexity floor: packages/decap-cms-widget-relation/src/RelationControl.js (4 of 5 changes were fixes)

Hotspot: packages/decap-cms-core/src/reducers/mediaLibrary.ts · ×4packages/decap-cms-core/src/reducers/mediaLibrary.ts:62

Repeated repair: packages/decap-cms-widget-relation/src/RelationControl.jspackages/decap-cms-widget-relation/src/RelationControl.js:276

What to do

Resolve the 4 Hotspot finding(s) in Churn × Complexity Hotspots — start with mediaLibrary.ts, EditorToolbar.js, editorialWorkflow.ts. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 1 Repeated repair finding(s) in Churn × Complexity Hotspots — start with RelationControl.js. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D16 · Bus Factor9.4 / 10Exemplary✓ Tool-verified

What it measures: Whether knowledge is concentrated in too few people (the "bus factor").

Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.

Maturity: Documented → Verified → Prevented · effective 9.4 / 10 · rule-coverage 100% · ceiling Documented

13 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is packages/decap-cms-backend-forgejo/src/API.ts. Counted over 200 of the 528 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Off-boarding risk: anonymized user #1

Further sole-owners (lower concentration)

✓ On the Gold path — maintain.

Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D17 · Explicit Debt9.9 / 10Stronggated by 15 serious findings✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 9.9 / 10 · rule-coverage 100% · ceiling Prevented

15 deducted task-comment markers across 26294 LoC (0.1/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 · ×15packages/decap-cms-backend-bitbucket/src/API.ts:735

What to do

Resolve the 15 TodoComment finding(s) in Explicit Debt — start with media.spec.ts (6), implementation.ts (3), backend.ts (2). — One of this dimension's main actionable groups (15 warning-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D19 · Documentation QualityAdequate◐ Sampled · advisory

What it measures: Whether the project's documentation is clear, complete, and useful.

Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.

Maturity: Documented → Verified → Prevented · effective Adequate / 10 · rule-coverage 100% · ceiling Documented

The repository's root README is clear and well written (overview + Decap CMS origin link + a full How It Works section plus installation/configuration), but the documentation is mostly at the directory level: each cypress/README.md, packages/decap-cms-app/README.md, etc. is an internal package README documenting its own directory rather than the repository as a whole (no overview, no install/build steps for the root repo). The architecture/design docs and XML-doc coverage are absent from this summary. The READMEs for packages decap-cms-widget-code and decap-cms-widget-colorstring are each a single 'Docs coming soon!' placeholder directing readers to the main repo's root README or an external site. There is no overview of what the package does, no installation/usage guidance, no contribution path, and no licence statement in any document.

Documentation: no installation or build instructionspackages/decap-cms-widget-code/README.md

What to do

Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 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: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

No architecture decision records were found.

No ADRs found

What to do

Resolve the 1 No ADRs found finding(s) in ADR Quality. — 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.

Do you agree with this assessment?

D21 · Naming ConsistencyExemplary◐ Sampled · advisory

What it measures: Whether names — types, methods, variables — are clear and consistent.

Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.

Maturity: Documented → Verified → Prevented · effective Exemplary / 10 · rule-coverage 100% · ceiling Verified

0 naming inconsistencies across 0 sampled symbols.

✓ On the Gold path — maintain.

Detailed fixes: d21_recommendation.md.

Do you agree with this assessment?

D26 · Project Cohesion9.5 / 10Exemplary✓ Tool-verified

What it measures: Whether each project is a focused, coherent unit rather than an oversized grab-bag.

Method: Project size overshoot penalties (LoC / public-type count / namespace count, 2-of-3 flag) weighted by log magnitude. Exhaustive across projects, deterministic, LLM-independent.

Maturity: Documented → Verified → Prevented · effective 9.5 / 10 · rule-coverage 100% · ceiling Documented

1 of 42 build units (npm) flagged as possibly oversized/incoherent.

Split packages/decap-cms-core

✓ On the Gold path — maintain.

Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D28 · Secrets (history)7.0 / 10Adequategated by 3 critical findings✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 7.0 / 10 · rule-coverage 100% · ceiling Documented

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

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.

Do you agree with this assessment?

D29 · Static Analysis (SAST)1.0 / 10Critical✓ Tool-verified

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).

Maturity: Documented → Verified → Prevented · effective 1.0 / 10 · rule-coverage 100% · ceiling Documented

48 finding(s): 0 critical, 39 high, 8 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 36 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`, … (+31 more) — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. 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

+ 10 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 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 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.

Do you agree with this assessment?

D30 · Dependency Vulnerabilities0.0 / 10Critical✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

94 finding(s): 8 critical, 48 high, 28 medium, 10 low.

REDACTED

+ 1 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

Resolve the 47 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (47). — One of this dimension's main actionable groups (47 issue-level).
Resolve the 8 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (8). — One of this dimension's main actionable groups (8 issue-level).
Resolve the 1 High vulnerability 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.

Do you agree with this assessment?

D34 · Knowledge Freshness5.6 / 10Adequate✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 5.6 / 10 · rule-coverage 100% · ceiling Documented

87 of 200 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-backend-bitbucket/src/API.ts. Counted over 200 of the 528 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned knowledge · ×4packages/decap-cms-backend-bitbucket/src/API.ts

Further orphaned files (smaller)

What to do

Resolve the 4 Orphaned knowledge finding(s) in Knowledge Freshness — start with API.ts, GraphQLAPI.ts, index.js. — One of this dimension's main actionable groups (4 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.

Do you agree with this assessment?

D35 · Change Coupling9.9 / 10Adequategated by 2 critical findings✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 9.9 / 10 · rule-coverage 100% · ceiling Documented

Strongest change-coupling: AuthenticationPage.js↔AuthenticationPage.js 55%; implementation.ts↔backend.ts 50%

Boundary-crossing change coupling: AuthenticationPage.js ↔ AuthenticationPage.js · ×2packages/decap-cms-backend-bitbucket/src/AuthenticationPage.js

What to do

Resolve the 2 Boundary-crossing change coupling finding(s) in Change Coupling — start with AuthenticationPage.js, implementation.ts. — One of this dimension's main actionable groups (2 issue-level).

Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D36 · Supply-chain Provenance & Signing2.5 / 10Weak✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 2.5 / 10 · rule-coverage 100% · ceiling Documented

1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).

REDACTED

+ 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. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D37 · Vulnerability-disclosure Policy10.0 / 10Exemplary✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.

✓ On the Gold path — maintain.

Detailed fixes: d37_recommendation.md.

Do you agree with this assessment?

D43 · Malicious Dependencies10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Scored apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.

Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. SCORED, not informational.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No dependency in any ecosystem this repository declares is published as malicious.

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

Do you agree with this assessment?

D44 · Platform End-of-Life10.0 / 10Exemplary✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 16 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Do you agree with this assessment?

Frontend & cross-cutting dimensions

R = React/JS · M = Maturity · P = Readiness.

AX10 · Code composition9.0 / 10Strong✓ Tool-verified

Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.

Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.

Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.

What to do

The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.

Do you agree with this assessment?

AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

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.

Do you agree with this assessment?

AX4 · Dependency direction6.0 / 10Adequate✓ Tool-verified

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.
`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.
`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.

What to do

Keep dependencies pointing inward: domain/application define interfaces, infrastructure/web implement them (Dependency Inversion).

Do you agree with this assessment?

M1 · Documentation (README)9.2 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.

Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.

What to do

Add a 'Testing' section to the root README — how to run the test suite.
Add a README to the 3 of 41 project(s) that lack one — worth up to 0.1 pts.

Do you agree with this assessment?

M2 · Architecture documentation2.0 / 10Critical✓ Tool-verified

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 significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree, with each file named `NNNN-title` in whatever markup those docs already use, is the most discoverable form).

Do you agree with this assessment?

M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repo is organised deliberately — src/test separation and consistent project naming.

Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.

Do you agree with this assessment?

M4 · Documentation accuracy10.0 / 10Exemplary◐ Sampled · advisory

Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).

Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.

Do you agree with this assessment?

P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

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 model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.

Do you agree with this assessment?

P2 · Observability7.0 / 10Strong✓ Tool-verified

Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.

Method: Filesystem/Roslyn scan: structured-logging frameworks (Serilog, NLog), OpenTelemetry, and health-check endpoint patterns. Exhaustive, deterministic.

What to do

Consider OpenTelemetry tracing/metrics (@opentelemetry/sdk-node) and a health-check endpoint (@godaddy/terminus or a /health route) for operability.

Do you agree with this assessment?

P3 · Security & performance tooling3.0 / 10Weak✓ Tool-verified

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 10919 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.

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.

Do you agree with this assessment?

P4 · Deployment & Rollback10.0 / 10Exemplary✓ Tool-verified

Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.

Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.

Do you agree with this assessment?

P6 · Release Hygiene10.0 / 10Exemplary✓ Tool-verified

Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.

Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.

Do you agree with this assessment?

PF3 · Async & latency hygiene10.0 / 10Exemplary✓ Tool-verified

Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.

Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from the language model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin) or inside a Java method returning a Reactor Mono/Flux — 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.0 / 10Critical✓ Tool-verified

React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.

Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.

136 typed · 549 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 (+543 more). 0 production file(s) opt out entirely with @ts-nocheck · 11 @ts-ignore suppression(s).

What to do

Migrate the remaining .js/.jsx files to TypeScript.

Do you agree with this assessment?

R10 · Code Duplication9.0 / 10Exemplary✓ Tool-verified

React / JS · Code Health — Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm over JS/TS tokens, D-386): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.

Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Deterministic.

90 duplicated blocks under packages/ have copies in at least two of the sibling directories decap-cms, decap-cms-app, decap-cms-backend-aws-cognito-github-proxy, decap-cms-backend-azure, decap-cms-backend-bitbucket, decap-cms-backend-forgejo (+24 more sibling(s) not listed) — 73 of them are reported below, and 17 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 90 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 90 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 90 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
7 duplicated blocks under packages/decap-cms-core/src/components/ have copies in at least two of the sibling directories Collection, Editor, MediaLibrary, UI, Workflow — 1 of them are reported below, and 6 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 7 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 7 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 7 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:7 · packages/decap-cms-widget-richtext/src/serializers/slateRemark.js:2 — these 2 files are line-for-line copies of one another — 192 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:7
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-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-widget-markdown/src/serializers/remarkSlate.js:11 · packages/decap-cms-widget-richtext/src/serializers/remarkSlate.js:6 — these 2 files are line-for-line copies of one another — 157 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:11
packages/decap-cms-backend-forgejo/src/implementation.tsx:41 · packages/decap-cms-backend-gitea/src/implementation.tsx:38 — the two spans are one implementation copied and then locally edited — 1011 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:41
packages/decap-cms-backend-azure/src/API.ts:511 · 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:511
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 — 633 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:2 · packages/decap-cms-widget-richtext/src/serializers/index.js:2 — these 2 files are line-for-line copies of one another — 90 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:2
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 — 423 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:8 — 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-core/src/actions/editorialWorkflow.ts:335 · packages/decap-cms-core/src/actions/entries.ts:961 — the two spans are one implementation copied and then locally edited — 310 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:335
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-widget-markdown/src/serializers/remarkPaddedLinks.js:20 · packages/decap-cms-widget-richtext/src/serializers/remarkPaddedLinks.js:14 — 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:525 · 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:525
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
packages/decap-cms-widget-markdown/src/serializers/remarkShortcodes.js: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. — packages/decap-cms-widget-markdown/src/serializers/remarkShortcodes.js: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:244 · packages/decap-cms-core/src/actions/entries.ts:283 — 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:244
REDACTED:45 · scripts/verify-published-packages.mjs:36 — the two spans are one implementation copied and then locally edited — 249 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:45
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:453 · packages/decap-cms-core/src/components/Editor/EditorToolbar.js:555 — 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:453
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:30 — 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:57 — 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-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
packages/decap-cms-core/src/reducers/entries.ts:703 · packages/decap-cms-core/src/reducers/entries.ts: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. — packages/decap-cms-core/src/reducers/entries.ts:703
packages/decap-cms-core/src/actions/entries.ts:211 · packages/decap-cms-core/src/actions/entries.ts:253 · packages/decap-cms-core/src/actions/entries.ts:292 — all 3 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:211

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.

Do you agree with this assessment?

R11 · Import Boundaries9.4 / 10Exemplary✓ Tool-verified

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/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

What to do

Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.

Do you agree with this assessment?

R2 · Cyclomatic Complexity8.9 / 10Strong✓ Tool-verified

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:232
(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-server/src/middlewares/localGit/index.ts:179
entryDraftReducer has cyclomatic complexity 31 and cognitive complexity 4; 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/entryDraft.js:72
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
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:229
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:322
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:599
Element has cyclomatic complexity 22 and cognitive complexity 4; 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/renderers.js:298
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. — packages/decap-cms-core/src/backend.ts:1246
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
unpublishedEntries has cyclomatic complexity 20 and cognitive complexity 4; 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/editorialWorkflow.ts:27
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
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
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
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:75
(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
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

What to do

Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.

Do you agree with this assessment?

R3 · Large Files7.1 / 10Strong✓ 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.

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 Coverage7.5 / 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
packages/decap-cms-backend-gitlab/src/__tests__/gitlab.spec.js:8 imports '../AuthenticationPage', 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. — packages/decap-cms-backend-gitlab/src/__tests__/gitlab.spec.js
packages/decap-cms-backend-proxy/src/__tests__/implementation.spec.ts:1 imports '../implementation', 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. — packages/decap-cms-backend-proxy/src/__tests__/implementation.spec.ts
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. (×37) — packages/decap-cms-backend-azure/src/API.ts, packages/decap-cms-widget-file/src/withFileControl.js, packages/decap-cms-core/src/components/MediaLibrary/MediaLibrary.js, …

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 and 2 other test file(s) in this workspace 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

Do you agree with this assessment?

R7 · Dead Code9.2 / 10Exemplary✓ Tool-verified

React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).

Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.

Unreachable from the 123 application, 65 tooling and 206 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 (123 application, 65 tooling, 206 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, setupTestFramework.js, …
Nothing imports this binding — it is safe to review for removal. (×14) — 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:1298, …
Nothing imports THIS copy of 'selectEntries' — but packages/decap-cms-core/src/reducers/entries.ts: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 packages/decap-cms-core/src/reducers/entries.ts'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:51

What to do

Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.

Do you agree with this assessment?

R8 · Dependency Hygiene3.5 / 10Weak✓ Tool-verified

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. (×3)

What to do

Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.

Do you agree with this assessment?

R9 · Circular Imports1.6 / 10Critical✓ Tool-verified

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/backend.ts → packages/decap-cms-core/src/lib/formatters.ts → packages/decap-cms-core/src/reducers/collections.ts → packages/decap-cms-core/src/actions/config.ts → packages/decap-cms-core/src/backend.ts (one verified cycle inside a mutually-dependent group of 30 files) — packages/decap-cms-core/src/backend.ts
packages/decap-cms-core/src/components/Collection/Entries/Entries.js → packages/decap-cms-core/src/components/Collection/Entries/EntryListing.js → packages/decap-cms-core/src/components/Collection/Entries/EntriesCollection.js → packages/decap-cms-core/src/components/Collection/Entries/Entries.js — packages/decap-cms-core/src/components/Collection/Entries/Entries.js
packages/decap-cms-widget-markdown/src/MarkdownControl/VisualEditor.js → packages/decap-cms-widget-markdown/src/MarkdownControl/renderers.js → packages/decap-cms-widget-markdown/src/MarkdownControl/components/InlineShortcode.js → packages/decap-cms-widget-markdown/src/MarkdownControl/index.js → packages/decap-cms-widget-markdown/src/MarkdownControl/VisualEditor.js (one verified cycle inside a mutually-dependent group of 6 files) — packages/decap-cms-widget-markdown/src/MarkdownControl/VisualEditor.js

What to do

Break each cycle by extracting the shared piece into a module both sides can import.

Do you agree with this assessment?

S1 · Web-Security Posture8.0 / 10Strong✓ Tool-verified

Other · Security — Only what this repository's own non-C# files could be read for was assessed — and because this repository commits the configuration that serves its own HTTP surface, that configuration could be read in full for the security response headers it sets. Nothing else in this dimension was assessed: the transport, cookie, input-validation and crypto controls are read from a source model that was not loaded for this repository’s language, so their absence here is not a finding about this repository.

Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. Deterministic.

No Content-Security-Policy / X-Frame-Options / X-Content-Type-Options configuration found — defense in depth, even when a reverse proxy could set them. This is reported because `netlify.toml` configures this repository's static hosting, including its response headers, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.) — netlify.toml:1

What to do

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.

Do you agree with this assessment?

X24 · Document value interpolated into markup unescaped10.0 / 10Exemplary○ Nothing flagged

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.

Do you agree with this assessment?

X25 · Inert configuration knob10.0 / 10Exemplary○ Nothing flagged

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. 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?

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.

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.

Lens	Score	Rating	Impact
Code Health	59%	Adequate — gated by D3, R1	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture	59%	Adequate — gated by R9	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity	68%	Adequate — gated by M2	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness	60%	Adequate — gated by R8, P3	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security	67%	Adequate — gated by D29, D30, D36	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance	100%	Exemplary	Strongest area.

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 — 11 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.

Not evidenced — 4 control(s) we could not find positive evidence for

These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.

C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control

Not included — 72 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 (3 DOM element(s) < 25) — too little surface to assess accessibility.
AC2 Forms & labels — Frontend below the scale floor (3 DOM element(s) < 25) — too little surface to assess accessibility.
AC3 Page structure — Frontend below the scale floor (3 DOM element(s) < 25) — too little surface to assess accessibility.
AC4 Keyboard semantics — Frontend below the scale floor (3 DOM element(s) < 25) — too little surface to assess accessibility.
AC5 ARIA correctness — Frontend below the scale floor (3 DOM element(s) < 25) — too little surface to assess accessibility.
AC6 Visual & motion safety — Frontend below the scale floor (3 DOM element(s) < 25) — too little surface to assess accessibility.
AC7 A11y enforcement — Frontend below the scale floor (3 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
AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
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 did not expose a crawlable HTTP endpoint in time — no runtime evidence This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no data at rest for these controls to protect. If it does persist personal data (through a hosted backend configured outside this repository, for instance), the controls belong to wherever that data is stored.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
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 — The exposed public-API surface could not be collected — no C#/VB projects loaded.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout nor 2+ sibling source directories each declaring an aggregate root. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — No inline comments to assess — comment value is not applicable here.
D25 ADR Conformance — no ADRs to check
D27 Navigability — symbol resolution incomplete — navigability not assessed
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
D4 Code Duplication — This repository's production source (.js, .mjs, .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 — This check finds retry-prone mutations (command handlers and message/event consumers) by walking the repository's declared types, and none was loaded here, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
GD1 Unfinished & placeholder code — no source files were read — this check reads C# syntax, and none was loaded for this repository. That is a limit of the analyzer, not a finding about your code.
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the JavaScript/TypeScript source (service entry point: packages/decap-server/src/index.ts:10 (express()))
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 — no coverage report found on disk — produce a coverage report in a standard format (lcov — `jest --coverage --coverageReporters=lcovonly`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for 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 applicable: TypeScript/JavaScript runs on a garbage-collected runtime that gives a program no allocation-control idiom to choose on a hot path — no pools, stack allocation or value types — so allocation awareness is not something this code can be rated on.
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.
X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X12 Unreachable branch — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X13 Undrained process stream — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X14 Bypassable address classification — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X15 Unvalidated length from an untrusted reader — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X16 Unfloored truncation loop — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X17 Uncapped recursion over a caller-supplied document — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X18 Disposal-pattern correctness — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X19 Unrestored process-global state — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X20 Mistyped argument guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X21 Side-effecting pattern guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X22 Contradicted release guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X23 Unguarded diagnostic materialisation — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X26 Unsynchronised callback handoff — 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 analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X28 Index access outside its own emptiness guard — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X30 Support guard that admits what it rejects — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.

Critical — 110 finding(s)

D30 · Dependency Vulnerabilities · High CVE · ×47

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 22 more in this group — see findings.md.

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 3 more in this group — see findings.md.

D30 · Dependency Vulnerabilities · Critical CVE · ×8

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D34 · Knowledge Freshness · Orphaned knowledge · ×4

Orphaned knowledge packages/decap-cms-backend-bitbucket/src/API.ts — 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-github/src/GraphQLAPI.ts — 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-locales/src/th/index.js — 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 — 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.

AX4 · Dependency direction · Dependency-rule violation · ×3

Dependency-rule violation: decap-cms-app (Application) → decap-cms-ui-auth (Web) — `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) — `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) — `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.

D28 · Secrets (history) · REDACTED · ×3

REDACTED
REDACTED
REDACTED

D35 · Change Coupling · Boundary-crossing change coupling · ×2

Boundary-crossing change coupling: AuthenticationPage.js ↔ AuthenticationPage.js packages/decap-cms-backend-bitbucket/src/AuthenticationPage.js — `packages/decap-cms-backend-bitbucket/src/AuthenticationPage.js` (context decap-cms-backend-bitbucket) and `packages/decap-cms-backend-github/src/AuthenticationPage.js` (context decap-cms-backend-github) sit in DIFFERENT parts of the tree yet change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — 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 6 shared commits counted here, the most recent 3 are `b540acec` feat: add logo to header (#7487); `ff85991b` chore: replace demo links (#6894); `7c45a3cd` fix(locale): Remove hard coded string literals (#3333) (at that commit the files were still `packages/netlify-cms-backend-bitbucket/src/AuthenticationPage.js` and `packages/netlify-cms-backend-github/src/AuthenticationPage.js`) — run `git show` on any of them.
Boundary-crossing change coupling: implementation.ts ↔ backend.ts packages/decap-cms-backend-test/src/implementation.ts — `packages/decap-cms-backend-test/src/implementation.ts` (context decap-cms-backend-test) and `packages/decap-cms-core/src/backend.ts` (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.

R9 · Circular Imports · Import cycle (4 files) · ×2

Import cycle (4 files) packages/decap-cms-core/src/backend.ts — packages/decap-cms-core/src/backend.ts → packages/decap-cms-core/src/lib/formatters.ts → packages/decap-cms-core/src/reducers/collections.ts → packages/decap-cms-core/src/actions/config.ts → packages/decap-cms-core/src/backend.ts (one verified cycle inside a mutually-dependent group of 30 files)
Import cycle (4 files) packages/decap-cms-widget-markdown/src/MarkdownControl/VisualEditor.js — packages/decap-cms-widget-markdown/src/MarkdownControl/VisualEditor.js → packages/decap-cms-widget-markdown/src/MarkdownControl/renderers.js → packages/decap-cms-widget-markdown/src/MarkdownControl/components/InlineShortcode.js → packages/decap-cms-widget-markdown/src/MarkdownControl/index.js → packages/decap-cms-widget-markdown/src/MarkdownControl/VisualEditor.js (one verified cycle inside a mutually-dependent group of 6 files)

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

D30 · Dependency Vulnerabilities · High vulnerability · ×1

REDACTED

R9 · Circular Imports · Import cycle (3 files) · ×1

Import cycle (3 files) packages/decap-cms-core/src/components/Collection/Entries/Entries.js — packages/decap-cms-core/src/components/Collection/Entries/Entries.js → packages/decap-cms-core/src/components/Collection/Entries/EntryListing.js → packages/decap-cms-core/src/components/Collection/Entries/EntriesCollection.js → packages/decap-cms-core/src/components/Collection/Entries/Entries.js

Serious — 309 finding(s)

R4 · Test Coverage · No test reaches this file · ×37

No test reaches this file packages/decap-cms-backend-azure/src/API.ts — 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-file/src/withFileControl.js — 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-core/src/components/MediaLibrary/MediaLibrary.js — 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 — 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 — 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 scripts/test-package-integrity.mjs — 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 REDACTED — 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-core/src/components/App/Header.js — 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-core/src/components/App/App.js — 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-core/src/components/Workflow/WorkflowList.js — 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-core/src/components/Workflow/WorkflowCard.js — 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 — 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-core/src/components/MediaLibrary/MediaLibraryModal.js — 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-core/src/components/MediaLibrary/MediaLibraryCardGrid.js — 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 — 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-core/src/components/Workflow/Workflow.js — 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 — 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-core/src/components/MediaLibrary/MediaLibraryTop.js — 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 — 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 — 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 — 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 — 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 — 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 — 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 — 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.
+ 12 more in this group — see findings.md.

D30 · Dependency Vulnerabilities · Medium CVE · ×28

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 3 more in this group — see findings.md.

D17 · Explicit Debt · TodoComment · ×15

TodoComment packages/decap-cms-backend-bitbucket/src/API.ts:735 — // 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.
TodoComment packages/decap-cms-backend-git-gateway/src/netlify-lfs-client.ts:50 — // 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-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-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-core/src/backend.ts:770 — // 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 packages/decap-cms-core/src/backend.ts:855 — // 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/actions/config.ts:372 — // 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-core/src/types/redux.ts:505 — // 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.

D3 · God Classes · FileTooLong · ×14

FileTooLong: src/API.ts packages/decap-cms-backend-github/src/API.ts — FileTooLong — 1293 significant lines (blank, comment-only and punctuation-only lines excluded), about 86% of them inside a single declaration: API (232-1979). The bar is 500 significant lines; this is 793 over it, 2.59× 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/backend.ts packages/decap-cms-core/src/backend.ts — FileTooLong — 1029 significant lines (blank, comment-only and punctuation-only lines excluded), about 73% of them inside a single declaration: Backend (362-1539). The bar is 500 significant lines; this is 529 over it, 2.06× 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 — 998 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 498 over it, 2.00× 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 — 737 significant lines (blank, comment-only and punctuation-only lines excluded), about 78% of them inside a single declaration: API (211-1042). The bar is 500 significant lines; this is 237 over it, 1.47× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/API.ts packages/decap-cms-backend-forgejo/src/API.ts — FileTooLong — 702 significant lines (blank, comment-only and punctuation-only lines excluded), about 87% of them inside a single declaration: API (113-1061). The bar is 500 significant lines; this is 202 over it, 1.40× 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 — 656 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 156 over it, 1.31× 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 — 600 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 78% of them inside a single declaration: ListControl (175-847). The bar is 500 significant lines; this is 100 over it, 1.20× 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: reducers/entries.ts packages/decap-cms-core/src/reducers/entries.ts — 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: src/API.ts packages/decap-cms-backend-bitbucket/src/API.ts — FileTooLong — 574 significant lines (blank, comment-only and punctuation-only lines excluded), about 74% of them inside a single declaration: API (203-829). 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: Editor/EditorToolbar.js packages/decap-cms-core/src/components/Editor/EditorToolbar.js — FileTooLong — 572 significant lines (blank, comment-only and punctuation-only lines excluded), about 64% of them inside a single declaration: EditorToolbar (266-730). The bar is 500 significant lines; this is 72 over it, 1.14× 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 — 551 significant lines (blank, comment-only and punctuation-only lines excluded), about 71% of them inside a single declaration: API (223-807). The bar is 500 significant lines; this is 51 over it, 1.10× 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 — 519 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 19 over it, 1.04× 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.

D3 · God Classes · TooManyMethods · ×13

TooManyMethods: API packages/decap-cms-backend-github/src/API.ts:232 — TooManyMethods — 92 methods. The bar is 30 methods; this is 62 over it, 3.07× 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 packages/decap-cms-core/src/backend.ts:362 — TooManyMethods — 61 methods. The bar is 30 methods; this is 31 over it, 2.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.
TooManyMethods: API packages/decap-cms-backend-forgejo/src/API.ts:113 — TooManyMethods — 57 methods. The bar is 30 methods; this is 27 over it, 1.90× 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:203 — TooManyMethods — 42 methods. The bar is 30 methods; this is 12 over it, 1.40× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: API packages/decap-cms-backend-azure/src/API.ts:223 — 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:98 — 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: 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: Forgejo packages/decap-cms-backend-forgejo/src/implementation.tsx:47 — TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× 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.

D3 · God Classes · FunctionTooLong · ×12

FunctionTooLong: index.localGitMiddleware packages/decap-server/src/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: 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:67 — 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: 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-server/src/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: entryDraft.entryDraftReducer packages/decap-cms-core/src/reducers/entryDraft.js:72 — FunctionTooLong — entryDraftReducer runs 134 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 34 over it, 1.34× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: 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:76 — 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.

D3 · God Classes · MethodTooLong · ×5

MethodTooLong: EditorInterface.render packages/decap-cms-core/src/components/Editor/EditorInterface.js:259 — MethodTooLong — render runs 217 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 117 over it, 2.17× 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:197 — MethodTooLong — render runs 174 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 74 over it, 1.74× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: 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: Widget.render packages/decap-cms-core/src/components/Editor/EditorControlPane/Widget.js: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.
MethodTooLong: App.render packages/decap-cms-core/src/components/App/App.js:146 — MethodTooLong — render runs 101 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1 over it, 1.01× 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.

D3 · God Classes · ClassTooLong · ×5

ClassTooLong: Backend packages/decap-cms-core/src/backend.ts:362 — ClassTooLong — 751 significant lines (blank, comment-only and punctuation-only lines excluded), 61 methods. The bar is 400 significant lines; this is 351 over it, 1.88× 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 — 611 significant lines (blank, comment-only and punctuation-only lines excluded), 57 methods. The bar is 400 significant lines; this is 211 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.
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 — 409 significant lines (blank, comment-only and punctuation-only lines excluded), 32 methods. The bar is 400 significant lines; this is 9 over it, 1.02× 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.

D15 · Churn × Complexity Hotspots · Hotspot · ×4

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-06-24..2026-09-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-24 14:36:34 +02:00' --until='2026-09-22 14:36:34 +02: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/EditorToolbar.js packages/decap-cms-core/src/components/Editor/EditorToolbar.js:599 — packages/decap-cms-core/src/components/Editor/EditorToolbar.js changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in EditorToolbar.renderWorkflowControls at line 599. 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-06-24..2026-09-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-24 14:36:34 +02:00' --until='2026-09-22 14:36:34 +02:00' --full-history --no-merges -- packages/decap-cms-core/src/components/Editor/EditorToolbar.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/editorialWorkflow.ts packages/decap-cms-core/src/reducers/editorialWorkflow.ts:27 — packages/decap-cms-core/src/reducers/editorialWorkflow.ts changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in editorialWorkflow.unpublishedEntries at line 27. 1 of those changes was a fix/bug commit, and the other 1 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-06-24..2026-09-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-24 14:36:34 +02:00' --until='2026-09-22 14:36:34 +02: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-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-06-24..2026-09-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-24 14:36:34 +02:00' --until='2026-09-22 14:36:34 +02: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.

R11 · Import Boundaries · Boundary violation [package · ×4

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.

D10 · Test Quality · No assertions · ×3

No assertions: should convert inline-shortcode between Slate and MDAST packages/decap-cms-widget-markdown/src/serializers/__tests__/slate.spec.js:343 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should parse inline shortcode inside paragraph without breaking paragraph into blocks packages/decap-cms-widget-markdown/src/serializers/__tests__/remarkShortcodes.spec.js:116 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should stringify inline shortcodes correctly in round-trip packages/decap-cms-widget-markdown/src/serializers/__tests__/remarkShortcodes.spec.js:253 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.

D6 · Cohesion (LCOM4) · Low cohesion · ×3

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) REDACTED: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:98 — 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.

R4 · Test Coverage · This test file cannot be loaded · ×3

This test file cannot be loaded cypress/run.mjs — 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.
This test file cannot be loaded packages/decap-cms-backend-gitlab/src/__tests__/gitlab.spec.js — packages/decap-cms-backend-gitlab/src/__tests__/gitlab.spec.js:8 imports '../AuthenticationPage', 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.
This test file cannot be loaded packages/decap-cms-backend-proxy/src/__tests__/implementation.spec.ts — packages/decap-cms-backend-proxy/src/__tests__/implementation.spec.ts:1 imports '../implementation', 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.

D1 · Cyclomatic Complexity · remarkToSlate · ×2

remarkToSlate::convertNode (cyclomatic 28) packages/decap-cms-widget-markdown/src/serializers/remarkSlate.js:235 — 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.
remarkToSlate::convertNode (cyclomatic 26) packages/decap-cms-widget-richtext/src/serializers/remarkSlate.js:229 — 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.

D1 · Cyclomatic Complexity · slateToRemark · ×2

slateToRemark::convertBlockNode (cyclomatic 26) packages/decap-cms-widget-richtext/src/serializers/slateRemark.js:322 — 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.
slateToRemark::convertBlockNode (cyclomatic 25) packages/decap-cms-widget-markdown/src/serializers/slateRemark.js:328 — 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.

D2 · Cognitive Complexity · slateRemark.slateToRemark (cognitive 62) · ×2

slateRemark.slateToRemark (cognitive 62) packages/decap-cms-widget-markdown/src/serializers/slateRemark.js:71 — slateRemark.slateToRemark has cognitive complexity 62 (threshold 15). Drivers by points: if/else 18 (31 pts), ternaries 9 (14 pts), boolean chains 9, match/switch 5, loops 2 (3 pts) (nesting depth added 19). Of this number, 59 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
slateRemark.slateToRemark (cognitive 62) packages/decap-cms-widget-richtext/src/serializers/slateRemark.js:67 — slateRemark.slateToRemark has cognitive complexity 62 (threshold 15). Drivers by points: if/else 18 (31 pts), ternaries 9 (14 pts), boolean chains 9, match/switch 5, loops 2 (3 pts) (nesting depth added 19). Of this number, 59 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · slateToRemark · ×2

slateToRemark::convertInlineAndTextChildren (cognitive 16) packages/decap-cms-widget-markdown/src/serializers/slateRemark.js:263 — 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.
slateToRemark::convertInlineAndTextChildren (cognitive 16) packages/decap-cms-widget-richtext/src/serializers/slateRemark.js:257 — 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.

D29 · Static Analysis (SAST) · REDACTED · ×2

REDACTED
REDACTED

D29 · Static Analysis (SAST) · REDACTED · ×2

REDACTED
REDACTED

D5 · Coupling · Off the main sequence · ×2

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 14 project(s), so it's rigid to change.

R10 · Code Duplication · Duplicated block (32 lines × 2 locations) · ×2

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:453 — packages/decap-cms-core/src/components/Editor/EditorToolbar.js:453 · packages/decap-cms-core/src/components/Editor/EditorToolbar.js:555 — 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.

R10 · Code Duplication · Duplicated block (27 lines × 2 locations) · ×2

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:30 — 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 (24 lines × 2 locations) · ×2

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:57 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.

R10 · Code Duplication · Duplicated block (23 lines × 2 locations) · ×2

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) packages/decap-cms-core/src/reducers/entries.ts:703 — packages/decap-cms-core/src/reducers/entries.ts:703 · packages/decap-cms-core/src/reducers/entries.ts: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.

D1 · Cyclomatic Complexity · slateRemark.slateToRemark (cyclomatic 73) · ×1

slateRemark.slateToRemark (cyclomatic 73) packages/decap-cms-widget-markdown/src/serializers/slateRemark.js:71 — slateRemark.slateToRemark has cyclomatic complexity 73 (threshold 15). Of this number, 66 points are the body's own statements and 7 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · slateRemark.slateToRemark (cyclomatic 71) · ×1

slateRemark.slateToRemark (cyclomatic 71) packages/decap-cms-widget-richtext/src/serializers/slateRemark.js:67 — slateRemark.slateToRemark has cyclomatic complexity 71 (threshold 15). Of this number, 65 points are the body's own statements and 6 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · remarkSlate.remarkToSlate (cyclomatic 46) · ×1

remarkSlate.remarkToSlate (cyclomatic 46) packages/decap-cms-widget-markdown/src/serializers/remarkSlate.js:82 — remarkSlate.remarkToSlate has cyclomatic complexity 46 (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.

D1 · Cyclomatic Complexity · remarkSlate.remarkToSlate (cyclomatic 44) · ×1

remarkSlate.remarkToSlate (cyclomatic 44) packages/decap-cms-widget-richtext/src/serializers/remarkSlate.js:76 — remarkSlate.remarkToSlate has cyclomatic complexity 44 (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.

D1 · Cyclomatic Complexity · config.applyDefaults (cyclomatic 40) · ×1

config.applyDefaults (cyclomatic 40) packages/decap-cms-core/src/actions/config.ts:231 — 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 232). 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.

D1 · Cyclomatic Complexity · entryDraft.entryDraftReducer (cyclomatic 38) · ×1

entryDraft.entryDraftReducer (cyclomatic 38) packages/decap-cms-core/src/reducers/entryDraft.js:72 — entryDraft.entryDraftReducer has cyclomatic complexity 38 (threshold 15). Of this number, 31 points are the body's own statements and 7 belong to 3 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.

D1 · Cyclomatic Complexity · mediaLibrary.mediaLibrary (cyclomatic 37) · ×1

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.

D1 · Cyclomatic Complexity · index.localGitMiddleware (cyclomatic 36) · ×1

index.localGitMiddleware (cyclomatic 36) packages/decap-server/src/middlewares/localGit/index.ts:173 — index.localGitMiddleware has cyclomatic complexity 36 (threshold 15). Most of this is not in the body itself: 1 of the 36 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 179, 331, 257, …). 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.

D1 · Cyclomatic Complexity · withFileControl.withFileControl (cyclomatic 29) · ×1

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.

D1 · Cyclomatic Complexity · GitGateway.authenticate (cyclomatic 22) · ×1

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.

D1 · Cyclomatic Complexity · formatters.commitMessageFormatter (cyclomatic 22) · ×1

formatters.commitMessageFormatter (cyclomatic 22) packages/decap-cms-core/src/lib/formatters.ts:50 — 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 69, 91). 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.

D1 · Cyclomatic Complexity · EditorToolbar.renderWorkflowControls (cyclomatic 22) · ×1

EditorToolbar.renderWorkflowControls (cyclomatic 22) packages/decap-cms-core/src/components/Editor/EditorToolbar.js:599 — 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.

D1 · Cyclomatic Complexity · renderWorkflowStatusControls · ×1

renderWorkflowStatusControls::renderWorkflowControls (cyclomatic 22) packages/decap-cms-core/src/components/Editor/EditorToolbar.js:599 — 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.

D1 · Cyclomatic Complexity · Backend.persistEntry (cyclomatic 21) · ×1

Backend.persistEntry (cyclomatic 21) packages/decap-cms-core/src/backend.ts:1246 — 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.

D1 · Cyclomatic Complexity · MediaLibraryModal.MediaLibraryModal (cyclomatic 20) · ×1

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.

D1 · Cyclomatic Complexity · Toolbar.render (cyclomatic 20) · ×1

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.

D1 · Cyclomatic Complexity · remarkShortcodes.createInlineShortcodeTokenizer (cyclomatic 20) · ×1

remarkShortcodes.createInlineShortcodeTokenizer (cyclomatic 20) packages/decap-cms-widget-markdown/src/serializers/remarkShortcodes.js:88 — remarkShortcodes.createInlineShortcodeTokenizer has cyclomatic complexity 20 (threshold 15). Of this number, 10 points are the body's own statements and 10 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.

D1 · Cyclomatic Complexity · GitHub.constructor (cyclomatic 18) · ×1

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.

D1 · Cyclomatic Complexity · GitLab.constructor (cyclomatic 18) · ×1

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.

D1 · Cyclomatic Complexity · InlineShortcode.InlineShortcode (cyclomatic 17) · ×1

InlineShortcode.InlineShortcode (cyclomatic 17) packages/decap-cms-widget-markdown/src/MarkdownControl/components/InlineShortcode.js:9 — InlineShortcode.InlineShortcode has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · withLists (cyclomatic 17) · ×1

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, …). 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.

D1 · Cyclomatic Complexity · BitbucketBackend.constructor (cyclomatic 16) · ×1

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.

D1 · Cyclomatic Complexity · EditorControl.render (cyclomatic 16) · ×1

EditorControl.render (cyclomatic 16) packages/decap-cms-core/src/components/Editor/EditorControlPane/EditorControl.js:197 — EditorControl.render has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 4 of the 16 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 251, 272). 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.

D1 · Cyclomatic Complexity · PKCEAuthenticationPage.normalizeClaimsToUser (cyclomatic 16) · ×1

PKCEAuthenticationPage.normalizeClaimsToUser (cyclomatic 16) packages/decap-cms-ui-auth/src/PKCEAuthenticationPage.js:12 — PKCEAuthenticationPage.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.

D1 · Cyclomatic Complexity · remarkRehypeShortcodes.remarkToRehypeShortcodes (cyclomatic 16) · ×1

remarkRehypeShortcodes.remarkToRehypeShortcodes (cyclomatic 16) packages/decap-cms-widget-markdown/src/serializers/remarkRehypeShortcodes.js:12 — remarkRehypeShortcodes.remarkToRehypeShortcodes has cyclomatic complexity 16 (threshold 15). Of this number, 11 points are the body's own statements and 5 belong to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · withHtml.deserialize (cyclomatic 16) · ×1

withHtml.deserialize (cyclomatic 16) packages/decap-cms-widget-markdown/src/MarkdownControl/plugins/html/withHtml.js:75 — 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.

D15 · Churn × Complexity Hotspots · Repeated repair · ×1

Repeated repair: packages/decap-cms-widget-relation/src/RelationControl.js packages/decap-cms-widget-relation/src/RelationControl.js:276 — packages/decap-cms-widget-relation/src/RelationControl.js changed 5 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 7 (its worst body is RelationControl.loadInitialOptions at line 276), 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: “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”; “Fix: improve relation widget (#7968)”. 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-06-24..2026-09-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-24 14:36:34 +02:00' --until='2026-09-22 14:36:34 +02: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.

D2 · Cognitive Complexity · config.applyDefaults (cognitive 69) · ×1

config.applyDefaults (cognitive 69) packages/decap-cms-core/src/actions/config.ts:231 — 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). Most of this is not in the body itself: 0 of the 69 points are its own statements and the rest belongs to one function literal inside it that branches (line 232). 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.

D2 · Cognitive Complexity · index.localGitMiddleware (cognitive 36) · ×1

index.localGitMiddleware (cognitive 36) packages/decap-server/src/middlewares/localGit/index.ts:173 — index.localGitMiddleware 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). Most of this is not in the body itself: 0 of the 36 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 179, 331, 257, …). 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.

D2 · Cognitive Complexity · mediaLibrary.mediaLibrary (cognitive 35) · ×1

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.

D2 · Cognitive Complexity · createInlineShortcodeTokenizer (cognitive 30) · ×1

createInlineShortcodeTokenizer (cognitive 30) packages/decap-cms-widget-markdown/src/serializers/remarkShortcodes.js: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). Most of this is not in the body itself: 0 of the 30 points are its own statements and the rest belongs to 5 function items inside it that branch (locateInlineShortcode::(anonymous), tokenizeInlineShortcode, (anonymous), …). 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.

D2 · Cognitive Complexity · withFileControl.withFileControl (cognitive 29) · ×1

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.

D2 · Cognitive Complexity · GitGateway.authenticate (cognitive 26) · ×1

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.

D2 · Cognitive Complexity · API.uploadFiles (cognitive 25) · ×1

API.uploadFiles (cognitive 25) packages/decap-cms-backend-bitbucket/src/API.ts:429 — 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.

D2 · Cognitive Complexity · NotesPollingManager.checkCurrentIssue (cognitive 23) · ×1

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.

D2 · Cognitive Complexity · insertShortcode.insertShortcode (cognitive 23) · ×1

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.

D2 · Cognitive Complexity · API.requestWithBackoff (cognitive 22) · ×1

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.

D2 · Cognitive Complexity · remarkSlate.remarkToSlate (cognitive 22) · ×1

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). 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.

D2 · Cognitive Complexity · GraphQLAPI.mutate (cognitive 20) · ×1

GraphQLAPI.mutate (cognitive 20) packages/decap-cms-backend-github/src/GraphQLAPI.ts:153 — 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.

D2 · Cognitive Complexity · configSchema.validateConfig (cognitive 20) · ×1

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.

D2 · Cognitive Complexity · entries.evaluateFolder (cognitive 20) · ×1

entries.evaluateFolder (cognitive 20) packages/decap-cms-core/src/reducers/entries.ts: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.

D2 · Cognitive Complexity · Backend.persistEntry (cognitive 20) · ×1

Backend.persistEntry (cognitive 20) packages/decap-cms-core/src/backend.ts:1246 — 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.

D2 · Cognitive Complexity · remarkSlate.remarkToSlate (cognitive 20) · ×1

remarkSlate.remarkToSlate (cognitive 20) packages/decap-cms-widget-richtext/src/serializers/remarkSlate.js:76 — 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). 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.

D2 · Cognitive Complexity · publish-packages.main (cognitive 20) · ×1

publish-packages.main (cognitive 20) REDACTED:212 — publish-packages.main has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (12 pts), loops 4 (7 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · InlineShortcode.InlineShortcode (cognitive 19) · ×1

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). 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.

D2 · Cognitive Complexity · withHtml.deserialize (cognitive 19) · ×1

withHtml.deserialize (cognitive 19) packages/decap-cms-widget-markdown/src/MarkdownControl/plugins/html/withHtml.js:75 — 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.

D2 · Cognitive Complexity · render (cognitive 19) · ×1

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.

D2 · Cognitive Complexity · API.listFiles (cognitive 18) · ×1

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.

D2 · Cognitive Complexity · GitHub.constructor (cognitive 18) · ×1

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.

D2 · Cognitive Complexity · formatters.commitMessageFormatter (cognitive 18) · ×1

formatters.commitMessageFormatter (cognitive 18) packages/decap-cms-core/src/lib/formatters.ts:50 — 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 69, 91). 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.

D2 · Cognitive Complexity · mediaLibrary.persistMedia (cognitive 18) · ×1

mediaLibrary.persistMedia (cognitive 18) packages/decap-cms-core/src/actions/mediaLibrary.ts:266 — mediaLibrary.persistMedia 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). Most of this is not in the body itself: 0 of the 18 points are its own statements and the rest belongs to one function literal inside it that branches (line 268). 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.

D2 · Cognitive Complexity · entries.createEmptyDraftData (cognitive 18) · ×1

entries.createEmptyDraftData (cognitive 18) packages/decap-cms-core/src/actions/entries.ts:852 — 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). Most of this is not in the body itself: 0 of the 18 points are its own statements and the rest belongs to one function literal inside it that branches (line 857). 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.

D2 · Cognitive Complexity · EditorToolbar.renderWorkflowControls (cognitive 18) · ×1

EditorToolbar.renderWorkflowControls (cognitive 18) packages/decap-cms-core/src/components/Editor/EditorToolbar.js:599 — 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.

D2 · Cognitive Complexity · renderWorkflowStatusControls · ×1

renderWorkflowStatusControls::renderWorkflowControls (cognitive 18) packages/decap-cms-core/src/components/Editor/EditorToolbar.js:599 — 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.

D2 · Cognitive Complexity · MediaLibraryModal (cognitive 18) · ×1

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.

D2 · Cognitive Complexity · withLists (cognitive 18) · ×1

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, …). 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.

D2 · Cognitive Complexity · API.hasWriteAccess (cognitive 17) · ×1

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.

D2 · Cognitive Complexity · entryDraft.entryDraftReducer (cognitive 17) · ×1

entryDraft.entryDraftReducer (cognitive 17) packages/decap-cms-core/src/reducers/entryDraft.js:72 — entryDraft.entryDraftReducer has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 3, ternaries 1 (2 pts), match/switch 1 (nesting depth added 6). Most of this is not in the body itself: 4 of the 17 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 131, 195, 243). 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.

D2 · Cognitive Complexity · CodeControl.handleChangeCodeMirrorProps (cognitive 17) · ×1

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.

D2 · Cognitive Complexity · remarkRehypeShortcodes.remarkToRehypeShortcodes (cognitive 17) · ×1

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). Of this number, 9 points are the body's own statements and 8 belong to one function literal inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.

D2 · Cognitive Complexity · verify-published-packages.main (cognitive 17) · ×1

verify-published-packages.main (cognitive 17) scripts/verify-published-packages.mjs:188 — verify-published-packages.main has cognitive complexity 17 (threshold 15). Drivers by points: loops 4 (8 pts), if/else 6 (7 pts), boolean chains 2 (nesting depth added 5). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.

D2 · Cognitive Complexity · Forgejo.constructor (cognitive 16) · ×1

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.

D2 · Cognitive Complexity · API.updateUnpublishedEntryStatus (cognitive 16) · ×1

API.updateUnpublishedEntryStatus (cognitive 16) packages/decap-cms-backend-github/src/API.ts:1194 — 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.

D2 · Cognitive Complexity · GitLab.constructor (cognitive 16) · ×1

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.

D2 · Cognitive Complexity · PKCEAuthenticationPage.normalizeClaimsToUser (cognitive 16) · ×1

PKCEAuthenticationPage.normalizeClaimsToUser (cognitive 16) packages/decap-cms-ui-auth/src/PKCEAuthenticationPage.js:12 — PKCEAuthenticationPage.normalizeClaimsToUser has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 5 (nesting depth added 3). Most of this is not in the body itself: 0 of the 16 points are its own statements 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.

D2 · Cognitive Complexity · remarkShortcodes.createShortcodeTokenizer (cognitive 16) · ×1

remarkShortcodes.createShortcodeTokenizer (cognitive 16) packages/decap-cms-widget-markdown/src/serializers/remarkShortcodes.js:26 — remarkShortcodes.createShortcodeTokenizer has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (8 pts), ternaries 2 (5 pts), error handling 1 (2 pts), boolean chains 1 (nesting depth added 6). Most of this is not in the body itself: 0 of the 16 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 34, 27, 37). 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.

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D5 · Coupling · Unstable project decap-cms-app · ×1

Unstable project decap-cms-app — decap-cms-app has instability 0.97 with 1 dependents.

D5 · Coupling · Unstable project decap-cms-backend-aws-cognito-github-proxy · ×1

Unstable project decap-cms-backend-aws-cognito-github-proxy — decap-cms-backend-aws-cognito-github-proxy has instability 0.83 with 1 dependents.

D5 · Coupling · Unstable project decap-cms-backend-git-gateway · ×1

Unstable project decap-cms-backend-git-gateway — decap-cms-backend-git-gateway has instability 0.88 with 1 dependents.

D5 · Coupling · Unstable project decap-cms-core · ×1

Unstable project decap-cms-core — decap-cms-core has instability 0.83 with 1 dependents.

R1 · Type Safety · Type Safety · ×1

Type Safety — 136 typed · 549 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 (+543 more). 0 production file(s) opt out entirely with @ts-nocheck · 11 @ts-ignore suppression(s).

R10 · Code Duplication · Duplication concentrated across 30 sibling directories (90 clone groups) · ×1

Duplication concentrated across 30 sibling directories (90 clone groups) packages/decap-cms-backend-forgejo/src/API.ts:56 — 90 duplicated blocks under packages/ have copies in at least two of the sibling directories decap-cms, decap-cms-app, decap-cms-backend-aws-cognito-github-proxy, decap-cms-backend-azure, decap-cms-backend-bitbucket, decap-cms-backend-forgejo (+24 more sibling(s) not listed) — 73 of them are reported below, and 17 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 90 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 90 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 90 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 · Duplication concentrated across 5 sibling directories (7 clone groups) · ×1

Duplication concentrated across 5 sibling directories (7 clone groups) packages/decap-cms-core/src/components/Collection/Entries/EntryCard.js:232 — 7 duplicated blocks under packages/decap-cms-core/src/components/ have copies in at least two of the sibling directories Collection, Editor, MediaLibrary, UI, Workflow — 1 of them are reported below, and 6 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 7 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 7 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 7 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 · Duplication concentrated across 4 sibling directories (6 clone groups) · ×1

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.

R10 · Code Duplication · Wholesale file copy (192 identical lines × 2 files) · ×1

Wholesale file copy (192 identical lines × 2 files) packages/decap-cms-widget-markdown/src/serializers/slateRemark.js:7 — packages/decap-cms-widget-markdown/src/serializers/slateRemark.js:7 · packages/decap-cms-widget-richtext/src/serializers/slateRemark.js:2 — these 2 files are line-for-line copies of one another — 192 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 (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.

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 · Wholesale file copy (157 identical lines × 2 files) · ×1

Wholesale file copy (157 identical lines × 2 files) packages/decap-cms-widget-markdown/src/serializers/remarkSlate.js:11 — packages/decap-cms-widget-markdown/src/serializers/remarkSlate.js:11 · packages/decap-cms-widget-richtext/src/serializers/remarkSlate.js:6 — these 2 files are line-for-line copies of one another — 157 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 (153 matched lines × 2 locations) · ×1

Duplicated block with local edits (153 matched lines × 2 locations) packages/decap-cms-backend-forgejo/src/implementation.tsx:41 — packages/decap-cms-backend-forgejo/src/implementation.tsx:41 · packages/decap-cms-backend-gitea/src/implementation.tsx:38 — the two spans are one implementation copied and then locally edited — 1011 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:511 — packages/decap-cms-backend-azure/src/API.ts:511 · 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.

R10 · Code Duplication · Duplicated block (106 lines × 2 locations) · ×1

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 (102 matched lines × 2 locations) · ×1

Duplicated block with local edits (102 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 — 633 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 (97 lines × 2 locations) · ×1

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.

R10 · Code Duplication · Wholesale file copy (90 identical lines × 2 files) · ×1

Wholesale file copy (90 identical lines × 2 files) packages/decap-cms-widget-markdown/src/serializers/index.js:2 — packages/decap-cms-widget-markdown/src/serializers/index.js:2 · packages/decap-cms-widget-richtext/src/serializers/index.js:2 — these 2 files are line-for-line copies of one another — 90 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 (71 lines × 2 locations) · ×1

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 — 423 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 (67 lines × 2 locations) · ×1

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:8 — 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 (65 matched lines × 2 locations) · ×1

Duplicated block with local edits (65 matched lines × 2 locations) packages/decap-cms-core/src/actions/editorialWorkflow.ts:335 — packages/decap-cms-core/src/actions/editorialWorkflow.ts:335 · packages/decap-cms-core/src/actions/entries.ts:961 — the two spans are one implementation copied and then locally edited — 310 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 (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 (48 lines × 2 locations) · ×1

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:14 — 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 (45 lines × 3 locations) · ×1

Duplicated block (45 lines × 3 locations) packages/decap-cms-backend-forgejo/src/implementation.tsx:525 — packages/decap-cms-backend-forgejo/src/implementation.tsx:525 · 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.

R10 · Code Duplication · Duplicated block (43 lines × 2 locations) · ×1

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.

R10 · Code Duplication · Duplicated block (42 lines × 2 locations) · ×1

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) packages/decap-cms-widget-markdown/src/serializers/remarkShortcodes.js:28 — packages/decap-cms-widget-markdown/src/serializers/remarkShortcodes.js: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.

R10 · Code Duplication · Duplicated block (36 lines × 2 locations) · ×1

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.

R10 · Code Duplication · Duplicated block (35 lines × 2 locations) · ×1

Duplicated block (35 lines × 2 locations) packages/decap-cms-core/src/actions/entries.ts:244 — packages/decap-cms-core/src/actions/entries.ts:244 · packages/decap-cms-core/src/actions/entries.ts:283 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.

R10 · Code Duplication · Duplicated block with local edits (35 matched lines × 2 locations) · ×1

Duplicated block with local edits (35 matched lines × 2 locations) REDACTED:45 — REDACTED:45 · scripts/verify-published-packages.mjs:36 — the two spans are one implementation copied and then locally edited — 249 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 (28 lines × 3 locations) · ×1

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.

R10 · Code Duplication · Duplicated block (26 lines × 2 locations) · ×1

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.

R10 · Code Duplication · Duplicated block (25 lines × 2 locations) · ×1

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.

R10 · Code Duplication · Duplicated block (22 lines × 3 locations) · ×1

Duplicated block (22 lines × 3 locations) packages/decap-cms-core/src/actions/entries.ts:211 — packages/decap-cms-core/src/actions/entries.ts:211 · packages/decap-cms-core/src/actions/entries.ts:253 · packages/decap-cms-core/src/actions/entries.ts:292 — all 3 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.

R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 40, cognitive 69) · ×1

Complex function (anonymous) (cyclomatic 40, cognitive 69) packages/decap-cms-core/src/actions/config.ts:232 — (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.

R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 31, cognitive 23) · ×1

Complex function (anonymous) (cyclomatic 31, cognitive 23) packages/decap-server/src/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.

R2 · Cyclomatic Complexity · Complex function entryDraftReducer (cyclomatic 31, cognitive 4) · ×1

Complex function entryDraftReducer (cyclomatic 31, cognitive 4) packages/decap-cms-core/src/reducers/entryDraft.js:72 — entryDraftReducer has cyclomatic complexity 31 and cognitive complexity 4; 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 mediaLibrary (cyclomatic 30, cognitive 24) · ×1

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.

R2 · Cyclomatic Complexity · Complex function convertNode (cyclomatic 28, cognitive 11) · ×1

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 convertNode (cyclomatic 26, cognitive 9) · ×1

Complex function convertNode (cyclomatic 26, cognitive 9) packages/decap-cms-widget-richtext/src/serializers/remarkSlate.js:229 — 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.

R2 · Cyclomatic Complexity · Complex function convertBlockNode (cyclomatic 26, cognitive 9) · ×1

Complex function convertBlockNode (cyclomatic 26, cognitive 9) packages/decap-cms-widget-richtext/src/serializers/slateRemark.js:322 — 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.

R2 · Cyclomatic Complexity · Complex function convertBlockNode (cyclomatic 25, cognitive 9) · ×1

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.

R2 · Cyclomatic Complexity · Complex function renderWorkflowControls (cyclomatic 22, cognitive 18) · ×1

Complex function renderWorkflowControls (cyclomatic 22, cognitive 18) packages/decap-cms-core/src/components/Editor/EditorToolbar.js:599 — 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.

R2 · Cyclomatic Complexity · Complex function Element (cyclomatic 22, cognitive 4) · ×1

Complex function Element (cyclomatic 22, cognitive 4) packages/decap-cms-widget-markdown/src/MarkdownControl/renderers.js:298 — Element has cyclomatic complexity 22 and cognitive complexity 4; 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 persistEntry (cyclomatic 21, cognitive 25) · ×1

Complex function persistEntry (cyclomatic 21, cognitive 25) packages/decap-cms-core/src/backend.ts:1246 — 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.

R2 · Cyclomatic Complexity · Complex function MediaLibraryModal (cyclomatic 20, cognitive 18) · ×1

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.

R2 · Cyclomatic Complexity · Complex function unpublishedEntries (cyclomatic 20, cognitive 4) · ×1

Complex function unpublishedEntries (cyclomatic 20, cognitive 4) packages/decap-cms-core/src/reducers/editorialWorkflow.ts:27 — unpublishedEntries has cyclomatic complexity 20 and cognitive complexity 4; 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 constructor (cyclomatic 18, cognitive 19) · ×1

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.

R2 · Cyclomatic Complexity · Complex function constructor (cyclomatic 18, cognitive 17) · ×1

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.

R2 · Cyclomatic Complexity · Complex function render (cyclomatic 17, cognitive 16) · ×1

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.

R2 · Cyclomatic Complexity · Complex function deserialize (cyclomatic 16, cognitive 19) · ×1

Complex function deserialize (cyclomatic 16, cognitive 19) packages/decap-cms-widget-markdown/src/MarkdownControl/plugins/html/withHtml.js:75 — 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.

R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 16, cognitive 16) · ×1

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.

R2 · Cyclomatic Complexity · Complex function constructor (cyclomatic 16, cognitive 15) · ×1

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.

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 — This repository declares test tooling, and the ✓ above records that declaration — but cypress/run.mjs and 2 other test file(s) in this workspace 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.

R7 · Dead Code · Dead file (~84 LoC) · ×1

Dead file (~84 LoC) functions/publish.js — no import path from any entry point (123 application, 65 tooling, 206 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

R7 · Dead Code · Dead file (~83 LoC) · ×1

Dead file (~83 LoC) packages/decap-cms-backend-aws-cognito-github-proxy/src/AuthenticationPage.js — no import path from any entry point (123 application, 65 tooling, 206 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

R7 · Dead Code · Dead file (~18 LoC) · ×1

Dead file (~18 LoC) setupTestFramework.js — no import path from any entry point (123 application, 65 tooling, 206 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

R7 · Dead Code · Dead file (~15 LoC) · ×1

Dead file (~15 LoC) scripts/cache.js — no import path from any entry point (123 application, 65 tooling, 206 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

R7 · Dead Code · Dead file (~7 LoC) · ×1

Dead file (~7 LoC) jest.resolver.js — no import path from any entry point (123 application, 65 tooling, 206 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

R8 · Dependency Hygiene · Unlisted import 'unified' · ×1

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.

R8 · Dependency Hygiene · Unused dependency 'all-contributors-cli' · ×1

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.

R8 · Dependency Hygiene · Unused dependency 'axios' · ×1

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.

R8 · Dependency Hygiene · Unused dependency 'browserify' · ×1

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.

Minor — 183 finding(s)

D10 · Test Quality · No direct assertions · ×132

No direct assertions: successfully loads cypress/e2e/simple_workflow_spec_test_backend.js:42 — No conventional assertion call was detected, and 132 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 a new entry cypress/e2e/simple_workflow_spec_test_backend.js:57 — No conventional assertion call was detected, and 132 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 a new entry and create new cypress/e2e/simple_workflow_spec_test_backend.js:63 — No conventional assertion call was detected, and 132 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 a new entry and duplicate cypress/e2e/simple_workflow_spec_test_backend.js:69 — No conventional assertion call was detected, and 132 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 edit an existing entry and publish cypress/e2e/simple_workflow_spec_test_backend.js:75 — No conventional assertion call was detected, and 132 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 edit an existing entry, publish and create new cypress/e2e/simple_workflow_spec_test_backend.js:83 — No conventional assertion call was detected, and 132 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 edit an existing entry, publish and duplicate cypress/e2e/simple_workflow_spec_test_backend.js:91 — No conventional assertion call was detected, and 132 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 duplicate an existing entry cypress/e2e/simple_workflow_spec_test_backend.js:99 — No conventional assertion call was detected, and 132 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 combine code mark with other marks cypress/e2e/richtext_widget_marks_spec.js:21 — No conventional assertion call was detected, and 132 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 add a new valid link cypress/e2e/richtext_widget_link_spec.js:20 — No conventional assertion call was detected, and 132 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 add a new invalid link cypress/e2e/richtext_widget_link_spec.js:35 — No conventional assertion call was detected, and 132 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 select existing text as link cypress/e2e/richtext_widget_link_spec.js:50 — No conventional assertion call was detected, and 132 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/richtext_widget_hotkeys_spec.js:30 — No conventional assertion call was detected, and 132 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/richtext_widget_hotkeys_spec.js:43 — No conventional assertion call was detected, and 132 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+shift+s displays a strike through the text cypress/e2e/richtext_widget_hotkeys_spec.js:56 — No conventional assertion call was detected, and 132 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+shift+c displays a code block around the text cypress/e2e/richtext_widget_hotkeys_spec.js:68 — No conventional assertion call was detected, and 132 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+k transforms the text to a link cypress/e2e/richtext_widget_hotkeys_spec.js:83 — No conventional assertion call was detected, and 132 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} transforms the text to a heading cypress/e2e/richtext_widget_hotkeys_spec.js:98 — No conventional assertion call was detected, and 132 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/richtext_widget_enter_spec.js:20 — No conventional assertion call was detected, and 132 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/richtext_widget_enter_spec.js:28 — No conventional assertion call was detected, and 132 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/richtext_widget_enter_spec.js:37 — No conventional assertion call was detected, and 132 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/richtext_widget_enter_spec.js:47 — No conventional assertion call was detected, and 132 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/richtext_widget_enter_spec.js:56 — No conventional assertion call was detected, and 132 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/richtext_widget_enter_spec.js:67 — No conventional assertion call was detected, and 132 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/richtext_widget_enter_spec.js:77 — No conventional assertion call was detected, and 132 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.
+ 107 more in this group — see findings.md.

X10 · Duplicated predicate · Duplicated predicate · ×11

Duplicated predicate packages/decap-cms-widget-relation/src/RelationControl.js:491 — `!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/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:266 — `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-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-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-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/MarkdownPreview.js:32 — `node.nodeName === 'IMG' && data.attrName === 'src' && isSameOriginBlobUrl(data.attrValue)` appears character-identically in 2 files — packages/decap-cms-widget-markdown/src/MarkdownPreview.js, 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-widget-markdown/src/serializers/remarkPaddedLinks.js:59 — `startsWith(text, ' ') && getEdgeTextChild(node)` 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/remarkPaddedLinks.js:84 — `trailingWhitespaceNode && u('text', ' ')` 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.

D30 · Dependency Vulnerabilities · Low CVE · ×9

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D16 · Bus Factor · Off-boarding risk · ×1

Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 3 significant file(s) lose their only recent owner: packages/decap-cms-backend-git-gateway/src/netlify-lfs-client.ts, packages/decap-cms-lib-auth/src/netlify-auth.js, packages/decap-cms-backend-bitbucket/src/git-lfs-client.ts. Pair on, review, or document these before any departure.

D16 · Bus Factor · Further sole-owners (lower concentration) · ×1

Further sole-owners (lower concentration) — 8 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 (13 single-owned of 200 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated and example/demo trees and test files identified by path convention, largest first; 200 of the 528 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)) (+2 more) — spread or document their files in the same way, at lower priority than the named off-boarding risks above.

D19 · Documentation Quality · Documentation · ×1

Documentation: no installation or build instructions packages/decap-cms-widget-code/README.md — There are no installation or build instructions for decap-cms-widget-code. Add a short install line (npm install) and any prerequisites, then a quick run command.

D20 · ADR Quality · No ADRs found · ×1

No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.

D26 · Project Cohesion · Split packages/decap-cms-core · ×1

Split packages/decap-cms-core — A 20k-LoC CMS core with 24 unrelated namespaces is a sprawling grab-bag. Suggested:

D28 · Secrets (history) · Rotate the exposed credentials · ×1

REDACTED

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

D30 · Dependency Vulnerabilities · Low vulnerability · ×1

REDACTED

D34 · Knowledge Freshness · Further orphaned files (smaller) · ×1

Further orphaned files (smaller) — 83 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 75 more) (87 orphaned of 200 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated and example/demo trees and test files identified by path convention, largest first; 200 of the 528 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.

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

M2 · Architecture documentation · No ADRs · ×1

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.

P3 · Security & performance tooling · No SAST · ×1

No SAST — 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 10919 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.

R7 · Dead Code · Unused export 'treeEntry' · ×1

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:1298 — 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:1449 — 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.

R7 · Dead Code · Unused export 'getFormatter' · ×1

Unused export 'getFormatter' packages/decap-cms-core/src/lib/registry.js:313 — 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:51 — Nothing imports THIS copy of 'selectEntries' — but packages/decap-cms-core/src/reducers/entries.ts: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 packages/decap-cms-core/src/reducers/entries.ts's, or, if this one is meant to be the survivor, repoint the importers before removing the other.

R7 · Dead Code · Unused export 'endpointConstants' · ×1

Unused export 'endpointConstants' packages/decap-cms-lib-util/src/API.ts:155 — 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.

R7 · Dead Code · Unused export 'default' · ×1

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.

S1 · Web-Security Posture · No security response headers detected · ×1

No security response headers detected netlify.toml:1 — No Content-Security-Policy / X-Frame-Options / X-Content-Type-Options configuration found — 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.)

X7 · Silent fallback defaults · Silent fallback default in catch · ×1

Silent fallback default in catch packages/decap-server/src/middlewares/utils/fs.ts:22 — `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.

Minor — 82 finding(s)

D12 · Dependency Hygiene · Outdated (npm) · ×82

Outdated (npm): @dnd-kit/modifiers — @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 — @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 — @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 — @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 — @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): @reduxjs/toolkit — @reduxjs/toolkit is pinned at 1.9.7; registry.npmjs.org publishes 2.13.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): ajv — ajv is pinned at 8.17.1; registry.npmjs.org publishes 8.20.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): clean-stack — clean-stack is pinned at 5.2.0; 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): 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.13; registry.npmjs.org publishes 3.4.16 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 10.0.0; registry.npmjs.org publishes 18.0.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): 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.21.2; 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): globby — 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): 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.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): 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.1.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): immutable — immutable is pinned at 4.3.9; registry.npmjs.org publishes 5.1.9 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.
+ 57 more in this group — see findings.md.

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.

Dimension	Tool	Version	Command	Findings	Raw output
D28 · Secrets (history)	gitleaks	—	gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-6e3351f1d668493aabbe487460889507/history.json --exit-code 0 --source .	5	artifacts/raw/gitleaks-history.json
D28 · Secrets (history)	gitleaks	—	gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-6e3351f1d668493aabbe487460889507/tree.json --exit-code 0 --source .	0	artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)	semgrep	—	semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off .	48	artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilities	trivy	—	trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs /bin/ --skip-dirs /obj/ . --skip-db-update	94	artifacts/raw/trivy-fs.json
D31 · IaC & Container Security	trivy	—	trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.	0	—
D32 · Data Compliance (PII/GDPR)	semgrep	—	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.	0	—
D40 · Network Egress Confinement	runtime-hardening	—	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.	0	—
D41 · Kernel & Syscall Confinement	runtime-hardening	—	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.	0	—
D42 · Runtime Threat Enforcement	runtime-hardening	—	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.	0	—
D43 · Malicious Dependencies	trivy	—	trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs /bin/ --skip-dirs /obj/ . --skip-db-update	0	artifacts/raw/trivy-fs.json

Run 01a0f8e4-25e6-7a29-949e-a76661745970 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Decaporg/decap-Cms

Findings by grade

This survey was produced by

Executive summary

Top priorities

Diagnosis — what's actually going on

Architecture — module dependency graph

Architecture — module dependency matrix

At a glance — Code Health · 59% · Adequate · gated by D3, R1 ·

At a glance — Architecture · 59% · Adequate · gated by R9 ·

At a glance — Maturity · 68% · Adequate · gated by M2 ·

At a glance — Readiness · 60% · Adequate · gated by R8, P3 ·

At a glance — Security · 67% · Adequate · gated by D29, D30, D36 ·

At a glance — Performance · 100% · Exemplary ·

Security & Compliance — OWASP Top-10 mapping

Roadmap

File quality

How the grades work

Methodology & how to trust this report

Tools & methods

Run transparency — what happened this run

Limitations & what we did not check

Per-dimension blind spots

The LLM boundary

Dimensions

Frontend & cross-cutting dimensions

Reference — by lens

Appendix A — Findings (grouped)

Appendix B — Reproduction & audit trail

Downloadable artifacts