Public report of NeuCharFramework/NCF, published 8 November 2026. It has the same score, grades and number of findings as the full report. The details of security findings (where they are in the code, which known vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive report Measured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.2). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey → Signed and filed in the standard's public register, 8 November 2026, 01:06 UTC · Survey ID cd_a203d2f2bd1240c9ab863ed2ad79b9e4

NeuCharFramework/NCF

Measured 8 November 2026, 01:02 UTC, at code version ca79b3f

CAI score 34out of 100 Weak
CriticalWeakAdequateStrongExemplary
Up 3 since the last survey

The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.

A large codebase: 105,103 lines of product code in 14 projects, tests not counted · Estimated rebuild effort: about 1.8 person-years · Weakest lens: Accessibility, 30

Findings by how serious they are

445 critical 593 serious 157 minor

7 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.

This survey was produced by

Assert small markCanine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
8 November 2026, 01:02 UTC

A measurement, not a certificate. The Code Assurance Index records a number together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that implements it, and today the Canine Code Analyzer is the only one that does.

The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸

104of 104 dimensions measured by tools.
1174of 1195 findings point to an exact file and line, so you can open each one in the code. The other 21 concern the repository as a whole, such as missing documentation.
104dimensions across 9 lenses, read from 105,103 lines of product code in 14 projects.
Chapters

Executive summary

NeuCharFramework/NCF falls short of our standard for a template or a sample, in part because it has controls that only work with a mouse. It scores 34 out of 100 and is rated Weak, and 300 of its 445 critical findings are security problems.

Accessibility, at 30, is the weakest lens and counts most in the score. The best first step is handling the discarded errors, worth about 2 points. Making the controls keyboard-usable would lift Accessibility itself, also worth about 2. Raising Accessibility to 58 would lift the score to about 37.

227 known security holes in the packages the code depends on can be used by attackers. Thirty-six passwords or keys in the code and 29 in the code's history are open to anyone who can read the repository, and twenty-five controls can't be used without a mouse. Making the controls work with a keyboard, updating the vulnerable packages and replacing each exposed password or key would close these risks. The eight unsafe settings in infrastructure or container files need changing to safe values. The 40 pieces of business logic tied to the database or web code need separating from the database and web code.

The product code is 105,103 lines, about €260,000 to rebuild.

A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.

How the score is built: what each lens counts for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Accessibility 30 · counts for 45%Code Health 32 · counts for 25%Production Readiness 35 · counts for 14%Security and Compliance 36 · counts for 8%Domain Modelling 41 · counts for 4%Performance 71 · counts for 2%Architecture 80 · counts for 1%Maturity 90 · counts for 1%Event-Driven 100 · counts for 0%

If Accessibility rose from 30 to 58, the lowest score rated Strong, the score would rise from 34 to about 37.

Code composition: what the lines of code are
Business logic 10%Supporting code 27%Tests 24%Generated by tools 39%
New since the last survey: 222 findings

These 222 critical or serious findings weren't in the previous survey, on 21 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.

We compare every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.

Fixed since the last survey: 856 findings

These 856 critical or serious findings were in the previous survey, on 21 October 2026, and are gone from this one. The first 100 are listed here.

  • Static Analysis (SAST) · Medium: watchdog-open-redirect-csharp REDACTED
  • Static Analysis (SAST) · Medium: watchdog-open-redirect-csharp REDACTED
  • Dependency Vulnerabilities · Critical CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High vulnerability: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High vulnerability: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High vulnerability: REDACTED REDACTED
  • Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
  • Platform End-of-Life · End-of-life runtime: .NET net9.0 src/back-end/testapphost/testapphost.csproj
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/layout/components/Navbar.vue
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/views/dashboard/admin/components/LineChart.vue
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/operation/application.vue
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/views/dashboard/admin/components/TodoList/index.vue
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/components/UploadExcel/index.vue
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/components/MarkdownEditor/index.vue
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/mock/article.js
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/views/dashboard/admin/components/RaddarChart.vue
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/router/index.js
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/components/DndList/index.vue
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/layout/components/Sidebar/SidebarItem.vue
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/components/Tinymce/components/EditorImage.vue
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/mock/role/index.js
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/views/dashboard/admin/components/BarChart.vue
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/permission.js
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/layout/components/Sidebar/index.vue
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/components/Pagination/index.vue
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/components/Sticky/index.vue
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/directive/sticky.js
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/api/admin.js
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/components/Upload/SingleImage3.vue
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/views/module/home.vue
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/mock/user.js
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/layout/components/Settings/index.vue
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/components/BackToTop/index.vue
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/mock/mock-server.js
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/views/dashboard/admin/components/TodoList/Todo.vue
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/views/dashboard/admin/components/PieChart.vue
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/components/Upload/SingleImage.vue
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/directive/el-drag-dialog/drag.js
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/components/RightPanel/index.vue
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/components/Upload/SingleImage2.vue
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/layout/components/TagsView/ScrollPane.vue
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/api/module.js
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/lightdemo/antvShow.vue
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.AdminModule/src/views/XncfStore/lightdemo/antvShow.vue
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/views/Senparc.Xncf.XncfStore/processdemo/antvShow.vue
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/directive/waves/waves.js
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/filters/index.js
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/utils/request.js
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/components/ErrorLog/index.vue
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/components/Breadcrumb/index.vue
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/main.js
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/api/menu.js
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/operation/subscribed.vue
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/plop-templates/store/prompt.js
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/layout/index.vue
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/views/dashboard/admin/components/BoxCard.vue
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/mock/index.js
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/api/roles.js
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/components/Tinymce/dynamicLoadScript.js
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/utils/scroll-to.js
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/views/error-page/401.vue
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/store/modules/app.js
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/components/Charts/mixins/resize.js
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/components/SizeSelect/index.vue
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/plop-templates/component/prompt.js
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/plop-templates/view/prompt.js
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/views/dashboard/admin/components/mixins/resize.js
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/components/JsonEditor/index.vue
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/components/Kanban/index.vue
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/mock/remote-search.js
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/directive/clipboard/clipboard.js
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/mock/utils.js
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/components/DragSelect/index.vue
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/components/Screenfull/index.vue
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/utils/auth.js
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/layout/mixin/ResizeHandler.js
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/layout/components/Sidebar/Link.vue
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/directive/el-table/adaptive.js
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/utils/pdf.js
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/views/dashboard/editor/index.vue
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/components/ImageCropper/utils/effectRipple.js
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/components/Share/DropdownMenu.vue
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/api/multiTenancyUser.js
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/layout/components/Sidebar/Item.vue
  • Test Coverage · No test reaches this file src/front-end/Senparc.Xncf.Admin/src/layout/components/Sidebar/Logo.vue
Rebuild cost: about €260,000 · Estimate
Cost to rebuild€86,000 to €440,000, for 1,438 to 4,591 hours of work, about 1.8 person-years for 1 to 4 engineers
Difficulty of the problemVery high, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.7 at a score of 34. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
SizeLarge: 105,103 lines of product code
What it is notNot a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.

How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty.

Top priorities

The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.

1
Resolve the 2 EmptyCatchBlock finding(s) in Explicit Debt — start with SenparcTraceHelper.cs, AdminChatStreamController.cs.
Raises the score by about 2 points · Low effort · Explicit Debt
2
Resolve the 5 NoWarnInCsproj finding(s) in Explicit Debt — start with Directory.Build.props (4), REDACTED.
Raises the score by about 2 points · Low effort · Explicit Debt
3
Resolve the 9 WriteOnlyPrivateField finding(s) in Explicit Debt — start with REDACTED (2), JeffreyMpMessageHandler.cs (2), AuthorizationPage.cshtml.cs.
Raises the score by about 2 points · Low effort · Explicit Debt

Diagnosis: what the measurements show together

Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.

Where the investment is most exposed · Value at risk
This code would cost about €260,000 to build again, about 1.8 person-years of work. Its weakest lens is Accessibility, at 30 (Weak). Accessibility is about whether the interface is built so that everyone can use it, including people who can't see the screen or can't use a mouse. Because the weakest lens counts most in the score, work on Accessibility also moves the score most.
Based on: the rebuild estimate · the Accessibility grade · how much each lens counts
What to do: Start with the Accessibility actions in Top priorities.
One cause behind 29 Domain Modelling findings · Common cause
29 findings in the Domain Modelling lens come from the same cause. The code models the business as objects, such as an order or a customer, and each object should guard its own rules: an order, for example, should refuse to be shipped before it has been paid. Here the objects don't do that. Other code can change an object's data directly, so it can put an order into a state the rules forbid. Some objects only hold data, while the rules that should keep that data valid sit elsewhere in the code. Identifiers, such as order numbers and customer numbers, are passed around as plain numbers or text, so nothing stops the code from using one kind where another belongs. Because all of these findings have the same cause, fixing it once, in the business objects themselves, deals with them together.
Based on: Encapsulated state (3 findings) · Rich vs anemic model (5 findings) · Strongly-typed ids (21 findings)
What to do: Give each business object the methods that enforce its rules, such as a method for shipping an order that first checks it has been paid, and let only those methods change its data. Give each kind of identifier a type of its own, so an order number can't be used where a customer number belongs.
If you do one thing first · First action
Resolve the 2 EmptyCatchBlock finding(s) in Explicit Debt. Of all the actions in this report, it raises the score most for the work it takes: about 2 points for low effort, because it clears the 2 Explicit Debt findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort

Architecture — module dependency graph

Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.

arch AutoUpgrade AutoUpgrade GenerateDbMigration GenerateDbMigration NCF.Template Template Senparc.Areas.Admin Admin Senparc.Aspire.AppHost AppHost Senparc.Web Web Senparc.Aspire.AppHost->Senparc.Web Senparc.Xncf.Accounts Accounts Senparc.Aspire.AppHost->Senparc.Xncf.Accounts Senparc.Xncf.Installer Installer Senparc.Aspire.AppHost->Senparc.Xncf.Installer Senparc.Aspire.ServiceDefaults ServiceDefaults Senparc.Web->Senparc.Areas.Admin Senparc.Web->Senparc.Xncf.Installer Senparc.Web.DatabasePlant DatabasePlant Senparc.Web.DatabasePlant->Senparc.Areas.Admin Senparc.Xncf.Accounts->Senparc.Aspire.ServiceDefaults Senparc.Xncf.Installer->Senparc.Areas.Admin Senparc.Xncf.Installer->Senparc.Aspire.ServiceDefaults Senparc.Xncf.Installer.Interface Interface Senparc.Xncf.Installer->Senparc.Xncf.Installer.Interface testapphost testapphost

Architecture: which parts of the code depend on which

The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.

87 modules, with 57 dependencies between them. One loop runs through 2 of the modules, marked above the diagonal.

The table shows the 40 modules with the most connections; 47 more are left out to keep it readable.

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 (global)2 Senparc.Areas.Admin.ACL3 Senparc.Areas.Admin.ACL.Repository4 Senparc.Areas.Admin.Domain.Dto5 Senparc.Areas.Admin.Domain.Models.DatabaseModel6 Senparc.Areas.Admin.Domain.Models.Dto7 Senparc.Areas.Admin.Domain.Models.VD8 Senparc.Areas.Admin.OHS.PL9 Senparc.Areas.Admin.SenparcTraceManager10 Senparc.Service.ACL11 Senparc.Web12 Senparc.Web.Models.VD13 Senparc.Xncf.Accounts.Domain14 Senparc.Xncf.Accounts.Domain.Models15 Senparc.Xncf.Installer16 Senparc.Xncf.Installer.Domain.Dto17 Senparc.Areas.Admin18 Senparc.Areas.Admin.Domain.Models19 Senparc.Areas.Admin.Domain.Models.DatabaseModel.Dto20 Senparc.Areas.Admin.Domain.Services21 Senparc.Areas.Admin.Domain.Services.AIPlugins22 Senparc.Areas.Admin.OHS.Local.PL23 Senparc.Service24 Senparc.Web.Pages25 Senparc.Xncf.Accounts.Domain.Cache26 Senparc.Xncf.Accounts.Domain.OperationQueue27 Senparc.Xncf.Accounts.Domain.Services28 Senparc.Xncf.Accounts.Models29 Senparc.Xncf.Installer.Domain.Services30 Senparc.Areas.Admin.Areas.Admin31 Senparc.Areas.Admin.Areas.Admin.Pages.NeuCharPivot32 Senparc.Areas.Admin.Domain33 Senparc.Areas.Admin.Models34 Senparc.Areas.Admin.OHS.Local.Controllers35 Senparc.Areas.Admin.Pages36 Senparc.Areas.Admin.Pages.AdminChat37 Senparc.Xncf.Installer.OHS.Local.AppService38 Senparc.Areas.Admin.Areas.Admin.Pages39 Senparc.Xncf.Instraller.Pages40 Senparc.Areas.Admin.OHS.Local.AppService
1 (global)
2 Senparc.Areas.Admin.ACL
3 Senparc.Areas.Admin.ACL.Repository
4 Senparc.Areas.Admin.Domain.Dto
5 Senparc.Areas.Admin.Domain.Models.DatabaseModel
6 Senparc.Areas.Admin.Domain.Models.Dto
7 Senparc.Areas.Admin.Domain.Models.VD
8 Senparc.Areas.Admin.OHS.PL
9 Senparc.Areas.Admin.SenparcTraceManager
10 Senparc.Service.ACL
11 Senparc.Web
12 Senparc.Web.Models.VD
13 Senparc.Xncf.Accounts.Domain
14 Senparc.Xncf.Accounts.Domain.Models
15 Senparc.Xncf.Installer
16 Senparc.Xncf.Installer.Domain.Dto
17 Senparc.Areas.Admin1
18 Senparc.Areas.Admin.Domain.Models9
19 Senparc.Areas.Admin.Domain.Models.DatabaseModel.Dto7
20 Senparc.Areas.Admin.Domain.Services921312
21 Senparc.Areas.Admin.Domain.Services.AIPlugins1
22 Senparc.Areas.Admin.OHS.Local.PL3
23 Senparc.Service112
24 Senparc.Web.Pages13
25 Senparc.Xncf.Accounts.Domain.Cache2
26 Senparc.Xncf.Accounts.Domain.OperationQueue1
27 Senparc.Xncf.Accounts.Domain.Services224
28 Senparc.Xncf.Accounts.Models3
29 Senparc.Xncf.Installer.Domain.Services4
30 Senparc.Areas.Admin.Areas.Admin1
31 Senparc.Areas.Admin.Areas.Admin.Pages.NeuCharPivot15
32 Senparc.Areas.Admin.Domain1211
33 Senparc.Areas.Admin.Models1
34 Senparc.Areas.Admin.OHS.Local.Controllers116
35 Senparc.Areas.Admin.Pages1
36 Senparc.Areas.Admin.Pages.AdminChat11
37 Senparc.Xncf.Installer.OHS.Local.AppService31
38 Senparc.Areas.Admin.Areas.Admin.Pages2119185
39 Senparc.Xncf.Instraller.Pages1211
40 Senparc.Areas.Admin.OHS.Local.AppService221539102211
Uses a module listed above itPart of a loopThe module itself
1 (global)2 Senparc.Areas.Admin.ACL3 Senparc.Areas.Admin.ACL.Repository4 Senparc.Areas.Admin.Domain.Dto5 Senparc.Areas.Admin.Domain.Models.DatabaseModel6 Senparc.Areas.Admin.Domain.Models.Dto7 Senparc.Areas.Admin.Domain.Models.VD8 Senparc.Areas.Admin.OHS.PL9 Senparc.Areas.Admin.SenparcTraceManager10 Senparc.Service.ACL11 Senparc.Web12 Senparc.Web.Models.VD13 Senparc.Xncf.Accounts.Domain14 Senparc.Xncf.Accounts.Domain.Models15 Senparc.Xncf.Installer16 Senparc.Xncf.Installer.Domain.Dto17 Senparc.Areas.Admin18 Senparc.Areas.Admin.Domain.Models19 Senparc.Areas.Admin.Domain.Models.DatabaseModel.Dto20 Senparc.Areas.Admin.Domain.Services21 Senparc.Areas.Admin.Domain.Services.AIPlugins22 Senparc.Areas.Admin.OHS.Local.PL23 Senparc.Service24 Senparc.Web.Pages25 Senparc.Xncf.Accounts.Domain.Cache26 Senparc.Xncf.Accounts.Domain.OperationQueue27 Senparc.Xncf.Accounts.Domain.Services28 Senparc.Xncf.Accounts.Models29 Senparc.Xncf.Installer.Domain.Services30 Senparc.Areas.Admin.Areas.Admin31 Senparc.Areas.Admin.Areas.Admin.Pages.NeuCharPivot32 Senparc.Areas.Admin.Domain33 Senparc.Areas.Admin.Models34 Senparc.Areas.Admin.OHS.Local.Controllers35 Senparc.Areas.Admin.Pages36 Senparc.Areas.Admin.Pages.AdminChat37 Senparc.Xncf.Installer.OHS.Local.AppService38 Senparc.Areas.Admin.Areas.Admin.Pages39 Senparc.Xncf.Instraller.Pages40 Senparc.Areas.Admin.OHS.Local.AppService(global)1Senparc.Areas.Admin.ACL2Senparc.Areas.Admin.ACL.Repository3Senparc.Areas.Admin.Domain.Dto4Senparc.Areas.Admin.Domain.Models.DatabaseModel5Senparc.Areas.Admin.Domain.Models.Dto6Senparc.Areas.Admin.Domain.Models.VD7Senparc.Areas.Admin.OHS.PL8Senparc.Areas.Admin.SenparcTraceManager9Senparc.Service.ACL10Senparc.Web11Senparc.Web.Models.VD12Senparc.Xncf.Accounts.Domain13Senparc.Xncf.Accounts.Domain.Models14Senparc.Xncf.Installer15Senparc.Xncf.Installer.Domain.Dto16Senparc.Areas.Admin17Senparc.Areas.Admin.Domain.Models18Senparc.Areas.Admin.Domain.Models.DatabaseModel.Dto19Senparc.Areas.Admin.Domain.Services20Senparc.Areas.Admin.Domain.Services.AIPlugins21Senparc.Areas.Admin.OHS.Local.PL22Senparc.Service23Senparc.Web.Pages24Senparc.Xncf.Accounts.Domain.Cache25Senparc.Xncf.Accounts.Domain.OperationQueue26Senparc.Xncf.Accounts.Domain.Services27Senparc.Xncf.Accounts.Models28Senparc.Xncf.Installer.Domain.Services29Senparc.Areas.Admin.Areas.Admin30Senparc.Areas.Admin.Areas.Admin.Pages.NeuCharPivot31Senparc.Areas.Admin.Domain32Senparc.Areas.Admin.Models33Senparc.Areas.Admin.OHS.Local.Controllers34Senparc.Areas.Admin.Pages35Senparc.Areas.Admin.Pages.AdminChat36Senparc.Xncf.Installer.OHS.Local.AppService37Senparc.Areas.Admin.Areas.Admin.Pages38Senparc.Xncf.Instraller.Pages39Senparc.Areas.Admin.OHS.Local.AppService4019792131213112132122434115121111161113121191851211221539102211+47 more modules (most-connected shown)

At a glance — Code Health · 32% · Weak · gated by D17, R1, R7 ·

At a glance — Architecture · 80% · Adequate · gated by AX2 ·

At a glance — Maturity · 90% · Exemplary ·

At a glance — Readiness · 35% · Adequate · gated by D13, R4, R8 ·

At a glance — Security · 36% · Weak · gated by D28, D29 ·

At a glance — Domain Modelling · 41% · Adequate · gated by DM2, DM6, DM7 ·

At a glance — Event-Driven · 100% · Exemplary ·

At a glance — Accessibility · 30% · Weak · gated by AC4, AC6 ·

At a glance — Performance · 71% · Strong ·

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 categoryFindingsSeverity
A03:2025 — Software Supply Chain Failures335High / Critical
A07:2025 — Authentication Failures66High / Critical
A05:2025 — Injection40Medium
A02:2025 — Security Misconfiguration24High / Critical
A08:2025 — Software or Data Integrity Failures1Medium

Roadmap

Top priorities: Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href; Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1; Resolve the 36 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (22), REDACTED (12), REDACTED.

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

Do thisHelpsEffortDimension
Resolve the 2 EmptyCatchBlock finding(s) in Explicit Debt — start with SenparcTraceHelper.cs, AdminChatStreamController.cs.+1.8 ptsLowExplicit Debt
Resolve the 5 NoWarnInCsproj finding(s) in Explicit Debt — start with Directory.Build.props (4), REDACTED.+1.8 ptsLowExplicit Debt
Resolve the 9 WriteOnlyPrivateField finding(s) in Explicit Debt — start with REDACTED (2), JeffreyMpMessageHandler.cs (2), AuthorizationPage.cshtml.cs.+1.8 ptsLowExplicit Debt
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.+2.2 ptsMediumKeyboard semantics
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.+2.2 ptsMediumVisual & motion safety
Resolve the 36 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (22), REDACTED (12), REDACTED.+2.0 ptsMediumREDACTED Scanning
Resolve the 1 Malicious package finding(s) in Malicious Dependencies — start with REDACTED.+0.8 ptsLowMalicious Dependencies
Enforce accessibility in the toolchain: add eslint-plugin-vuejs-accessibility, then assert with your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) in tests, then gate axe/pa11y/Lighthouse in CI.+1.6 ptsMediumA11y enforcement

File quality

Per-file score 0–10 — a quality signature. Of 104 files carrying findings, judged against the Template bar: 12% slop · 17% mixed · 71% near-clean.

FileScoreBandWorst signal
REDACTED0.0SlopREDACTED Scanning: Leaked secret: REDACTED
REDACTED0.0SlopREDACTED Scanning: Leaked secret: REDACTED
REDACTED0.0SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED0.0SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED0.0SlopDependency Vulnerabilities: High CVE: REDACTED
REDACTED0.1SlopDependency Vulnerabilities: High CVE: REDACTED
REDACTED0.3SlopREDACTED Scanning: Leaked secret: REDACTED
REDACTED0.3SlopREDACTED Scanning: Leaked secret: REDACTED
REDACTED0.3SlopREDACTED Scanning: Leaked secret: REDACTED
REDACTED2.0SlopREDACTED Scanning: Leaked secret: REDACTED
REDACTED2.0SlopREDACTED Scanning: Leaked secret: REDACTED
REDACTED2.0SlopREDACTED Scanning: Leaked secret: REDACTED
src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/XncfModule/Index.cshtml.cs2.7MixedExplicit Debt: WriteOnlyPrivateField
REDACTED3.0MixedIaC & Container Security: High IaC: REDACTED
REDACTED3.4MixedIaC & Container Security: High IaC: REDACTED
REDACTED3.4MixedIaC & Container Security: High IaC: REDACTED
REDACTED3.4MixedIaC & Container Security: High IaC: REDACTED
REDACTED3.7MixedIaC & Container Security: High IaC: REDACTED
REDACTED4.0MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.0MixedStatic Analysis (SAST): Medium: REDACTED

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

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

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

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

Could not be resolved — 7

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

Methodology & how to trust this report

This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 104 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.

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

What we checked — 104 dimensions across the health lenses
D4D5D6D9D10D11D13D14D15D17D18D19D22D24D26D27D28D29D30D31D34D35D39D43D44AC1AC2AC3AC4AC5AC6AC7AX1AX10AX2AX3AX4AX5AX6AX8DM1DM11DM12DM2DM3DM4DM5DM6DM7DM9ED1ED3ED4ED5GD1IC1M1M3P1P10P2P4P6P7P8PF1PF3R1R10R11R2R3R4R5R6R7R8R9S1X1X12X13X14X15X16X17X18X19X2X20X21X22X23X24X25X26X27X28X29X3X30X32X4X5

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
  1. 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, 1174 of 1195 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.)
  2. Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
  3. 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.

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Canine Code Analyzer duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivy · checkovSecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3 · 3.2.533✓ deterministic

Every finding is locatable in findings.md. Run 01a1b8ad-95aa-71fd-ad52-81059876778f.

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.

  • D1 Cyclomatic Complexity — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Most of this repository's production source (.js, .vue) had no cyclomatic complexity computed for it: no method bodies were exposed for those file kinds by any language model this pass could load.
  • D2 Cognitive Complexity — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Most of this repository's production source (.js, .vue) had no cognitive complexity computed for it: no method bodies were exposed for those file kinds by any language model this pass could load.
  • D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the .NET half could not be measured — no coverage produced (collector absent, or test run exceeded the inline budget); the JavaScript/TypeScript half could not be measured — the JavaScript/TypeScript suite(s) run through a browser-driven runner the coverage collector does not drive — src/back-end/Senparc.Web/wwwroot/lib/Chart.js/ (karma) — a gap in the analyzer, not something this repository is missing. This repository's production source spans both ecosystems, and no partial figure is published as if it were the whole: 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.
  • D10 Test Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 101 test(s) behind this row are the ones the C# collector could read, and this repository also carries at least 6 test source file(s) (.js) that it cannot: it parses C# syntax and matches C# test attributes, so a vitest/jest/JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
  • D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: `dotnet list package` exited 1 with no output.
  • D16 Bus Factor — 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. Single-maintainer repository — bus factor is not applicable (24 contributor(s) across 1767 commit(s) sampled, automation and bot accounts excluded). One of them holds 85% of the history; the other 23 hold 0.7% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
  • D17 Explicit Debt — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 126 deducted marker(s) and the 3.3/KLoC density on this row were taken over this repository's .NET projects ALONE: .js (60,629 lines, 59% of production source), .vue (19,658 lines, 19% of production source) went unread, because every marker collector on this path is reached through a C# workspace. D17's marker collectors need a compiler we do not have for that language, so none of its nine marker kinds were read there. The debt in that source is UNMEASURED — its absence from the score above is a gap in this analyzer's language coverage, not a finding that the code carries none.
  • D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
  • D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
  • D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. D24 compares a comment's words with the identifiers, literals and constructs of the code it annotates, using English function-word and rationale lexicons. Comments in another script or language were left unread rather than counted as clean.
  • D28 Secrets (history) — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. D28's config-credential rule (WD-SECRET-0002) parses each committed `.json` config as a document and reads credential-named values; `REDACTED`, `REDACTED`, `src/back-end/Senparc.Xncf.Accounts/swaggerconfig.json`, `REDACTED` did not parse (JSON5, a template, several concatenated documents), so a credential bound there is UNMEASURED by that rule. gitleaks still scanned the same files as text.
  • D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `src/back-end/Senparc.Areas.Admin/ACL/Repository/SysMenuRepository.cs`, `src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/AdminUserInfo/AuthorizationPage.cshtml.cs`, `src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/AdminUserInfo/Edit.cshtml.cs`, `src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/AdminUserInfo/Index.cshtml.cs`, `src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Index.cshtml.cs`, … (+19 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
  • AC2 Forms & labels — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 8 further occurrence(s) are not listed individually; the score already reflects all 48.
  • AC4 Keyboard semantics — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 21 further occurrence(s) are not listed individually; the score already reflects all 61.
  • AC6 Visual & motion safety — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 244 further occurrence(s) are not listed individually; the score already reflects all 284.
  • AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via AspireAppHost (REDACTED). the Aspire AppHost did not expose a crawlable HTTP endpoint in time (or only the dashboard) — no runtime evidence.
  • DM12 Ambient inputs in the domain — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 4 further occurrence(s) are not listed individually; the score already reflects all 44.
  • DM6 Domain ↔ infrastructure boundary — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 348 further occurrence(s) are not listed individually; the score already reflects all 388.
  • DM8 Value-object opportunities — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
  • IC1 Incompleteness & stubs — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 113 further occurrence(s) are not listed individually; the score already reflects all 153.
  • R4 Test Coverage — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 120 further occurrence(s) are not listed individually; the score already reflects all 160.
  • R7 Dead Code — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 65 further occurrence(s) are not listed individually; the score already reflects all 105.
  • X2 Cancellation propagation — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 8 further occurrence(s) are not listed individually; the score already reflects all 48.

Repo exclusion declarations: 10 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.

Limitations & what we did not check

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

Per-dimension blind spots

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

  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • 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.
  • D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
  • 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.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
  • D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
  • D22 Internal API Consistency: API consistency compares the call shapes of members that play the same role on the exposed C# surface: whether the API suits its callers is not measured, and surfaces in other languages are not measured.
  • D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
  • AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
  • AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
  • AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
  • AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
  • AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
  • AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
  • AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
  • 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.
  • DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
  • DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
  • ED5 Idempotency: Idempotency is read from the handler body and one hop below: a mutation is flagged only on structural double-apply evidence (a fresh-identity insert, an accumulation, a growing list, an unkeyed POST/send/charge), so a duplicate effect through a home-grown gateway two hops down, or an insert keyed on the message with no unique constraint, is not flagged but counted as not classified; a guard enforced by a database constraint or a broker's exactly-once delivery is invisible either way. It flags the at-least-once double-apply SHAPE, not a runtime proof of a duplicate effect.
  • 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.

Dimensions

D4 · Code Duplication9.6 / 10Stronggated by 15 serious findings✓ Tool-verified

What it measures: Copy-pasted code that should be shared instead.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.

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

15 duplicated block group(s) detected. Measured on part of this repository only: .js, .vue (78% of production source) was not exposed to THIS dimension's token comparison and is not in this count; duplication there is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream.

Duplicated block (5 lines × 2) · ×3src/back-end/Senparc.Areas.Admin/OHS/Local/AppService/AdminChatAppService.cs:467
Duplicated block (15 lines × 2) · ×2src/back-end/Senparc.Areas.Admin/Domain/Models/VD/BaseVD.cs:43
Duplicated block (7 lines × 2) · ×2src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Session.cshtml.cs:48
Duplicated block (48–50 lines × 2)REDACTED:481
Duplicated block (29–30 lines × 2)src/back-end/Senparc.Areas.Admin/Domain/Services/InstallerService.cs:211

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

What to do

  1. Resolve the 3 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with AdminChatAppService.cs, REDACTED, AdminUserInfoService.cs. — One of this dimension's main actionable groups (3 warning-level).
  2. Resolve the 2 Duplicated block (15 lines × 2) finding(s) in Code Duplication — start with BaseVD.cs, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
  3. Resolve the 2 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with Session.cshtml.cs, AdminUserInfo.cs. — One of this dimension's main actionable groups (2 warning-level).
  4. Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

D5 · Coupling10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.

Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.

Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.

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

14 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).

✓ On the Gold path — maintain.

Detailed fixes: d5_recommendation.md.

D6 · Cohesion (LCOM4)10.0 / 10Exemplary✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 of 45 classes have LCOM4 above 3.

✓ On the Gold path — maintain.

Detailed fixes: d6_recommendation.md.

D9 · Test Distribution9.7 / 10Exemplary✓ 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 9.7 / 10 · rule-coverage 100% · ceiling Documented

124 test methods: 121 unit, 0 integration, 0 BDD, 3 e2e. The JavaScript/TypeScript suite contributes 26 `it`/`test` case(s) across 6 test file(s) declaring at least one beside 98 .NET test method(s); its tier split is read from package names and paths only.

✓ On the Gold path — maintain.

Detailed fixes: d9_recommendation.md.

D10 · Test Quality10.0 / 10Exemplary✓ Tool-verified

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

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

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

0 skipped, 0 zero-assertion, 1 mock references across 101 tests. Measured on the C# suite only — at least 6 test source file(s) (.js) went unread, so its test quality is unmeasured and is not in these counts.

Mock framework: Moq

✓ On the Gold path — maintain.

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

D11 · Test Reliability10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the tests pass reliably, with no flakiness.

Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.

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

0 flaky across 3 measured tier(s). unit: measured (0 flaky); e2e: measured (0 flaky); other: measured (0 flaky).

✓ On the Gold path — maintain.

Detailed fixes: d11_recommendation.md.

D13 · REDACTED Scanning0.0 / 10Critical✓ Tool-verified

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 0.0 / 10 · rule-coverage 100% · ceiling Prevented

12 secret(s) detected.

REDACTED

What to do

  1. Resolve the 36 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (22), REDACTED (12), REDACTED. — One of this dimension's main actionable groups (36 issue-level).
  2. Enforce REDACTED Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

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 305 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 62 direct `PackageReference`(s), and 189 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

D15 · Churn × Complexity Hotspots9.9 / 10Stronggated by 3 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: src/back-end/Senparc.Areas.Admin/Domain/Services/AdminChatAiService.cs (6×27=162); src/back-end/Senparc.Areas.Admin/wwwroot/js/Admin/Pages/XncfModule/start.js (4×31=124); REDACTED (7×17=119)

Hotspot: src/back-end/Senparc.Areas.Admin/Domain/Services/AdminChatAiService.cs · ×3src/back-end/Senparc.Areas.Admin/Domain/Services/AdminChatAiService.cs:115

What to do

  1. Resolve the 3 Hotspot finding(s) in Churn × Complexity Hotspots — start with AdminChatAiService.cs, start.js, REDACTED. — One of this dimension's main actionable groups (3 warning-level).

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

D17 · Explicit Debt3.4 / 10Weak✓ 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 3.4 / 10 · rule-coverage 100% · ceiling Prevented

126 deducted debt markers + 11 dead symbols across 19154 LoC in the .NET projects (3.3/KLoC) → score 3.4. Measured on the .NET source only: .js, .vue (78% of production source) was not read, and carries at least 0 uncounted task marker(s) in 0 file(s).

WriteOnlyPrivateField · ×9src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/AdminUserInfo/AuthorizationPage.cshtml.cs:17
NoWarnInCsproj — 38 warning codes suppressed in one element · ×5src/back-end/Directory.Build.props:5
EmptyCatchBlock · ×2src/back-end/Senparc.Areas.Admin/Domain/SeparcTraceManager/SenparcTraceHelper.cs:448
CommentedOutCode · ×45src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Index.cshtml.cs:109
TodoComment · ×31src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Index.cshtml.cs:39

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

What to do

  1. Resolve the 9 WriteOnlyPrivateField finding(s) in Explicit Debt — start with REDACTED (2), JeffreyMpMessageHandler.cs (2), AuthorizationPage.cshtml.cs. — One of this dimension's main actionable groups (9 issue-level).
  2. Resolve the 5 NoWarnInCsproj finding(s) in Explicit Debt — start with Directory.Build.props (4), REDACTED. — One of this dimension's main actionable groups (5 issue-level).
  3. Resolve the 2 EmptyCatchBlock finding(s) in Explicit Debt — start with SenparcTraceHelper.cs, AdminChatStreamController.cs. — One of this dimension's main actionable groups (2 issue-level).
  4. 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.

D18 · Solution Shape10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the solution is laid out in a sensible, conventional structure.

Method: Solution structure: project count, decomposition, shell-project detection, build success (confirmed failures cap the score); traced to actual .sln files and binaries. Deterministic.

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

14 projects, 436 source files, 21841 hand-written lines of code (19154 production / 2687 test — the split is derived per file: test is what its project, its own path, or a compile-guarded region marks as test, and a file carrying no test signal counts as production), plus 24739 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 8 inter-project edges. Measured across 3 solutions loaded as one workspace: `src/NCF.Template.sln`, `src/back-end/NCF.sln`, `tools/AutoUpgrade/src/AutoUpgrade.sln`.

✓ On the Gold path — maintain.

Detailed fixes: d18_recommendation.md.

D19 · Documentation Quality8.3 / 10Strong✓ Tool-verified

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

Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.

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

1 of 2 documentation facets pass in full; short on: F2 example. 18 document(s) read across 7 unit(s).

Documentation: no build, run or usage examplesrc/front-end/Senparc.Xncf.Admin/readme.md:1

What to do

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

D22 · Internal API Consistency10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether the internal API surface is consistent and coherent.

Method: Call-shape rules (A1-A9) over the structured code model of the intentionally exposed C# surface: members of one type, overloads of one name and the same slot across sibling types are compared, and a member that makes a caller use a different convention for the same kind of operation is flagged. Deterministic, no model. Advisory.

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

0 API inconsistencies among 14 exposed members measured against a convention their peers follow.

✓ On the Gold path — maintain.

Detailed fixes: d22_recommendation.md.

D24 · Comment Value6.4 1.8 / 10Critical✓ Tool-verified

What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).

Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.

Maturity: Documented → Verified → Prevented · effective 1.8 / 10 · rule-coverage 28% · ceiling Documented

5 of 139 judged comments only repeat the code they sit on (3.6 %). 727 comment(s) in another language or script were not judged.

redundant comment · ×5src/back-end/Senparc.Xncf.Accounts/Program.cs:38
doc comments repeat the names · ×6src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/AdminUserInfo/Edit.cshtml.cs:17

What to do

  1. Resolve the 5 redundant comment finding(s) in Comment Value — start with REDACTED (2), permission.js, formatTime.spec.js. — One of this dimension's main actionable groups (5 recommendation-level).

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

D26 · Project Cohesion8.6 / 10Strong✓ 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.

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

1 of 14 projects flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesionREDACTED:1

What to do

  1. Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).

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

D27 · Navigability9.9 / 10Exemplary✓ Tool-verified

What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.

Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.

Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.

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

99 % of calls cross a namespace and 0 % go through an interface, but 99 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: medium — clean/modular boundaries expected.

✓ On the Gold path — maintain.

Detailed fixes: d27_recommendation.md.

D28 · Secrets (history)0.0 / 10Critical✓ 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 0.0 / 10 · rule-coverage 100% · ceiling Documented

29 finding(s): 0 critical, 29 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.

REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 26 High secret finding(s) in Secrets (history) — start with REDACTED (24), REDACTED (2). — One of this dimension's main actionable groups (26 issue-level).
  2. Resolve the 3 REDACTED finding(s) in Secrets (history) — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
  3. 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.

D29 · Static Analysis (SAST)1.2 / 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.2 / 10 · rule-coverage 100% · ceiling Documented

40 finding(s): 0 critical, 0 high, 40 medium, 0 low. semgrep hit a parse error in 31 file(s) — `REDACTED` (lines 8–19), `src/back-end/Senparc.Areas.Admin/ACL/Repository/SysMenuRepository.cs` (lines 11–108), `src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/AdminUserInfo/AuthorizationPage.cshtml.cs` (line 14, line 15, line 20), `src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/AdminUserInfo/Edit.cshtml.cs` (lines 14–16, line 118), `src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/AdminUserInfo/Index.cshtml.cs` (line 32, line 33, line 36, …), … (+26 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. In 12 of those file(s) — `src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/AdminUserInfo/AuthorizationPage.cshtml.cs`, `src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/AdminUserInfo/Edit.cshtml.cs`, `src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/AdminUserInfo/Index.cshtml.cs`, `src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Index.cshtml.cs`, `src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/NeuCharPivot/Aggregate.cshtml.cs`, … (+7 more) — the break is a C# primary constructor, which semgrep's grammar cannot parse and which hides the type from every rule scoped to it; those files were re-scanned from a shadow copy with the constructor's parameter list blanked (line and column preserving), which restores the type to the rules, and 0 additional row(s) came from that pass. Only the header's own parameter list is unread in them. In 3 of those file(s) — `src/back-end/Senparc.Areas.Admin/ACL/Repository/SysMenuRepository.cs`, `src/back-end/Senparc.Areas.Admin/Domain/Services/InstallerService.cs`, `src/back-end/Senparc.Areas.Admin/Domain/Services/NeuCharFunctionService.cs` — the break is at a TYPE DECLARATION (a C# primary constructor semgrep's grammar cannot parse), so the loss is wider than the named lines: rules scoped to that type see no type to scope to and are blind over its whole body, while rules matching statements keep working there. Absence of a type-scoped finding in those types is not evidence of anything.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

  1. Resolve the 17 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED (3), REDACTED (2). — One of this dimension's main actionable groups (17 warning-level).
  2. Resolve the 6 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (6 warning-level).
  3. Resolve the 6 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (5), REDACTED. — One of this dimension's main actionable groups (6 warning-level).

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

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. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

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

335 finding(s): 56 critical, 171 high, 83 medium, 25 low.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

  1. Resolve the 161 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (98), REDACTED (52), REDACTED (5). — One of this dimension's main actionable groups (161 issue-level).
  2. Resolve the 53 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (36), REDACTED (17). — One of this dimension's main actionable groups (53 issue-level).
  3. Resolve the 10 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (6), REDACTED (4). — One of this dimension's main actionable groups (10 issue-level).

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

D31 · IaC & Container Security6.2 / 10Adequate✓ Tool-verified

What it measures: Whether Dockerfiles / Terraform / Kubernetes config follow security best practices.

Method: IaC/container misconfiguration scan via trivy config (REDACTED/Terraform/K8s/Helm/CloudFormation); severity rules to 0-10 moderate normalizer. NotApplicable without manifests. Exhaustive, deterministic.

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

24 finding(s): 0 critical, 8 high, 10 medium, 6 low.

REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 8 High IaC finding(s) in IaC & Container Security — start with REDACTED (5), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (8 issue-level).
  2. Resolve the 10 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (7), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (10 warning-level).
  3. Resolve the 6 Low IaC finding(s) in IaC & Container Security — start with REDACTED (3), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (6 recommendation-level).

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

D34 · Knowledge Freshness10.0 / 10Exemplary✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Documented

Every significant source file has living knowledge — recently and meaningfully worked. Counted over 88 of the 197 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

✓ On the Gold path — maintain.

Detailed fixes: d34_recommendation.md.

D35 · Change Coupling9.9 / 10Stronggated by 2 serious 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: REDACTED↔InstallerService.cs 62%; REDACTED↔InstallOptionsService.cs 54%

Change coupling: REDACTED ↔ InstallerService.cs · ×2REDACTED:1

What to do

  1. Resolve the 2 Change coupling finding(s) in Change Coupling — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).

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

D39 · IL Efficiency9.9 / 10Exemplary✓ Tool-verified

Method: IL instruction count per method, read from the BUILT first-party assemblies via Mono.Cecil (the target is compiled on a deep run); scored on the fraction of methods whose emitted IL body exceeds the size threshold. Sees compiler-generated bloat source can't; not-applicable when the target fails to build. Deterministic.

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

6 of 1110 first-party methods have an oversized IL body.

IL efficiency: 6 authored method(s) exceed the IL budgetsrc/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/AdminSenparcEntities.cs:102

✓ On the Gold path — maintain.

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

D43 · Malicious Dependencies0.0 / 10Critical✓ 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. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.

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

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

1 finding(s): 0 critical, 0 high, 1 medium, 0 low.

REDACTED

What to do

  1. Resolve the 1 Malicious package finding(s) in Malicious Dependencies — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).

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

D44 · Platform End-of-Life6.0 / 10Adequate✓ 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 6.0 / 10 · rule-coverage 100% · ceiling Documented

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

End-of-life runtime: .NET netcoreapp3.1src/back-end/Tools/GenerateDbMigration/GenerateDbMigration.csproj:5

What to do

  1. Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with GenerateDbMigration.csproj. — One of this dimension's main actionable groups (1 warning-level).

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

Frontend & cross-cutting dimensions

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

AC1 · Text alternatives4.2 / 10Adequate✓ Tool-verified

Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.

Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.

  • An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. (×17) — src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Login.cshtml:43, REDACTED:58, REDACTED:66, …
  • A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content. — src/front-end/Senparc.Xncf.Admin/src/components/ImageCropper/index.vue:132

What to do

  • Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
AC2 · Forms & labels4.6 / 10Adequate✓ Tool-verified

Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.

Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

  • This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×7) — src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/AdminUserInfo/Edit.cshtml:26, src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/AdminUserInfo/Edit.cshtml:27, src/front-end/Senparc.Xncf.Admin/src/components/Dropzone/index.vue:3, …
  • This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label. (×24) — src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/AdminUserInfo/Edit.cshtml:34, src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/AdminUserInfo/Edit.cshtml:42, src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/AdminUserInfo/Edit.cshtml:57, …
  • This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id. — src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/NeuCharPivot/Aggregate.cshtml:46
  • A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label. — src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Shared/_HeaderPartial.cshtml:16
  • This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label. (×4) — src/front-end/Senparc.Xncf.Admin/src/components/BackToTop/index.vue:3, src/front-end/Senparc.Xncf.Admin/src/components/Hamburger/index.vue:2, src/front-end/Senparc.Xncf.Admin/src/components/ImageCropper/index.vue:4, …
  • This <span> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label. — src/front-end/Senparc.Xncf.Admin/src/components/DndList/index.vue:11
  • This <i> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label. (×2) — src/front-end/Senparc.Xncf.Admin/src/components/Upload/SingleImage.vue:21, src/front-end/Senparc.Xncf.Admin/src/components/Upload/SingleImage.vue:0

What to do

  • Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure6.0 / 10Strong✓ Tool-verified

Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.

Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

  • No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×3) — src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Login.cshtml:9, src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Shared/_Layout_Vue.cshtml:29, src/back-end/Senparc.Xncf.Installer/Areas/Install/Pages/Index.cshtml:10
  • Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. (×6) — src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/NeuCharPivot/Aggregate.cshtml:42, src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/lightdemo/antv.vue:127, src/front-end/Senparc.Xncf.Admin/src/views/error-page/401.vue:13, …
  • The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). (×2) — src/front-end/Senparc.Xncf.Admin/public/index.html:2, src/front-end/Senparc.Xncf.XncfStore/xncfstore/public/index.html:2
  • user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta. — src/front-end/Senparc.Xncf.Admin/public/index.html:7

What to do

  • Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC4 · Keyboard semantics1.0 / 10Critical✓ Tool-verified

Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.

Coverage: Population: elements that pose a keyboard-semantics question, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) — a non-natively-interactive element carrying a click handler, a double-click or hover enter/leave binding, a pointer-only gesture on a tabindex="0" element, or `cursor: pointer` from the repo's own CSS; an href-less or placeholder-href (#, javascript:) anchor; and any element with a positive tabindex. Natively interactive elements used correctly (<button>, <a href>, form controls) are NOT in the population — there is nothing to judge — so a page of nothing but correct controls gives AC4 nothing to measure. Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".

  • The repo's own CSS styles .session-actions with `cursor: pointer`, so this <span> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler. — src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/AdminChat/Chat.cshtml:46
  • An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action. (×15) — src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/AdminUserInfo/AuthorizationPage.cshtml:34, src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Menu/Edit.cshtml:23, src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Menu/Edit.cshtml:29, …
  • The repo's own CSS styles .menu-icon-item with `cursor: pointer`, so this <div> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler. — src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Menu/Index.cshtml:112
  • The repo's own CSS styles .el-dropdown-link with `cursor: pointer`, so this <span> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler. — src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Shared/_Layout_Vue.cshtml:99
  • A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler. (×22) — src/front-end/Senparc.Xncf.Admin/src/components/BackToTop/index.vue:3, src/front-end/Senparc.Xncf.Admin/src/components/DndList/index.vue:11, src/front-end/Senparc.Xncf.Admin/src/components/DndList/index.vue:22, …

What to do

  • Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC5 · ARIA correctness10.0 / 10Exemplary○ Nothing flagged

Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.

Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

AC6 · Visual & motion safety1.0 / 10Critical✓ Tool-verified

Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.

Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.

Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

  • `.host-comparison-bar-fill` moves (`transition: width 0.35s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Index.cshtml:200
  • `.shake-animation` moves (`animation: shake 0.8s cubic-bezier(.36,.07,.19,.97) both`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Index.cshtml:657
  • `.glow-animation` moves (`animation: glow 1.2s ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Index.cshtml:661
  • `#xncf-modules-area .xncf-item .version.version-upgradeable` sets color: #409EFF on background-color: #e6f1fc — 2.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Index.cshtml:558
  • `.shoptit` sets color: #929292 on background-color: #ffffff — 3.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/views/Senparc.Xncf.XncfStore/operation/application.vue:270
  • `.addArea:hover` sets color: white on background-color: #37bc9b — 2.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/views/Senparc.Xncf.XncfStore/operation/application.vue:352
  • `&__return-home` sets color: #ffffff on background-color: #1482f0 — 3.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/front-end/Senparc.Xncf.Admin/src/views/error-page/404.vue:201
  • `.box-card .box-card-action` sets color: #fff on background-color: #ff6a00 — 2.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. (×2) — src/front-end/Senparc.Xncf.Admin/src/views/Admin/XncfModule/Index.vue:639, src/front-end/Senparc.Xncf.Admin/src/views/Admin/XncfModule/Start.vue:1080
  • `.box-card .box-card-action2` sets color: #fff on background-color: #909399 — 3.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. (×2) — src/front-end/Senparc.Xncf.Admin/src/views/Admin/XncfModule/Index.vue:657, src/front-end/Senparc.Xncf.Admin/src/views/Admin/XncfModule/Start.vue:1099
  • `&:hover` sets color: #fff on background-color: #b4bccc — 1.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/front-end/Senparc.Xncf.Admin/src/layout/components/TagsView/index.vue:286
  • `.custom-theme .el-select .el-tag__close.el-icon-close` sets color: #fff on background-color: #b4bccc — 1.9:1, below the 4.5:1 WCAG AA minimum for normal text. This is a MINIFIED, build-generated sheet — editing the literal here is undone by the next vendor drop or rebuild, so override the rule in your own stylesheet (or fix it upstream / in the source the bundle is built from). — src/front-end/Senparc.Xncf.Admin/src/assets/custom-theme/index.css:1
  • `.custom-theme .el-tabs__item .el-icon-close:hover` sets color: #fff on background-color: #b4bccc — 1.9:1, below the 4.5:1 WCAG AA minimum for normal text. This is a MINIFIED, build-generated sheet — editing the literal here is undone by the next vendor drop or rebuild, so override the rule in your own stylesheet (or fix it upstream / in the source the bundle is built from). — src/front-end/Senparc.Xncf.Admin/src/assets/custom-theme/index.css:1
  • `.el-pagination.is-background .el-pager li:not(.disabled).active` sets color: #FFF on background-color: #409EFF — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/back-end/Senparc.Web/wwwroot/lib/element-ui_2.13.2/element.css:1394
  • `.el-select .el-tag__close.el-icon-close` sets color: #FFF on background-color: #C0C4CC — 1.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/back-end/Senparc.Web/wwwroot/lib/element-ui_2.13.2/element.css:2699
  • `.el-date-table td.current:not(.disabled) span` sets color: #FFF on background-color: #409EFF — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/back-end/Senparc.Web/wwwroot/lib/element-ui_2.13.2/element.css:3384
  • `.el-date-table td.selected span` sets color: #FFF on background-color: #409EFF — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/back-end/Senparc.Web/wwwroot/lib/element-ui_2.13.2/element.css:3427
  • `.el-month-table td.end-date .cell, .el-month-table td.start-date .cell` sets color: #FFF on background-color: #409EFF — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/back-end/Senparc.Web/wwwroot/lib/element-ui_2.13.2/element.css:3508
  • `.el-picker-panel__shortcut.active` sets color: #409EFF on background-color: #e6f1fe — 2.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/back-end/Senparc.Web/wwwroot/lib/element-ui_2.13.2/element.css:4041
  • `.el-tabs__item .el-icon-close:hover` sets color: #FFF on background-color: #C0C4CC — 1.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/back-end/Senparc.Web/wwwroot/lib/element-ui_2.13.2/element.css:5020
  • `.el-cascader__tags .el-tag .el-icon-close` sets color: #FFF on background-color: #C0C4CC — 1.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/back-end/Senparc.Web/wwwroot/lib/element-ui_2.13.2/element.css:11725
  • `div.meneame a:hover` sets color: #ff6500 on background-color: #ffc794 — 1.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/back-end/Senparc.Web/wwwroot/css/User/base/pagecss.css:181
  • `div.meneame a:active` sets color: #ff6500 on background-color: #ffc794 — 1.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/back-end/Senparc.Web/wwwroot/css/User/base/pagecss.css:191
  • `div.meneame span.current` sets color: #ff6500 on background-color: #ffbe94 — 1.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/back-end/Senparc.Web/wwwroot/css/User/base/pagecss.css:201
  • `div.scott a:hover` sets color: #638425 on background-color: #f1ffd6 — 4.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/back-end/Senparc.Web/wwwroot/css/User/base/pagecss.css:395
  • `div.scott a:active` sets color: #638425 on background-color: #f1ffd6 — 4.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/back-end/Senparc.Web/wwwroot/css/User/base/pagecss.css:404
  • `div.scott span.current` sets color: #fff on background-color: #b2e05d — 1.5:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/back-end/Senparc.Web/wwwroot/css/User/base/pagecss.css:413
  • `div.quotes span.current` sets color: #aaa on background-color: #f0f0f0 — 2.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/back-end/Senparc.Web/wwwroot/css/User/base/pagecss.css:491
  • `div.black-red a:hover` sets color: #fff on background-color: #ec5210 — 3.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/back-end/Senparc.Web/wwwroot/css/User/base/pagecss.css:691
  • `div.black-red a:active` sets color: #fff on background-color: #ec5210 — 3.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/back-end/Senparc.Web/wwwroot/css/User/base/pagecss.css:696
  • `div.black-red span.disabled` sets color: #868686 on background-color: #3e3e3e — 2.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/back-end/Senparc.Web/wwwroot/css/User/base/pagecss.css:712
  • `div.grayr span.disabled` sets color: #797979 on background-color: #c1c1c1 — 2.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/back-end/Senparc.Web/wwwroot/css/User/base/pagecss.css:767
  • `div.yellow span.current` sets color: #fff on background-color: #d9d300 — 1.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/back-end/Senparc.Web/wwwroot/css/User/base/pagecss.css:819
  • `div.jogger a` sets color: #fff on background-color: #ee4e4e — 3.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/back-end/Senparc.Web/wwwroot/css/User/base/pagecss.css:859
  • `div.starcraft2 span.disabled` sets color: #444 on background-color: #000 — 2.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/back-end/Senparc.Web/wwwroot/css/User/base/pagecss.css:944
  • `div.tres a` sets color: #fff on background-color: #d90 — 2.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/back-end/Senparc.Web/wwwroot/css/User/base/pagecss.css:965
  • `div.megas512 a:hover` sets color: #fff on background-color: #777777 — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/back-end/Senparc.Web/wwwroot/css/User/base/pagecss.css:1042
  • `div.megas512 a:active` sets color: #fff on background-color: #777777 — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/back-end/Senparc.Web/wwwroot/css/User/base/pagecss.css:1052
  • `div.badoo` sets color: #48b9ef on background-color: #fff — 2.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/back-end/Senparc.Web/wwwroot/css/User/base/pagecss.css:1247

What to do

  • Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AC7 · A11y enforcement4.0 / 10Adequate✓ Tool-verified

Other · Accessibility — Whether accessibility is ENFORCED in the toolchain — an accessibility checker configured over the markup (an a11y lint rule set, e.g. eslint-plugin-jsx-a11y or vuejs-accessibility where the project lints JavaScript) and an automated accessibility assertion wired into tests or CI (axe/pa11y/Lighthouse or an equivalent) — on the Documented→Verified→Prevented ladder.

Method: Repo config/CI scan: an accessibility checker configured over the markup (an a11y lint rule set such as eslint-plugin-jsx-a11y / vuejs-accessibility where JavaScript is linted) and an automated accessibility assertion in tests or CI (axe/pa11y/Lighthouse or equivalent), graded on the Documented→Verified→Prevented rungs. Deterministic, presence/rung detection.

Coverage: Population: the repository's own tooling configuration — lint config, test and CI files — NOT the markup. It is read for a configured accessibility checker and an automated accessibility assertion (axe/pa11y/Lighthouse, or a native-toolkit equivalent), and it credits an INVOCATION, never a mention: a licence filename, an import comment or a doc reference earns no rung. Enforcement configured entirely outside the repository leaves no evidence here and cannot be credited.

  • No accessibility enforcement found — no a11y linter (eslint-plugin-vuejs-accessibility) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 146 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here. — src/front-end/package.json:55

What to do

  • Enforce accessibility in the toolchain: add eslint-plugin-vuejs-accessibility, then assert with your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) in tests, then gate axe/pa11y/Lighthouse in CI.
AX1 · Captive dependencies10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether any singleton service captures a scoped/transient dependency — a silent lifetime/threading bug.

Method: Roslyn scan: DI registrations parsed from AddSingleton/Scoped/Transient; each singleton checked for captured shorter-lifetime dependencies. Exhaustive, deterministic.

AX10 · Code composition8.8 / 10Exemplary✓ 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.

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.

AX2 · Stateful singletons3.9 / 10Weak✓ Tool-verified

Other · Architecture — Whether singleton services avoid mutable shared instance state that concurrent callers would race on.

Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.

  • `Register` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (StartTime; e.g. `StartTime` at line 53). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/back-end/Senparc.Web/Register.cs:47
  • `SenparcDbContextFactoryConfig` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_rootDirectoryPath; e.g. `_rootDirectoryPath` at line 30). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/back-end/Senparc.Areas.Admin/Domain/Models/MultipleDatabase/SenparcDbContextFactoryConfig.cs:11
  • `SenparcDbContextFactoryConfig` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_rootDictionaryPath; e.g. `_rootDictionaryPath` at line 30). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/back-end/Senparc.Xncf.Accounts/Domain/Models/DatabaseModel/MultipleDatabase/SenparcDbContextFactoryConfig.cs:11

What to do

  • A `static` field is one slot for the whole process, however its type is created: back it with a thread-safe type (ConcurrentDictionary, Interlocked), take a lock around every write, or move it into a registered singleton that does.
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.

  • The namespaces Senparc.Areas.Admin.Domain ↔ Senparc.Areas.Admin.Domain.Services depend on each other. The lightest dependency in the cycle is Senparc.Areas.Admin.Domain → Senparc.Areas.Admin.Domain.Services (Senparc.Areas.Admin.Domain.AdminUserInfoService → Senparc.Areas.Admin.Domain.Services.AdminAuthConfigService, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/back-end/Senparc.Areas.Admin/Domain/Services/AdminUserInfoService.cs:40

What to do

  • Break namespace cycles inside a project by moving the shared type to a namespace both sides can use, or by inverting the back edge behind an interface.
AX4 · Dependency direction10.0 / 10Exemplary✓ 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.

AX5 · Architecture & structure10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.

Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.

AX6 · Interface segregation10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').

Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.

AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.

Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.

DM1 · Aggregate boundaries5.4 / 10Adequate✓ Tool-verified

Other · Domain Modelling — Whether aggregates reference each other by identity (id) rather than by direct object reference — the core DDD consistency-boundary rule.

Method: Roslyn (DDD-gated): aggregate roots identified by convention; each aggregate field checked for direct references to other aggregates versus id-only. Deterministic, DDD-native.

Coverage: Population: aggregate roots identified by AggregateRoot/IAggregateRoot base/interface NAME convention; reference-by-identity then checked exhaustively within that set — a root not using those names is invisible.

  • `AdminChatMessage` references the aggregate root `AdminChatSession` directly (via `Session`) — hold its `AdminChatSessionId` instead. — src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/AdminChatMessage.cs:53

What to do

  • Reference other aggregates by their strongly-typed id, never by object reference, so each aggregate stays an independent consistency boundary.
DM11 · Constructible invalid state6.2 / 10Strong✓ Tool-verified

Other · Domain Modelling — Whether an aggregate can be constructed in a state its own rules forbid — a public constructor that takes a raw primitive, stores it, and validates nothing, with no factory beside it. A constructor taking only value objects is not counted: each parameter has already validated itself.

Method: Neutral surface (DDD-gated): each non-abstract entity/aggregate checked for a PUBLIC constructor taking at least one RAW PRIMITIVE parameter whose body contains no guard token (throw / Guard. / Ensure. / ArgumentException / CheckRule / an XException.ThrowIf* helper). C#: a static factory beside a public constructor does not exempt it, and a public parameterless constructor followed by public raw-primitive setters that refuse nothing is charged when the type also declares a validating way in (a guarded constructor or a guarding static method returning the type); TypeScript: a static Create/Of/From/New factory exempts the type. A constructor taking only value objects is never charged -- measured: 64 of 87 unguarded public constructors on the C# corpus take value objects only, so ignoring parameter types would be 73% false positives. One finding per entity. Deterministic.

  • `AdminAuthConfig`'s public constructor takes `adminWebLoginExpireMinutes`, `backendJwtExpireMinutes` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `AdminAuthConfig` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/AdminAuthConfig.cs:37
  • `AdminChatMessage`'s public constructor takes `sessionId`, `content`, `sequence`, `modelIdentifier` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `AdminChatMessage` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/AdminChatMessage.cs:69
  • `AdminChatSession`'s public constructor takes `title`, `userId` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `AdminChatSession` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/AdminChatSession.cs:48
  • `NeuCharPivotConfiguration`'s public constructor takes `moduleUid`, `name`, `adminUserId` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `NeuCharPivotConfiguration` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/NeuCharPivotModels.cs:50
  • `NeuCharPivotFunction`'s public constructor takes `pivotId`, `moduleUid`, `functionKey`, `functionName`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `NeuCharPivotFunction` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/NeuCharPivotModels.cs:120
  • `NeuCharPivotLoopTask`'s public constructor takes `functionId`, `adminUserId` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `NeuCharPivotLoopTask` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/NeuCharPivotModels.cs:185
  • `NeuCharExecutionLog`'s public constructor takes `sourceType`, `sourceId`, `moduleUid`, `functionKey`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `NeuCharExecutionLog` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/NeuCharPivotModels.cs:269

What to do

  • Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure.
DM12 · Ambient inputs in the domain9.5 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether domain types receive the time and randomness their rules depend on, rather than reading the process clock or a global random source directly — an ambient read makes the rule it feeds untestable at the instant that matters and lets two reads inside one operation disagree.

Method: Roslyn (DDD-gated, C#/VB only): domain-layer types scanned for ambient reads — DateTime/DateTimeOffset.Now/UtcNow/Today, Random.Shared, new Random(), Stopwatch.GetTimestamp — resolved against the semantic model, with a comment/string-stripped token fallback only where resolution fails. Body reads are scored; field/property initialisers are surfaced unscored. Apply/When folds excluded (ES1 owns them). Deterministic, symbol-resolved.

  • `AccountPayLogService` reads `DateTime.Now` inside `CreateOrder`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. (×2) — src/back-end/Senparc.Xncf.Accounts/Domain/Services/AccountPayLogService.cs:32, src/back-end/Senparc.Xncf.Accounts/Domain/Services/AccountPayLogService.cs:33
  • `AccountPayLogService` reads `DateTime.Now` inside `CancelOrder`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. — src/back-end/Senparc.Xncf.Accounts/Domain/Services/AccountPayLogService.cs:55
  • `AccountPayLogService` reads `DateTime.Now` inside `PayLogFinish`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. — src/back-end/Senparc.Xncf.Accounts/Domain/Services/AccountPayLogService.cs:74
  • `AccountService` reads `DateTime.Now` inside `GetSalt`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. — src/back-end/Senparc.Xncf.Accounts/Domain/Services/AccountService.cs:28
  • `AccountService` reads `DateTimeOffset.UtcNow` inside `Login`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. — src/back-end/Senparc.Xncf.Accounts/Domain/Services/AccountService.cs:190
  • `AccountService` reads `DateTime.Now` inside `Login`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. — src/back-end/Senparc.Xncf.Accounts/Domain/Services/AccountService.cs:222
  • `AccountService` reads `DateTime.Now` inside `CreateAccount`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. (×3) — src/back-end/Senparc.Xncf.Accounts/Domain/Services/AccountService.cs:245, src/back-end/Senparc.Xncf.Accounts/Domain/Services/AccountService.cs:247, src/back-end/Senparc.Xncf.Accounts/Domain/Services/AccountService.cs:248
  • `AdminChatSession` reads `DateTime.Now` inside `UpdateLastMessageTime`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. — src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/AdminChatSession.cs:73
  • `AdminUserInfo` draws from `new Random()` inside `GenerateUserName`. The outcome is not a function of the inputs, so no test can assert which result this produces, and the same inputs replay differently. Take the randomness as a parameter — an injected `Random`, a seeded generator, or the already-chosen value — so a caller (and a test) can decide it. — src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/AdminUserInfo.cs:117
  • `AdminUserInfo` reads `DateTime.Now` inside `GeneratePasswordSalt`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. — src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/AdminUserInfo.cs:135
  • `AdminUserInfoService` reads `DateTimeOffset.UtcNow` inside `KeepCookieLoginAliveAsync`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. (×2) — src/back-end/Senparc.Areas.Admin/Domain/Services/AdminUserInfoService.cs:112, src/back-end/Senparc.Areas.Admin/Domain/Services/AdminUserInfoService.cs:117
  • `AdminUserInfoService` reads `DateTimeOffset.UtcNow` inside `LoginAsync`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. (×2) — src/back-end/Senparc.Areas.Admin/Domain/Services/AdminUserInfoService.cs:224, src/back-end/Senparc.Areas.Admin/Domain/Services/AdminUserInfoService.cs:229
  • `AdminUserInfoService` reads `DateTime.Now` inside `TryLoginAsync`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. (×5) — src/back-end/Senparc.Areas.Admin/Domain/Services/AdminUserInfoService.cs:268, src/back-end/Senparc.Areas.Admin/Domain/Services/AdminUserInfoService.cs:293, src/back-end/Senparc.Areas.Admin/Domain/Services/AdminUserInfoService.cs:297, …
  • `AdminUserInfoService` reads `DateTimeOffset.UtcNow` inside `GenerateTokenForDesktopHandoffAsync`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. — src/back-end/Senparc.Areas.Admin/Domain/Services/AdminUserInfoService.cs:520
  • `AdminUserInfoService` reads `DateTimeOffset.UtcNow` inside `GenerateToken`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. — src/back-end/Senparc.Areas.Admin/Domain/Services/AdminUserInfoService.cs:554
  • `DesktopAdminAuthTokenIssuer` reads `DateTimeOffset.UtcNow` inside `IssueAsync`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. — src/back-end/Senparc.Areas.Admin/Domain/Services/DesktopAdminAuthTokenIssuer.cs:36
  • `FullAccountBase` reads `DateTime.Now` inside `IsLogined`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. — src/back-end/Senparc.Xncf.Accounts/Domain/Models/DatabaseModel/ExtensionEntity.cs:45
  • `HostMetricsCollector` reads `DateTimeOffset.UtcNow` inside `Collect`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. — src/back-end/Senparc.Areas.Admin/Domain/Services/HostMetricsCollector.cs:68
  • `HostMetricsCollector` reads `Stopwatch.GetTimestamp` inside `CollectProcess`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. — src/back-end/Senparc.Areas.Admin/Domain/Services/HostMetricsCollector.cs:175
  • `HostMetricsCollector` reads `DateTime.UtcNow` inside `CollectProcess`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. — src/back-end/Senparc.Areas.Admin/Domain/Services/HostMetricsCollector.cs:196
  • `HostMetricsCollector` reads `Stopwatch.GetTimestamp` inside `ReadNetworkCounters`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. — src/back-end/Senparc.Areas.Admin/Domain/Services/HostMetricsCollector.cs:423
  • `InstallOptionsService` draws from `new Random()` inside `GetDefaultAdminUserName`. The outcome is not a function of the inputs, so no test can assert which result this produces, and the same inputs replay differently. Take the randomness as a parameter — an injected `Random`, a seeded generator, or the already-chosen value — so a caller (and a test) can decide it. — src/back-end/Senparc.Xncf.Installer/Domain/Services/InstallOptionsService.cs:69
  • `NeuBellTestProvider` reads `DateTimeOffset.Now` inside `Send`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. — src/back-end/Senparc.Areas.Admin/Domain/Services/NeuBellTestProvider.cs:53
  • `NeuCharExecutionLog` reads `DateTime.UtcNow` inside `Complete`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. — src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/NeuCharPivotModels.cs:288
  • `NeuCharPivotConfiguration` reads `DateTime.UtcNow` inside `ApplyGeneratedLayout`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. — src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/NeuCharPivotModels.cs:75
  • `NeuCharPivotLoopTask` reads `DateTime.UtcNow` inside `Configure`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. — src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/NeuCharPivotModels.cs:199
  • `NeuCharPivotLoopTask` reads `DateTime.UtcNow` inside `MarkStarted`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. — src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/NeuCharPivotModels.cs:209
  • `NeuCharPivotLoopTaskHostedService` reads `new PeriodicTimer(` inside `ExecuteAsync`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. — src/back-end/Senparc.Areas.Admin/Domain/Services/NeuCharPivotLoopTaskHostedService.cs:94
  • `NeuCharPivotLoopTaskHostedService` reads `DateTime.UtcNow` inside `RunDueTasksAsync`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. — src/back-end/Senparc.Areas.Admin/Domain/Services/NeuCharPivotLoopTaskHostedService.cs:122
  • `NeuCharPivotLoopTaskHostedService` reads `DateTimeOffset.UtcNow` inside `RunDueTasksAsync`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. (×2) — src/back-end/Senparc.Areas.Admin/Domain/Services/NeuCharPivotLoopTaskHostedService.cs:150, src/back-end/Senparc.Areas.Admin/Domain/Services/NeuCharPivotLoopTaskHostedService.cs:191

What to do

  • Take the instant and the randomness as inputs to the domain methods that need them — inject `TimeProvider` (BCL, .NET 8+) and a `Random`/seeded generator — so a test can choose both.
DM2 · Strongly-typed ids3.0 / 10Weak✓ Tool-verified

Other · Domain Modelling — How much of the domain uses strongly-typed ids vs raw Guid/string/int — adoption curve, not all-or-nothing.

Method: Roslyn (DDD-gated): strongly-typed id adoption on domain entities/events; raw Guid/int/string ids counted versus wrapped types. An id wrapper is recognised by VALUE SEMANTICS, not by being a struct — a record struct, a record class (`record ApartmentId(Guid Value)`) or a class declared by a typed-id base (`class MemberId : TypedIdValueBase`) all count, while a plain mutable class (reference equality) and a verb-phrase query record (`GetCustomerById`) do not. Deterministic, adoption percentage.

Coverage: Population: id-like members by *Id/*Key NAME suffix; strongly-typed-ID shape then checked semantically — non-suffixed identifiers are not seen.

  • `AdminChatMessage.SessionId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that. — src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/AdminChatMessage.cs:18
  • `AdminChatSession.UserId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that. — src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/AdminChatSession.cs:24
  • `AdminChatSessionModule.SessionId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that. — src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/AdminChatSessionModule.cs:18
  • `AdminChatSessionWorkflow.SessionId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that. — src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/AdminChatSessionWorkflow.cs:29
  • `AdminChatSessionWorkflow.WorkflowId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that. — src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/AdminChatSessionWorkflow.cs:32
  • `NeuCharPivotConfiguration.AiModelId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that. — src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/NeuCharPivotModels.cs:36
  • `NeuCharPivotConfiguration.AdminUserId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that. — src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/NeuCharPivotModels.cs:38
  • `NeuCharPivotConfiguration.ChatSessionId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that. — src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/NeuCharPivotModels.cs:40
  • `NeuCharPivotFunction.PivotId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that. — src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/NeuCharPivotModels.cs:94
  • `NeuCharPivotFunction.FunctionKey` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/NeuCharPivotModels.cs:99
  • `NeuCharPivotLoopTask.FunctionId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that. — src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/NeuCharPivotModels.cs:161
  • `NeuCharPivotLoopTask.AdminUserId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that. — src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/NeuCharPivotModels.cs:163
  • `NeuCharExecutionLog.SourceId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that. — src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/NeuCharPivotModels.cs:243
  • `NeuCharExecutionLog.FunctionKey` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/NeuCharPivotModels.cs:248
  • `NeuCharExecutionLog.CorrelationId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/NeuCharPivotModels.cs:264
  • `Account.WeixinUnionId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — src/back-end/Senparc.Xncf.Accounts/Domain/Models/DatabaseModel/Account.cs:55
  • `Account.WeixinOpenId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — src/back-end/Senparc.Xncf.Accounts/Domain/Models/DatabaseModel/Account.cs:57
  • `AccountPayLog.AccountId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that. — src/back-end/Senparc.Xncf.Accounts/Domain/Models/DatabaseModel/AccountPayLog.cs:19
  • `AccountPayLog.PrepayId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — src/back-end/Senparc.Xncf.Accounts/Domain/Models/DatabaseModel/AccountPayLog.cs:41
  • `PointsLog.AccountId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that. — src/back-end/Senparc.Xncf.Accounts/Domain/Models/DatabaseModel/PointsLog.cs:13
  • `PointsLog.AccountPayLogId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that. — src/back-end/Senparc.Xncf.Accounts/Domain/Models/DatabaseModel/PointsLog.cs:14

What to do

  • Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs.
DM3 · Integration-event coupling10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether cross-context integration events stay loosely coupled — no producer-owned enums/domain types leaking to consumers. Shared-kernel/contracts types are allowed.

Method: Roslyn (DDD-gated): integration-event properties scanned for producer-domain type/enum leaks versus primitives and shared-kernel types. Deterministic, hard fact.

DM4 · Rich vs anemic model7.3 / 10Strong✓ Tool-verified

Other · Domain Modelling — Whether aggregates/entities carry the behaviour that protects their invariants, rather than being data bags driven by external services.

Method: Roslyn (DDD-gated): entity method BODIES classified mutator-vs-query — only methods that mutate the entity's own declared state count as invariant-protecting behaviour, so a getter/passthrough doesn't rescue an anemic class. Deterministic, exhaustive over domain-layer entities.

Coverage: Population: entities by name/base convention; rich-vs-anemic judged by classifying each method body mutator-vs-query — logic-bearing domain types outside the convention are invisible.

  • `AdminChatSessionModule` is an aggregate/entity with 6 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/AdminChatSessionModule.cs:11
  • `AdminChatSessionWorkflow` is an aggregate/entity with 6 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/AdminChatSessionWorkflow.cs:25
  • `Account` is an aggregate/entity with 34 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/back-end/Senparc.Xncf.Accounts/Domain/Models/DatabaseModel/Account.cs:11
  • `AccountPayLog` is an aggregate/entity with 20 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/back-end/Senparc.Xncf.Accounts/Domain/Models/DatabaseModel/AccountPayLog.cs:9
  • `PointsLog` is an aggregate/entity with 8 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/back-end/Senparc.Xncf.Accounts/Domain/Models/DatabaseModel/PointsLog.cs:9

What to do

  • Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services.
DM5 · Encapsulated state9.1 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether entities protect their state — private/init-only setters, and collections handed out as read-only views rather than the mutable backing collection — instead of exposing writable state that bypasses invariants. Softened when a rehydration framework (Marten/EF) is present.

Method: Roslyn (DDD-gated): entities scanned for publicly writable state — public setters, and (C#/VB) own mutable collections handed out through an auto-property, a public field or a bare-field expression getter, where a computed/copying getter is never charged. One finding per entity; score softened when Marten/EF rehydration frameworks present. Deterministic, framework-aware.

Coverage: Population: entities by convention; encapsulation (setter shape) checked exhaustively within the set.

  • `Account` exposes publicly writable state (UserName, Password, PasswordSalt, NickName, RealName, Phone, and 28 more). — src/back-end/Senparc.Xncf.Accounts/Domain/Models/DatabaseModel/Account.cs:11
  • `AccountPayLog` exposes publicly writable state (AccountId, OrderNumber, TotalPrice, PayMoney, UsedPoints, CompleteTime, and 14 more). — src/back-end/Senparc.Xncf.Accounts/Domain/Models/DatabaseModel/AccountPayLog.cs:9
  • `PointsLog` exposes publicly writable state (AccountId, AccountPayLogId, Points, BeforePoints, AfterPoints, Description, and 2 more). — src/back-end/Senparc.Xncf.Accounts/Domain/Models/DatabaseModel/PointsLog.cs:9

What to do

  • Make entity setters private/init-only and hand collections out as IReadOnlyList/IReadOnlyCollection over a private backing field; change state only through methods that enforce the invariants (Marten/EF can bind via constructor or private setters).
DM6 · Domain ↔ infrastructure boundary1.0 / 10Critical✓ Tool-verified

Other · Domain Modelling — Whether the domain layer stays free of infrastructure dependencies (EF/Marten/HTTP/ASP.NET) — the clean-architecture dependency rule.

Method: Roslyn (DDD-gated): domain-layer types scanned for infrastructure usage in member SIGNATURES and inside method/accessor BODIES — resolved calls and object-creations into EF/Marten/HTTP/Mongo/Redis/message-bus types (not just a namespace allowlist). Deterministic, symbol-resolved, exhaustive over domain-layer bodies, DDD-native.

Coverage: Domain layer identified by NAMESPACE heuristic; infrastructure then resolved by symbol in member SIGNATURES and method/accessor BODIES — rename the layer and the check evaporates.

  • `Add_Chat_Tables` (domain layer) names `Migration` from `Microsoft.EntityFrameworkCore.Migrations` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — src/back-end/Senparc.Areas.Admin/Domain/Migrations/Dm/20260325233351_Add_Chat_Tables.cs:9
  • `Add_Chat_Tables` (domain layer) names `MigrationBuilder` from `Microsoft.EntityFrameworkCore.Migrations` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. (×2) — src/back-end/Senparc.Areas.Admin/Domain/Migrations/Dm/20260325233351_Add_Chat_Tables.cs:12, src/back-end/Senparc.Areas.Admin/Domain/Migrations/Dm/20260325233351_Add_Chat_Tables.cs:135
  • `Add_Chat_Tables` (domain layer) names `ReferentialAction` from `Microsoft.EntityFrameworkCore.Migrations` — a persistence type (in a method body). The domain should own a port and let an infrastructure adapter implement it. (×2) — src/back-end/Senparc.Areas.Admin/Domain/Migrations/Dm/20260325233351_Add_Chat_Tables.cs:91, src/back-end/Senparc.Areas.Admin/Domain/Migrations/Dm/20260325233351_Add_Chat_Tables.cs:120
  • `Add_LoginTimeout` (domain layer) names `Migration` from `Microsoft.EntityFrameworkCore.Migrations` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — src/back-end/Senparc.Areas.Admin/Domain/Migrations/Dm/20260704171548_Add_LoginTimeout.cs:25
  • `Add_LoginTimeout` (domain layer) names `MigrationBuilder` from `Microsoft.EntityFrameworkCore.Migrations` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. (×2) — src/back-end/Senparc.Areas.Admin/Domain/Migrations/Dm/20260704171548_Add_LoginTimeout.cs:28, src/back-end/Senparc.Areas.Admin/Domain/Migrations/Dm/20260704171548_Add_LoginTimeout.cs:52
  • `Add_NeuCharPivot_Workflow` (domain layer) names `Migration` from `Microsoft.EntityFrameworkCore.Migrations` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — src/back-end/Senparc.Areas.Admin/Domain/Migrations/Dm/20260808150932_Add_NeuCharPivot_Workflow.cs:23
  • `Add_NeuCharPivot_Workflow` (domain layer) names `MigrationBuilder` from `Microsoft.EntityFrameworkCore.Migrations` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. (×2) — src/back-end/Senparc.Areas.Admin/Domain/Migrations/Dm/20260808150932_Add_NeuCharPivot_Workflow.cs:26, src/back-end/Senparc.Areas.Admin/Domain/Migrations/Dm/20260808150932_Add_NeuCharPivot_Workflow.cs:174
  • `Tune_NeuCharPivot_Storage` (domain layer) names `Migration` from `Microsoft.EntityFrameworkCore.Migrations` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — src/back-end/Senparc.Areas.Admin/Domain/Migrations/Dm/20260808152032_Tune_NeuCharPivot_Storage.cs:22
  • `Tune_NeuCharPivot_Storage` (domain layer) names `MigrationBuilder` from `Microsoft.EntityFrameworkCore.Migrations` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. (×2) — src/back-end/Senparc.Areas.Admin/Domain/Migrations/Dm/20260808152032_Tune_NeuCharPivot_Storage.cs:25, src/back-end/Senparc.Areas.Admin/Domain/Migrations/Dm/20260808152032_Tune_NeuCharPivot_Storage.cs:72
  • `Add_NeuCharWorkflow_AutoSave_Versions` (domain layer) names `Migration` from `Microsoft.EntityFrameworkCore.Migrations` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — src/back-end/Senparc.Areas.Admin/Domain/Migrations/Dm/20260808175020_Add_NeuCharWorkflow_AutoSave_Versions.cs:23
  • `Add_NeuCharWorkflow_AutoSave_Versions` (domain layer) names `MigrationBuilder` from `Microsoft.EntityFrameworkCore.Migrations` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. (×2) — src/back-end/Senparc.Areas.Admin/Domain/Migrations/Dm/20260808175020_Add_NeuCharWorkflow_AutoSave_Versions.cs:26, src/back-end/Senparc.Areas.Admin/Domain/Migrations/Dm/20260808175020_Add_NeuCharWorkflow_AutoSave_Versions.cs:72
  • `Add_AdminChatSessionWorkflows` (domain layer) names `Migration` from `Microsoft.EntityFrameworkCore.Migrations` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — src/back-end/Senparc.Areas.Admin/Domain/Migrations/Dm/20260821135045_Add_AdminChatSessionWorkflows.cs:22
  • `Add_AdminChatSessionWorkflows` (domain layer) names `MigrationBuilder` from `Microsoft.EntityFrameworkCore.Migrations` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. (×2) — src/back-end/Senparc.Areas.Admin/Domain/Migrations/Dm/20260821135045_Add_AdminChatSessionWorkflows.cs:24, src/back-end/Senparc.Areas.Admin/Domain/Migrations/Dm/20260821135045_Add_AdminChatSessionWorkflows.cs:62
  • `Add_AdminChatSessionWorkflows` (domain layer) names `ReferentialAction` from `Microsoft.EntityFrameworkCore.Migrations` — a persistence type (in a method body). The domain should own a port and let an infrastructure adapter implement it. — src/back-end/Senparc.Areas.Admin/Domain/Migrations/Dm/20260821135045_Add_AdminChatSessionWorkflows.cs:52
  • `AdminSenparcEntities_DmModelSnapshot` (domain layer) names `DbContextAttribute` from `Microsoft.EntityFrameworkCore.Infrastructure` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. — src/back-end/Senparc.Areas.Admin/Domain/Migrations/Dm/AdminSenparcEntities_DmModelSnapshot.cs:27
  • `AdminSenparcEntities_DmModelSnapshot` (domain layer) names `ModelSnapshot` from `Microsoft.EntityFrameworkCore.Infrastructure` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — src/back-end/Senparc.Areas.Admin/Domain/Migrations/Dm/AdminSenparcEntities_DmModelSnapshot.cs:28
  • `AdminSenparcEntities_DmModelSnapshot` (domain layer) names `ModelBuilder` from `Microsoft.EntityFrameworkCore` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. — src/back-end/Senparc.Areas.Admin/Domain/Migrations/Dm/AdminSenparcEntities_DmModelSnapshot.cs:30
  • `AdminSenparcEntities_DmModelSnapshot` (domain layer) names `DmValueGenerationStrategy` from `Microsoft.EntityFrameworkCore.Metadata` — a persistence type (in a method body). The domain should own a port and let an infrastructure adapter implement it. (×11) — src/back-end/Senparc.Areas.Admin/Domain/Migrations/Dm/AdminSenparcEntities_DmModelSnapshot.cs:34, src/back-end/Senparc.Areas.Admin/Domain/Migrations/Dm/AdminSenparcEntities_DmModelSnapshot.cs:43, src/back-end/Senparc.Areas.Admin/Domain/Migrations/Dm/AdminSenparcEntities_DmModelSnapshot.cs:105, …
  • `AdminSenparcEntities_DmModelSnapshot` (domain layer) names `DeleteBehavior` from `Microsoft.EntityFrameworkCore` — a persistence type (in a method body). The domain should own a port and let an infrastructure adapter implement it. (×3) — src/back-end/Senparc.Areas.Admin/Domain/Migrations/Dm/AdminSenparcEntities_DmModelSnapshot.cs:638, src/back-end/Senparc.Areas.Admin/Domain/Migrations/Dm/AdminSenparcEntities_DmModelSnapshot.cs:649, src/back-end/Senparc.Areas.Admin/Domain/Migrations/Dm/AdminSenparcEntities_DmModelSnapshot.cs:660
  • `Init` (domain layer) names `Migration` from `Microsoft.EntityFrameworkCore.Migrations` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it. — src/back-end/Senparc.Areas.Admin/Domain/Migrations/MySql/20211225064239_Init.cs:9
  • `Init` (domain layer) names `MigrationBuilder` from `Microsoft.EntityFrameworkCore.Migrations` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. — src/back-end/Senparc.Areas.Admin/Domain/Migrations/MySql/20211225064239_Init.cs:11

What to do

  • Invert domain→infrastructure dependencies: declare interfaces in the domain, implement them in infrastructure (Dependency Inversion).
DM7 · Repository granularity3.7 / 10Weak✓ Tool-verified

Other · Domain Modelling — Whether repositories are per aggregate root (not per child entity) and keep the persistence query handle behind the contract, so the root's invariants can't be bypassed.

Method: Roslyn (DDD-gated): repository abstraction detection; repositories over non-aggregate-root entities flagged, and (C#/VB) repository INTERFACES whose members return a live persistence query handle (IQueryable/DbSet/IMongoQueryable) — implementations and specification evaluators are out of population by design, since composing a query internally is what an implementation is for. Deterministic, DDD-native.

Coverage: Population: repositories + aggregate roots by NAME convention; per-root repository rule checked within the set.

  • `IAdminChatSessionModuleRepository` is a repository over `AdminChatSessionModule`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `AdminChatSessionModule` through its owning aggregate instead. — src/back-end/Senparc.Areas.Admin/ACL/Repository/AdminChatSessionModuleRepository.cs:7
  • `IAdminChatSessionWorkflowRepository` is a repository over `AdminChatSessionWorkflow`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `AdminChatSessionWorkflow` through its owning aggregate instead. — src/back-end/Senparc.Areas.Admin/ACL/Repository/AdminChatSessionWorkflowRepository.cs:21
  • `ISysMenuRepository` is a repository over `SysMenu`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `SysMenu` through its owning aggregate instead. — src/back-end/Senparc.Areas.Admin/ACL/Repository/SysMenuRepository.cs:13
  • `ISysRolePermissionRepository` is a repository over `SysRolePermission`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `SysRolePermission` through its owning aggregate instead. — src/back-end/Senparc.Areas.Admin/ACL/Repository/SysRolePermissionRepository.cs:13
  • `IAccountPayLogRepository` is a repository over `AccountPayLog`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `AccountPayLog` through its owning aggregate instead. — src/back-end/Senparc.Xncf.Accounts/ACL/Repository/AccountPayLogRepository.cs:7
  • `IAccountRepository` is a repository over `Account`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Account` through its owning aggregate instead. — src/back-end/Senparc.Xncf.Accounts/ACL/Repository/AccountRepository.cs:7
  • `IPointsLogRepository` is a repository over `PointsLog`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `PointsLog` through its owning aggregate instead. — src/back-end/Senparc.Xncf.Accounts/ACL/Repository/PointsLogRepository.cs:7

What to do

  • Define repositories per aggregate root and keep the query handle inside them; reach child entities through their root so invariants can't be bypassed.
DM9 · Scattered domain decisions10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether one domain rule is decided — or one measurement produced — in more than one place, rather than living on the type that owns it.

Method: Neutral body surface plus Roslyn (DDD-gated), two arms. DECISION (Roslyn only): a predicate over a domain type's members judged in two or more types, where none of those decisions live on the owning type — operands of comparisons and relational property patterns only, so a member merely passed as an argument is not judged. DERIVATION: a plain all-numeric carrier of ≥2 members, with no base type and exactly one constructor, CONSTRUCTED as the result of a method (returned or assigned, never inline as an argument) in two or more types other than its own — the same measurement produced twice, which centralising the judgement does not fix. DERIVATION runs on every language whose frontend declares the produced-or-passed fact per construction (Roslyn and the Java sidecar today); a target with only the derivation arm carries an engine gap naming the decision arm as not assessed, and a frontend that declares nothing keeps the dimension not measured rather than clean. Single-member rules, test code and generated code are out of population for both. Advisory.

ED1 · Handler temporal coupling10.0 / 10Exemplary✓ Tool-verified

Other · Event-Driven — Whether event handlers stay asynchronous (no blocking remote HTTP/gRPC calls awaited inside a handler).

Method: Roslyn semantic scan (event-driven gated): event-handler bodies scanned for HTTP/gRPC invocations by resolved symbol type, not substring. Deterministic, semantic-resolved.

ED3 · Event naming7.0 / 10Strong✓ Tool-verified

Other · Event-Driven — Whether events are named in the past tense (a clarity nudge — low weight).

Method: Roslyn scan (event-driven gated): domain and integration events checked for past-tense naming (-ed/-en suffix or irregular set). Naming nudge, low-weight advisory.

  • `AdminChatSyncEvent` reads as an instruction, not a fact that happened. Events describe something that already occurred — name them in the past tense (e.g. `OrderPlaced`, `PaymentCaptured`) so the ubiquitous language stays clear. — src/back-end/Senparc.Areas.Admin/OHS/Local/Events/AdminChatSyncEvent.cs:26

What to do

  • Name events in the past tense — they record facts that already happened.
ED4 · Outbox / dual-write10.0 / 10Exemplary○ Nothing flagged

Other · Event-Driven — Whether state changes and message publishes are atomic (a transactional outbox) rather than a crash-unsafe dual write.

Method: Roslyn semantic scan (event-driven gated): event-handler methods scanned for DB-save plus bus-publish without a transactional outbox reference. Deterministic, semantic-resolved.

ED5 · Idempotency10.0 / 10Exemplary○ Nothing flagged

Other · Readiness — Whether retry-prone mutations (command handlers and message or event consumers) are idempotent, so an at-least-once redelivery or a client retry does not apply the effect twice.

Method: Roslyn (any mutation, ungated): each persistent write of a command handler or message/event consumer is idempotent when a guard is visible (an exists/dedup read that gates an exit, upsert, idempotency-key/inbox used in a condition or store call, versioned or fixed-value write, dedup envelope or pipeline), at risk only on positive double-apply evidence (a fresh-identity insert, an accumulation on a loaded and saved object, a growing member list, an unkeyed POST/SMTP send/Stripe charge), and otherwise not classified. Deterministic, no model; not scored when more than half are not classified. Advisory.

Coverage: Population: retry-prone mutations — command handlers (CQRS write side) + message/event consumers (IConsumer/I*EventHandler) — that mutate persistent state; runs on any repo with mutations, not only event-driven ones. Every mutation is classified exhaustively and deterministically: guarded, at risk on positive evidence, or not classified; the score is over the classified ones and is withheld when they are fewer than half.

GD1 · Unfinished & placeholder code10.0 / 10Exemplary✓ Tool-verified

Other · Code Health — Unreviewed-generation residue: shipped members still throwing NotImplementedException, and placeholder string literals left in non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.

Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.

  • A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface. (×2) — src/back-end/Senparc.Xncf.Installer/Register.cs:60, src/back-end/Senparc.Xncf.Installer/Register.cs:62

What to do

  • Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
IC1 · Incompleteness & stubs7.1 / 10Strong✓ Tool-verified

Other · Code Health — Unfinished work detected by code SHAPE, not keywords: members that only throw a "not implemented" exception, methods that take inputs and return a constant, async methods that never await, dead `if (false)` / `#if false` branches, and skeleton types most of whose members are holes. A real, objective slice of technical debt.

Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.

  • `OnGetAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — REDACTED:30
  • `OnGetRequestTenantInfoAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — REDACTED:35
  • `InitAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — src/back-end/Senparc.Areas.Admin/Domain/Services/AdminUserInfoService.cs:384
  • `OnVoiceRequestAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — src/back-end/Senparc.Areas.Admin/MyMessageHandler.cs:44
  • `AfterRunBotAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — src/back-end/Senparc.Areas.Admin/MyMessageHandler.cs:55
  • `DatabaseUniquePrefix` is a shipped property whose accessors only throw NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — src/back-end/Senparc.Xncf.Installer/Register.cs:60
  • `TryGetXncfDatabaseDbContextType` is a shipped property whose accessors only throw NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — src/back-end/Senparc.Xncf.Installer/Register.cs:62
  • A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×33) — src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/AdminUserInfo/Edit.cshtml.cs:71, src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/AdminUserInfo/Index.cshtml.cs:86, src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Index.cshtml.cs:51, …

What to do

  • Finish or delete the unfinished stubs (NotImplementedException / empty / constant-returning bodies) — they are dead surface that looks live.
  • Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
M1 · Documentation (README)7.7 / 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 build/run (quick start) section to the root README — the first thing a newcomer needs.
  • Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
  • Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
  • Add a README to the 2 of 12 project(s) that lack one — worth up to 0.3 pts.
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.

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.

P10 · Library API & versioning6.0 / 10Strong✓ Tool-verified

Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.

Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.

  • 61/66 types (92%) are public. For a library, every public type is a stability contract — make internal-by-default and expose only the intended API.

What to do

  • Make types internal by default; expose only the deliberate public API so internals can change without breaking consumers.
P2 · Observability8.2 / 10Exemplary✓ 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.

  • Only 4/10 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 10, 7 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
  • `src/back-end/Senparc.Areas.Admin/Domain/Services/AdminChatAiService.cs` reports through `Console.Write…` at line 501 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — src/back-end/Senparc.Areas.Admin/Domain/Services/AdminChatAiService.cs:501
  • `src/back-end/Senparc.Areas.Admin/Domain/Services/AdminChatAiService.cs` reports through `Console.Write…` at line 504 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — src/back-end/Senparc.Areas.Admin/Domain/Services/AdminChatAiService.cs:504
  • `src/back-end/Senparc.Xncf.Installer/Domain/Services/InstallerService.cs` reports through `Console.Write…` at line 191 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — src/back-end/Senparc.Xncf.Installer/Domain/Services/InstallerService.cs:191
  • `src/back-end/Senparc.Xncf.Installer/Domain/Services/InstallerService.cs` reports through `Console.Write…` at line 361 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — src/back-end/Senparc.Xncf.Installer/Domain/Services/InstallerService.cs:361
  • `src/back-end/Senparc.Xncf.Installer/Domain/Services/InstallOptionsService.cs` reports through `Console.Write…` at line 160 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — src/back-end/Senparc.Xncf.Installer/Domain/Services/InstallOptionsService.cs:160
  • `REDACTED` reports through `Console.Write…` at line 51 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — REDACTED:51
  • `REDACTED` reports through `Console.Write…` at line 52 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — REDACTED:52
  • `REDACTED` reports through `Console.Write…` at line 53 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — REDACTED:53
  • `REDACTED` reports through `Console.Write…` at line 124 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — REDACTED:124
  • `src/back-end/Senparc.Xncf.Accounts/Program.cs` reports through `Console.Write…` at line 48 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — src/back-end/Senparc.Xncf.Accounts/Program.cs:48
  • `src/back-end/Senparc.Xncf.Accounts/Program.cs` reports through `Console.Write…` at line 49 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — src/back-end/Senparc.Xncf.Accounts/Program.cs:49
  • `src/back-end/Senparc.Xncf.Accounts/Program.cs` reports through `Console.Write…` at line 50 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — src/back-end/Senparc.Xncf.Accounts/Program.cs:50
  • `src/back-end/Senparc.Xncf.Accounts/Program.cs` reports through `Console.Write…` at line 109 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — src/back-end/Senparc.Xncf.Accounts/Program.cs:109
  • `src/back-end/Senparc.Xncf.Accounts/Program.cs` reports through `Console.Write…` at line 113 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — src/back-end/Senparc.Xncf.Accounts/Program.cs:113

What to do

  • Extend structured logging across the projects you operate, and give the library ones a diagnostics seam instead — an `EventSource`/`ActivitySource` the host can subscribe to, or an optional logger on your options object — rather than taking a logging dependency on your consumers' behalf.
  • Replace `Console.Write…` in service code with the project's injected `ILogger<T>` (message templates with named properties), so delivery outcomes and failures reach the log pipeline with a level and a category.
P4 · Deployment & Rollback5.0 / 10Adequate✓ 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.

  • Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
  • Deployment is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever reaches the release trigger goes to production unreviewed, so a mistaken merge or tag is live before anyone can stop it.

What to do

  • Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
  • Add an approval/environment gate (required reviewers / protection rules) before production promotion.
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.

P7 · Outbound HTTP resilience10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.

Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.

P8 · Schema migrations10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — Whether EF Core schema changes go through versioned migrations rather than the un-evolvable EnsureCreated().

Method: Roslyn scan: EF Core DbContext for a versioned migrations directory versus bare EnsureCreated usage; off .NET, a file scan of dependency manifests, migration histories (Flyway, Liquibase, Alembic, Django, Rails, Prisma, TypeORM, Knex/Sequelize, golang-migrate, goose, Laravel, Doctrine, Diesel/sqlx) and schema auto-create in production source or config. Exhaustive, deterministic.

PF1 · Benchmark discipline6.0 / 10Strong✓ Tool-verified

Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.

Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.

  • No benchmark suite was found by the two searches this check runs. FIRST, a BenchmarkDotNet package reference in any project file — every project the workspace loaded, plus a walk of project files on disk that never loaded, because a benchmark suite is exactly the project a partial load drops. SECOND, a script harness: a file whose name contains `benchmark` and ends `.py`, `.sh`, `.ps1`, `.bash`, `.rb`, `.js` or `.mjs`, credited ONLY when this repository's CI text also mentions benchmarks — a harness no pipeline runs is read as a fixture, deliberately. Neither search can see a benchmark suite in another ecosystem's idiom (a Go `testing.B` file, a JMH or criterion project, a pytest-benchmark run), so this is 'no benchmark found by those two searches', not a verdict that the repository has none. Where code is performance-sensitive, a benchmark guards against silent regressions — but it's a bonus here, not a deduction.

What to do

  • Add a benchmarking harness for the hot paths and run it in CI to catch regressions (for .NET, a BenchmarkDotNet project with [MemoryDiagnoser] to track allocations).
PF3 · Async & latency hygiene8.5 / 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 each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.

  • 1 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • `.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). — src/back-end/Senparc.Xncf.Accounts/Domain/OperationQueue/OperationQueue.cs:72

What to do

  • Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult().
R1 · Type Safety0.0 / 10Critical✓ Tool-verified

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

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

  • 0 typed · 198 plain JS — the untyped files are src/back-end/Tests/Senparc.Areas.Admin.Tests/Client/AdminFooterLifecycleTests.js, src/back-end/Tests/Senparc.Areas.Admin.Tests/Client/AgentsA2AHealthTests.js, src/back-end/Tests/Senparc.Areas.Admin.Tests/Client/AgentsGroupStartMentionsTests.js, src/back-end/Tests/Senparc.Areas.Admin.Tests/Client/AgentsOverviewDashboardTests.js, src/back-end/Tests/Senparc.Areas.Admin.Tests/Client/AgentsSystemMessageTypeTests.js, src/back-end/Tests/Senparc.Areas.Admin.Tests/Client/HostMetricsDashboardTests.js (+192 more).

What to do

  • Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
R10 · Code Duplication9.3 / 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.

  • 10 duplicated blocks under src/front-end/ have copies in at least two of the sibling directories Senparc.Xncf.Admin, Senparc.Xncf.AdminModule, Senparc.Xncf.XncfStore — 8 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 10 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 10 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 10 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/lightdemo/antv.vue:352
  • src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/lightdemo/antv.vue:352 · src/front-end/Senparc.Xncf.AdminModule/src/views/XncfStore/lightdemo/antv.vue:352 · src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/views/Senparc.Xncf.XncfStore/processdemo/antv.vue:352 — these 3 files are line-for-line copies of one another — 369 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. — src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/lightdemo/antv.vue:352
  • src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/lightdemo/antvShow.vue:18 · src/front-end/Senparc.Xncf.AdminModule/src/views/XncfStore/lightdemo/antvShow.vue:18 · src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/views/Senparc.Xncf.XncfStore/processdemo/antvShow.vue:18 — 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. — src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/lightdemo/antvShow.vue:18
  • src/front-end/Senparc.Xncf.Admin/src/components/Upload/SingleImage.vue:32 · src/front-end/Senparc.Xncf.Admin/src/components/Upload/SingleImage3.vue:40 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — src/front-end/Senparc.Xncf.Admin/src/components/Upload/SingleImage.vue:32
  • src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/shopping/detail.vue:318 · src/front-end/Senparc.Xncf.AdminModule/src/views/XncfStore/shopping/detail.vue:320 — 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. — src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/shopping/detail.vue:318
  • src/front-end/Senparc.Xncf.Admin/src/components/Upload/SingleImage.vue:32 · src/front-end/Senparc.Xncf.Admin/src/components/Upload/SingleImage2.vue:32 · src/front-end/Senparc.Xncf.Admin/src/components/Upload/SingleImage3.vue:40 — the 3 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — src/front-end/Senparc.Xncf.Admin/src/components/Upload/SingleImage.vue:32
  • src/front-end/Senparc.Xncf.Admin/src/views/dashboard/admin/components/PieChart.vue:10 · src/front-end/Senparc.Xncf.Admin/src/views/dashboard/admin/components/RaddarChart.vue:12 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/front-end/Senparc.Xncf.Admin/src/views/dashboard/admin/components/PieChart.vue:10
  • src/front-end/Senparc.Xncf.Admin/plop-templates/component/prompt.js:8 · src/front-end/Senparc.Xncf.Admin/plop-templates/view/prompt.js:8 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/front-end/Senparc.Xncf.Admin/plop-templates/component/prompt.js:8
  • src/front-end/Senparc.Xncf.Admin/src/components/Charts/Keyboard.vue:9 · src/front-end/Senparc.Xncf.Admin/src/components/Charts/LineMarker.vue:9 · src/front-end/Senparc.Xncf.Admin/src/components/Charts/MixChart.vue:9 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/front-end/Senparc.Xncf.Admin/src/components/Charts/Keyboard.vue:9
  • src/front-end/Senparc.Xncf.Admin/src/views/dashboard/admin/components/BarChart.vue:10 · src/front-end/Senparc.Xncf.Admin/src/views/dashboard/admin/components/PieChart.vue:10 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/front-end/Senparc.Xncf.Admin/src/views/dashboard/admin/components/BarChart.vue:10
  • src/front-end/Senparc.Xncf.Admin/src/utils/antvSetting.js:39 · src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/lightdemo/antvShow.vue:27 · src/front-end/Senparc.Xncf.AdminModule/src/views/XncfStore/lightdemo/antvShow.vue:27 · src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/views/Senparc.Xncf.XncfStore/processdemo/antvShow.vue:27 — the 4 copies are spread across 4 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/front-end/Senparc.Xncf.Admin/src/utils/antvSetting.js:39
  • src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/shopping/application.vue:182 · src/front-end/Senparc.Xncf.AdminModule/src/views/XncfStore/shopping/application.vue: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. — src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/shopping/application.vue:182
  • src/front-end/Senparc.Xncf.Admin/src/components/Charts/mixins/resize.js:1 · src/front-end/Senparc.Xncf.Admin/src/views/dashboard/admin/components/mixins/resize.js:1 — the two spans are one implementation copied and then locally edited — 121 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/front-end/Senparc.Xncf.Admin/src/components/Charts/mixins/resize.js:1
  • src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/shopping/Index.vue:143 · src/front-end/Senparc.Xncf.AdminModule/src/views/XncfStore/shopping/Index.vue:139 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/shopping/Index.vue:143
  • src/front-end/Senparc.Xncf.Admin/src/views/Admin/Menu/Index.vue:386 · src/front-end/Senparc.Xncf.Admin/src/views/Admin/TenantInfo/Index.vue:272 — the two spans are one implementation copied and then locally edited — 108 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/front-end/Senparc.Xncf.Admin/src/views/Admin/Menu/Index.vue:386
  • src/front-end/Senparc.Xncf.Admin/src/store/modules/tagsView.js:82 · src/front-end/Senparc.Xncf.Admin/src/store/modules/tagsView.js:105 — 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. — src/front-end/Senparc.Xncf.Admin/src/store/modules/tagsView.js:82
  • src/front-end/Senparc.Xncf.Admin/src/views/Admin/XncfModule/Start.vue:888 · src/front-end/Senparc.Xncf.Admin/src/views/Admin/XncfModule/Start.vue:909 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/front-end/Senparc.Xncf.Admin/src/views/Admin/XncfModule/Start.vue:888
  • src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/operation/application.vue:100 · src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/views/Senparc.Xncf.XncfStore/operation/application.vue:213 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/operation/application.vue:100
  • src/front-end/Senparc.Xncf.Admin/mock/utils.js:5 · REDACTED:164 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — src/front-end/Senparc.Xncf.Admin/mock/utils.js:5
  • src/front-end/Senparc.Xncf.Admin/src/views/Admin/AdminUserInfo/Index.vue:417 · src/front-end/Senparc.Xncf.Admin/src/views/Admin/AdminUserInfo/Index.vue:439 — 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. — src/front-end/Senparc.Xncf.Admin/src/views/Admin/AdminUserInfo/Index.vue:417
  • src/front-end/Senparc.Xncf.Admin/src/views/Admin/Menu/Index.vue:386 · src/front-end/Senparc.Xncf.Admin/src/views/Admin/SystemConfig/Index.vue:146 — the two spans are one implementation copied and then locally edited — 62 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/front-end/Senparc.Xncf.Admin/src/views/Admin/Menu/Index.vue:386
  • src/front-end/Senparc.Xncf.Admin/src/views/Admin/Role/Index.vue:340 · src/front-end/Senparc.Xncf.Admin/src/views/Admin/Role/Index.vue:398 — the two spans are one implementation copied and then locally edited — 70 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/front-end/Senparc.Xncf.Admin/src/views/Admin/Role/Index.vue:340
  • src/front-end/Senparc.Xncf.Admin/src/views/dashboard/admin/components/BarChart.vue:30 · src/front-end/Senparc.Xncf.Admin/src/views/dashboard/admin/components/LineChart.vue:46 · src/front-end/Senparc.Xncf.Admin/src/views/dashboard/admin/components/PieChart.vue:30 · src/front-end/Senparc.Xncf.Admin/src/views/dashboard/admin/components/RaddarChart.vue:32 — the 4 copies are spread across 4 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/front-end/Senparc.Xncf.Admin/src/views/dashboard/admin/components/BarChart.vue:30
  • src/front-end/Senparc.Xncf.Admin/mock/utils.js:30 · REDACTED:296 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — src/front-end/Senparc.Xncf.Admin/mock/utils.js:30
  • src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/views/Senparc.Xncf.XncfStore/shopping/application.vue:318 · src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/views/Senparc.Xncf.XncfStore/shopping/applicationall.vue:303 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/views/Senparc.Xncf.XncfStore/shopping/application.vue:318
  • src/front-end/Senparc.Xncf.Admin/src/views/Admin/XncfModule/Index.vue:564 · src/front-end/Senparc.Xncf.Admin/src/views/Admin/XncfModule/Index.vue:581 · src/front-end/Senparc.Xncf.Admin/src/views/Admin/XncfModule/Index.vue:598 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. — src/front-end/Senparc.Xncf.Admin/src/views/Admin/XncfModule/Index.vue:564
  • src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/shopping/detail.vue:356 · src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/views/Senparc.Xncf.XncfStore/shopping/detail.vue:422 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/shopping/detail.vue:356
  • src/front-end/Senparc.Xncf.Admin/src/components/DndList/index.vue:74 · src/front-end/Senparc.Xncf.Admin/src/components/DndList/index.vue:86 — 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. — src/front-end/Senparc.Xncf.Admin/src/components/DndList/index.vue:74
  • src/front-end/Senparc.Xncf.Admin/src/components/HeaderSearch/index.vue:47 · src/front-end/Senparc.Xncf.Admin/src/layout/components/TagsView/index.vue:55 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/front-end/Senparc.Xncf.Admin/src/components/HeaderSearch/index.vue:47
  • src/front-end/Senparc.Xncf.Admin/src/components/ImageCropper/utils/effectRipple.js:17 · src/front-end/Senparc.Xncf.Admin/src/directive/waves/waves.js:20 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — src/front-end/Senparc.Xncf.Admin/src/components/ImageCropper/utils/effectRipple.js:17
  • src/front-end/Senparc.Xncf.Admin/src/directive/clipboard/clipboard.js:8 · src/front-end/Senparc.Xncf.Admin/src/directive/clipboard/clipboard.js:29 — the two spans are one implementation copied and then locally edited — 66 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/front-end/Senparc.Xncf.Admin/src/directive/clipboard/clipboard.js:8
  • src/front-end/Senparc.Xncf.Admin/src/components/Dropzone/index.vue:112 · src/front-end/Senparc.Xncf.Admin/src/components/Dropzone/index.vue:121 — 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. — src/front-end/Senparc.Xncf.Admin/src/components/Dropzone/index.vue:112
  • src/front-end/Senparc.Xncf.Admin/src/components/Dropzone/index.vue:188 · src/front-end/Senparc.Xncf.Admin/src/components/Dropzone/index.vue:196 — 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. — src/front-end/Senparc.Xncf.Admin/src/components/Dropzone/index.vue:188
  • src/front-end/Senparc.Xncf.Admin/src/components/Tinymce/components/EditorImage.vue:65 · src/front-end/Senparc.Xncf.Admin/src/components/Tinymce/components/EditorImage.vue:76 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/front-end/Senparc.Xncf.Admin/src/components/Tinymce/components/EditorImage.vue:65

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

  • src/front-end/Senparc.Xncf.Admin/src/directive/el-table/adaptive.js:1 imports element-ui/src/utils/resize-event, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/front-end/Senparc.Xncf.Admin/src/directive/el-table/adaptive.js:1

What to do

  • Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
R2 · Cyclomatic Complexity9.6 / 10Exemplary✓ 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.

  • editForm has cyclomatic complexity 50 and cognitive complexity 65; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. (×3) — src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/lightdemo/antv.vue:560, src/front-end/Senparc.Xncf.AdminModule/src/views/XncfStore/lightdemo/antv.vue:557, src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/views/Senparc.Xncf.XncfStore/processdemo/antv.vue:560
  • handleRun has cyclomatic complexity 27 and cognitive complexity 39; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/front-end/Senparc.Xncf.Admin/src/views/Admin/XncfModule/Start.vue:859
  • (anonymous) has cyclomatic complexity 11 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. — src/front-end/Senparc.Xncf.Admin/src/store/modules/permission.js:166
  • searchInfo has cyclomatic complexity 11 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/views/Senparc.Xncf.XncfStore/shopping/Index.vue:211

What to do

  • Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
R3 · Large Files6.3 / 10Adequate✓ Tool-verified

React / JS · Code Health — How many source files exceed the large-file threshold.

Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.

  • src/front-end/Senparc.Xncf.Admin/src/components/ImageCropper/index.vue has 1772 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/front-end/Senparc.Xncf.Admin/src/components/ImageCropper/index.vue:1
  • src/front-end/Senparc.Xncf.Admin/src/views/Admin/XncfModule/Start.vue has 1215 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/front-end/Senparc.Xncf.Admin/src/views/Admin/XncfModule/Start.vue:1
  • src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/lightdemo/antv.vue has 1110 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/lightdemo/antv.vue:1
  • src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/views/Senparc.Xncf.XncfStore/processdemo/antv.vue has 1110 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/views/Senparc.Xncf.XncfStore/processdemo/antv.vue:1
  • src/front-end/Senparc.Xncf.AdminModule/src/views/XncfStore/lightdemo/antv.vue has 1106 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/front-end/Senparc.Xncf.AdminModule/src/views/XncfStore/lightdemo/antv.vue:1
  • src/front-end/Senparc.Xncf.Admin/src/views/Admin/XncfModule/Index.vue has 778 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/front-end/Senparc.Xncf.Admin/src/views/Admin/XncfModule/Index.vue:1
  • src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/views/Senparc.Xncf.XncfStore/shopping/detail.vue has 768 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/views/Senparc.Xncf.XncfStore/shopping/detail.vue:1
  • src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/shopping/detail.vue has 609 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/shopping/detail.vue:1
  • src/front-end/Senparc.Xncf.AdminModule/src/views/XncfStore/shopping/detail.vue has 605 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/front-end/Senparc.Xncf.AdminModule/src/views/XncfStore/shopping/detail.vue:1
  • src/front-end/Senparc.Xncf.Admin/src/views/Admin/AdminUserInfo/Index.vue has 543 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/front-end/Senparc.Xncf.Admin/src/views/Admin/AdminUserInfo/Index.vue:1
  • src/front-end/Senparc.Xncf.Admin/src/utils/antvSetting.js has 473 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/front-end/Senparc.Xncf.Admin/src/utils/antvSetting.js:1
  • src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/views/Senparc.Xncf.XncfStore/shopping/application.vue has 455 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/views/Senparc.Xncf.XncfStore/shopping/application.vue:1
  • src/front-end/Senparc.Xncf.Admin/src/views/Admin/Menu/Index.vue has 452 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/front-end/Senparc.Xncf.Admin/src/views/Admin/Menu/Index.vue:1
  • src/front-end/Senparc.Xncf.Admin/src/views/Admin/Role/Index.vue has 449 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/front-end/Senparc.Xncf.Admin/src/views/Admin/Role/Index.vue:1
  • src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/views/Senparc.Xncf.XncfStore/shopping/applicationall.vue has 435 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/views/Senparc.Xncf.XncfStore/shopping/applicationall.vue:1

What to do

  • Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage0.2 / 10Critical✓ Tool-verified

React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.

Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.

  • 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. (×40) — src/front-end/Senparc.Xncf.Admin/src/views/Admin/XncfModule/Start.vue:1, src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/lightdemo/antv.vue:1, src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/views/Senparc.Xncf.XncfStore/processdemo/antv.vue:1, …

What to do

  • Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness6.6 / 10Strong✓ Tool-verified

React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).

Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.

  • 34 outdated package(s); JS/npm CVEs scored in D30

What to do

  • Bump outdated dependencies to current versions to limit upgrade debt.
R6 · Tooling6.7 / 10Strong✓ Tool-verified

React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each REDACTED script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.

Method: REDACTED scanned for test/lint/typecheck script wiring. Deterministic presence check.

  • test ✓ · lint ✓ · typecheck ✗ — read from this repository's REDACTED scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.

What to do

  • Add type checking (adopt TypeScript, or type-check the existing JavaScript with `checkJs`) as REDACTED scripts and run them in CI.
R7 · Dead Code0.0 / 10Critical✓ 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.

  • 10 file(s) (~4028 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package.
  • Unreachable from the 9 application, 9 tooling and 17 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
  • no import path from any entry point (9 application, 9 tooling, 17 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 (×34) — src/front-end/Senparc.Xncf.Admin/src/views/Admin/XncfModule/Start.vue, src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/lightdemo/antv.vue, src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/views/Senparc.Xncf.XncfStore/processdemo/antv.vue, …
  • no import path from any entry point (9 application, 9 tooling, 17 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/front-end/Senparc.Xncf.Admin/src/views/Admin/Menu/Index.vue) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/front-end/Senparc.Xncf.Admin/src/views/Admin/Menu/icons.js
  • no import path from any entry point (9 application, 9 tooling, 17 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/lightdemo/antv.vue, src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/lightdemo/antvShow.vue) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/front-end/Senparc.Xncf.Admin/src/utils/antvSetting.js
  • no import path from any entry point (9 application, 9 tooling, 17 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/front-end/Senparc.Xncf.Admin/src/components/ImageCropper/index.vue) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/front-end/Senparc.Xncf.Admin/src/components/ImageCropper/utils/language.js
  • no import path from any entry point (9 application, 9 tooling, 17 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/front-end/Senparc.Xncf.Admin/src/components/Tinymce/index.vue) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/front-end/Senparc.Xncf.Admin/src/components/Tinymce/components/EditorImage.vue

What to do

  • Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene0.0 / 10Critical✓ 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 but not declared in any reachable REDACTED — installs work only by hoisting accident. — src/front-end/Senparc.Xncf.Admin/mock/mock-server.js:2
  • Declared in src/front-end/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.
R9 · Circular Imports10.0 / 10Exemplary✓ 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.

S1 · Web-Security Posture4.0 / 10Weak✓ Tool-verified

Other · Security — Transport security, security headers, secure cookies, input validation, middleware order and crypto hygiene (presence, not runtime).

Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.

  • None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
  • No UseHttpsRedirection/UseHsts and no reverse-proxy signal — transport security is unverified at the app layer. (−2.0 on this card.)
  • No ModelState/[ApiController]/FluentValidation signal — inbound payloads reach handlers unvalidated. (−2.0 on this card.)

What to do

  • Add security response headers (Content-Security-Policy first, then Strict-Transport-Security, X-Content-Type-Options and a frame policy) — defense in depth, even when a reverse proxy could set them.
  • Enforce HTTPS at the app layer (UseHttpsRedirection / UseHsts) — only skip this if a reverse proxy demonstrably terminates TLS.
  • Validate inbound models (ModelState/[ApiController]/FluentValidation) to reduce injection and bad-data risk.
X1 · Async correctness7.7 / 10Strong✓ Tool-verified

Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.

Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.

  • `Thread.Sleep` parks the thread for the whole delay: no other work runs on it, and under load the pool must grow to make up for it. `await Task.Delay(…)` suspends only this method. — src/back-end/Senparc.Areas.Admin/OHS/Local/AppService/SystemInfoAppService.cs:267
  • This blocks on a Task **while holding a `lock`**, which is worse than an ordinary sync-over-async in two ways. `await` is illegal inside a `lock` body, so the usual fix — make the caller `async` and await it — cannot be applied where this block stands. And the thread parks while still holding the lock, so it occupies the critical section doing no work: every other caller serialises behind an operation that is only waiting, and if the awaited task itself needs a thread the pool has run out of, they wait forever. Do the async work OUTSIDE the critical section: take the lock only to read the shared state, release it, await the call, then re-take the lock to publish the result — re-checking on re-entry whether another caller won the race and, if so, discarding your result rather than overwriting theirs. Where the critical section genuinely has to span the async call, `lock` is the wrong primitive: use an async-aware one (`SemaphoreSlim` with `await WaitAsync()`) so waiters yield their thread instead of parking it. — src/back-end/Senparc.Xncf.Accounts/Domain/OperationQueue/OperationQueue.cs:72
  • `FileStream.Flush` blocks the thread on I/O while `FileStream.FlushAsync` exists to wait without one — inside a method that is already `async`, await the twin. — src/back-end/Senparc.Xncf.Accounts/Domain/OperationQueue/OperationQueueService.cs:48

What to do

  • Blocking `Thread.Sleep` inside an `async` method
X12 · Unreachable branch10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.

Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.

X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.

Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.

X14 · Bypassable address classification10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.

Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.

X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.

Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.

X16 · Unfloored truncation loop10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.

Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.

X17 · Uncapped recursion over a caller-supplied document10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.

Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.

X18 · Disposal-pattern correctness10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.

Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.

X19 · Unrestored process-global state10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.

Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.

X2 · Cancellation propagation6.3 / 10Adequate✓ Tool-verified

Other · Code Health — Whether async methods accept a CancellationToken so work can be cancelled (adoption curve).

Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.

  • Only 29/74 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
  • No CancellationToken parameter — this work can't be stopped early once started. (×31) — src/back-end/Senparc.Areas.Admin/ACL/Repository/SysMenuRepository.cs:42, src/back-end/Senparc.Areas.Admin/ACL/Repository/SysMenuRepository.cs:76, src/back-end/Senparc.Areas.Admin/ACL/Repository/SysRolePermissionRepository.cs:34, …
  • No CancellationToken parameter — the body observes an ambient token instead (a field or a context object), so the work does stop on cancellation, but a caller cannot cancel this call independently of the owner that created that token. (×8) — src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/NeuCharPivot/Aggregate.cshtml.cs:39, src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/NeuCharPivot/Aggregate.cshtml.cs:49, src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/NeuCharPivot/Aggregate.cshtml.cs:89, …

What to do

  • Thread a CancellationToken through async methods so work stops promptly on cancellation.
X20 · Mistyped argument guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `ArgumentNullException` tells the caller a parameter was null when it provably was not.

Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements controlled by an `if`, whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`). Deterministic, provable per finding. Advisory.

X21 · Side-effecting pattern guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.

Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.

X22 · Contradicted release guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back. Also whether a `finally` that gives the primitive back unconditionally can run in a state where the method does not hold it: after a timed wait whose result was discarded, after an acquire inside the `try` that can fail, after the body already released it, or never, because a `return` left between the acquire and the `try`.

Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.

X23 · Unguarded diagnostic materialisation10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.

Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.

X24 · Document value interpolated into markup unescaped2.8 / 10Weak✓ Tool-verified

Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.

Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.

  • `System.Text.Json.JsonSerializer.Serialize(Model.InitialMessage ?? string.Empty)` is text this program did not author, and it is written into the text of an element through Razor's `Html.Raw` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/AdminChat/Chat.cshtml:413
  • `System.Text.Json.JsonSerializer.Serialize(Model.ModuleUids ?? string.Empty)` is text this program did not author, and it is written into the text of an element through Razor's `Html.Raw` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/AdminChat/Chat.cshtml:415
  • `System.Text.Json.JsonSerializer.Serialize(DateTimeOffset.Now)` is text this program did not author, and it is written into the text of an element through Razor's `Html.Raw` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Shared/_Layout_Vue.cshtml:260
  • `System.Text.Json.JsonSerializer.Serialize(currentAccountName)` is text this program did not author, and it is written into the text of an element through Razor's `Html.Raw` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Shared/_Layout_Vue.cshtml:261
  • `System.Text.Json.JsonSerializer.Serialize(AR["Admin.Session.Title"].Value)` is text this program did not author, and it is written into the text of an element through Razor's `Html.Raw` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Shared/_Layout_Vue.cshtml:276
  • `System.Text.Json.JsonSerializer.Serialize(AR["Admin.Session.Message"].Value)` is text this program did not author, and it is written into the text of an element through Razor's `Html.Raw` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Shared/_Layout_Vue.cshtml:277
  • `System.Text.Json.JsonSerializer.Serialize(AR["Admin.Session.KeepLogin"].Value)` is text this program did not author, and it is written into the text of an element through Razor's `Html.Raw` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Shared/_Layout_Vue.cshtml:278
  • `System.Text.Json.JsonSerializer.Serialize(AR["Admin.Session.LogoutNow"].Value)` is text this program did not author, and it is written into the text of an element through Razor's `Html.Raw` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Shared/_Layout_Vue.cshtml:279
  • `System.Text.Json.JsonSerializer.Serialize(AR["Admin.Session.KeepLoginSuccess"].Value)` is text this program did not author, and it is written into the text of an element through Razor's `Html.Raw` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Shared/_Layout_Vue.cshtml:280
  • `translationsJson` is text this program did not author, and it is written into the text of an element through Razor's `Html.Raw` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Shared/_LocalizationScripts.cshtml:15
  • `JsonSerializer.Serialize(sourceTranslations)` is text this program did not author, and it is written into the text of an element through Razor's `Html.Raw` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Shared/_LocalizationScripts.cshtml:161
  • `System.Globalization.CultureInfo.CurrentUICulture.Name` is text this program did not author, and it is written into a quoted attribute value through `ContentResult` with an HTML content type with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/back-end/Senparc.Web/Pages/Index.cshtml.cs:79
  • `title` is text this program did not author, and it is written into the text of an element through `ContentResult` with an HTML content type with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×2) — src/back-end/Senparc.Web/Pages/Index.cshtml.cs:84, src/back-end/Senparc.Web/Pages/Index.cshtml.cs:94
  • `message` is text this program did not author, and it is written into the text of an element through `ContentResult` with an HTML content type with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/back-end/Senparc.Web/Pages/Index.cshtml.cs:95
  • `link` is text this program did not author, and it is written into the text of an element through `ContentResult` with an HTML content type with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/back-end/Senparc.Web/Pages/Index.cshtml.cs:96
  • `JsonSerializer.Serialize(strings)` is text this program did not author, and it is written into the text of an element through Razor's `Html.Raw` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/back-end/Senparc.Web/Pages/Shared/_LocalizationScripts.cshtml:8
  • `System.Text.Json.JsonSerializer.Serialize(new { started = IR["Install.AlreadyRunning"].Value, startConfirm = IR["Install.Confirm"].Value, startConfirmDetail = IR["Install.ConfirmDetail"].Value, confirmButtonText = IR["Install.ConfirmButton"].Value, cancelButtonText = IR["Install.CancelButton"].Value, startedWaiting = IR["Install.StartedWaiting"].Value, failedPrefix = IR["Install.FailedPrefix"].Value, loadOptionsFailed = IR["Install.LoadOptionsFailed"].Value })` is text this program did not author, and it is written into the text of an element through Razor's `Html.Raw` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/back-end/Senparc.Xncf.Installer/Areas/Install/Pages/Index.cshtml:137
  • `String(value||'')` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/back-end/Senparc.Areas.Admin/wwwroot/js/Admin/Pages/XncfModule/start.js:96
  • `(window.ncfInstallI18n&&window.ncfInstallI18n.startedWaiting)||'Installation started, please wait...'` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/back-end/Senparc.Xncf.Installer/wwwroot/js/Installer/Pages/index.js:86
  • `res.data` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/back-end/Senparc.Xncf.Installer/wwwroot/js/Installer/Pages/index.js:93
  • `((window.ncfInstallI18n&&window.ncfInstallI18n.failedPrefix)||'Install failed:')+error` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/back-end/Senparc.Xncf.Installer/wwwroot/js/Installer/Pages/index.js:95
  • `val` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:188
  • `runResult.tip` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/front-end/Senparc.Xncf.Admin/src/views/Admin/XncfModule/Start.vue:562
  • `runResult.msg` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/front-end/Senparc.Xncf.Admin/src/views/Admin/XncfModule/Start.vue:563
  • `scope.row.key.storyHtml` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/front-end/Senparc.Xncf.Admin/src/views/Admin/XncfModule/Start.vue:606

What to do

  • Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
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, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.

Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.

X26 · Unsynchronised callback handoff10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.

Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.

X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a `foreach` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is enumerating invalidates the enumerator it is holding, so the next `MoveNext` throws `InvalidOperationException` and the remaining items are never seen.

Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.

X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.

Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.

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.

X3 · Exception handling6.8 / 10Strong✓ Tool-verified

Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.

Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.

  • An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×2) — src/back-end/Senparc.Areas.Admin/Domain/SeparcTraceManager/SenparcTraceHelper.cs:448, src/back-end/Senparc.Areas.Admin/OHS/Local/Controllers/AdminChatStreamController.cs:154
  • `catch (JsonException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. — src/back-end/Senparc.Areas.Admin/Domain/Services/NeuCharPivotService.cs:314

What to do

  • Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.

Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.

X32 · Type resolved by simple name across every loaded assembly10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a plugin lookup names the type it means — searching every assembly loaded into the process for a candidate whose SIMPLE name equals a string supplied at runtime, and taking the first one found, is decided by assembly LOAD ORDER rather than by this source, so the same name can resolve to a different type on the next run.

Method: Roslyn syntax only, no semantic model: every invocation of `First`/`FirstOrDefault`/`Single`/`SingleOrDefault` whose OWN expression subtree contains both a `GetAssemblies()` call and a `GetTypes()`/`GetExportedTypes()` call — a single-element pick out of every type loaded into the process. A nested selector in the same chain sees no `GetAssemblies()` in its own subtree and is outside the population, so one lookup counts once however many links its chain has. A finding additionally needs both remaining halves: the selector must be `First`/`FirstOrDefault` (`Single`/`SingleOrDefault` reports the ambiguity rather than resolving it, and is counted and never reported), and the chain must carry an `==` comparison of `<lambda parameter>.Name` against something that is not a literal. The receiver must be a plain identifier bound by one of the chain’s own lambdas, which places `assembly.GetName().Name == "X"` outside the rule by construction. One exemption: a `.Name` test joined by `&&` to a `FullName`/`AssemblyQualifiedName` test on the same identifier is spared; joined by `||` it is not. Deterministic, provable per finding. Advisory.

X4 · Structured logging10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.

Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `REDACTED` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.

X5 · Nullable reference types5.3 / 10Adequate✓ Tool-verified

Other · Code Health — Whether nullable reference types are enabled and not undermined by heavy `!` suppression.

Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.

  • This method contradicts itself about `runner`: line 378 writes `runner?.Kernel`, which says `runner` can be null, but line 381 then dereferences it directly as `runner.RunChatAsync` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `runner` truly cannot be null here, the `?.` is misleading. Settle it one way — test `runner` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side. — src/back-end/Senparc.Areas.Admin/Domain/Services/AdminChatAiService.cs:381
  • This method contradicts itself about `taskFunc`: line 477 assigns it with `as Task`, which hands back null rather than throwing when the value is not a `Task`, but line 478 then dereferences it directly as `taskFunc.ConfigureAwait` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `taskFunc` once before the first use and handle the null case, or cast with `(Task)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/back-end/Senparc.Areas.Admin/OHS/Local/AppService/ModuleAppService.cs:478
  • This method contradicts itself about `result`: line 484 assigns it with `as IAppResponse`, which hands back null rather than throwing when the value is not a `IAppResponse`, but line 504 then dereferences it directly as `result.Data` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `result` once before the first use and handle the null case, or cast with `(IAppResponse)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/back-end/Senparc.Areas.Admin/OHS/Local/AppService/ModuleAppService.cs:504
  • This method contradicts itself about `ctx`: line 107 assigns it with `as AccountSenparcEntities`, which hands back null rather than throwing when the value is not a `AccountSenparcEntities`, but line 108 then dereferences it directly as `ctx.Set` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `ctx` once before the first use and handle the null case, or cast with `(AccountSenparcEntities)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/back-end/Senparc.Xncf.Accounts/Program.cs:108
  • 5/12 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.

What to do

  • Where a method uses `?.` on a symbol and then dereferences it directly, settle the question once: test it before the first use and handle null, or drop the `?.`.
  • Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.

WCAG coverage — what static analysis assessed

Statically assessed 15 of 55 WCAG 2.2 Level A/AA success criteria (27%; ≈30% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 40 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).

DimensionWCAG 2.2 A/AA criteriaCoverage
AC1 · Text alternatives1.1.1, 1.2.2, 1.2.5Partial signal
AC2 · Forms & labels1.3.1, 3.3.2, 4.1.2Partial signal
AC3 · Page structure1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2Partial signal
AC4 · Keyboard semantics2.1.1, 2.4.3Partial signal
AC5 · ARIA correctness4.1.2Partial signal
AC6 · Visual & motion safety1.4.3, 2.4.7Partial — literal CSS only
AC7 · A11y enforcementenforcement — no page criterionEnforcement posture (process)

Not statically assessed — these 40 Level A/AA criteria need runtime or manual evaluation (WCAG-EM): 1.2.1, 1.2.3, 1.2.4, 1.3.2, 1.3.3, 1.3.4, 1.3.5, 1.4.1, 1.4.2, 1.4.5, 1.4.10, 1.4.11, 1.4.12, 1.4.13, 2.1.2, 2.1.4, 2.2.2, 2.3.1, 2.4.4, 2.4.5, 2.4.6, 2.4.11, 2.5.1, 2.5.2, 2.5.3, 2.5.4, 2.5.7, 2.5.8, 3.1.2, 3.2.1, 3.2.2, 3.2.3, 3.2.4, 3.2.6, 3.3.1, 3.3.3, 3.3.4, 3.3.7, 3.3.8, 4.1.3.

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.

LensScoreRatingImpact
Code Health32%Weak — gated by D17, R1, R7Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture80%Adequate — gated by AX2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity90%ExemplarySolid.
Readiness35%Adequate — gated by D13, R4, R8Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security36%Weak — gated by D28, D29Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Domain Modelling41%Adequate — gated by DM2, DM6, DM7Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Event-Driven100%ExemplaryStrongest area.
Accessibility30%Weak — gated by AC4, AC6Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance71%StrongSolid.
Unscored — 5 check(s) recorded observations but carry no score

These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.

  • P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
  • SC1 Supply-chain hygiene — 5 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X10 Duplicated predicate — 19 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 8 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X9 Subsumed condition operand — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for

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

  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 36 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.

  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • 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 Aspire AppHost did not expose a crawlable HTTP endpoint in time (or only the dashboard) — 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 the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
  • C2 Access Controls — This is a dotnet-new template — authorization is deferred to the application you build from it. Add [Authorize]/policies (or imperative guards) when you wire up real users; until then there are no real endpoints to protect.
  • C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
  • C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
  • C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
  • D1 Cyclomatic Complexity — cyclomatic complexity not measured — .js, .vue exposed no member bodies
  • D12 Dependency Hygiene — Dependency hygiene not measured
  • D16 Bus Factor — single-maintainer repository — bus factor is not applicable
  • D2 Cognitive Complexity — cognitive complexity not measured — .js, .vue exposed no member bodies
  • D20 ADR Quality — N/A — this repo declares itself a template / kata / sample / demo; a formal ADR log is deferred to a real application built from it.
  • D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; JavaScript, html not measured.
  • D23 Boundary Type-Coupling — small single-context codebase (19,154 production LoC in the .NET projects) — bounded contexts are not needed at this size No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Aggregate roots were found in only one source directory (back-end), which is a layered codebase, not two contexts. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D25 ADR Conformance — no ADRs to check
  • D3 God Classes — Most of this repository's production source (.html, .js, .vue) was not read by god-class detection, so class size was not assessed for the languages that are the product — whatever else this pass did read is not this repository's class size. Not scored — this is a gap in the analyzer, not a verdict about this repository.
  • D32 Data Compliance (PII/GDPR) — 24 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
  • D36 Supply-chain Provenance & Signing — This is a dotnet-new template — it produces no released artifact to attest. Supply-chain provenance, signing and SBOM are deferred to the application you build from it (add SLSA provenance / cosign signing / an SBOM in your app's release pipeline).
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
  • D8 Code Coverage — Coverage not measured — .NET and JavaScript/TypeScript suite
  • DM10 One transaction, one aggregate — no repository writes detected — no operation to judge against the one-aggregate rule
  • DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
  • ED2 Event/command shape — no command-shaped messages detected — single-handler-per-command check not applicable
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • M2 Architecture documentation — This repo declares itself a template / kata / sample / demo — formal architecture documentation (ADRs, C4 diagrams) is deferred to a real application built from it, so its absence is not a defect here.
  • M4 Documentation accuracy — Not applicable: the 31 current-state document(s) make no claim of a kind M4 checks. 28 claim(s) of kinds M4 does not check were not checked (path 10, command argument 13, install 3, environment variable 2); M4 checks only links and versions and artefact counts.
  • P3 Security & performance tooling — This repo declares itself a template / kata / sample / demo — code meant to be read or copied, not operated. SAST, secret/dependency scanning and performance benchmarks are deferred to the application you build from it, so their absence is not a defect here. The dimension reactivates once the repo becomes a real app.
  • P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
  • PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
  • X6 Hand-rolled structured-format parsing — 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 — 445 finding(s)
D30 · Dependency Vulnerabilities · High CVE · ×161
  • 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
  • + 136 more in this group — see findings.md.
D30 · Dependency Vulnerabilities · Critical CVE · ×53
  • 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
  • + 28 more in this group — see findings.md.
DM6 · Domain ↔ infrastructure boundary · Domain depends on infrastructure · ×40
  • Domain depends on infrastructure: Add_Chat_Tables src/back-end/Senparc.Areas.Admin/Domain/Migrations/Dm/20260325233351_Add_Chat_Tables.cs:9 — `Add_Chat_Tables` (domain layer) names `Migration` from `Microsoft.EntityFrameworkCore.Migrations` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: Add_Chat_Tables src/back-end/Senparc.Areas.Admin/Domain/Migrations/Dm/20260325233351_Add_Chat_Tables.cs:12 — `Add_Chat_Tables` (domain layer) names `MigrationBuilder` from `Microsoft.EntityFrameworkCore.Migrations` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: Add_Chat_Tables src/back-end/Senparc.Areas.Admin/Domain/Migrations/Dm/20260325233351_Add_Chat_Tables.cs:91 — `Add_Chat_Tables` (domain layer) names `ReferentialAction` from `Microsoft.EntityFrameworkCore.Migrations` — a persistence type (in a method body). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: Add_Chat_Tables src/back-end/Senparc.Areas.Admin/Domain/Migrations/Dm/20260325233351_Add_Chat_Tables.cs:120 — `Add_Chat_Tables` (domain layer) names `ReferentialAction` from `Microsoft.EntityFrameworkCore.Migrations` — a persistence type (in a method body). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: Add_Chat_Tables src/back-end/Senparc.Areas.Admin/Domain/Migrations/Dm/20260325233351_Add_Chat_Tables.cs:135 — `Add_Chat_Tables` (domain layer) names `MigrationBuilder` from `Microsoft.EntityFrameworkCore.Migrations` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: Add_LoginTimeout src/back-end/Senparc.Areas.Admin/Domain/Migrations/Dm/20260704171548_Add_LoginTimeout.cs:25 — `Add_LoginTimeout` (domain layer) names `Migration` from `Microsoft.EntityFrameworkCore.Migrations` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: Add_LoginTimeout src/back-end/Senparc.Areas.Admin/Domain/Migrations/Dm/20260704171548_Add_LoginTimeout.cs:28 — `Add_LoginTimeout` (domain layer) names `MigrationBuilder` from `Microsoft.EntityFrameworkCore.Migrations` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: Add_LoginTimeout src/back-end/Senparc.Areas.Admin/Domain/Migrations/Dm/20260704171548_Add_LoginTimeout.cs:52 — `Add_LoginTimeout` (domain layer) names `MigrationBuilder` from `Microsoft.EntityFrameworkCore.Migrations` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: Add_NeuCharPivot_Workflow src/back-end/Senparc.Areas.Admin/Domain/Migrations/Dm/20260808150932_Add_NeuCharPivot_Workflow.cs:23 — `Add_NeuCharPivot_Workflow` (domain layer) names `Migration` from `Microsoft.EntityFrameworkCore.Migrations` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: Add_NeuCharPivot_Workflow src/back-end/Senparc.Areas.Admin/Domain/Migrations/Dm/20260808150932_Add_NeuCharPivot_Workflow.cs:26 — `Add_NeuCharPivot_Workflow` (domain layer) names `MigrationBuilder` from `Microsoft.EntityFrameworkCore.Migrations` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: Add_NeuCharPivot_Workflow src/back-end/Senparc.Areas.Admin/Domain/Migrations/Dm/20260808150932_Add_NeuCharPivot_Workflow.cs:174 — `Add_NeuCharPivot_Workflow` (domain layer) names `MigrationBuilder` from `Microsoft.EntityFrameworkCore.Migrations` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: Tune_NeuCharPivot_Storage src/back-end/Senparc.Areas.Admin/Domain/Migrations/Dm/20260808152032_Tune_NeuCharPivot_Storage.cs:22 — `Tune_NeuCharPivot_Storage` (domain layer) names `Migration` from `Microsoft.EntityFrameworkCore.Migrations` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: Tune_NeuCharPivot_Storage src/back-end/Senparc.Areas.Admin/Domain/Migrations/Dm/20260808152032_Tune_NeuCharPivot_Storage.cs:25 — `Tune_NeuCharPivot_Storage` (domain layer) names `MigrationBuilder` from `Microsoft.EntityFrameworkCore.Migrations` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: Tune_NeuCharPivot_Storage src/back-end/Senparc.Areas.Admin/Domain/Migrations/Dm/20260808152032_Tune_NeuCharPivot_Storage.cs:72 — `Tune_NeuCharPivot_Storage` (domain layer) names `MigrationBuilder` from `Microsoft.EntityFrameworkCore.Migrations` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: Add_NeuCharWorkflow_AutoSave_Versions src/back-end/Senparc.Areas.Admin/Domain/Migrations/Dm/20260808175020_Add_NeuCharWorkflow_AutoSave_Versions.cs:23 — `Add_NeuCharWorkflow_AutoSave_Versions` (domain layer) names `Migration` from `Microsoft.EntityFrameworkCore.Migrations` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: Add_NeuCharWorkflow_AutoSave_Versions src/back-end/Senparc.Areas.Admin/Domain/Migrations/Dm/20260808175020_Add_NeuCharWorkflow_AutoSave_Versions.cs:26 — `Add_NeuCharWorkflow_AutoSave_Versions` (domain layer) names `MigrationBuilder` from `Microsoft.EntityFrameworkCore.Migrations` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: Add_NeuCharWorkflow_AutoSave_Versions src/back-end/Senparc.Areas.Admin/Domain/Migrations/Dm/20260808175020_Add_NeuCharWorkflow_AutoSave_Versions.cs:72 — `Add_NeuCharWorkflow_AutoSave_Versions` (domain layer) names `MigrationBuilder` from `Microsoft.EntityFrameworkCore.Migrations` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: Add_AdminChatSessionWorkflows src/back-end/Senparc.Areas.Admin/Domain/Migrations/Dm/20260821135045_Add_AdminChatSessionWorkflows.cs:22 — `Add_AdminChatSessionWorkflows` (domain layer) names `Migration` from `Microsoft.EntityFrameworkCore.Migrations` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: Add_AdminChatSessionWorkflows src/back-end/Senparc.Areas.Admin/Domain/Migrations/Dm/20260821135045_Add_AdminChatSessionWorkflows.cs:24 — `Add_AdminChatSessionWorkflows` (domain layer) names `MigrationBuilder` from `Microsoft.EntityFrameworkCore.Migrations` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: Add_AdminChatSessionWorkflows src/back-end/Senparc.Areas.Admin/Domain/Migrations/Dm/20260821135045_Add_AdminChatSessionWorkflows.cs:52 — `Add_AdminChatSessionWorkflows` (domain layer) names `ReferentialAction` from `Microsoft.EntityFrameworkCore.Migrations` — a persistence type (in a method body). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: Add_AdminChatSessionWorkflows src/back-end/Senparc.Areas.Admin/Domain/Migrations/Dm/20260821135045_Add_AdminChatSessionWorkflows.cs:62 — `Add_AdminChatSessionWorkflows` (domain layer) names `MigrationBuilder` from `Microsoft.EntityFrameworkCore.Migrations` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: AdminSenparcEntities_DmModelSnapshot src/back-end/Senparc.Areas.Admin/Domain/Migrations/Dm/AdminSenparcEntities_DmModelSnapshot.cs:27 — `AdminSenparcEntities_DmModelSnapshot` (domain layer) names `DbContextAttribute` from `Microsoft.EntityFrameworkCore.Infrastructure` — a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: AdminSenparcEntities_DmModelSnapshot src/back-end/Senparc.Areas.Admin/Domain/Migrations/Dm/AdminSenparcEntities_DmModelSnapshot.cs:28 — `AdminSenparcEntities_DmModelSnapshot` (domain layer) names `ModelSnapshot` from `Microsoft.EntityFrameworkCore.Infrastructure` — a persistence type (as a base type). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: AdminSenparcEntities_DmModelSnapshot src/back-end/Senparc.Areas.Admin/Domain/Migrations/Dm/AdminSenparcEntities_DmModelSnapshot.cs:30 — `AdminSenparcEntities_DmModelSnapshot` (domain layer) names `ModelBuilder` from `Microsoft.EntityFrameworkCore` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it.
  • Domain depends on infrastructure: AdminSenparcEntities_DmModelSnapshot src/back-end/Senparc.Areas.Admin/Domain/Migrations/Dm/AdminSenparcEntities_DmModelSnapshot.cs:34 — `AdminSenparcEntities_DmModelSnapshot` (domain layer) names `DmValueGenerationStrategy` from `Microsoft.EntityFrameworkCore.Metadata` — a persistence type (in a method body). The domain should own a port and let an infrastructure adapter implement it.
  • + 15 more in this group — see findings.md.
D13 · REDACTED Scanning · Leaked secret · ×36
  • 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
  • + 11 more in this group — see findings.md.
AC2 · Forms & labels · <input> without a programmatic label · ×29
  • <input> without a programmatic label src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/AdminUserInfo/Edit.cshtml:26 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/AdminUserInfo/Edit.cshtml:27 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/AdminUserInfo/Edit.cshtml:34 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/AdminUserInfo/Edit.cshtml:42 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/AdminUserInfo/Edit.cshtml:57 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/AdminUserInfo/Edit.cshtml:68 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/AdminUserInfo/Edit.cshtml:79 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Menu/Edit.cshtml:56 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Menu/Edit.cshtml:66 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Menu/Edit.cshtml:76 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Menu/Edit.cshtml:86 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Menu/Edit.cshtml:122 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Menu/Edit.cshtml:132 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Menu/Edit.cshtml:145 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Menu/Edit.cshtml:152 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Menu/Edit.cshtml:159 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Role/Edit.cshtml:29 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Role/Edit.cshtml:39 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Role/Edit.cshtml:62 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Role/Edit.cshtml:72 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label src/front-end/Senparc.Xncf.Admin/src/components/Dropzone/index.vue:3 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label src/front-end/Senparc.Xncf.Admin/src/components/ImageCropper/index.vue:24 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label src/front-end/Senparc.Xncf.Admin/src/components/ImageCropper/index.vue:66 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label src/front-end/Senparc.Xncf.Admin/src/components/MDinput/index.vue:5 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label src/front-end/Senparc.Xncf.Admin/src/components/MDinput/index.vue:20 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • + 4 more in this group — see findings.md.
D28 · Secrets (history) · High secret · ×26
  • 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
  • + 1 more in this group — see findings.md.
AC1 · Text alternatives · <img> without a text alternative · ×17
  • <img> without a text alternative src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Login.cshtml:43 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative REDACTED:58 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative REDACTED:66 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative src/back-end/Senparc.Web/Pages/Index.cshtml:24 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative src/back-end/Senparc.Xncf.Installer/Areas/Install/Pages/Index.cshtml:42 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative src/front-end/Senparc.Xncf.Admin/src/components/ImageCropper/index.vue:39 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative src/front-end/Senparc.Xncf.Admin/src/components/ImageCropper/index.vue:96 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative src/front-end/Senparc.Xncf.Admin/src/components/ImageCropper/index.vue:100 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative src/front-end/Senparc.Xncf.Admin/src/components/Upload/SingleImage.vue:19 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative src/front-end/Senparc.Xncf.Admin/src/components/Upload/SingleImage2.vue:19 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative src/front-end/Senparc.Xncf.Admin/src/components/Upload/SingleImage3.vue:19 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative src/front-end/Senparc.Xncf.Admin/src/components/Upload/SingleImage3.vue:27 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative src/front-end/Senparc.Xncf.Admin/src/views/dashboard/admin/components/BoxCard.vue:4 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative src/front-end/Senparc.Xncf.Admin/src/views/dashboard/editor/index.vue:15 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative src/front-end/Senparc.Xncf.AdminModule/src/components/HelloWorld.vue:4 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/views/Senparc.Xncf.XncfStore/shopping/Index.vue:101 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/views/Senparc.Xncf.XncfStore/shopping/Index.vue:114 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
D30 · Dependency Vulnerabilities · High vulnerability · ×10
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D17 · Explicit Debt · WriteOnlyPrivateField · ×9
  • WriteOnlyPrivateField src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/AdminUserInfo/AuthorizationPage.cshtml.cs:17 — private IServiceProvider _serviceProvider — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/AdminUserInfo/Edit.cshtml.cs:30 — private IServiceProvider _serviceProvider — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/XncfModule/Index.cshtml.cs:39 — private IServiceProvider _serviceProvider — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField src/back-end/Senparc.Web/Pages/Index.cshtml.cs:31 — private IServiceProvider _serviceProvider — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField src/back-end/Senparc.Xncf.Installer/Domain/Services/InstallOptionsService.cs:52 — private IServiceProvider _serviceProvider — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField src/back-end/Senparc.Xncf.Installer/Domain/Services/InstallerService.cs:40 — private IServiceProvider _serviceProvider — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Role/Permission.cshtml.cs:33 — private SysMenuService _sysMenuService — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField src/back-end/Senparc.Web/JeffreyMpMessageHandler.cs:22 — private MpAccountDto _mpAccountDto — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField src/back-end/Senparc.Web/JeffreyMpMessageHandler.cs:23 — private ServiceProvider _services — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
AC4 · Keyboard semantics · Click handler on a non-interactive <div> · ×8
  • Click handler on a non-interactive <div> src/front-end/Senparc.Xncf.Admin/src/components/BackToTop/index.vue:3 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> src/front-end/Senparc.Xncf.Admin/src/components/DndList/index.vue:22 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> src/front-end/Senparc.Xncf.Admin/src/components/Hamburger/index.vue:2 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> src/front-end/Senparc.Xncf.Admin/src/components/ImageCropper/index.vue:4 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> src/front-end/Senparc.Xncf.Admin/src/components/ImageCropper/index.vue:9 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> src/front-end/Senparc.Xncf.Admin/src/components/RightPanel/index.vue:5 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> src/front-end/Senparc.Xncf.Admin/src/layout/index.vue:3 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> src/front-end/Senparc.Xncf.Admin/src/views/Admin/Menu/Index.vue:144 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
D31 · IaC & Container Security · High IaC · ×8
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AC4 · Keyboard semantics · Click handler on a non-interactive <i> · ×7
  • Click handler on a non-interactive <i> src/front-end/Senparc.Xncf.Admin/src/components/Upload/SingleImage.vue:21 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <i> src/front-end/Senparc.Xncf.Admin/src/components/Upload/SingleImage.vue — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <i> src/front-end/Senparc.Xncf.Admin/src/components/Upload/SingleImage2.vue:21 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <i> src/front-end/Senparc.Xncf.Admin/src/components/Upload/SingleImage2.vue — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <i> src/front-end/Senparc.Xncf.Admin/src/components/Upload/SingleImage3.vue:21 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <i> src/front-end/Senparc.Xncf.Admin/src/components/Upload/SingleImage3.vue — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <i> src/front-end/Senparc.Xncf.Admin/src/components/Upload/SingleImage3.vue:29 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
D17 · Explicit Debt · NoWarnInCsproj · ×5
  • NoWarnInCsproj — 38 warning codes suppressed in one element src/back-end/Directory.Build.props:5 — A single <NoWarn> suppresses 38 warning codes (NU1510;NU1603;NU1901;NU1902;NU1903;EF1001;ASPDEPR006;SYSLIB0014;SYSLIB0021;AD0001;CS0105;CS0108;CS0114;CS0162;CS0168;CS0169;CS0219;CS0414;CS0618;CS0628;CS0649;CS0809;CS1572;CS1573;CS1574;CS1587;CS1591;CS8321;CS8602;CS8604;CS8618;CS8619;CS8632;CS8669;CS9113;CA2022;CA2024;CA2200) in one stroke — one team-wide decision, not 38 independent debts. Review the set centrally rather than code-by-code; each code you can re-enable is one less blanket suppression. (Every code still counts toward the score and metrics.)
  • NoWarnInCsproj REDACTED:11 — NU5104 — this warning is switched off for the WHOLE project, including builds years from now. It is raised by the build itself — the packaging, restore or SDK step — about the project as a whole, not by the compiler or an analyzer at a line of code, so there is no call site to narrow it to and no per-site directive that could carry a reason: this element is the only place the decision can be recorded. Say WHY here, in a comment on the entry, or fix what the rule is reporting and drop the code from the list.
  • NoWarnInCsproj — known-vulnerability alert suppressed src/back-end/Directory.Build.props:5 — NU1901 — this is not a style rule being switched off: it is the dependency audit reporting that a package this project references has a KNOWN, already-published security vulnerability, and the entry deletes that report for the whole project — for this package and for every dependency the project takes from here on, including ones added long after whoever wrote the line has moved on. Nothing in the build will raise it again, so the next reader has no way to learn it was ever accepted. Upgrade the package to a version carrying the fix, or replace it, and drop the code from the list. Where the fix genuinely does not exist yet, keep the report and stop it FAILING the build — demote it to a warning without silencing it — and write down which advisory is being accepted and until when, so it is the acceptance that expires rather than the alert.
  • NoWarnInCsproj — known-vulnerability alert suppressed src/back-end/Directory.Build.props:5 — NU1902 — this is not a style rule being switched off: it is the dependency audit reporting that a package this project references has a KNOWN, already-published security vulnerability, and the entry deletes that report for the whole project — for this package and for every dependency the project takes from here on, including ones added long after whoever wrote the line has moved on. Nothing in the build will raise it again, so the next reader has no way to learn it was ever accepted. Upgrade the package to a version carrying the fix, or replace it, and drop the code from the list. Where the fix genuinely does not exist yet, keep the report and stop it FAILING the build — demote it to a warning without silencing it — and write down which advisory is being accepted and until when, so it is the acceptance that expires rather than the alert.
  • NoWarnInCsproj — known-vulnerability alert suppressed src/back-end/Directory.Build.props:5 — NU1903 — this is not a style rule being switched off: it is the dependency audit reporting that a package this project references has a KNOWN, already-published security vulnerability, and the entry deletes that report for the whole project — for this package and for every dependency the project takes from here on, including ones added long after whoever wrote the line has moved on. Nothing in the build will raise it again, so the next reader has no way to learn it was ever accepted. Upgrade the package to a version carrying the fix, or replace it, and drop the code from the list. Where the fix genuinely does not exist yet, keep the report and stop it FAILING the build — demote it to a warning without silencing it — and write down which advisory is being accepted and until when, so it is the acceptance that expires rather than the alert.
AC2 · Forms & labels · Custom control with no accessible name on <div> · ×4
  • Custom control with no accessible name on <div> src/front-end/Senparc.Xncf.Admin/src/components/BackToTop/index.vue:3 — This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
  • Custom control with no accessible name on <div> src/front-end/Senparc.Xncf.Admin/src/components/Hamburger/index.vue:2 — This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
  • Custom control with no accessible name on <div> src/front-end/Senparc.Xncf.Admin/src/components/ImageCropper/index.vue:4 — This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
  • Custom control with no accessible name on <div> src/front-end/Senparc.Xncf.Admin/src/components/RightPanel/index.vue:5 — This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
AC4 · Keyboard semantics · Click handler on a non-interactive <li> · ×4
  • Click handler on a non-interactive <li> src/front-end/Senparc.Xncf.Admin/src/layout/components/TagsView/index.vue:21 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <li> src/front-end/Senparc.Xncf.Admin/src/layout/components/TagsView/index.vue:22 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <li> src/front-end/Senparc.Xncf.Admin/src/layout/components/TagsView/index.vue:23 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <li> src/front-end/Senparc.Xncf.Admin/src/layout/components/TagsView/index.vue:24 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
AC4 · Keyboard semantics · Clickable element isn't keyboard-operable · ×3
  • Clickable element isn't keyboard-operable src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/AdminChat/Chat.cshtml:46 — The repo's own CSS styles .session-actions with `cursor: pointer`, so this <span> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
  • Clickable element isn't keyboard-operable src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Menu/Index.cshtml:112 — The repo's own CSS styles .menu-icon-item with `cursor: pointer`, so this <div> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
  • Clickable element isn't keyboard-operable src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Shared/_Layout_Vue.cshtml:99 — The repo's own CSS styles .el-dropdown-link with `cursor: pointer`, so this <span> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
AC4 · Keyboard semantics · Click handler on a non-interactive <span> · ×3
  • Click handler on a non-interactive <span> src/front-end/Senparc.Xncf.Admin/src/components/DndList/index.vue:11 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <span> src/front-end/Senparc.Xncf.Admin/src/views/Admin/XncfModule/Start.vue:76 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <span> src/front-end/Senparc.Xncf.Admin/src/views/Admin/XncfModule/Start.vue:401 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
D28 · Secrets (history) · REDACTED · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · Critical vulnerability · ×3
  • REDACTED
  • REDACTED
  • REDACTED
AC2 · Forms & labels · <textarea> without a programmatic label · ×2
  • <textarea> without a programmatic label src/front-end/Senparc.Xncf.Admin/src/components/JsonEditor/index.vue:3 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <textarea> without a programmatic label src/front-end/Senparc.Xncf.Admin/src/components/Tinymce/index.vue:3 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC2 · Forms & labels · Custom control with no accessible name on <i> · ×2
  • Custom control with no accessible name on <i> src/front-end/Senparc.Xncf.Admin/src/components/Upload/SingleImage.vue:21 — This <i> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
  • Custom control with no accessible name on <i> src/front-end/Senparc.Xncf.Admin/src/components/Upload/SingleImage.vue — This <i> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
AC3 · Page structure · <html> without a lang · ×2
  • <html> without a lang src/front-end/Senparc.Xncf.Admin/public/index.html:2 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang src/front-end/Senparc.Xncf.XncfStore/xncfstore/public/index.html:2 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
D17 · Explicit Debt · EmptyCatchBlock · ×2
  • EmptyCatchBlock src/back-end/Senparc.Areas.Admin/Domain/SeparcTraceManager/SenparcTraceHelper.cs:448 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/back-end/Senparc.Areas.Admin/OHS/Local/Controllers/AdminChatStreamController.cs:154 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
AC2 · Forms & labels · <label> that labels no control · ×1
  • <label> that labels no control src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/NeuCharPivot/Aggregate.cshtml:46 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
AC2 · Forms & labels · Link with no accessible name · ×1
  • Link with no accessible name src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Shared/_HeaderPartial.cshtml:16 — A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
AC2 · Forms & labels · Custom control with no accessible name on <span> · ×1
  • Custom control with no accessible name on <span> src/front-end/Senparc.Xncf.Admin/src/components/DndList/index.vue:11 — This <span> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
AC3 · Page structure · Viewport restricts zoom · ×1
  • Viewport restricts zoom src/front-end/Senparc.Xncf.Admin/public/index.html:7 — user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta.
AX3 · Project dependency cycles · Namespace dependency cycle · ×1
  • Namespace dependency cycle src/back-end/Senparc.Areas.Admin/Domain/Services/AdminUserInfoService.cs:40 — The namespaces Senparc.Areas.Admin.Domain ↔ Senparc.Areas.Admin.Domain.Services depend on each other. The lightest dependency in the cycle is Senparc.Areas.Admin.Domain → Senparc.Areas.Admin.Domain.Services (Senparc.Areas.Admin.Domain.AdminUserInfoService → Senparc.Areas.Admin.Domain.Services.AdminAuthConfigService, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
DM1 · Aggregate boundaries · Aggregate holds a reference to another aggregate · ×1
  • Aggregate holds a reference to another aggregate: AdminChatMessage.Session src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/AdminChatMessage.cs:53 — `AdminChatMessage` references the aggregate root `AdminChatSession` directly (via `Session`) — hold its `AdminChatSessionId` instead.
R8 · Dependency Hygiene · Unlisted import 'body-parser' · ×1
  • Unlisted import 'body-parser' src/front-end/Senparc.Xncf.Admin/mock/mock-server.js:2 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
X1 · Async correctness · Blocking wait while holding a `lock` · ×1
  • Blocking wait while holding a `lock` src/back-end/Senparc.Xncf.Accounts/Domain/OperationQueue/OperationQueue.cs:72 — This blocks on a Task **while holding a `lock`**, which is worse than an ordinary sync-over-async in two ways. `await` is illegal inside a `lock` body, so the usual fix — make the caller `async` and await it — cannot be applied where this block stands. And the thread parks while still holding the lock, so it occupies the critical section doing no work: every other caller serialises behind an operation that is only waiting, and if the awaited task itself needs a thread the pool has run out of, they wait forever. Do the async work OUTSIDE the critical section: take the lock only to read the shared state, release it, await the call, then re-take the lock to publish the result — re-checking on re-entry whether another caller won the race and, if so, discarding your result rather than overwriting theirs. Where the critical section genuinely has to span the async call, `lock` is the wrong primitive: use an async-aware one (`SemaphoreSlim` with `await WaitAsync()`) so waiters yield their thread instead of parking it.
Serious — 593 finding(s)
D30 · Dependency Vulnerabilities · Medium CVE · ×80
  • 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
  • + 55 more in this group — see findings.md.
D17 · Explicit Debt · CommentedOutCode · ×45
  • CommentedOutCode src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Index.cshtml.cs:109 — 4 consecutive commented-code lines
  • CommentedOutCode REDACTED:99 — 4 consecutive commented-code lines
  • CommentedOutCode REDACTED:107 — 4 consecutive commented-code lines
  • CommentedOutCode src/back-end/Senparc.Areas.Admin/Domain/Services/AdminChatAiService.cs:327 — 4 consecutive commented-code lines
  • CommentedOutCode src/back-end/Senparc.Areas.Admin/Domain/Services/InstallerService.cs:98 — 4 consecutive commented-code lines
  • CommentedOutCode src/back-end/Senparc.Areas.Admin/OHS/Local/AppService/ModuleAppService.cs:487 — 4 consecutive commented-code lines
  • CommentedOutCode src/back-end/Senparc.Areas.Admin/Register.cs:458 — 4 consecutive commented-code lines
  • CommentedOutCode src/back-end/Senparc.Xncf.Accounts/Domain/Services/AccountService.cs:333 — 4 consecutive commented-code lines
  • CommentedOutCode src/back-end/Senparc.Xncf.Installer/Domain/Services/InstallerService.cs:75 — 4 consecutive commented-code lines
  • CommentedOutCode src/back-end/Senparc.Web/Pages/Index.cshtml:12 — 4 consecutive commented-code lines
  • CommentedOutCode REDACTED:63 — 8 consecutive commented-code lines
  • CommentedOutCode REDACTED:95 — 8 consecutive commented-code lines
  • CommentedOutCode src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/XncfModule/Index.cshtml.cs:129 — 8 consecutive commented-code lines
  • CommentedOutCode REDACTED:83 — 11 consecutive commented-code lines
  • CommentedOutCode src/back-end/Senparc.Xncf.Accounts/Domain/Services/AccountService.cs:456 — 11 consecutive commented-code lines
  • CommentedOutCode src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Role/Edit.cshtml.cs:93 — 5 consecutive commented-code lines
  • CommentedOutCode REDACTED:123 — 5 consecutive commented-code lines
  • CommentedOutCode REDACTED:138 — 5 consecutive commented-code lines
  • CommentedOutCode src/back-end/Senparc.Areas.Admin/MyMessageHandler.cs:68 — 5 consecutive commented-code lines
  • CommentedOutCode src/back-end/Senparc.Areas.Admin/OHS/Local/AppService/ModuleAppService.cs:498 — 5 consecutive commented-code lines
  • CommentedOutCode src/back-end/Senparc.Areas.Admin/Register.cs:550 — 5 consecutive commented-code lines
  • CommentedOutCode src/back-end/Senparc.Aspire.ServiceDefaults/Extensions.cs:82 — 5 consecutive commented-code lines
  • CommentedOutCode REDACTED:40 — 5 consecutive commented-code lines
  • CommentedOutCode src/back-end/Senparc.Web/Register.cs:144 — 5 consecutive commented-code lines
  • CommentedOutCode src/back-end/Senparc.Web/Register.cs:151 — 5 consecutive commented-code lines
  • + 20 more in this group — see findings.md.
R4 · Test Coverage · No test reaches this file · ×40
  • No test reaches this file src/front-end/Senparc.Xncf.Admin/src/views/Admin/XncfModule/Start.vue:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/lightdemo/antv.vue:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/views/Senparc.Xncf.XncfStore/processdemo/antv.vue:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/front-end/Senparc.Xncf.AdminModule/src/views/XncfStore/lightdemo/antv.vue:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/front-end/Senparc.Xncf.Admin/src/components/ImageCropper/index.vue:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/front-end/Senparc.Xncf.Admin/src/views/Admin/Menu/icons.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/front-end/Senparc.Xncf.Admin/src/views/Admin/XncfModule/Index.vue:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/front-end/Senparc.Xncf.Admin/src/views/Admin/AdminUserInfo/Index.vue:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/front-end/Senparc.Xncf.Admin/src/utils/antvSetting.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/front-end/Senparc.Xncf.Admin/src/views/Admin/Role/Index.vue:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/views/Senparc.Xncf.XncfStore/shopping/detail.vue:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/front-end/Senparc.Xncf.Admin/src/views/Admin/Menu/Index.vue:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/shopping/detail.vue:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/front-end/Senparc.Xncf.AdminModule/src/views/XncfStore/shopping/detail.vue:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/views/Senparc.Xncf.XncfStore/shopping/application.vue:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/front-end/Senparc.Xncf.Admin/src/views/Admin/TenantInfo/Index.vue:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/views/Senparc.Xncf.XncfStore/shopping/applicationall.vue:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/front-end/Senparc.Xncf.Admin/src/store/modules/permission.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/front-end/Senparc.Xncf.Admin/src/components/Charts/MixChart.vue:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/views/Senparc.Xncf.XncfStore/operation/application.vue:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/shopping/application.vue:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/front-end/Senparc.Xncf.AdminModule/src/views/XncfStore/shopping/application.vue:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/front-end/Senparc.Xncf.Admin/src/components/Charts/LineMarker.vue:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/views/Senparc.Xncf.XncfStore/shopping/Index.vue:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/front-end/Senparc.Xncf.Admin/src/store/modules/user.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • + 15 more in this group — see findings.md.
DM12 · Ambient inputs in the domain · Domain type reads the wall clock · ×38
  • Domain type reads the wall clock: AccountPayLogService src/back-end/Senparc.Xncf.Accounts/Domain/Services/AccountPayLogService.cs:32 — `AccountPayLogService` reads `DateTime.Now` inside `CreateOrder`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
  • Domain type reads the wall clock: AccountPayLogService src/back-end/Senparc.Xncf.Accounts/Domain/Services/AccountPayLogService.cs:33 — `AccountPayLogService` reads `DateTime.Now` inside `CreateOrder`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
  • Domain type reads the wall clock: AccountPayLogService src/back-end/Senparc.Xncf.Accounts/Domain/Services/AccountPayLogService.cs:55 — `AccountPayLogService` reads `DateTime.Now` inside `CancelOrder`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
  • Domain type reads the wall clock: AccountPayLogService src/back-end/Senparc.Xncf.Accounts/Domain/Services/AccountPayLogService.cs:74 — `AccountPayLogService` reads `DateTime.Now` inside `PayLogFinish`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
  • Domain type reads the wall clock: AccountService src/back-end/Senparc.Xncf.Accounts/Domain/Services/AccountService.cs:28 — `AccountService` reads `DateTime.Now` inside `GetSalt`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
  • Domain type reads the wall clock: AccountService src/back-end/Senparc.Xncf.Accounts/Domain/Services/AccountService.cs:190 — `AccountService` reads `DateTimeOffset.UtcNow` inside `Login`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
  • Domain type reads the wall clock: AccountService src/back-end/Senparc.Xncf.Accounts/Domain/Services/AccountService.cs:222 — `AccountService` reads `DateTime.Now` inside `Login`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
  • Domain type reads the wall clock: AccountService src/back-end/Senparc.Xncf.Accounts/Domain/Services/AccountService.cs:245 — `AccountService` reads `DateTime.Now` inside `CreateAccount`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
  • Domain type reads the wall clock: AccountService src/back-end/Senparc.Xncf.Accounts/Domain/Services/AccountService.cs:247 — `AccountService` reads `DateTime.Now` inside `CreateAccount`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
  • Domain type reads the wall clock: AccountService src/back-end/Senparc.Xncf.Accounts/Domain/Services/AccountService.cs:248 — `AccountService` reads `DateTime.Now` inside `CreateAccount`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
  • Domain type reads the wall clock: AdminChatSession src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/AdminChatSession.cs:73 — `AdminChatSession` reads `DateTime.Now` inside `UpdateLastMessageTime`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
  • Domain type reads the wall clock: AdminUserInfo src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/AdminUserInfo.cs:135 — `AdminUserInfo` reads `DateTime.Now` inside `GeneratePasswordSalt`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
  • Domain type reads the wall clock: AdminUserInfoService src/back-end/Senparc.Areas.Admin/Domain/Services/AdminUserInfoService.cs:112 — `AdminUserInfoService` reads `DateTimeOffset.UtcNow` inside `KeepCookieLoginAliveAsync`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
  • Domain type reads the wall clock: AdminUserInfoService src/back-end/Senparc.Areas.Admin/Domain/Services/AdminUserInfoService.cs:117 — `AdminUserInfoService` reads `DateTimeOffset.UtcNow` inside `KeepCookieLoginAliveAsync`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
  • Domain type reads the wall clock: AdminUserInfoService src/back-end/Senparc.Areas.Admin/Domain/Services/AdminUserInfoService.cs:224 — `AdminUserInfoService` reads `DateTimeOffset.UtcNow` inside `LoginAsync`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
  • Domain type reads the wall clock: AdminUserInfoService src/back-end/Senparc.Areas.Admin/Domain/Services/AdminUserInfoService.cs:229 — `AdminUserInfoService` reads `DateTimeOffset.UtcNow` inside `LoginAsync`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
  • Domain type reads the wall clock: AdminUserInfoService src/back-end/Senparc.Areas.Admin/Domain/Services/AdminUserInfoService.cs:268 — `AdminUserInfoService` reads `DateTime.Now` inside `TryLoginAsync`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
  • Domain type reads the wall clock: AdminUserInfoService src/back-end/Senparc.Areas.Admin/Domain/Services/AdminUserInfoService.cs:293 — `AdminUserInfoService` reads `DateTime.Now` inside `TryLoginAsync`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
  • Domain type reads the wall clock: AdminUserInfoService src/back-end/Senparc.Areas.Admin/Domain/Services/AdminUserInfoService.cs:297 — `AdminUserInfoService` reads `DateTime.Now` inside `TryLoginAsync`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
  • Domain type reads the wall clock: AdminUserInfoService src/back-end/Senparc.Areas.Admin/Domain/Services/AdminUserInfoService.cs:301 — `AdminUserInfoService` reads `DateTime.Now` inside `TryLoginAsync`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
  • Domain type reads the wall clock: AdminUserInfoService src/back-end/Senparc.Areas.Admin/Domain/Services/AdminUserInfoService.cs:305 — `AdminUserInfoService` reads `DateTime.Now` inside `TryLoginAsync`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
  • Domain type reads the wall clock: AdminUserInfoService src/back-end/Senparc.Areas.Admin/Domain/Services/AdminUserInfoService.cs:520 — `AdminUserInfoService` reads `DateTimeOffset.UtcNow` inside `GenerateTokenForDesktopHandoffAsync`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
  • Domain type reads the wall clock: AdminUserInfoService src/back-end/Senparc.Areas.Admin/Domain/Services/AdminUserInfoService.cs:554 — `AdminUserInfoService` reads `DateTimeOffset.UtcNow` inside `GenerateToken`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
  • Domain type reads the wall clock: DesktopAdminAuthTokenIssuer src/back-end/Senparc.Areas.Admin/Domain/Services/DesktopAdminAuthTokenIssuer.cs:36 — `DesktopAdminAuthTokenIssuer` reads `DateTimeOffset.UtcNow` inside `IssueAsync`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
  • Domain type reads the wall clock: FullAccountBase src/back-end/Senparc.Xncf.Accounts/Domain/Models/DatabaseModel/ExtensionEntity.cs:45 — `FullAccountBase` reads `DateTime.Now` inside `IsLogined`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
  • + 13 more in this group — see findings.md.
D17 · Explicit Debt · TodoComment · ×31
  • TodoComment src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Index.cshtml.cs:39 — //TODO:从其他模块获得 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Index.cshtml.cs:204 — //TODO:判断Xncf条件还可以更细 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Index.cshtml.cs:242 — //TODO:判断Xncf条件还可以更细 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment REDACTED:160 — //TODO 需要把 userInfo 获取过程封装到下面的方法中,统一处理账号锁定 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/XncfModule/Index.cshtml.cs:44 — //TODO:从其他模块获得,或独立到对应模块的API — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/XncfModule/Index.cshtml.cs:104 — //TODO:使用DTO操作 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/XncfModule/Index.cshtml.cs:125 — //TODO:使用DTO操作 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment REDACTED:515 — //遍历某个 Register 下所有的方法 TODO:未来可添加分组 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/back-end/Senparc.Areas.Admin/OHS/Local/AppService/ModuleAppService.cs:214 — //遍历某个 Register 下所有的方法 TODO:未来可添加分组 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment REDACTED:538 — //TODO:页面上需要给提示 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/AdminUserInfo.cs:96 — //TODO:用户名及密码合规性验证 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/back-end/Senparc.Areas.Admin/Domain/Services/AdminChatAiService.cs:332 — // TODO: 测试 MAF 中是否自动开启工具调用 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/back-end/Senparc.Areas.Admin/Domain/Services/AdminUserInfoService.cs:171 — ////TODO:放到 OHS 的 Service — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/back-end/Senparc.Areas.Admin/Domain/Services/InstallerService.cs:110 — //TODO:选择性安装用户自定义模块 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/back-end/Senparc.Xncf.Installer/Domain/Services/InstallerService.cs:131 — //TODO:选择性安装用户自定义模块 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/back-end/Senparc.Areas.Admin/Domain/Services/InstallerService.cs:173 — //开始安装用户模块(如有) TODO:选择性安装 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/back-end/Senparc.Xncf.Installer/Domain/Services/InstallerService.cs:178 — //开始安装用户模块(如有) TODO:选择性安装 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/back-end/Senparc.Areas.Admin/Domain/Services/InstallerService.cs:234 — // //TODO:判断是否已存在 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/back-end/Senparc.Xncf.Installer/Domain/Services/InstallerService.cs:253 — // //TODO:判断是否已存在 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/back-end/Senparc.Areas.Admin/MyMessageHandler.cs:57 — /* TODO:AgentKernel暂时未支持 Image 模型,支持后重新开放。*/ — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/back-end/Senparc.Areas.Admin/OHS/Local/AppService/AdminUserInfoAppService.cs:255 — //TODO:进行更多层级判断 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/back-end/Senparc.Areas.Admin/OHS/Local/AppService/ModuleAppService.cs:501 — // await cache.SetAsync(tempId, result.Data.ToJson(), TimeSpan.FromMinutes(5));//TODO:可设置 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/back-end/Senparc.Areas.Admin/Register.cs:171 — //TODO:可以提供一个 BeforeUninstall 方法,阻止卸载。 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/back-end/Senparc.Areas.Admin/Register.cs:592 — //TODO: Oracle 未升级到 .NET 8.0,此处会抛错 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/back-end/Senparc.Xncf.Accounts/Domain/Cache/FullAccountCache.cs:90 — //TODO:需要使用分布式缓存 — 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.
  • + 6 more in this group — see findings.md.
X2 · Cancellation propagation · Async method without CancellationToken · ×31
  • Async method without CancellationToken: GetAllMenuDtosAsync src/back-end/Senparc.Areas.Admin/ACL/Repository/SysMenuRepository.cs:42 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetVisibleMenuDtosAsync src/back-end/Senparc.Areas.Admin/ACL/Repository/SysMenuRepository.cs:76 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetAllResouceCodesByAccountIdAsync src/back-end/Senparc.Areas.Admin/ACL/Repository/SysRolePermissionRepository.cs:34 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: OnGetSelectItemsAsync src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Role/Edit.cshtml.cs:72 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: OnGetAsync src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/SenparcTrace/DateLog.cshtml.cs:22 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: OnGetDetailAsync src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/SenparcTrace/DateLog.cshtml.cs:29 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetLogScanResultAsync src/back-end/Senparc.Areas.Admin/Domain/SeparcTraceManager/SenparcTraceHelper.cs:72 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetAllLogsAsync src/back-end/Senparc.Areas.Admin/Domain/SeparcTraceManager/SenparcTraceHelper.cs:113 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: ScanLogFileAsync src/back-end/Senparc.Areas.Admin/Domain/SeparcTraceManager/SenparcTraceHelper.cs:260 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: OpenLogReaderAsync src/back-end/Senparc.Areas.Admin/Domain/SeparcTraceManager/SenparcTraceHelper.cs:363 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GenerateResponseAsync src/back-end/Senparc.Areas.Admin/Domain/Services/AdminChatAiService.cs:115 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: LoginAsync src/back-end/Senparc.Areas.Admin/Domain/Services/AdminUserInfoService.cs:435 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetAdminUserInfoAsync src/back-end/Senparc.Areas.Admin/Domain/Services/AdminUserInfoService.cs:478 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetAllMenusTreeAsync src/back-end/Senparc.Areas.Admin/Domain/Services/SysMenuService.cs:57 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetAllMenuListAsync src/back-end/Senparc.Areas.Admin/Domain/Services/SysMenuService.cs:72 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: HasPermissionAsync src/back-end/Senparc.Areas.Admin/Domain/Services/SysRolePermissionService.cs:29 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: CreateSessionAsync src/back-end/Senparc.Areas.Admin/OHS/Local/AppService/AdminChatAppService.cs:90 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetSessionDetailAsync src/back-end/Senparc.Areas.Admin/OHS/Local/AppService/AdminChatAppService.cs:200 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: DeleteSessionAsync src/back-end/Senparc.Areas.Admin/OHS/Local/AppService/AdminChatAppService.cs:236 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: SendMessageAsync src/back-end/Senparc.Areas.Admin/OHS/Local/AppService/AdminChatAppService.cs:266 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: DeleteMessagesAsync src/back-end/Senparc.Areas.Admin/OHS/Local/AppService/AdminChatAppService.cs:361 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: AddModulesToSessionAsync src/back-end/Senparc.Areas.Admin/OHS/Local/AppService/AdminChatAppService.cs:404 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: SetSessionModulesAsync src/back-end/Senparc.Areas.Admin/OHS/Local/AppService/AdminChatAppService.cs:443 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: SetSessionWorkflowsAsync src/back-end/Senparc.Areas.Admin/OHS/Local/AppService/AdminChatAppService.cs:542 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetAvailableModulesAsync src/back-end/Senparc.Areas.Admin/OHS/Local/AppService/AdminChatAppService.cs:584 — No CancellationToken parameter — this work can't be stopped early once started.
  • + 6 more in this group — see findings.md.
X24 · Document value interpolated into markup unescaped · Untrusted text written into markup unescaped · ×26
  • Untrusted text written into markup unescaped src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/AdminChat/Chat.cshtml:413 — `System.Text.Json.JsonSerializer.Serialize(Model.InitialMessage ?? string.Empty)` is text this program did not author, and it is written into the text of an element through Razor's `Html.Raw` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/AdminChat/Chat.cshtml:415 — `System.Text.Json.JsonSerializer.Serialize(Model.ModuleUids ?? string.Empty)` is text this program did not author, and it is written into the text of an element through Razor's `Html.Raw` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Shared/_Layout_Vue.cshtml:260 — `System.Text.Json.JsonSerializer.Serialize(DateTimeOffset.Now)` is text this program did not author, and it is written into the text of an element through Razor's `Html.Raw` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Shared/_Layout_Vue.cshtml:261 — `System.Text.Json.JsonSerializer.Serialize(currentAccountName)` is text this program did not author, and it is written into the text of an element through Razor's `Html.Raw` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Shared/_Layout_Vue.cshtml:276 — `System.Text.Json.JsonSerializer.Serialize(AR["Admin.Session.Title"].Value)` is text this program did not author, and it is written into the text of an element through Razor's `Html.Raw` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Shared/_Layout_Vue.cshtml:277 — `System.Text.Json.JsonSerializer.Serialize(AR["Admin.Session.Message"].Value)` is text this program did not author, and it is written into the text of an element through Razor's `Html.Raw` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Shared/_Layout_Vue.cshtml:278 — `System.Text.Json.JsonSerializer.Serialize(AR["Admin.Session.KeepLogin"].Value)` is text this program did not author, and it is written into the text of an element through Razor's `Html.Raw` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Shared/_Layout_Vue.cshtml:279 — `System.Text.Json.JsonSerializer.Serialize(AR["Admin.Session.LogoutNow"].Value)` is text this program did not author, and it is written into the text of an element through Razor's `Html.Raw` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Shared/_Layout_Vue.cshtml:280 — `System.Text.Json.JsonSerializer.Serialize(AR["Admin.Session.KeepLoginSuccess"].Value)` is text this program did not author, and it is written into the text of an element through Razor's `Html.Raw` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Shared/_LocalizationScripts.cshtml:15 — `translationsJson` is text this program did not author, and it is written into the text of an element through Razor's `Html.Raw` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Shared/_LocalizationScripts.cshtml:161 — `JsonSerializer.Serialize(sourceTranslations)` is text this program did not author, and it is written into the text of an element through Razor's `Html.Raw` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped src/back-end/Senparc.Web/Pages/Index.cshtml.cs:79 — `System.Globalization.CultureInfo.CurrentUICulture.Name` is text this program did not author, and it is written into a quoted attribute value through `ContentResult` with an HTML content type with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped src/back-end/Senparc.Web/Pages/Index.cshtml.cs:84 — `title` is text this program did not author, and it is written into the text of an element through `ContentResult` with an HTML content type with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped src/back-end/Senparc.Web/Pages/Index.cshtml.cs:94 — `title` is text this program did not author, and it is written into the text of an element through `ContentResult` with an HTML content type with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped src/back-end/Senparc.Web/Pages/Index.cshtml.cs:95 — `message` is text this program did not author, and it is written into the text of an element through `ContentResult` with an HTML content type with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped src/back-end/Senparc.Web/Pages/Index.cshtml.cs:96 — `link` is text this program did not author, and it is written into the text of an element through `ContentResult` with an HTML content type with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped src/back-end/Senparc.Web/Pages/Shared/_LocalizationScripts.cshtml:8 — `JsonSerializer.Serialize(strings)` is text this program did not author, and it is written into the text of an element through Razor's `Html.Raw` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped src/back-end/Senparc.Xncf.Installer/Areas/Install/Pages/Index.cshtml:137 — `System.Text.Json.JsonSerializer.Serialize(new { started = IR["Install.AlreadyRunning"].Value, startConfirm = IR["Install.Confirm"].Value, startConfirmDetail = IR["Install.ConfirmDetail"].Value, confirmButtonText = IR["Install.ConfirmButton"].Value, cancelButtonText = IR["Install.CancelButton"].Value, startedWaiting = IR["Install.StartedWaiting"].Value, failedPrefix = IR["Install.FailedPrefix"].Value, loadOptionsFailed = IR["Install.LoadOptionsFailed"].Value })` is text this program did not author, and it is written into the text of an element through Razor's `Html.Raw` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped src/back-end/Senparc.Areas.Admin/wwwroot/js/Admin/Pages/XncfModule/start.js:96 — `String(value||'')` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped src/back-end/Senparc.Xncf.Installer/wwwroot/js/Installer/Pages/index.js:86 — `(window.ncfInstallI18n&&window.ncfInstallI18n.startedWaiting)||'Installation started, please wait...'` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped src/back-end/Senparc.Xncf.Installer/wwwroot/js/Installer/Pages/index.js:93 — `res.data` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped src/back-end/Senparc.Xncf.Installer/wwwroot/js/Installer/Pages/index.js:95 — `((window.ncfInstallI18n&&window.ncfInstallI18n.failedPrefix)||'Install failed:')+error` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped REDACTED:188 — `val` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped src/front-end/Senparc.Xncf.Admin/src/views/Admin/XncfModule/Start.vue:562 — `runResult.tip` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped src/front-end/Senparc.Xncf.Admin/src/views/Admin/XncfModule/Start.vue:563 — `runResult.msg` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • + 1 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
AC4 · Keyboard semantics · Anchor without href · ×15
  • Anchor without href src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/AdminUserInfo/AuthorizationPage.cshtml:34 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Menu/Edit.cshtml:23 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Menu/Edit.cshtml:29 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Menu/Edit.cshtml:163 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Menu/Edit.cshtml:173 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Menu/Edit.cshtml:176 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Role/Permission.cshtml:35 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/SenparcTrace/DateLog.cshtml:11 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href REDACTED:125 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href src/front-end/Senparc.Xncf.Admin/src/components/Breadcrumb/index.vue:6 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href src/front-end/Senparc.Xncf.Admin/src/components/ImageCropper/index.vue:31 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href src/front-end/Senparc.Xncf.Admin/src/components/ImageCropper/index.vue:107 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href src/front-end/Senparc.Xncf.Admin/src/components/ImageCropper/index.vue:108 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href src/front-end/Senparc.Xncf.Admin/src/components/ImageCropper/index.vue:128 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href src/front-end/Senparc.Xncf.Admin/src/components/ImageCropper/index.vue:129 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
D17 · Explicit Debt · Dead code · ×11
  • Dead code: ErrorViewModel src/back-end/Senparc.Web/Models/ErrorViewModel.cs:5 — NamedType ErrorViewModel — Roslyn's SymbolFinder walked every project the solution loads, including Senparc.Web, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: ValidateTenant REDACTED:211 — Method ValidateTenant — Roslyn's SymbolFinder walked every project the solution loads, including Senparc.Areas.Admin, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: AccountDto src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/Dto/AccountDto.cs:26 — NamedType AccountDto — Roslyn's SymbolFinder walked every project the solution loads, including Senparc.Areas.Admin, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: HasPermissionAsync src/back-end/Senparc.Areas.Admin/Domain/Services/SysRolePermissionService.cs:29 — Method HasPermissionAsync — Roslyn's SymbolFinder walked every project the solution loads, including Senparc.Areas.Admin, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: SysMenu_Request src/back-end/Senparc.Areas.Admin/OHS/Local/PL/SysMenu_Request.cs:10 — NamedType SysMenu_Request — Roslyn's SymbolFinder walked every project the solution loads, including Senparc.Areas.Admin, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: SysMenu_Response src/back-end/Senparc.Areas.Admin/OHS/Local/PL/SysMenu_Response.cs:10 — NamedType SysMenu_Response — Roslyn's SymbolFinder walked every project the solution loads, including Senparc.Areas.Admin, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: SysRole_Request src/back-end/Senparc.Areas.Admin/OHS/Local/PL/SysRole_Request.cs:10 — NamedType SysRole_Request — Roslyn's SymbolFinder walked every project the solution loads, including Senparc.Areas.Admin, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: SenparcDbContextFactoryHeler src/back-end/Senparc.Xncf.Accounts/Domain/Models/DatabaseModel/AccountSenparcEntities.cs:46 — NamedType SenparcDbContextFactoryHeler — Roslyn's SymbolFinder walked every project the solution loads, including Senparc.Xncf.Accounts, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: AccountDto src/back-end/Senparc.Xncf.Accounts/Domain/Models/DatabaseModel/Dto/AccountDto.cs:8 — NamedType AccountDto — Roslyn's SymbolFinder walked every project the solution loads, including Senparc.Xncf.Accounts, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: GenerateKey src/back-end/Senparc.Xncf.Accounts/Domain/OperationQueue/OperationQueue.cs:43 — Method GenerateKey — Roslyn's SymbolFinder walked every project the solution loads, including Senparc.Xncf.Accounts, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
  • Dead code: OperateQueue src/back-end/Senparc.Xncf.Accounts/Domain/OperationQueue/OperationQueue.cs:53 — Method OperateQueue — Roslyn's SymbolFinder walked every project the solution loads, including Senparc.Xncf.Accounts, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
D31 · IaC & Container Security · Medium IaC · ×10
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
DM11 · Constructible invalid state · Constructible in an invalid state · ×7
  • Constructible in an invalid state: AdminAuthConfig src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/AdminAuthConfig.cs:37 — `AdminAuthConfig`'s public constructor takes `adminWebLoginExpireMinutes`, `backendJwtExpireMinutes` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `AdminAuthConfig` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: AdminChatMessage src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/AdminChatMessage.cs:69 — `AdminChatMessage`'s public constructor takes `sessionId`, `content`, `sequence`, `modelIdentifier` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `AdminChatMessage` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: AdminChatSession src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/AdminChatSession.cs:48 — `AdminChatSession`'s public constructor takes `title`, `userId` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `AdminChatSession` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: NeuCharPivotConfiguration src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/NeuCharPivotModels.cs:50 — `NeuCharPivotConfiguration`'s public constructor takes `moduleUid`, `name`, `adminUserId` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `NeuCharPivotConfiguration` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: NeuCharPivotFunction src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/NeuCharPivotModels.cs:120 — `NeuCharPivotFunction`'s public constructor takes `pivotId`, `moduleUid`, `functionKey`, `functionName`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `NeuCharPivotFunction` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: NeuCharPivotLoopTask src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/NeuCharPivotModels.cs:185 — `NeuCharPivotLoopTask`'s public constructor takes `functionId`, `adminUserId` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `NeuCharPivotLoopTask` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: NeuCharExecutionLog src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/NeuCharPivotModels.cs:269 — `NeuCharExecutionLog`'s public constructor takes `sourceType`, `sourceId`, `moduleUid`, `functionKey`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `NeuCharExecutionLog` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
DM7 · Repository granularity · Repository for a non-root entity · ×7
  • Repository for a non-root entity: IAdminChatSessionModuleRepository → AdminChatSessionModule src/back-end/Senparc.Areas.Admin/ACL/Repository/AdminChatSessionModuleRepository.cs:7 — `IAdminChatSessionModuleRepository` is a repository over `AdminChatSessionModule`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `AdminChatSessionModule` through its owning aggregate instead.
  • Repository for a non-root entity: IAdminChatSessionWorkflowRepository → AdminChatSessionWorkflow src/back-end/Senparc.Areas.Admin/ACL/Repository/AdminChatSessionWorkflowRepository.cs:21 — `IAdminChatSessionWorkflowRepository` is a repository over `AdminChatSessionWorkflow`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `AdminChatSessionWorkflow` through its owning aggregate instead.
  • Repository for a non-root entity: ISysMenuRepository → SysMenu src/back-end/Senparc.Areas.Admin/ACL/Repository/SysMenuRepository.cs:13 — `ISysMenuRepository` is a repository over `SysMenu`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `SysMenu` through its owning aggregate instead.
  • Repository for a non-root entity: ISysRolePermissionRepository → SysRolePermission src/back-end/Senparc.Areas.Admin/ACL/Repository/SysRolePermissionRepository.cs:13 — `ISysRolePermissionRepository` is a repository over `SysRolePermission`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `SysRolePermission` through its owning aggregate instead.
  • Repository for a non-root entity: IAccountPayLogRepository → AccountPayLog src/back-end/Senparc.Xncf.Accounts/ACL/Repository/AccountPayLogRepository.cs:7 — `IAccountPayLogRepository` is a repository over `AccountPayLog`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `AccountPayLog` through its owning aggregate instead.
  • Repository for a non-root entity: IAccountRepository → Account src/back-end/Senparc.Xncf.Accounts/ACL/Repository/AccountRepository.cs:7 — `IAccountRepository` is a repository over `Account`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Account` through its owning aggregate instead.
  • Repository for a non-root entity: IPointsLogRepository → PointsLog src/back-end/Senparc.Xncf.Accounts/ACL/Repository/PointsLogRepository.cs:7 — `IPointsLogRepository` is a repository over `PointsLog`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `PointsLog` through its owning aggregate instead.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AC6 · Visual & motion safety · Low contrast colour pair in CSS (2.4 · ×5
  • Low contrast colour pair in CSS (2.4:1) src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Index.cshtml:558 — `#xncf-modules-area .xncf-item .version.version-upgradeable` sets color: #409EFF on background-color: #e6f1fc — 2.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
  • Low contrast colour pair in CSS (2.4:1) src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/views/Senparc.Xncf.XncfStore/operation/application.vue:352 — `.addArea:hover` sets color: white on background-color: #37bc9b — 2.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
  • Low contrast colour pair in CSS (2.4:1) src/back-end/Senparc.Web/wwwroot/lib/element-ui_2.13.2/element.css:4041 — `.el-picker-panel__shortcut.active` sets color: #409EFF on background-color: #e6f1fe — 2.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
  • Low contrast colour pair in CSS (2.4:1) src/back-end/Senparc.Web/wwwroot/css/User/base/pagecss.css:767 — `div.grayr span.disabled` sets color: #797979 on background-color: #c1c1c1 — 2.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
  • Low contrast colour pair in CSS (2.4:1) src/back-end/Senparc.Web/wwwroot/css/User/base/pagecss.css:965 — `div.tres a` sets color: #fff on background-color: #d90 — 2.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (1.9 · ×5
  • Low contrast colour pair in CSS (1.9:1) src/front-end/Senparc.Xncf.Admin/src/layout/components/TagsView/index.vue:286 — `&:hover` sets color: #fff on background-color: #b4bccc — 1.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
  • Low contrast colour pair in CSS (1.9:1) src/front-end/Senparc.Xncf.Admin/src/assets/custom-theme/index.css:1 — `.custom-theme .el-select .el-tag__close.el-icon-close` sets color: #fff on background-color: #b4bccc — 1.9:1, below the 4.5:1 WCAG AA minimum for normal text. This is a MINIFIED, build-generated sheet — editing the literal here is undone by the next vendor drop or rebuild, so override the rule in your own stylesheet (or fix it upstream / in the source the bundle is built from).
  • Low contrast colour pair in CSS (1.9:1) src/front-end/Senparc.Xncf.Admin/src/assets/custom-theme/index.css:1 — `.custom-theme .el-tabs__item .el-icon-close:hover` sets color: #fff on background-color: #b4bccc — 1.9:1, below the 4.5:1 WCAG AA minimum for normal text. This is a MINIFIED, build-generated sheet — editing the literal here is undone by the next vendor drop or rebuild, so override the rule in your own stylesheet (or fix it upstream / in the source the bundle is built from).
  • Low contrast colour pair in CSS (1.9:1) src/back-end/Senparc.Web/wwwroot/css/User/base/pagecss.css:181 — `div.meneame a:hover` sets color: #ff6500 on background-color: #ffc794 — 1.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
  • Low contrast colour pair in CSS (1.9:1) src/back-end/Senparc.Web/wwwroot/css/User/base/pagecss.css:191 — `div.meneame a:active` sets color: #ff6500 on background-color: #ffc794 — 1.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
DM4 · Rich vs anemic model · Anemic entity · ×5
  • Anemic entity: AdminChatSessionModule src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/AdminChatSessionModule.cs:11 — `AdminChatSessionModule` is an aggregate/entity with 6 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: AdminChatSessionWorkflow src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/AdminChatSessionWorkflow.cs:25 — `AdminChatSessionWorkflow` is an aggregate/entity with 6 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: Account src/back-end/Senparc.Xncf.Accounts/Domain/Models/DatabaseModel/Account.cs:11 — `Account` is an aggregate/entity with 34 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: AccountPayLog src/back-end/Senparc.Xncf.Accounts/Domain/Models/DatabaseModel/AccountPayLog.cs:9 — `AccountPayLog` is an aggregate/entity with 20 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: PointsLog src/back-end/Senparc.Xncf.Accounts/Domain/Models/DatabaseModel/PointsLog.cs:9 — `PointsLog` is an aggregate/entity with 8 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
IC1 · Incompleteness & stubs · Fake-async · ×5
  • Fake-async — async method never awaits REDACTED:30 — `OnGetAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
  • Fake-async — async method never awaits REDACTED:35 — `OnGetRequestTenantInfoAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
  • Fake-async — async method never awaits src/back-end/Senparc.Areas.Admin/Domain/Services/AdminUserInfoService.cs:384 — `InitAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
  • Fake-async — async method never awaits src/back-end/Senparc.Areas.Admin/MyMessageHandler.cs:44 — `OnVoiceRequestAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
  • Fake-async — async method never awaits src/back-end/Senparc.Areas.Admin/MyMessageHandler.cs:55 — `AfterRunBotAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (2.8 · ×4
  • Low contrast colour pair in CSS (2.8:1) src/back-end/Senparc.Web/wwwroot/lib/element-ui_2.13.2/element.css:1394 — `.el-pagination.is-background .el-pager li:not(.disabled).active` sets color: #FFF on background-color: #409EFF — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
  • Low contrast colour pair in CSS (2.8:1) src/back-end/Senparc.Web/wwwroot/lib/element-ui_2.13.2/element.css:3384 — `.el-date-table td.current:not(.disabled) span` sets color: #FFF on background-color: #409EFF — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
  • Low contrast colour pair in CSS (2.8:1) src/back-end/Senparc.Web/wwwroot/lib/element-ui_2.13.2/element.css:3427 — `.el-date-table td.selected span` sets color: #FFF on background-color: #409EFF — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
  • Low contrast colour pair in CSS (2.8:1) src/back-end/Senparc.Web/wwwroot/lib/element-ui_2.13.2/element.css:3508 — `.el-month-table td.end-date .cell, .el-month-table td.start-date .cell` sets color: #FFF on background-color: #409EFF — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
SC1 · Supply-chain hygiene · JavaScript dependencies are not locked · ×4
  • JavaScript dependencies are not locked src/back-end/Senparc.Web/wwwroot/lib/Chart.js/package.json:12 — src/back-end/Senparc.Web/wwwroot/lib/Chart.js/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / REDACTED / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
  • JavaScript dependencies are not locked src/back-end/Senparc.Web/wwwroot/lib/echarts/package.json:37 — src/back-end/Senparc.Web/wwwroot/lib/echarts/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / REDACTED / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
  • JavaScript dependencies are not locked src/front-end/Senparc.Xncf.XncfStore/xncfstore/package.json:9 — src/front-end/Senparc.Xncf.XncfStore/xncfstore/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / REDACTED / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
  • JavaScript dependencies are not locked src/front-end/package.json:19 — src/front-end/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / REDACTED / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
X5 · Nullable reference types · Symbol treated as nullable, then dereferenced unguarded · ×4
  • Symbol treated as nullable, then dereferenced unguarded src/back-end/Senparc.Areas.Admin/Domain/Services/AdminChatAiService.cs:381 — This method contradicts itself about `runner`: line 378 writes `runner?.Kernel`, which says `runner` can be null, but line 381 then dereferences it directly as `runner.RunChatAsync` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `runner` truly cannot be null here, the `?.` is misleading. Settle it one way — test `runner` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded src/back-end/Senparc.Areas.Admin/OHS/Local/AppService/ModuleAppService.cs:478 — This method contradicts itself about `taskFunc`: line 477 assigns it with `as Task`, which hands back null rather than throwing when the value is not a `Task`, but line 478 then dereferences it directly as `taskFunc.ConfigureAwait` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `taskFunc` once before the first use and handle the null case, or cast with `(Task)` so the failure is reported where it happens — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded src/back-end/Senparc.Areas.Admin/OHS/Local/AppService/ModuleAppService.cs:504 — This method contradicts itself about `result`: line 484 assigns it with `as IAppResponse`, which hands back null rather than throwing when the value is not a `IAppResponse`, but line 504 then dereferences it directly as `result.Data` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `result` once before the first use and handle the null case, or cast with `(IAppResponse)` so the failure is reported where it happens — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded src/back-end/Senparc.Xncf.Accounts/Program.cs:108 — This method contradicts itself about `ctx`: line 107 assigns it with `as AccountSenparcEntities`, which hands back null rather than throwing when the value is not a `AccountSenparcEntities`, but line 108 then dereferences it directly as `ctx.Set` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `ctx` once before the first use and handle the null case, or cast with `(AccountSenparcEntities)` so the failure is reported where it happens — rather than leaving the two readings side by side.
AC3 · Page structure · Page without a main landmark · ×3
  • Page without a main landmark src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Login.cshtml:9 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Shared/_Layout_Vue.cshtml:29 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark src/back-end/Senparc.Xncf.Installer/Areas/Install/Pages/Index.cshtml:10 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
AC3 · Page structure · Heading level jumps from h3 to h5 · ×3
  • Heading level jumps from h3 to h5 src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/lightdemo/antv.vue:127 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
  • Heading level jumps from h3 to h5 src/front-end/Senparc.Xncf.AdminModule/src/views/XncfStore/lightdemo/antv.vue:127 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
  • Heading level jumps from h3 to h5 src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/views/Senparc.Xncf.XncfStore/processdemo/antv.vue:127 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
AC6 · Visual & motion safety · Animation without a prefers-reduced-motion guard · ×3
  • Animation without a prefers-reduced-motion guard src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Index.cshtml:200 — `.host-comparison-bar-fill` moves (`transition: width 0.35s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Index.cshtml:657 — `.shake-animation` moves (`animation: shake 0.8s cubic-bezier(.36,.07,.19,.97) both`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Index.cshtml:661 — `.glow-animation` moves (`animation: glow 1.2s ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (3.1 · ×3
  • Low contrast colour pair in CSS (3.1:1) src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/views/Senparc.Xncf.XncfStore/operation/application.vue:270 — `.shoptit` sets color: #929292 on background-color: #ffffff — 3.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
  • Low contrast colour pair in CSS (3.1:1) src/front-end/Senparc.Xncf.Admin/src/views/Admin/XncfModule/Index.vue:657 — `.box-card .box-card-action2` sets color: #fff on background-color: #909399 — 3.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
  • Low contrast colour pair in CSS (3.1:1) src/front-end/Senparc.Xncf.Admin/src/views/Admin/XncfModule/Start.vue:1099 — `.box-card .box-card-action2` sets color: #fff on background-color: #909399 — 3.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (2.9 · ×3
  • Low contrast colour pair in CSS (2.9:1) src/front-end/Senparc.Xncf.Admin/src/views/Admin/XncfModule/Index.vue:639 — `.box-card .box-card-action` sets color: #fff on background-color: #ff6a00 — 2.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
  • Low contrast colour pair in CSS (2.9:1) src/front-end/Senparc.Xncf.Admin/src/views/Admin/XncfModule/Start.vue:1080 — `.box-card .box-card-action` sets color: #fff on background-color: #ff6a00 — 2.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
  • Low contrast colour pair in CSS (2.9:1) src/back-end/Senparc.Web/wwwroot/css/User/base/pagecss.css:712 — `div.black-red span.disabled` sets color: #868686 on background-color: #3e3e3e — 2.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (1.7 · ×3
  • Low contrast colour pair in CSS (1.7:1) src/back-end/Senparc.Web/wwwroot/lib/element-ui_2.13.2/element.css:2699 — `.el-select .el-tag__close.el-icon-close` sets color: #FFF on background-color: #C0C4CC — 1.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
  • Low contrast colour pair in CSS (1.7:1) src/back-end/Senparc.Web/wwwroot/lib/element-ui_2.13.2/element.css:5020 — `.el-tabs__item .el-icon-close:hover` sets color: #FFF on background-color: #C0C4CC — 1.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
  • Low contrast colour pair in CSS (1.7:1) src/back-end/Senparc.Web/wwwroot/lib/element-ui_2.13.2/element.css:11725 — `.el-cascader__tags .el-tag .el-icon-close` sets color: #FFF on background-color: #C0C4CC — 1.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (3.6 · ×3
  • Low contrast colour pair in CSS (3.6:1) src/back-end/Senparc.Web/wwwroot/css/User/base/pagecss.css:691 — `div.black-red a:hover` sets color: #fff on background-color: #ec5210 — 3.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
  • Low contrast colour pair in CSS (3.6:1) src/back-end/Senparc.Web/wwwroot/css/User/base/pagecss.css:696 — `div.black-red a:active` sets color: #fff on background-color: #ec5210 — 3.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
  • Low contrast colour pair in CSS (3.6:1) src/back-end/Senparc.Web/wwwroot/css/User/base/pagecss.css:859 — `div.jogger a` sets color: #fff on background-color: #ee4e4e — 3.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AX2 · Stateful singletons · Process-global static state · ×3
  • Process-global static state: Register src/back-end/Senparc.Web/Register.cs:47 — `Register` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (StartTime; e.g. `StartTime` at line 53). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: SenparcDbContextFactoryConfig src/back-end/Senparc.Areas.Admin/Domain/Models/MultipleDatabase/SenparcDbContextFactoryConfig.cs:11 — `SenparcDbContextFactoryConfig` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_rootDirectoryPath; e.g. `_rootDirectoryPath` at line 30). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: SenparcDbContextFactoryConfig src/back-end/Senparc.Xncf.Accounts/Domain/Models/DatabaseModel/MultipleDatabase/SenparcDbContextFactoryConfig.cs:11 — `SenparcDbContextFactoryConfig` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_rootDictionaryPath; e.g. `_rootDictionaryPath` at line 30). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
D15 · Churn × Complexity Hotspots · Hotspot · ×3
  • Hotspot: src/back-end/Senparc.Areas.Admin/Domain/Services/AdminChatAiService.cs src/back-end/Senparc.Areas.Admin/Domain/Services/AdminChatAiService.cs:115 — src/back-end/Senparc.Areas.Admin/Domain/Services/AdminChatAiService.cs changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in AdminChatAiService.GenerateResponseAsync at line 115. 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-05-27..2026-08-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-27 15:06:43 +08:00' --until='2026-08-25 15:06:43 +08:00' --full-history --no-merges -- src/back-end/Senparc.Areas.Admin/Domain/Services/AdminChatAiService.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: src/back-end/Senparc.Areas.Admin/wwwroot/js/Admin/Pages/XncfModule/start.js src/back-end/Senparc.Areas.Admin/wwwroot/js/Admin/Pages/XncfModule/start.js:495 — src/back-end/Senparc.Areas.Admin/wwwroot/js/Admin/Pages/XncfModule/start.js changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 31 in handleRun at line 495. 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-05-27..2026-08-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-27 15:06:43 +08:00' --until='2026-08-25 15:06:43 +08:00' --full-history --no-merges -- src/back-end/Senparc.Areas.Admin/wwwroot/js/Admin/Pages/XncfModule/start.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: REDACTED REDACTED:57 — REDACTED changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in top-level statements at line 57. 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-05-27..2026-08-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-27 15:06:43 +08:00' --until='2026-08-25 15:06:43 +08:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · Medium vulnerability · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×3
  • Duplicated block (5 lines × 2) src/back-end/Senparc.Areas.Admin/OHS/Local/AppService/AdminChatAppService.cs:467 — src/back-end/Senparc.Areas.Admin/OHS/Local/AppService/AdminChatAppService.cs:467-471 | src/back-end/Senparc.Areas.Admin/OHS/Local/AppService/AdminChatAppService.cs:590-594 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/back-end/Senparc.Areas.Admin/OHS/Local/AppService/AdminChatAppService.cs:467` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/back-end/Senparc.Areas.Admin/OHS/Local/AppService/AdminChatAppService.cs:473` calls `Append`, `ToHashSet` and `src/back-end/Senparc.Areas.Admin/OHS/Local/AppService/AdminChatAppService.cs:596` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (5 lines × 2) src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/XncfModule/Index.cshtml.cs:103 — src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/XncfModule/Index.cshtml.cs:103-108 | src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/XncfModule/Index.cshtml.cs:124-128 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/XncfModule/Index.cshtml.cs:103` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (5 lines × 2) src/back-end/Senparc.Areas.Admin/Domain/Services/AdminUserInfoService.cs:458 — src/back-end/Senparc.Areas.Admin/Domain/Services/AdminUserInfoService.cs:458-462 | src/back-end/Senparc.Areas.Admin/Domain/Services/AdminUserInfoService.cs:484-488 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/back-end/Senparc.Areas.Admin/Domain/Services/AdminUserInfoService.cs:484` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
R10 · Code Duplication · Duplicated block (12 lines × 2 locations) · ×3
  • Duplicated block (12 lines × 2 locations) src/front-end/Senparc.Xncf.Admin/src/components/DndList/index.vue:74 — src/front-end/Senparc.Xncf.Admin/src/components/DndList/index.vue:74 · src/front-end/Senparc.Xncf.Admin/src/components/DndList/index.vue:86 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (12 lines × 2 locations) src/front-end/Senparc.Xncf.Admin/src/components/HeaderSearch/index.vue:47 — src/front-end/Senparc.Xncf.Admin/src/components/HeaderSearch/index.vue:47 · src/front-end/Senparc.Xncf.Admin/src/layout/components/TagsView/index.vue:55 — 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 (12 lines × 2 locations) src/front-end/Senparc.Xncf.Admin/src/components/ImageCropper/utils/effectRipple.js:17 — src/front-end/Senparc.Xncf.Admin/src/components/ImageCropper/utils/effectRipple.js:17 · src/front-end/Senparc.Xncf.Admin/src/directive/waves/waves.js:20 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R2 · Cyclomatic Complexity · Complex function editForm (cyclomatic 50, cognitive 65) · ×3
  • Complex function editForm (cyclomatic 50, cognitive 65) src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/lightdemo/antv.vue:560 — editForm has cyclomatic complexity 50 and cognitive complexity 65; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
  • Complex function editForm (cyclomatic 50, cognitive 65) src/front-end/Senparc.Xncf.AdminModule/src/views/XncfStore/lightdemo/antv.vue:557 — editForm has cyclomatic complexity 50 and cognitive complexity 65; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
  • Complex function editForm (cyclomatic 50, cognitive 65) src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/views/Senparc.Xncf.XncfStore/processdemo/antv.vue:560 — editForm has cyclomatic complexity 50 and cognitive complexity 65; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (4.1 · ×2
  • Low contrast colour pair in CSS (4.1:1) src/back-end/Senparc.Web/wwwroot/css/User/base/pagecss.css:395 — `div.scott a:hover` sets color: #638425 on background-color: #f1ffd6 — 4.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
  • Low contrast colour pair in CSS (4.1:1) src/back-end/Senparc.Web/wwwroot/css/User/base/pagecss.css:404 — `div.scott a:active` sets color: #638425 on background-color: #f1ffd6 — 4.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (2.2 · ×2
  • Low contrast colour pair in CSS (2.2:1) src/back-end/Senparc.Web/wwwroot/css/User/base/pagecss.css:944 — `div.starcraft2 span.disabled` sets color: #444 on background-color: #000 — 2.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
  • Low contrast colour pair in CSS (2.2:1) src/back-end/Senparc.Web/wwwroot/css/User/base/pagecss.css:1247 — `div.badoo` sets color: #48b9ef on background-color: #fff — 2.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (4.4 · ×2
  • Low contrast colour pair in CSS (4.4:1) src/back-end/Senparc.Web/wwwroot/css/User/base/pagecss.css:1042 — `div.megas512 a:hover` sets color: #fff on background-color: #777777 — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
  • Low contrast colour pair in CSS (4.4:1) src/back-end/Senparc.Web/wwwroot/css/User/base/pagecss.css:1052 — `div.megas512 a:active` sets color: #fff on background-color: #777777 — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
D35 · Change Coupling · Change coupling · ×2
  • Change coupling: REDACTED ↔ InstallerService.cs REDACTED:1 — `REDACTED` and `src/back-end/Senparc.Xncf.Installer/Domain/Services/InstallerService.cs` change together 62% of the time (13 of the 21 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). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 13 shared commits counted here, the most recent 3 are `caf8608d` Support for new Tenant System; `dd7bc672` 解决冲突; `c3892048` 解决冲突 — run `git show` on any of them.
  • Change coupling: REDACTED ↔ InstallOptionsService.cs REDACTED:1 — `REDACTED` and `src/back-end/Senparc.Xncf.Installer/Domain/Services/InstallOptionsService.cs` change together 54% of the time (7 of the 13 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). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `dd7bc672` 解决冲突; `c3892048` 解决冲突; `6e641c70` 添加了选择安装模块列表选项初步实现初始化系统页面,获取可选安装模块选择功能 — run `git show` on any of them.
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×2
  • Duplicated block (15 lines × 2) src/back-end/Senparc.Areas.Admin/Domain/Models/VD/BaseVD.cs:43 — src/back-end/Senparc.Areas.Admin/Domain/Models/VD/BaseVD.cs:43-57 | src/back-end/Senparc.Web/Models/BaseVD.cs:43-57 — before extracting anything, compare `src/back-end/Senparc.Areas.Admin/Domain/Models/VD/BaseVD.cs` and `src/back-end/Senparc.Web/Models/BaseVD.cs` as WHOLE FILES: 96% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/back-end/Senparc.Areas.Admin/Domain/Models/VD/BaseVD.cs:43` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 2) REDACTED:453 — REDACTED:453-468 | src/back-end/Senparc.Areas.Admin/OHS/Local/AppService/ModuleAppService.cs:369-383 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:453` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×2
  • Duplicated block (7 lines × 2) src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Session.cshtml.cs:48 — src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Session.cshtml.cs:48-54 | src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Session.cshtml.cs:84-90 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Session.cshtml.cs:48` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 2) src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/AdminUserInfo.cs:55 — src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/AdminUserInfo.cs:55-61 | src/back-end/Senparc.Xncf.Accounts/Domain/Services/AccountService.cs:139-145 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
DM12 · Ambient inputs in the domain · Domain type reads a global random source · ×2
  • Domain type reads a global random source: AdminUserInfo src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/AdminUserInfo.cs:117 — `AdminUserInfo` draws from `new Random()` inside `GenerateUserName`. The outcome is not a function of the inputs, so no test can assert which result this produces, and the same inputs replay differently. Take the randomness as a parameter — an injected `Random`, a seeded generator, or the already-chosen value — so a caller (and a test) can decide it.
  • Domain type reads a global random source: InstallOptionsService src/back-end/Senparc.Xncf.Installer/Domain/Services/InstallOptionsService.cs:69 — `InstallOptionsService` draws from `new Random()` inside `GetDefaultAdminUserName`. The outcome is not a function of the inputs, so no test can assert which result this produces, and the same inputs replay differently. Take the randomness as a parameter — an injected `Random`, a seeded generator, or the already-chosen value — so a caller (and a test) can decide it.
GD1 · Unfinished & placeholder code · Unfinished stub · ×2
  • Unfinished stub — throws NotImplementedException src/back-end/Senparc.Xncf.Installer/Register.cs:60 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException src/back-end/Senparc.Xncf.Installer/Register.cs:62 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
IC1 · Incompleteness & stubs · Unfinished stub · ×2
  • Unfinished stub — throws NotImplementedException src/back-end/Senparc.Xncf.Installer/Register.cs:60 — `DatabaseUniquePrefix` is a shipped property whose accessors only throw NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException src/back-end/Senparc.Xncf.Installer/Register.cs:62 — `TryGetXncfDatabaseDbContextType` is a shipped property whose accessors only throw NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
PF3 · Async & latency hygiene · Sync-over-async blocking · ×2
  • Sync-over-async blocking — 1 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking src/back-end/Senparc.Xncf.Accounts/Domain/OperationQueue/OperationQueue.cs:72 — `.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
R10 · Code Duplication · Duplicated block (17 lines × 2 locations) · ×2
  • Duplicated block (17 lines × 2 locations) src/front-end/Senparc.Xncf.Admin/mock/utils.js:5 — src/front-end/Senparc.Xncf.Admin/mock/utils.js:5 · REDACTED:164 — 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 (17 lines × 2 locations) src/front-end/Senparc.Xncf.Admin/src/views/Admin/AdminUserInfo/Index.vue:417 — src/front-end/Senparc.Xncf.Admin/src/views/Admin/AdminUserInfo/Index.vue:417 · src/front-end/Senparc.Xncf.Admin/src/views/Admin/AdminUserInfo/Index.vue:439 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
R10 · Code Duplication · Duplicated block with local edits (17 matched lines × 2 locations) · ×2
  • Duplicated block with local edits (17 matched lines × 2 locations) src/front-end/Senparc.Xncf.Admin/src/views/Admin/Menu/Index.vue:386 — src/front-end/Senparc.Xncf.Admin/src/views/Admin/Menu/Index.vue:386 · src/front-end/Senparc.Xncf.Admin/src/views/Admin/SystemConfig/Index.vue:146 — the two spans are one implementation copied and then locally edited — 62 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
  • Duplicated block with local edits (17 matched lines × 2 locations) src/front-end/Senparc.Xncf.Admin/src/views/Admin/Role/Index.vue:340 — src/front-end/Senparc.Xncf.Admin/src/views/Admin/Role/Index.vue:340 · src/front-end/Senparc.Xncf.Admin/src/views/Admin/Role/Index.vue:398 — the two spans are one implementation copied and then locally edited — 70 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (14 lines × 2 locations) · ×2
  • Duplicated block (14 lines × 2 locations) src/front-end/Senparc.Xncf.Admin/mock/utils.js:30 — src/front-end/Senparc.Xncf.Admin/mock/utils.js:30 · REDACTED:296 — 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 (14 lines × 2 locations) src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/views/Senparc.Xncf.XncfStore/shopping/application.vue:318 — src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/views/Senparc.Xncf.XncfStore/shopping/application.vue:318 · src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/views/Senparc.Xncf.XncfStore/shopping/applicationall.vue:303 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
R10 · Code Duplication · Duplicated block (5 lines × 2 locations) · ×2
  • Duplicated block (5 lines × 2 locations) src/front-end/Senparc.Xncf.Admin/src/components/Dropzone/index.vue:188 — src/front-end/Senparc.Xncf.Admin/src/components/Dropzone/index.vue:188 · src/front-end/Senparc.Xncf.Admin/src/components/Dropzone/index.vue:196 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (5 lines × 2 locations) src/front-end/Senparc.Xncf.Admin/src/components/Tinymce/components/EditorImage.vue:65 — src/front-end/Senparc.Xncf.Admin/src/components/Tinymce/components/EditorImage.vue:65 · src/front-end/Senparc.Xncf.Admin/src/components/Tinymce/components/EditorImage.vue:76 — 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.
R7 · Dead Code · Dead file (~923 LoC) · ×2
  • Dead file (~923 LoC) src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/lightdemo/antv.vue — no import path from any entry point (9 application, 9 tooling, 17 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
  • Dead file (~923 LoC) src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/views/Senparc.Xncf.XncfStore/processdemo/antv.vue — no import path from any entry point (9 application, 9 tooling, 17 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 (~227 LoC) · ×2
  • Dead file (~227 LoC) src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/shopping/application.vue — no import path from any entry point (9 application, 9 tooling, 17 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
  • Dead file (~227 LoC) src/front-end/Senparc.Xncf.AdminModule/src/views/XncfStore/shopping/application.vue — no import path from any entry point (9 application, 9 tooling, 17 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 (~122 LoC) · ×2
  • Dead file (~122 LoC) src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/operation/application.vue — no import path from any entry point (9 application, 9 tooling, 17 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
  • Dead file (~122 LoC) src/front-end/Senparc.Xncf.Admin/src/views/dashboard/admin/components/TodoList/index.vue — no import path from any entry point (9 application, 9 tooling, 17 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 (~90 LoC) · ×2
  • Dead file (~90 LoC) src/front-end/Senparc.Xncf.Admin/src/components/Pagination/index.vue — no import path from any entry point (9 application, 9 tooling, 17 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
  • Dead file (~90 LoC) src/front-end/Senparc.Xncf.Admin/src/directive/sticky.js — no import path from any entry point (9 application, 9 tooling, 17 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
X3 · Exception handling · Swallowed exception (empty catch) · ×2
  • Swallowed exception (empty catch) src/back-end/Senparc.Areas.Admin/Domain/SeparcTraceManager/SenparcTraceHelper.cs:448 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) src/back-end/Senparc.Areas.Admin/OHS/Local/Controllers/AdminChatStreamController.cs:154 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
AC1 · Text alternatives · <canvas> without a text alternative · ×1
  • <canvas> without a text alternative src/front-end/Senparc.Xncf.Admin/src/components/ImageCropper/index.vue:132 — A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content.
AC3 · Page structure · Heading level jumps from h2 to h4 · ×1
  • Heading level jumps from h2 to h4 src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/NeuCharPivot/Aggregate.cshtml:42 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
AC3 · Page structure · Heading level jumps from h2 to h6 · ×1
  • Heading level jumps from h2 to h6 src/front-end/Senparc.Xncf.Admin/src/views/error-page/401.vue:13 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
AC3 · Page structure · Heading level jumps from h1 to h3 · ×1
  • Heading level jumps from h1 to h3 src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/components/HelloWorld.vue:9 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (3.8 · ×1
  • Low contrast colour pair in CSS (3.8:1) src/front-end/Senparc.Xncf.Admin/src/views/error-page/404.vue:201 — `&__return-home` sets color: #ffffff on background-color: #1482f0 — 3.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (1.8 · ×1
  • Low contrast colour pair in CSS (1.8:1) src/back-end/Senparc.Web/wwwroot/css/User/base/pagecss.css:201 — `div.meneame span.current` sets color: #ff6500 on background-color: #ffbe94 — 1.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (1.5 · ×1
  • Low contrast colour pair in CSS (1.5:1) src/back-end/Senparc.Web/wwwroot/css/User/base/pagecss.css:413 — `div.scott span.current` sets color: #fff on background-color: #b2e05d — 1.5:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (2.0 · ×1
  • Low contrast colour pair in CSS (2.0:1) src/back-end/Senparc.Web/wwwroot/css/User/base/pagecss.css:491 — `div.quotes span.current` sets color: #aaa on background-color: #f0f0f0 — 2.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (1.6 · ×1
  • Low contrast colour pair in CSS (1.6:1) src/back-end/Senparc.Web/wwwroot/css/User/base/pagecss.css:819 — `div.yellow span.current` sets color: #fff on background-color: #d9d300 — 1.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC7 · A11y enforcement · Accessibility enforcement below the top rung · ×1
  • Accessibility enforcement below the top rung src/front-end/package.json:55 — No accessibility enforcement found — no a11y linter (eslint-plugin-vuejs-accessibility) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 146 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
D4 · Code Duplication · Duplicated block (48–50 lines × 2) · ×1
  • Duplicated block (48–50 lines × 2) REDACTED:481 — REDACTED:481-528 | src/back-end/Senparc.Areas.Admin/OHS/Local/AppService/ModuleAppService.cs:178-227 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:481` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (29–30 lines × 2) · ×1
  • Duplicated block (29–30 lines × 2) src/back-end/Senparc.Areas.Admin/Domain/Services/InstallerService.cs:211 — src/back-end/Senparc.Areas.Admin/Domain/Services/InstallerService.cs:211-239 | src/back-end/Senparc.Xncf.Installer/Domain/Services/InstallerService.cs:229-258 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/back-end/Senparc.Areas.Admin/Domain/Services/InstallerService.cs:211` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/back-end/Senparc.Areas.Admin/Domain/Services/InstallerService.cs:209` calls `SetTenantInfo`, `GetRequestTenantInfo` and `src/back-end/Senparc.Xncf.Installer/Domain/Services/InstallerService.cs:227` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (21 lines × 2) · ×1
  • Duplicated block (21 lines × 2) src/back-end/Senparc.Areas.Admin/Domain/Models/VD/BaseVD.cs:19 — src/back-end/Senparc.Areas.Admin/Domain/Models/VD/BaseVD.cs:19-39 | src/back-end/Senparc.Web/Models/BaseVD.cs:19-39 — before extracting anything, compare `src/back-end/Senparc.Areas.Admin/Domain/Models/VD/BaseVD.cs` and `src/back-end/Senparc.Web/Models/BaseVD.cs` as WHOLE FILES: 96% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/back-end/Senparc.Areas.Admin/Domain/Models/VD/BaseVD.cs:19` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×1
  • Duplicated block (11 lines × 2) src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Index.cshtml.cs:60 — src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Index.cshtml.cs:60-70 | src/back-end/Senparc.Areas.Admin/OHS/Local/AppService/ModuleAppService.cs:74-84 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×1
  • Duplicated block (12 lines × 2) src/back-end/Senparc.Areas.Admin/Domain/Dto/SystemConfigDto.cs:33 — src/back-end/Senparc.Areas.Admin/Domain/Dto/SystemConfigDto.cs:33-44 | src/back-end/Senparc.Areas.Admin/Domain/Dto/SystemConfigDto.cs:49-60 — 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.
D4 · Code Duplication · Duplicated block (11 lines × 3) · ×1
  • Duplicated block (11 lines × 3) src/back-end/Senparc.Areas.Admin/Domain/Services/InstallerService.cs:39 — src/back-end/Senparc.Areas.Admin/Domain/Services/InstallerService.cs:39-49 | src/back-end/Senparc.Xncf.Installer/Domain/Services/InstallOptionsService.cs:97-107 | src/back-end/Senparc.Xncf.Installer/Domain/Services/InstallerService.cs:56-66 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×1
  • Duplicated block (6 lines × 2) src/back-end/Senparc.Areas.Admin/Domain/Models/MultipleDatabase/SenparcDbContextFactoryConfig.cs:24 — src/back-end/Senparc.Areas.Admin/Domain/Models/MultipleDatabase/SenparcDbContextFactoryConfig.cs:24-29 | src/back-end/Senparc.Xncf.Accounts/Domain/Models/DatabaseModel/MultipleDatabase/SenparcDbContextFactoryConfig.cs:24-29 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/back-end/Senparc.Areas.Admin/Domain/Models/MultipleDatabase/SenparcDbContextFactoryConfig.cs:24` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×1
  • Duplicated block (13 lines × 2) src/back-end/Senparc.Areas.Admin/Domain/Services/AdminAuthConfigService.cs:65 — src/back-end/Senparc.Areas.Admin/Domain/Services/AdminAuthConfigService.cs:65-77 | src/back-end/Senparc.Areas.Admin/Domain/Services/AdminUserInfoService.cs:76-88 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D43 · Malicious Dependencies · Malicious package · ×1
  • REDACTED
D44 · Platform End-of-Life · End-of-life runtime · ×1
  • End-of-life runtime: .NET netcoreapp3.1 src/back-end/Tools/GenerateDbMigration/GenerateDbMigration.csproj:5 — src/back-end/Tools/GenerateDbMigration/GenerateDbMigration.csproj declares .NET netcoreapp3.1 as this project's target framework, and .NET Core 3.1 LTS, support ended 2022-12-13. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2022-12-13 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
P12 · CI test-gate honesty · Coverage collected but not gated · ×1
  • Coverage collected but not gated — CI collects a coverage report but no step enforces a minimum — coverage could halve and CI stays green. Add a step that fails the build when coverage drops below a floor (your coverage tool's minimum-threshold flag, or a coverage-gate action) so the number guards something. What was searched, so you can tell an absence from a miss: this repository's CI files AND its coverage configuration — the well-known coverage and test-runner config files, read at the repository root and inside workspace package directories two levels down, so a floor declared beside the tests rather than in the pipeline is credited — matched against the threshold settings this check knows by name. A floor set in your coverage service's web UI rather than in a committed file, or under a setting whose name is not one of those, is not seen here.
R1 · Type Safety · Type Safety · ×1
  • Type Safety — 0 typed · 198 plain JS — the untyped files are src/back-end/Tests/Senparc.Areas.Admin.Tests/Client/AdminFooterLifecycleTests.js, src/back-end/Tests/Senparc.Areas.Admin.Tests/Client/AgentsA2AHealthTests.js, src/back-end/Tests/Senparc.Areas.Admin.Tests/Client/AgentsGroupStartMentionsTests.js, src/back-end/Tests/Senparc.Areas.Admin.Tests/Client/AgentsOverviewDashboardTests.js, src/back-end/Tests/Senparc.Areas.Admin.Tests/Client/AgentsSystemMessageTypeTests.js, src/back-end/Tests/Senparc.Areas.Admin.Tests/Client/HostMetricsDashboardTests.js (+192 more).
R10 · Code Duplication · Duplication concentrated across 3 sibling directories (10 clone groups) · ×1
  • Duplication concentrated across 3 sibling directories (10 clone groups) src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/lightdemo/antv.vue:352 — 10 duplicated blocks under src/front-end/ have copies in at least two of the sibling directories Senparc.Xncf.Admin, Senparc.Xncf.AdminModule, Senparc.Xncf.XncfStore — 8 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 10 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 10 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 10 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Wholesale file copy (369 identical lines × 3 files) · ×1
  • Wholesale file copy (369 identical lines × 3 files) src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/lightdemo/antv.vue:352 — src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/lightdemo/antv.vue:352 · src/front-end/Senparc.Xncf.AdminModule/src/views/XncfStore/lightdemo/antv.vue:352 · src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/views/Senparc.Xncf.XncfStore/processdemo/antv.vue:352 — these 3 files are line-for-line copies of one another — 369 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 (54 lines × 3 locations) · ×1
  • Duplicated block (54 lines × 3 locations) src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/lightdemo/antvShow.vue:18 — src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/lightdemo/antvShow.vue:18 · src/front-end/Senparc.Xncf.AdminModule/src/views/XncfStore/lightdemo/antvShow.vue:18 · src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/views/Senparc.Xncf.XncfStore/processdemo/antvShow.vue:18 — 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 (46 lines × 2 locations) · ×1
  • Duplicated block (46 lines × 2 locations) src/front-end/Senparc.Xncf.Admin/src/components/Upload/SingleImage.vue:32 — src/front-end/Senparc.Xncf.Admin/src/components/Upload/SingleImage.vue:32 · src/front-end/Senparc.Xncf.Admin/src/components/Upload/SingleImage3.vue:40 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
R10 · Code Duplication · Duplicated block (41 lines × 2 locations) · ×1
  • Duplicated block (41 lines × 2 locations) src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/shopping/detail.vue:318 — src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/shopping/detail.vue:318 · src/front-end/Senparc.Xncf.AdminModule/src/views/XncfStore/shopping/detail.vue:320 — 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 (39 lines × 3 locations) · ×1
  • Duplicated block (39 lines × 3 locations) src/front-end/Senparc.Xncf.Admin/src/components/Upload/SingleImage.vue:32 — src/front-end/Senparc.Xncf.Admin/src/components/Upload/SingleImage.vue:32 · src/front-end/Senparc.Xncf.Admin/src/components/Upload/SingleImage2.vue:32 · src/front-end/Senparc.Xncf.Admin/src/components/Upload/SingleImage3.vue:40 — the 3 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.
R10 · Code Duplication · Duplicated block (39 lines × 2 locations) · ×1
  • Duplicated block (39 lines × 2 locations) src/front-end/Senparc.Xncf.Admin/src/views/dashboard/admin/components/PieChart.vue:10 — src/front-end/Senparc.Xncf.Admin/src/views/dashboard/admin/components/PieChart.vue:10 · src/front-end/Senparc.Xncf.Admin/src/views/dashboard/admin/components/RaddarChart.vue:12 — 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 (38 lines × 2 locations) · ×1
  • Duplicated block (38 lines × 2 locations) src/front-end/Senparc.Xncf.Admin/plop-templates/component/prompt.js:8 — src/front-end/Senparc.Xncf.Admin/plop-templates/component/prompt.js:8 · src/front-end/Senparc.Xncf.Admin/plop-templates/view/prompt.js:8 — 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 (38 lines × 3 locations) · ×1
  • Duplicated block (38 lines × 3 locations) src/front-end/Senparc.Xncf.Admin/src/components/Charts/Keyboard.vue:9 — src/front-end/Senparc.Xncf.Admin/src/components/Charts/Keyboard.vue:9 · src/front-end/Senparc.Xncf.Admin/src/components/Charts/LineMarker.vue:9 · src/front-end/Senparc.Xncf.Admin/src/components/Charts/MixChart.vue:9 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (36 lines × 2 locations) · ×1
  • Duplicated block (36 lines × 2 locations) src/front-end/Senparc.Xncf.Admin/src/views/dashboard/admin/components/BarChart.vue:10 — src/front-end/Senparc.Xncf.Admin/src/views/dashboard/admin/components/BarChart.vue:10 · src/front-end/Senparc.Xncf.Admin/src/views/dashboard/admin/components/PieChart.vue:10 — 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 (32 lines × 4 locations) · ×1
  • Duplicated block (32 lines × 4 locations) src/front-end/Senparc.Xncf.Admin/src/utils/antvSetting.js:39 — src/front-end/Senparc.Xncf.Admin/src/utils/antvSetting.js:39 · src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/lightdemo/antvShow.vue:27 · src/front-end/Senparc.Xncf.AdminModule/src/views/XncfStore/lightdemo/antvShow.vue:27 · src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/views/Senparc.Xncf.XncfStore/processdemo/antvShow.vue:27 — the 4 copies are spread across 4 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (30 lines × 2 locations) · ×1
  • Duplicated block (30 lines × 2 locations) src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/shopping/application.vue:182 — src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/shopping/application.vue:182 · src/front-end/Senparc.Xncf.AdminModule/src/views/XncfStore/shopping/application.vue: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 (27 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (27 matched lines × 2 locations) src/front-end/Senparc.Xncf.Admin/src/components/Charts/mixins/resize.js:1 — src/front-end/Senparc.Xncf.Admin/src/components/Charts/mixins/resize.js:1 · src/front-end/Senparc.Xncf.Admin/src/views/dashboard/admin/components/mixins/resize.js:1 — the two spans are one implementation copied and then locally edited — 121 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (25 lines × 2 locations) · ×1
  • Duplicated block (25 lines × 2 locations) src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/shopping/Index.vue:143 — src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/shopping/Index.vue:143 · src/front-end/Senparc.Xncf.AdminModule/src/views/XncfStore/shopping/Index.vue:139 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block with local edits (24 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (24 matched lines × 2 locations) src/front-end/Senparc.Xncf.Admin/src/views/Admin/Menu/Index.vue:386 — src/front-end/Senparc.Xncf.Admin/src/views/Admin/Menu/Index.vue:386 · src/front-end/Senparc.Xncf.Admin/src/views/Admin/TenantInfo/Index.vue:272 — the two spans are one implementation copied and then locally edited — 108 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 (22 lines × 2 locations) · ×1
  • Duplicated block (22 lines × 2 locations) src/front-end/Senparc.Xncf.Admin/src/store/modules/tagsView.js:82 — src/front-end/Senparc.Xncf.Admin/src/store/modules/tagsView.js:82 · src/front-end/Senparc.Xncf.Admin/src/store/modules/tagsView.js:105 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
R10 · Code Duplication · Duplicated block (20 lines × 2 locations) · ×1
  • Duplicated block (20 lines × 2 locations) src/front-end/Senparc.Xncf.Admin/src/views/Admin/XncfModule/Start.vue:888 — src/front-end/Senparc.Xncf.Admin/src/views/Admin/XncfModule/Start.vue:888 · src/front-end/Senparc.Xncf.Admin/src/views/Admin/XncfModule/Start.vue:909 — 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 (19 lines × 2 locations) · ×1
  • Duplicated block (19 lines × 2 locations) src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/operation/application.vue:100 — src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/operation/application.vue:100 · src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/views/Senparc.Xncf.XncfStore/operation/application.vue:213 — 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 (16 lines × 4 locations) · ×1
  • Duplicated block (16 lines × 4 locations) src/front-end/Senparc.Xncf.Admin/src/views/dashboard/admin/components/BarChart.vue:30 — src/front-end/Senparc.Xncf.Admin/src/views/dashboard/admin/components/BarChart.vue:30 · src/front-end/Senparc.Xncf.Admin/src/views/dashboard/admin/components/LineChart.vue:46 · src/front-end/Senparc.Xncf.Admin/src/views/dashboard/admin/components/PieChart.vue:30 · src/front-end/Senparc.Xncf.Admin/src/views/dashboard/admin/components/RaddarChart.vue:32 — the 4 copies are spread across 4 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (13 lines × 3 locations) · ×1
  • Duplicated block (13 lines × 3 locations) src/front-end/Senparc.Xncf.Admin/src/views/Admin/XncfModule/Index.vue:564 — src/front-end/Senparc.Xncf.Admin/src/views/Admin/XncfModule/Index.vue:564 · src/front-end/Senparc.Xncf.Admin/src/views/Admin/XncfModule/Index.vue:581 · src/front-end/Senparc.Xncf.Admin/src/views/Admin/XncfModule/Index.vue:598 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
R10 · Code Duplication · Duplicated block (13 lines × 2 locations) · ×1
  • Duplicated block (13 lines × 2 locations) src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/shopping/detail.vue:356 — src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/shopping/detail.vue:356 · src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/views/Senparc.Xncf.XncfStore/shopping/detail.vue:422 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block with local edits (9 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (9 matched lines × 2 locations) src/front-end/Senparc.Xncf.Admin/src/directive/clipboard/clipboard.js:8 — src/front-end/Senparc.Xncf.Admin/src/directive/clipboard/clipboard.js:8 · src/front-end/Senparc.Xncf.Admin/src/directive/clipboard/clipboard.js:29 — the two spans are one implementation copied and then locally edited — 66 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (6 lines × 2 locations) · ×1
  • Duplicated block (6 lines × 2 locations) src/front-end/Senparc.Xncf.Admin/src/components/Dropzone/index.vue:112 — src/front-end/Senparc.Xncf.Admin/src/components/Dropzone/index.vue:112 · src/front-end/Senparc.Xncf.Admin/src/components/Dropzone/index.vue:121 — 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.
R11 · Import Boundaries · Boundary violation [package · ×1
  • Boundary violation [package:third-party-deep-import] src/front-end/Senparc.Xncf.Admin/src/directive/el-table/adaptive.js:1 — src/front-end/Senparc.Xncf.Admin/src/directive/el-table/adaptive.js:1 imports element-ui/src/utils/resize-event, 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.
R2 · Cyclomatic Complexity · Complex function handleRun (cyclomatic 27, cognitive 39) · ×1
  • Complex function handleRun (cyclomatic 27, cognitive 39) src/front-end/Senparc.Xncf.Admin/src/views/Admin/XncfModule/Start.vue:859 — handleRun has cyclomatic complexity 27 and cognitive complexity 39; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 11, cognitive 16) · ×1
  • Complex function (anonymous) (cyclomatic 11, cognitive 16) src/front-end/Senparc.Xncf.Admin/src/store/modules/permission.js:166 — (anonymous) has cyclomatic complexity 11 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 searchInfo (cyclomatic 11, cognitive 12) · ×1
  • Complex function searchInfo (cyclomatic 11, cognitive 12) src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/views/Senparc.Xncf.XncfStore/shopping/Index.vue:211 — searchInfo has cyclomatic complexity 11 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files · src/front-end/Senparc.Xncf.Admin/src/components/ImageCropper/index.vue · ×1
  • src/front-end/Senparc.Xncf.Admin/src/components/ImageCropper/index.vue: 1772 lines of code src/front-end/Senparc.Xncf.Admin/src/components/ImageCropper/index.vue:1 — src/front-end/Senparc.Xncf.Admin/src/components/ImageCropper/index.vue has 1772 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · src/front-end/Senparc.Xncf.Admin/src/views/Admin/XncfModule/Start.vue · ×1
  • src/front-end/Senparc.Xncf.Admin/src/views/Admin/XncfModule/Start.vue: 1215 lines of code src/front-end/Senparc.Xncf.Admin/src/views/Admin/XncfModule/Start.vue:1 — src/front-end/Senparc.Xncf.Admin/src/views/Admin/XncfModule/Start.vue has 1215 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/lightdemo/antv.vue · ×1
  • src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/lightdemo/antv.vue: 1110 lines of code src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/lightdemo/antv.vue:1 — src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/lightdemo/antv.vue has 1110 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/views/Senparc.Xncf.XncfStore/processdemo/antv.vue · ×1
  • src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/views/Senparc.Xncf.XncfStore/processdemo/antv.vue: 1110 lines of code src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/views/Senparc.Xncf.XncfStore/processdemo/antv.vue:1 — src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/views/Senparc.Xncf.XncfStore/processdemo/antv.vue has 1110 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · src/front-end/Senparc.Xncf.AdminModule/src/views/XncfStore/lightdemo/antv.vue · ×1
  • src/front-end/Senparc.Xncf.AdminModule/src/views/XncfStore/lightdemo/antv.vue: 1106 lines of code src/front-end/Senparc.Xncf.AdminModule/src/views/XncfStore/lightdemo/antv.vue:1 — src/front-end/Senparc.Xncf.AdminModule/src/views/XncfStore/lightdemo/antv.vue has 1106 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · src/front-end/Senparc.Xncf.Admin/src/views/Admin/XncfModule/Index.vue · ×1
  • src/front-end/Senparc.Xncf.Admin/src/views/Admin/XncfModule/Index.vue: 778 lines of code src/front-end/Senparc.Xncf.Admin/src/views/Admin/XncfModule/Index.vue:1 — src/front-end/Senparc.Xncf.Admin/src/views/Admin/XncfModule/Index.vue has 778 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/views/Senparc.Xncf.XncfStore/shopping/detail.vue · ×1
  • src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/views/Senparc.Xncf.XncfStore/shopping/detail.vue: 768 lines of code src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/views/Senparc.Xncf.XncfStore/shopping/detail.vue:1 — src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/views/Senparc.Xncf.XncfStore/shopping/detail.vue has 768 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/shopping/detail.vue · ×1
  • src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/shopping/detail.vue: 609 lines of code src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/shopping/detail.vue:1 — src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/shopping/detail.vue has 609 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · src/front-end/Senparc.Xncf.AdminModule/src/views/XncfStore/shopping/detail.vue · ×1
  • src/front-end/Senparc.Xncf.AdminModule/src/views/XncfStore/shopping/detail.vue: 605 lines of code src/front-end/Senparc.Xncf.AdminModule/src/views/XncfStore/shopping/detail.vue:1 — src/front-end/Senparc.Xncf.AdminModule/src/views/XncfStore/shopping/detail.vue has 605 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · src/front-end/Senparc.Xncf.Admin/src/views/Admin/AdminUserInfo/Index.vue · ×1
  • src/front-end/Senparc.Xncf.Admin/src/views/Admin/AdminUserInfo/Index.vue: 543 lines of code src/front-end/Senparc.Xncf.Admin/src/views/Admin/AdminUserInfo/Index.vue:1 — src/front-end/Senparc.Xncf.Admin/src/views/Admin/AdminUserInfo/Index.vue has 543 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · src/front-end/Senparc.Xncf.Admin/src/utils/antvSetting.js · ×1
  • src/front-end/Senparc.Xncf.Admin/src/utils/antvSetting.js: 473 lines of code src/front-end/Senparc.Xncf.Admin/src/utils/antvSetting.js:1 — src/front-end/Senparc.Xncf.Admin/src/utils/antvSetting.js has 473 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/views/Senparc.Xncf.XncfStore/shopping/application.vue · ×1
  • src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/views/Senparc.Xncf.XncfStore/shopping/application.vue: 455 lines of code src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/views/Senparc.Xncf.XncfStore/shopping/application.vue:1 — src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/views/Senparc.Xncf.XncfStore/shopping/application.vue has 455 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · src/front-end/Senparc.Xncf.Admin/src/views/Admin/Menu/Index.vue · ×1
  • src/front-end/Senparc.Xncf.Admin/src/views/Admin/Menu/Index.vue: 452 lines of code src/front-end/Senparc.Xncf.Admin/src/views/Admin/Menu/Index.vue:1 — src/front-end/Senparc.Xncf.Admin/src/views/Admin/Menu/Index.vue has 452 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · src/front-end/Senparc.Xncf.Admin/src/views/Admin/Role/Index.vue · ×1
  • src/front-end/Senparc.Xncf.Admin/src/views/Admin/Role/Index.vue: 449 lines of code src/front-end/Senparc.Xncf.Admin/src/views/Admin/Role/Index.vue:1 — src/front-end/Senparc.Xncf.Admin/src/views/Admin/Role/Index.vue has 449 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/views/Senparc.Xncf.XncfStore/shopping/applicationall.vue · ×1
  • src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/views/Senparc.Xncf.XncfStore/shopping/applicationall.vue: 435 lines of code src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/views/Senparc.Xncf.XncfStore/shopping/applicationall.vue:1 — src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/views/Senparc.Xncf.XncfStore/shopping/applicationall.vue has 435 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R5 · Dependency Freshness · Dependency Freshness · ×1
  • Dependency Freshness — 34 outdated package(s); JS/npm CVEs scored in D30
R6 · Tooling · No typecheck script · ×1
  • No typecheck script — test ✓ · lint ✓ · typecheck ✗ — read from this repository's REDACTED scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
R7 · Dead Code · Dead file (~1048 LoC) · ×1
  • Dead file (~1048 LoC) src/front-end/Senparc.Xncf.Admin/src/views/Admin/XncfModule/Start.vue — no import path from any entry point (9 application, 9 tooling, 17 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 (~919 LoC) · ×1
  • Dead file (~919 LoC) src/front-end/Senparc.Xncf.AdminModule/src/views/XncfStore/lightdemo/antv.vue — no import path from any entry point (9 application, 9 tooling, 17 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 (~818 LoC) · ×1
  • Dead file (~818 LoC) src/front-end/Senparc.Xncf.Admin/src/components/ImageCropper/index.vue — no import path from any entry point (9 application, 9 tooling, 17 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 (~622 LoC) · ×1
  • Dead file (~622 LoC) src/front-end/Senparc.Xncf.Admin/src/views/Admin/Menu/icons.js — no import path from any entry point (9 application, 9 tooling, 17 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/front-end/Senparc.Xncf.Admin/src/views/Admin/Menu/Index.vue) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~613 LoC) · ×1
  • Dead file (~613 LoC) src/front-end/Senparc.Xncf.Admin/src/views/Admin/XncfModule/Index.vue — no import path from any entry point (9 application, 9 tooling, 17 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 (~534 LoC) · ×1
  • Dead file (~534 LoC) src/front-end/Senparc.Xncf.Admin/src/views/Admin/AdminUserInfo/Index.vue — no import path from any entry point (9 application, 9 tooling, 17 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 (~478 LoC) · ×1
  • Dead file (~478 LoC) src/front-end/Senparc.Xncf.Admin/src/utils/antvSetting.js — no import path from any entry point (9 application, 9 tooling, 17 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/lightdemo/antv.vue, src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/lightdemo/antvShow.vue) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~453 LoC) · ×1
  • Dead file (~453 LoC) src/front-end/Senparc.Xncf.Admin/src/views/Admin/Role/Index.vue — no import path from any entry point (9 application, 9 tooling, 17 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 (~426 LoC) · ×1
  • Dead file (~426 LoC) src/front-end/Senparc.Xncf.Admin/src/views/Admin/Menu/Index.vue — no import path from any entry point (9 application, 9 tooling, 17 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 (~375 LoC) · ×1
  • Dead file (~375 LoC) src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/shopping/detail.vue — no import path from any entry point (9 application, 9 tooling, 17 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 (~371 LoC) · ×1
  • Dead file (~371 LoC) src/front-end/Senparc.Xncf.AdminModule/src/views/XncfStore/shopping/detail.vue — no import path from any entry point (9 application, 9 tooling, 17 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 (~320 LoC) · ×1
  • Dead file (~320 LoC) src/front-end/Senparc.Xncf.Admin/src/views/Admin/TenantInfo/Index.vue — no import path from any entry point (9 application, 9 tooling, 17 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 (~319 LoC) · ×1
  • Dead file (~319 LoC) src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/views/Senparc.Xncf.XncfStore/shopping/applicationall.vue — no import path from any entry point (9 application, 9 tooling, 17 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 (~270 LoC) · ×1
  • Dead file (~270 LoC) src/front-end/Senparc.Xncf.Admin/src/components/Charts/MixChart.vue — no import path from any entry point (9 application, 9 tooling, 17 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 (~251 LoC) · ×1
  • Dead file (~251 LoC) src/front-end/Senparc.Xncf.XncfStore/xncfstore/src/views/Senparc.Xncf.XncfStore/operation/application.vue — no import path from any entry point (9 application, 9 tooling, 17 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 (~232 LoC) · ×1
  • Dead file (~232 LoC) src/front-end/Senparc.Xncf.Admin/src/components/ImageCropper/utils/language.js — no import path from any entry point (9 application, 9 tooling, 17 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/front-end/Senparc.Xncf.Admin/src/components/ImageCropper/index.vue) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~226 LoC) · ×1
  • Dead file (~226 LoC) src/front-end/Senparc.Xncf.Admin/src/components/Charts/LineMarker.vue — no import path from any entry point (9 application, 9 tooling, 17 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 (~210 LoC) · ×1
  • Dead file (~210 LoC) src/front-end/Senparc.Xncf.Admin/src/components/Tinymce/index.vue — no import path from any entry point (9 application, 9 tooling, 17 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 (~205 LoC) · ×1
  • Dead file (~205 LoC) src/front-end/Senparc.Xncf.Admin/src/components/Dropzone/index.vue — no import path from any entry point (9 application, 9 tooling, 17 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 (~197 LoC) · ×1
  • Dead file (~197 LoC) src/front-end/Senparc.Xncf.Admin/src/components/MDinput/index.vue — no import path from any entry point (9 application, 9 tooling, 17 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 (~191 LoC) · ×1
  • Dead file (~191 LoC) src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/shopping/Index.vue — no import path from any entry point (9 application, 9 tooling, 17 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 (~175 LoC) · ×1
  • Dead file (~175 LoC) src/front-end/Senparc.Xncf.Admin/src/views/XncfStore/cells/index.vue — no import path from any entry point (9 application, 9 tooling, 17 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 (~172 LoC) · ×1
  • Dead file (~172 LoC) src/front-end/Senparc.Xncf.Admin/src/views/Admin/SystemConfig/Index.vue — no import path from any entry point (9 application, 9 tooling, 17 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 (~154 LoC) · ×1
  • Dead file (~154 LoC) src/front-end/Senparc.Xncf.Admin/src/components/Charts/Keyboard.vue — no import path from any entry point (9 application, 9 tooling, 17 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 (~118 LoC) · ×1
  • Dead file (~118 LoC) src/front-end/Senparc.Xncf.Admin/src/components/UploadExcel/index.vue — no import path from any entry point (9 application, 9 tooling, 17 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 (~117 LoC) · ×1
  • Dead file (~117 LoC) src/front-end/Senparc.Xncf.Admin/src/components/MarkdownEditor/index.vue — no import path from any entry point (9 application, 9 tooling, 17 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 (~115 LoC) · ×1
  • Dead file (~115 LoC) src/front-end/Senparc.Xncf.Admin/src/views/dashboard/admin/components/RaddarChart.vue — no import path from any entry point (9 application, 9 tooling, 17 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 (~104 LoC) · ×1
  • Dead file (~104 LoC) src/front-end/Senparc.Xncf.Admin/src/components/DndList/index.vue — no import path from any entry point (9 application, 9 tooling, 17 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 (~101 LoC) · ×1
  • Dead file (~101 LoC) src/front-end/Senparc.Xncf.Admin/src/components/Tinymce/components/EditorImage.vue — no import path from any entry point (9 application, 9 tooling, 17 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/front-end/Senparc.Xncf.Admin/src/components/Tinymce/index.vue) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~85 LoC) · ×1
  • Dead file (~85 LoC) src/front-end/Senparc.Xncf.Admin/src/components/Upload/SingleImage3.vue — no import path from any entry point (9 application, 9 tooling, 17 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 · Unused dependency '@vue/cli-plugin-unit-jest' · ×1
  • Unused dependency '@vue/cli-plugin-unit-jest' — Declared in src/front-end/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 'core-js' · ×1
  • Unused dependency 'core-js' — Declared in src/front-end/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 'driver.js' · ×1
  • Unused dependency 'driver.js' — Declared in src/front-end/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.
SC1 · Supply-chain hygiene · NuGet dependencies are not locked · ×1
  • NuGet dependencies are not locked — No packages.lock.json and no central package management — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
X1 · Async correctness · Blocking `Thread.Sleep` inside an `async` method · ×1
  • Blocking `Thread.Sleep` inside an `async` method src/back-end/Senparc.Areas.Admin/OHS/Local/AppService/SystemInfoAppService.cs:267 — `Thread.Sleep` parks the thread for the whole delay: no other work runs on it, and under load the pool must grow to make up for it. `await Task.Delay(…)` suspends only this method.
X1 · Async correctness · Blocking `FileStream.Flush` inside an `async` method · ×1
  • Blocking `FileStream.Flush` inside an `async` method src/back-end/Senparc.Xncf.Accounts/Domain/OperationQueue/OperationQueueService.cs:48 — `FileStream.Flush` blocks the thread on I/O while `FileStream.FlushAsync` exists to wait without one — inside a method that is already `async`, await the twin.
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×1
  • Swallowed exception (caught, then discarded) src/back-end/Senparc.Areas.Admin/Domain/Services/NeuCharPivotService.cs:314 — `catch (JsonException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
Minor — 150 finding(s)
IC1 · Incompleteness & stubs · Commented-out code · ×33
  • Commented-out code src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/AdminUserInfo/Edit.cshtml.cs:71 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/AdminUserInfo/Index.cshtml.cs:86 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Index.cshtml.cs:51 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Index.cshtml.cs:111 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code REDACTED:61 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code REDACTED:67 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code REDACTED:69 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code REDACTED:81 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code REDACTED:83 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code REDACTED:155 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code REDACTED:163 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Menu/Edit.cshtml.cs:63 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Role/Edit.cshtml.cs:95 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Role/Edit.cshtml.cs:96 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Role/Index.cshtml.cs:69 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Role/Permission.cshtml.cs:42 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/SenparcTrace/Index.cshtml.cs:20 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/XncfModule/Index.cshtml.cs:95 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/XncfModule/Index.cshtml.cs:131 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/XncfModule/Index.cshtml.cs:135 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/XncfModule/Index.cshtml.cs:172 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/XncfModule/Index.cshtml.cs:213 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/XncfModule/Index.cshtml.cs:214 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/XncfModule/Index.cshtml.cs:216 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code REDACTED:101 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • + 8 more in this group — see findings.md.
D30 · Dependency Vulnerabilities · Low CVE · ×25
  • 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
DM2 · Strongly-typed ids · Primitive id on a domain type · ×21
  • Primitive id on a domain type: AdminChatMessage.SessionId src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/AdminChatMessage.cs:18 — `AdminChatMessage.SessionId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that.
  • Primitive id on a domain type: AdminChatSession.UserId src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/AdminChatSession.cs:24 — `AdminChatSession.UserId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that.
  • Primitive id on a domain type: AdminChatSessionModule.SessionId src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/AdminChatSessionModule.cs:18 — `AdminChatSessionModule.SessionId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that.
  • Primitive id on a domain type: AdminChatSessionWorkflow.SessionId src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/AdminChatSessionWorkflow.cs:29 — `AdminChatSessionWorkflow.SessionId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that.
  • Primitive id on a domain type: AdminChatSessionWorkflow.WorkflowId src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/AdminChatSessionWorkflow.cs:32 — `AdminChatSessionWorkflow.WorkflowId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that.
  • Primitive id on a domain type: NeuCharPivotConfiguration.AiModelId src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/NeuCharPivotModels.cs:36 — `NeuCharPivotConfiguration.AiModelId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that.
  • Primitive id on a domain type: NeuCharPivotConfiguration.AdminUserId src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/NeuCharPivotModels.cs:38 — `NeuCharPivotConfiguration.AdminUserId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that.
  • Primitive id on a domain type: NeuCharPivotConfiguration.ChatSessionId src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/NeuCharPivotModels.cs:40 — `NeuCharPivotConfiguration.ChatSessionId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that.
  • Primitive id on a domain type: NeuCharPivotFunction.PivotId src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/NeuCharPivotModels.cs:94 — `NeuCharPivotFunction.PivotId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that.
  • Primitive id on a domain type: NeuCharPivotFunction.FunctionKey src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/NeuCharPivotModels.cs:99 — `NeuCharPivotFunction.FunctionKey` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that.
  • Primitive id on a domain type: NeuCharPivotLoopTask.FunctionId src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/NeuCharPivotModels.cs:161 — `NeuCharPivotLoopTask.FunctionId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that.
  • Primitive id on a domain type: NeuCharPivotLoopTask.AdminUserId src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/NeuCharPivotModels.cs:163 — `NeuCharPivotLoopTask.AdminUserId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that.
  • Primitive id on a domain type: NeuCharExecutionLog.SourceId src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/NeuCharPivotModels.cs:243 — `NeuCharExecutionLog.SourceId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that.
  • Primitive id on a domain type: NeuCharExecutionLog.FunctionKey src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/NeuCharPivotModels.cs:248 — `NeuCharExecutionLog.FunctionKey` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that.
  • Primitive id on a domain type: NeuCharExecutionLog.CorrelationId src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/NeuCharPivotModels.cs:264 — `NeuCharExecutionLog.CorrelationId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that.
  • Primitive id on a domain type: Account.WeixinUnionId src/back-end/Senparc.Xncf.Accounts/Domain/Models/DatabaseModel/Account.cs:55 — `Account.WeixinUnionId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that.
  • Primitive id on a domain type: Account.WeixinOpenId src/back-end/Senparc.Xncf.Accounts/Domain/Models/DatabaseModel/Account.cs:57 — `Account.WeixinOpenId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that.
  • Primitive id on a domain type: AccountPayLog.AccountId src/back-end/Senparc.Xncf.Accounts/Domain/Models/DatabaseModel/AccountPayLog.cs:19 — `AccountPayLog.AccountId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that.
  • Primitive id on a domain type: AccountPayLog.PrepayId src/back-end/Senparc.Xncf.Accounts/Domain/Models/DatabaseModel/AccountPayLog.cs:41 — `AccountPayLog.PrepayId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that.
  • Primitive id on a domain type: PointsLog.AccountId src/back-end/Senparc.Xncf.Accounts/Domain/Models/DatabaseModel/PointsLog.cs:13 — `PointsLog.AccountId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that.
  • Primitive id on a domain type: PointsLog.AccountPayLogId src/back-end/Senparc.Xncf.Accounts/Domain/Models/DatabaseModel/PointsLog.cs:14 — `PointsLog.AccountPayLogId` is a raw `Int32` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int32`, in whatever form your language spells that.
X10 · Duplicated predicate · Duplicated predicate · ×19
  • Duplicated predicate REDACTED:194 — `!SiteConfig.IsInstalling || installRequestDto == null` appears character-identically in 2 files — REDACTED, src/back-end/Senparc.Xncf.Installer/Domain/Services/InstallerService.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/back-end/Senparc.Areas.Admin/wwwroot/js/Admin/Pages/XncfModule/start.js:567 — `(res.data.log || '').length > 0 && (res.data.tempId || '').length > 0` appears character-identically in 2 files — src/back-end/Senparc.Areas.Admin/wwwroot/js/Admin/Pages/XncfModule/start.js, src/back-end/Senparc.Areas.Admin/wwwroot/js/Admin/Pages/XncfModule/startOld.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 src/back-end/Senparc.Areas.Admin/wwwroot/js/Admin/Pages/AdminChat/Chat.js:79 — `event.key === 'Enter' && (event.ctrlKey || event.metaKey)` appears character-identically in 2 files — src/back-end/Senparc.Areas.Admin/wwwroot/js/Admin/Pages/AdminChat/Chat.js, src/back-end/Senparc.Areas.Admin/wwwroot/js/Admin/Pages/AdminChat/ChatLauncherMixin.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 src/back-end/Senparc.Areas.Admin/wwwroot/js/Admin/Pages/NeuCharPivot/common.js:30 — `parameter.parameterType === 2 && !Array.isArray(value)` appears character-identically in 2 files — src/back-end/Senparc.Areas.Admin/wwwroot/js/Admin/Pages/NeuCharPivot/common.js, src/back-end/Senparc.Areas.Admin/wwwroot/js/Admin/Pages/XncfModule/start.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 src/back-end/Senparc.Areas.Admin/wwwroot/js/Admin/Pages/XncfModule/start.js:445 — `res.parameterType === 1 && res.selectionList.items` appears character-identically in 2 files — src/back-end/Senparc.Areas.Admin/wwwroot/js/Admin/Pages/XncfModule/start.js, src/back-end/Senparc.Areas.Admin/wwwroot/js/Admin/Pages/XncfModule/startOld.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 src/back-end/Senparc.Areas.Admin/wwwroot/js/Admin/Pages/XncfModule/start.js:434 — `res.parameterType === 2 && res.selectionList.items` appears character-identically in 2 files — src/back-end/Senparc.Areas.Admin/wwwroot/js/Admin/Pages/XncfModule/start.js, src/back-end/Senparc.Areas.Admin/wwwroot/js/Admin/Pages/XncfModule/startOld.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 src/back-end/Senparc.Areas.Admin/wwwroot/js/Admin/Pages/AdminChat/Chat.js:58 — `response.data && response.data.success && response.data.data` appears character-identically in 2 files — src/back-end/Senparc.Areas.Admin/wwwroot/js/Admin/Pages/AdminChat/Chat.js, src/back-end/Senparc.Areas.Admin/wwwroot/js/Admin/Pages/AdminChat/ChatLauncherMixin.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 src/front-end/Senparc.Xncf.Admin/mock/utils.js:36 — `source[keys] && typeof source[keys] === 'object'` appears character-identically in 2 files — src/front-end/Senparc.Xncf.Admin/mock/utils.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 src/front-end/Senparc.Xncf.Admin/src/components/Charts/mixins/resize.js:43 — `this.$_sidebarElm && this.$_sidebarElm.addEventListener('transitionend', this.$_sidebarResizeHandler)` appears character-identically in 2 files — src/front-end/Senparc.Xncf.Admin/src/components/Charts/mixins/resize.js, src/front-end/Senparc.Xncf.Admin/src/views/dashboard/admin/components/mixins/resize.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 src/front-end/Senparc.Xncf.Admin/src/components/Charts/mixins/resize.js:49 — `this.$_sidebarElm && this.$_sidebarElm.removeEventListener('transitionend', this.$_sidebarResizeHandler)` appears character-identically in 2 files — src/front-end/Senparc.Xncf.Admin/src/components/Charts/mixins/resize.js, src/front-end/Senparc.Xncf.Admin/src/views/dashboard/admin/components/mixins/resize.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 src/back-end/Senparc.Areas.Admin/wwwroot/js/Admin/Pages/XncfModule/start.js:497 — `this.runData.hasOwnProperty('SourcePath') && this.runData.SourcePath.length < 1` appears character-identically in 2 files — src/back-end/Senparc.Areas.Admin/wwwroot/js/Admin/Pages/XncfModule/start.js, src/back-end/Senparc.Areas.Admin/wwwroot/js/Admin/Pages/XncfModule/startOld.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 src/back-end/Senparc.Areas.Admin/wwwroot/js/Admin/Pages/XncfModule/start.js:514 — `this.runData[i].item.isRequired && this.runData[i].value.length === 0` appears character-identically in 2 files — src/back-end/Senparc.Areas.Admin/wwwroot/js/Admin/Pages/XncfModule/start.js, src/back-end/Senparc.Areas.Admin/wwwroot/js/Admin/Pages/XncfModule/startOld.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 src/back-end/Senparc.Areas.Admin/wwwroot/js/Admin/Pages/NeuCharPivot/common.js:36 — `value === null || typeof value === 'undefined'` appears character-identically in 2 files — src/back-end/Senparc.Areas.Admin/wwwroot/js/Admin/Pages/NeuCharPivot/common.js, src/back-end/Senparc.Areas.Admin/wwwroot/js/Admin/Pages/XncfModule/start.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 src/back-end/Senparc.Areas.Admin/wwwroot/js/Admin/Pages/NeuCharPivot/common.js:50 — `value === null || typeof value === 'undefined' || value === '' || (Array.isArray(value) && value.length === 0)` appears character-identically in 2 files — src/back-end/Senparc.Areas.Admin/wwwroot/js/Admin/Pages/NeuCharPivot/common.js, src/back-end/Senparc.Areas.Admin/wwwroot/js/Admin/Pages/XncfModule/start.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 src/back-end/Senparc.Areas.Admin/wwwroot/js/Admin/Pages/NeuCharPivot/common.js:35 — `value === true || value === 'true' || value === 'True'` appears character-identically in 2 files — src/back-end/Senparc.Areas.Admin/wwwroot/js/Admin/Pages/NeuCharPivot/common.js, src/back-end/Senparc.Areas.Admin/wwwroot/js/Admin/Pages/XncfModule/start.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 src/front-end/Senparc.Xncf.Admin/plop-templates/component/prompt.js:32 — `value.indexOf('script') === -1 && value.indexOf('template') === -1` appears character-identically in 2 files — src/front-end/Senparc.Xncf.Admin/plop-templates/component/prompt.js, src/front-end/Senparc.Xncf.Admin/plop-templates/view/prompt.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 src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/NeuCharPivot/Aggregate.cshtml.cs:91 — `request == null || request.FunctionId <= 0` appears character-identically in 2 files — src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/NeuCharPivot/Aggregate.cshtml.cs, 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 src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/NeuCharPivot/Aggregate.cshtml.cs:75 — `snapshot.FunctionAvailability.TryGetValue(function.Id, out var available) && available` appears character-identically in 2 files — src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/NeuCharPivot/Aggregate.cshtml.cs, 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 src/back-end/Senparc.Areas.Admin/Domain/Services/AdminUserInfoService.cs:168 — `z.Id != id && z.UserName.ToUpper() == userName` appears character-identically in 2 files — src/back-end/Senparc.Areas.Admin/Domain/Services/AdminUserInfoService.cs, src/back-end/Senparc.Xncf.Accounts/Domain/Services/AccountService.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
P2 · Observability · Console output used as the logging channel · ×14
  • Console output used as the logging channel src/back-end/Senparc.Areas.Admin/Domain/Services/AdminChatAiService.cs:501 — `src/back-end/Senparc.Areas.Admin/Domain/Services/AdminChatAiService.cs` reports through `Console.Write…` at line 501 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
  • Console output used as the logging channel src/back-end/Senparc.Areas.Admin/Domain/Services/AdminChatAiService.cs:504 — `src/back-end/Senparc.Areas.Admin/Domain/Services/AdminChatAiService.cs` reports through `Console.Write…` at line 504 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
  • Console output used as the logging channel src/back-end/Senparc.Xncf.Installer/Domain/Services/InstallerService.cs:191 — `src/back-end/Senparc.Xncf.Installer/Domain/Services/InstallerService.cs` reports through `Console.Write…` at line 191 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
  • Console output used as the logging channel src/back-end/Senparc.Xncf.Installer/Domain/Services/InstallerService.cs:361 — `src/back-end/Senparc.Xncf.Installer/Domain/Services/InstallerService.cs` reports through `Console.Write…` at line 361 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
  • Console output used as the logging channel src/back-end/Senparc.Xncf.Installer/Domain/Services/InstallOptionsService.cs:160 — `src/back-end/Senparc.Xncf.Installer/Domain/Services/InstallOptionsService.cs` reports through `Console.Write…` at line 160 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
  • Console output used as the logging channel REDACTED:51 — `REDACTED` reports through `Console.Write…` at line 51 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
  • Console output used as the logging channel REDACTED:52 — `REDACTED` reports through `Console.Write…` at line 52 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
  • Console output used as the logging channel REDACTED:53 — `REDACTED` reports through `Console.Write…` at line 53 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
  • Console output used as the logging channel REDACTED:124 — `REDACTED` reports through `Console.Write…` at line 124 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
  • Console output used as the logging channel src/back-end/Senparc.Xncf.Accounts/Program.cs:48 — `src/back-end/Senparc.Xncf.Accounts/Program.cs` reports through `Console.Write…` at line 48 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
  • Console output used as the logging channel src/back-end/Senparc.Xncf.Accounts/Program.cs:49 — `src/back-end/Senparc.Xncf.Accounts/Program.cs` reports through `Console.Write…` at line 49 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
  • Console output used as the logging channel src/back-end/Senparc.Xncf.Accounts/Program.cs:50 — `src/back-end/Senparc.Xncf.Accounts/Program.cs` reports through `Console.Write…` at line 50 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
  • Console output used as the logging channel src/back-end/Senparc.Xncf.Accounts/Program.cs:109 — `src/back-end/Senparc.Xncf.Accounts/Program.cs` reports through `Console.Write…` at line 109 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
  • Console output used as the logging channel src/back-end/Senparc.Xncf.Accounts/Program.cs:113 — `src/back-end/Senparc.Xncf.Accounts/Program.cs` reports through `Console.Write…` at line 113 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
D31 · IaC & Container Security · Low IaC · ×6
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
X7 · Silent fallback defaults · Silent fallback default in catch · ×6
  • Silent fallback default in catch src/back-end/Senparc.Areas.Admin/Domain/Services/AdminUserInfoService.cs:142 — `TryGetJwtExpiresUtc` swallows every exception into `return null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch src/back-end/Senparc.Areas.Admin/Domain/Services/NeuCharFunctionService.cs:123 — `GetCatalogAsync` swallows every exception and sets `parameters = Array.Empty<FunctionParameterInfo>();` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch src/back-end/Senparc.Areas.Admin/Domain/Services/NeuCharFunctionService.cs:265 — `ValidateRequiredParameters` swallows `JsonException` into `return "参数不是有效的 JSON 对象。";` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch REDACTED:263 — `IsSystemInitialized` swallows `NcfUninstallException` into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch src/back-end/Senparc.Areas.Admin/wwwroot/js/Admin/store.js:10 — `getStoredNavMenuOpenedMenus` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
  • Silent fallback default in catch src/back-end/Senparc.Web/wwwroot/js/Download/download.js:76 — `readWebGlRenderer` 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.
D24 · Comment Value · redundant comment · ×5
  • redundant comment src/back-end/Senparc.Xncf.Accounts/Program.cs:38 — "Add services to the container." is ASP.NET Core project template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment REDACTED:41 — "Add services to the container." is ASP.NET Core project template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/front-end/Senparc.Xncf.Admin/src/permission.js:17 — "set page title" repeats the code it sits on: 3 of its 3 words (set, page, title) are already in `document.title = getPageTitle(to.meta.title);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/front-end/Senparc.Xncf.Admin/tests/unit/utils/formatTime.spec.js:3 — ""2018-07-13 17:54:01"" repeats the code it sits on: 6 of its 6 words (2018, 07, 13, 17, 54, 01) are already in `const d = new Date('2018-07-13 17:54:01')`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/front-end/Senparc.Xncf.Admin/tests/unit/utils/parseTime.spec.js:4 — ""2018-07-13 17:54:01"" repeats the code it sits on: 6 of its 6 words (2018, 07, 13, 17, 54, 01) are already in `const d = new Date('2018-07-13 17:54:01')`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
DM5 · Encapsulated state · Mutable entity · ×3
  • Mutable entity: Account src/back-end/Senparc.Xncf.Accounts/Domain/Models/DatabaseModel/Account.cs:11 — `Account` exposes publicly writable state (UserName, Password, PasswordSalt, NickName, RealName, Phone, and 28 more).
  • Mutable entity: AccountPayLog src/back-end/Senparc.Xncf.Accounts/Domain/Models/DatabaseModel/AccountPayLog.cs:9 — `AccountPayLog` exposes publicly writable state (AccountId, OrderNumber, TotalPrice, PayMoney, UsedPoints, CompleteTime, and 14 more).
  • Mutable entity: PointsLog src/back-end/Senparc.Xncf.Accounts/Domain/Models/DatabaseModel/PointsLog.cs:9 — `PointsLog` exposes publicly writable state (AccountId, AccountPayLogId, Points, BeforePoints, AfterPoints, Description, and 2 more).
X7 · Silent fallback defaults · Silent fallback default on parse failure · ×2
  • Silent fallback default on parse failure src/back-end/Senparc.Areas.Admin/Domain/Services/HostMetricsCollector.cs:357 — `ParseLinuxMemoryKb` falls back to `0` when `parts.Length >= 2 && long.TryParse(parts[1], NumberStyles.None, CultureInfo.Inva…` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
  • Silent fallback default on parse failure src/back-end/Senparc.Areas.Admin/OHS/Local/Controllers/AdminChatStreamController.cs:199 — `GetCurrentAdminUserInfoId` falls back to `-1` when `int.TryParse(value, out var userId)` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
D19 · Documentation Quality · Documentation · ×1
  • Documentation: no build, run or usage example src/front-end/Senparc.Xncf.Admin/readme.md:1 — `Senparc.Xncf.Admin` is a published package (`REDACTED` without `"private": true`) and neither `src/front-end/Senparc.Xncf.Admin/readme.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1
  • Projects may be oversized for their cohesion REDACTED:1 — `Senparc.Areas.Admin` overshoots its size bounds (14286 LoC, 244 public types across 27 namespaces). 1 of 14 project(s) overshoot their size bounds, lowering Project Cohesion to 8.6/10. Review these for cohesion — split a project that spans unrelated responsibilities.
D28 · Secrets (history) · Rotate the exposed credentials · ×1
  • REDACTED
D39 · IL Efficiency · IL efficiency · ×1
  • IL efficiency: 6 authored method(s) exceed the IL budget src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/AdminSenparcEntities.cs:102 — 6 of 1110 first-party methods compile to oversized IL bodies (> 250 instructions); worst: Senparc.Areas.Admin.Domain.Models.AdminSenparcEntities.OnModelCreating @ src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/AdminSenparcEntities.cs:102, 423 IL instructions; that pulled this dimension to 9.9/10. These bodies are far past the JIT's inline budget, so splitting them does not make them inlinable — what moves the number is emitting less: collapsing LINQ chains and closures on hot paths, and interpolation built eagerly where it is only sometimes used.
ED3 · Event naming · Event not named in past tense · ×1
  • Event not named in past tense: AdminChatSyncEvent src/back-end/Senparc.Areas.Admin/OHS/Local/Events/AdminChatSyncEvent.cs:26 — `AdminChatSyncEvent` reads as an instruction, not a fact that happened. Events describe something that already occurred — name them in the past tense (e.g. `OrderPlaced`, `PaymentCaptured`) so the ubiquitous language stays clear.
P10 · Library API & versioning · Large public API surface · ×1
  • Large public API surface — 61/66 types (92%) are public. For a library, every public type is a stability contract — make internal-by-default and expose only the intended API.
P2 · Observability · Logging is not universal · ×1
  • Logging is not universal — Only 4/10 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 10, 7 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
P4 · Deployment & Rollback · No rollback/health safety · ×1
  • No rollback/health safety — Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
P4 · Deployment & Rollback · No release approval gate · ×1
  • No release approval gate — Deployment is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever reaches the release trigger goes to production unreviewed, so a mistaken merge or tag is live before anyone can stop it.
PF1 · Benchmark discipline · No performance benchmarks · ×1
  • No performance benchmarks — No benchmark suite was found by the two searches this check runs. FIRST, a BenchmarkDotNet package reference in any project file — every project the workspace loaded, plus a walk of project files on disk that never loaded, because a benchmark suite is exactly the project a partial load drops. SECOND, a script harness: a file whose name contains `benchmark` and ends `.py`, `.sh`, `.ps1`, `.bash`, `.rb`, `.js` or `.mjs`, credited ONLY when this repository's CI text also mentions benchmarks — a harness no pipeline runs is read as a fixture, deliberately. Neither search can see a benchmark suite in another ecosystem's idiom (a Go `testing.B` file, a JMH or criterion project, a pytest-benchmark run), so this is 'no benchmark found by those two searches', not a verdict that the repository has none. Where code is performance-sensitive, a benchmark guards against silent regressions — but it's a bonus here, not a deduction.
S1 · Web-Security Posture · No security response headers detected · ×1
  • No security response headers detected — None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
S1 · Web-Security Posture · No app-layer HTTPS enforcement detected · ×1
  • No app-layer HTTPS enforcement detected — No UseHttpsRedirection/UseHsts and no reverse-proxy signal — transport security is unverified at the app layer. (−2.0 on this card.)
S1 · Web-Security Posture · No inbound model validation detected · ×1
  • No inbound model validation detected — No ModelState/[ApiController]/FluentValidation signal — inbound payloads reach handlers unvalidated. (−2.0 on this card.)
X2 · Cancellation propagation · Not all async methods take a CancellationToken · ×1
  • Not all async methods take a CancellationToken — Only 29/74 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
X5 · Nullable reference types · Nullable reference types not enabled everywhere · ×1
  • Nullable reference types not enabled everywhere — 5/12 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
X9 · Subsumed condition operand · Subsumed condition operand · ×1
  • Subsumed condition operand src/back-end/Senparc.Web/Register.cs:96 — `name.Contains("Senparc.Xncf.", StringComparison.Ordinal)` can never decide this `||` — every value satisfying `name.Contains("Senparc.Xncf.", StringComparison.Ordinal)` also satisfies `name.Contains(".Xncf.", StringComparison.Ordinal)`, so the `||` chain is already decided by the latter. The expression is equivalent to the chain without it, which means it is wider than it reads. Delete the dead operand, or narrow the surviving one if IT is the accident.
Minor — 7 finding(s)
D24 · Comment Value · doc comments repeat the names · ×6
  • doc comments repeat the names src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/AdminUserInfo/Edit.cshtml.cs:17 — 0 of 71 documented parameters and 2 of 39 summaries in `Senparc.Areas.Admin` only repeat the member or parameter name (e.g. "Id" for `Id`). 86 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names src/back-end/Senparc.Web/Register.cs:208 — 0 of 4 documented parameters and 0 of 4 summaries in `Senparc.Web` only repeat the member or parameter name (e.g. "" for `senparcSetting`). 3 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names src/back-end/Senparc.Web.FirefoxDriverTest/AdminUserInfoModuleTest.cs:51 — 0 of 2 documented parameters and 0 of 5 summaries in `Senparc.Web.FirefoxDriverTest` only repeat the member or parameter name (e.g. "" for `tr`). 2 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names src/back-end/Senparc.Xncf.Accounts/Domain/Cache/FullAccountCache.cs:52 — 0 of 30 documented parameters and 0 of 2 summaries in `Senparc.Xncf.Accounts` only repeat the member or parameter name (e.g. "" for `where`). 30 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names src/back-end/Senparc.Xncf.Installer/Domain/Services/InstallerService.cs:203 — 0 of 1 documented parameters and 0 of 2 summaries in `Senparc.Xncf.Installer` only repeat the member or parameter name (e.g. "" for `register`). 1 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names src/front-end/Senparc.Xncf.Admin/src/store/modules/permission.js:8 — 0 of 10 documented parameters and 0 of 15 summaries in `vue-element-admin` only repeat the member or parameter name (e.g. "" for `menuTree`). 7 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
D10 · Test Quality · Mock framework · ×1
  • Mock framework: Moq — Senparc.Areas.Admin.Tests references Moq.

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.

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-e5df6655591648368979313f9f660227/history.json --exit-code 0 --source .132artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-e5df6655591648368979313f9f660227/tree.json --exit-code 0 --source .87artifacts/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/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude src/back-end/Senparc.Areas.Admin/Domain/Migrations --exclude src/back-end/Senparc.Areas.Admin/wwwroot/js/Admin/lib --exclude src/back-end/Senparc.Web/wwwroot/lib/axios --exclude src/back-end/Senparc.Xncf.Accounts/Domain/Migrations/MySql --exclude src/back-end/Senparc.Xncf.Accounts/Domain/Migrations/Oracle --exclude src/back-end/Senparc.Xncf.Accounts/Domain/Migrations/PostgreSQL --exclude src/back-end/Senparc.Xncf.Accounts/Domain/Migrations/SqlServer --exclude src/back-end/Senparc.Xncf.Accounts/Domain/Migrations/Sqlite --exclude src/front-end/Senparc.Xncf.Admin/build .40artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesdotnet—dotnet list src/back-end/NCF.sln package --vulnerable --include-transitive --format json335artifacts/raw/dotnet-vulnerable-2.json
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .24artifacts/raw/trivy-config.json
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. semgrep could not parse 24 file(s) — `src/back-end/Senparc.Areas.Admin/ACL/Repository/SysMenuRepository.cs`, `src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/AdminUserInfo/AuthorizationPage.cshtml.cs`, `src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/AdminUserInfo/Edit.cshtml.cs`, `src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/AdminUserInfo/Index.cshtml.cs`, `src/back-end/Senparc.Areas.Admin/Areas/Admin/Pages/Index.cshtml.cs`, … (+19 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.0—
D36 · Supply-chain Provenance & Signingprovenance—provenance: not applicable — This is a dotnet-new template — it produces no released artifact to attest. Supply-chain provenance, signing and SBOM are deferred to the application you build from it (add SLSA provenance / cosign signing / an SBOM in your app's release pipeline).0—
D37 · Vulnerability-disclosure Policydisclosure—disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.0—
D40 · Network Egress Confinementruntime-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 Confinementruntime-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 Enforcementruntime-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 Dependenciestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update1artifacts/raw/trivy-fs.json

Run 01a1b8ad-95aa-71fd-ad52-81059876778f · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Appendix C — Personal-data map

Every field, property and record parameter whose name is conventional personal data — 6 field(s) across 2 categories, each with an exact repo-relative file:line. This is the data inventory a compliance review starts from — right-to-erasure, retention, minimisation. Detected by NAME, from the C# syntax tree, with a deliberately specific identifier classifier — the same one the C1–C5 compliance cards use to decide whether personal data is present, so CardDefinition or FileName don't trip. Two caveats stated rather than glossed: those cards additionally require corroboration (a persistence/account signal, or two distinct PII categories) that this inventory deliberately does not, so it lists more than they gate on; and D32 Data Compliance shares nothing with it — that dimension is a separate semgrep ruleset for personal data leaking into logs, URLs and browser storage, and a clean D32 result says nothing about this list. Informational — it feeds no score.

Phone — 4 field(s)
  • AdminUserInfo.Phone src/back-end/Senparc.Areas.Admin/Domain/Models/DatabaseModel/AdminUserInfo.cs:38
  • AdminUserInfo_CreateOrUpdateRequest.Phone src/back-end/Senparc.Areas.Admin/OHS/Local/PL/AdminUserInfo_Request.cs:86
  • Account.Phone src/back-end/Senparc.Xncf.Accounts/Domain/Models/DatabaseModel/Account.cs:28
  • FullAccount.Phone src/back-end/Senparc.Xncf.Accounts/Domain/Models/DatabaseModel/ExtensionEntity.cs:96
Email — 2 field(s)
  • Account.Email src/back-end/Senparc.Xncf.Accounts/Domain/Models/DatabaseModel/Account.cs:31
  • FullAccount.Email src/back-end/Senparc.Xncf.Accounts/Domain/Models/DatabaseModel/ExtensionEntity.cs:90

Downloadable artifacts

Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.

⬇ Findings, MITRE CWE-tagged .sarif⬇ Health changelog .md