Public report of shahzadahamad/Instant, published 22 October 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.10.5). Watchdog 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, 22 October 2026, 16:48 UTC · Survey ID cd_50e0e0f2bdde43a2807f8ff1bdc5c042

shahzadahamad/Instant

Measured 22 October 2026, 16:31 UTC, at code version 25db2de

Test distribution: not measured

Test distribution is not measured: No automated tests.

CAI score 31out of 100 At risk Down 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.

Performance 100 Exemplary Architecture 57 Adequate Code Health 56 Adequate Maturity 53 Adequate Security and Compliance 45 Weak Accessibility 37 Weak Production Readiness 14 Critical

A medium codebase: 27,770 lines of product code in 2 projects, tests not counted · Estimated rebuild effort: about 0.2 person-years · Weakest lens: Production Readiness, 14

Findings by how serious they are

124 critical 383 serious 101 minor

9 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks 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

Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
22 October 2026, 16:31 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 Watchdog. It is open to any tool that implements it, and today Watchdog is the only one that does.

A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.

The score is deterministic, which means the same code always gets the same score. Watchdog works 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 ▸

78of 82 dimensions measured by tools. The other 4 are advisory notes from an AI model, which explain the code but don't count towards the score.
535of 608 findings point to an exact file and line, so you can open each one in the code. The other 73 concern the repository as a whole, such as missing documentation.
82dimensions across 7 lenses, read from 27,770 lines of product code in 2 projects.
Chapters

Executive summary

shahzadahamad/Instant scores 31 out of 100, but it is rated At risk while a critical security finding is open; the score itself is unchanged.

The weakest lens counts most in the score, and here that is Production Readiness, which scores 14 and is rated Critical. Its Code Coverage dimension scores 0 out of 10, and until that reaches 4, Production Readiness can't be rated higher than Adequate. The first actions are to resolve the 1 No automated tests finding(s) in Code Coverage and to resolve the 1 No tests found finding(s) in Test Distribution, and if Production Readiness rose to 70, the score would rise from 31 to about 45.

124 findings are critical: 43 in Dependency Vulnerabilities, 40 in Keyboard semantics, 34 in Forms & labels, four in Text alternatives, two in Circular Imports and one in Code Coverage.

Watchdog couldn't measure 5 dimensions in this code, among them Internal API Consistency, Navigability and Platform End-of-Life, so they are left out of the score. The product code is 27,770 lines, which would take an estimated 0.2 person-years, around €26,000, to rebuild.

Code Health 56 Adequate, capped by Cyclomatic Complexity, Cognitive Complexity and God Classes Architecture 57 Adequate, capped by Project Cohesion and Import Boundaries Maturity 53 Adequate, capped by Architecture documentation Production Readiness 14 ⚠ Critical, capped by Code Coverage, Test Distribution, Test Coverage, CI/CD gates, Observability and Security & performance tooling Security and Compliance 45 Weak, capped by Static Analysis (SAST), Dependency Vulnerabilities and Data Protection Accessibility 37 Weak, capped by Keyboard semantics and Visual & motion safety Performance 100 ★ Exemplary

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.
Production Readiness 14 · counts for 46%Accessibility 37 · counts for 25%Security and Compliance 45 · counts for 14%Maturity 53 · counts for 8%Code Health 56 · counts for 4%Architecture 57 · counts for 2%Performance 100 · counts for 1%

If Production Readiness rose from 14 to 70, the lowest score rated Strong, the score would rise from 31 to about 45.

Code composition: what the lines of code are
Product code 100%
New since the last survey: 82 findings

These 82 critical or serious findings weren't in the previous survey, on 8 October 2026.

Watchdog compares 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: 468 findings

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

  • Cyclomatic Complexity · SelectAspectRatio.SelectAspectRatioAndUplaod (cyclomatic 42) Frontend/src/components/create-post/SelectAspectRatio.tsx
  • Cognitive Complexity · SelectAspectRatio.SelectAspectRatioAndUplaod (cognitive 58) Frontend/src/components/create-post/SelectAspectRatio.tsx
  • Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
  • Code Duplication · Duplicated block (28 lines × 2 locations) Frontend/src/components/common/PostViewModal/PostModalActions.tsx
  • Code Duplication · Duplicated block with local edits (28 matched lines × 2 locations) Frontend/src/components/explore/ExploreDetials.tsx
  • Code Duplication · Duplicated block (27 lines × 2 locations) Frontend/src/components/admin/profile/AdminProfileChangePassword.tsx
  • Code Duplication · Duplicated block (27 lines × 2 locations) Frontend/src/components/common/PostViewModal/PostModal.tsx
  • Code Duplication · Duplicated block (27 lines × 2 locations) Frontend/src/components/common/PostViewModal/PostModal.tsx
  • Code Duplication · Duplicated block (25 lines × 2 locations) Frontend/src/components/create-post/CreatePostFormSubmit.tsx
  • Code Duplication · Duplicated block (23 lines × 2 locations) Backend/src/infrastructure/controllers/admin/authentication/refreshTokenAdminController.ts
  • Code Duplication · Duplicated block (22 lines × 3 locations) Backend/src/infrastructure/controllers/admin/authentication/authenticateAdminController.ts
  • Code Duplication · Duplicated block (22 lines × 2 locations) Frontend/src/components/admin/music/AddMusicForm.tsx
  • Code Duplication · Duplicated block (21 lines × 2 locations) Frontend/src/components/authentication/ResetPasswordForm.tsx
  • Code Duplication · Duplicated block (20 lines × 2 locations) Backend/src/application/repositories/user/implements/postRepository.ts
  • Code Duplication · Duplicated block (20 lines × 2 locations) Backend/src/application/useCases/user/chat/fileMessage.ts
  • Code Duplication · Duplicated block (20 lines × 2 locations) Frontend/src/components/common/PostViewModal/PostModal.tsx
  • Code Duplication · Duplicated block (19 lines × 3 locations) Backend/src/application/repositories/user/implements/notificationRepository.ts
  • Code Duplication · Duplicated block (19 lines × 2 locations) Backend/src/infrastructure/controllers/admin/music/getMusicDataController.ts
  • Code Duplication · Duplicated block (19 lines × 2 locations) Frontend/src/components/common/PostViewModal/PostModal.tsx
  • Code Duplication · Duplicated block (18 lines × 3 locations) Backend/src/application/repositories/admin/implements/musicRepository.ts
  • Code Duplication · Duplicated block (18 lines × 2 locations) Backend/src/infrastructure/controllers/user/post/commentPostController.ts
  • Code Duplication · Duplicated block (18 lines × 2 locations) Backend/src/infrastructure/controllers/user/post/explorePostController.ts
  • Code Duplication · Duplicated block (18 lines × 2 locations) Frontend/src/components/admin/common/Sidebar.tsx
  • Code Duplication · Duplicated block (18 lines × 2 locations) Frontend/src/components/admin/profile/AdminProfileChangePassword.tsx
  • Code Duplication · Duplicated block with local edits (18 matched lines × 2 locations) Frontend/src/components/authentication/OtpForm.tsx
  • Code Duplication · Duplicated block with local edits (18 matched lines × 2 locations) Frontend/src/components/create-post/ChangePost.tsx
  • Code Duplication · Duplicated block (18 lines × 2 locations) Frontend/src/components/home/Posts.tsx
  • Code Duplication · Duplicated block (18 lines × 3 locations) Frontend/src/components/profile/ProfilePostSection.tsx
  • Code Duplication · Duplicated block (18 lines × 2 locations) Frontend/src/components/ui/dropdown-menu.tsx
  • Code Duplication · Duplicated block (17 lines × 2 locations) Backend/src/application/useCases/user/post/editPost.ts
  • Code Duplication · Duplicated block (17 lines × 2 locations) Backend/src/infrastructure/controllers/admin/admin/getAdminDataController.ts
  • Code Duplication · Duplicated block with local edits (17 matched lines × 2 locations) Backend/src/infrastructure/controllers/admin/post/getPostDataAdminController.ts
  • Code Duplication · Duplicated block (17 lines × 4 locations) Backend/src/infrastructure/controllers/user/post/checkingHasUserLikedPostController.ts
  • Code Duplication · Duplicated block (17 lines × 2 locations) Backend/src/infrastructure/controllers/user/post/getLikedPostDataController.ts
  • Code Duplication · Duplicated block (17 lines × 2 locations) Backend/src/infrastructure/controllers/user/post/reelsController.ts
  • Code Duplication · Duplicated block (17 lines × 4 locations) Backend/src/infrastructure/controllers/user/user/acceptRequestUserController.ts
  • Code Duplication · Duplicated block (17 lines × 5 locations) Frontend/src/components/admin/subscription/AddSubscriptionForm.tsx
  • Code Duplication · Duplicated block (17 lines × 2 locations) Frontend/src/components/chats/ChatMessageHeader.tsx
  • Code Duplication · Duplicated block (17 lines × 2 locations) Frontend/src/components/common/PostViewModal/PostModal.tsx
  • Code Duplication · Duplicated block (17 lines × 2 locations) Frontend/src/components/common/PostViewModal/PostModal.tsx
  • Code Duplication · Duplicated block (17 lines × 2 locations) Frontend/src/components/common/PostViewModal/PostModal.tsx
  • Code Duplication · Duplicated block (17 lines × 2 locations) Frontend/src/components/common/PostViewModal/PostModal.tsx
  • Code Duplication · Duplicated block with local edits (16 matched lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (16 lines × 2 locations) Backend/src/application/useCases/user/user/removeUser.ts
  • Code Duplication · Duplicated block (16 lines × 3 locations) Backend/src/infrastructure/controllers/admin/music/listAndUnlistMuciAdminController.ts
  • Code Duplication · Duplicated block (16 lines × 3 locations) Backend/src/infrastructure/controllers/user/authentication/forgotPasswordController.ts
  • Code Duplication · Duplicated block (16 lines × 4 locations) Backend/src/infrastructure/controllers/user/chat/getIndividualChatDataController.ts
  • Code Duplication · Duplicated block (16 lines × 6 locations) Backend/src/infrastructure/controllers/user/chat/getSingleChatData.ts
  • Code Duplication · Duplicated block with local edits (16 matched lines × 2 locations) Backend/src/infrastructure/controllers/user/post/likeOrUnlikeCommentController.ts
  • Code Duplication · Duplicated block with local edits (16 matched lines × 2 locations) Backend/src/infrastructure/controllers/user/post/reportPostController.ts
  • Code Duplication · Duplicated block with local edits (16 matched lines × 2 locations) Backend/src/infrastructure/controllers/user/search/removeController.ts
  • Code Duplication · Duplicated block (16 lines × 2 locations) Frontend/src/components/admin/music/MusicDetialsTable.tsx
  • Code Duplication · Duplicated block (16 lines × 2 locations) Frontend/src/components/admin/post/PostDetialsTable.tsx
  • Code Duplication · Duplicated block (16 lines × 2 locations) Frontend/src/components/common/PostViewModal/PostModal.tsx
  • Code Duplication · Duplicated block (16 lines × 2 locations) Frontend/src/components/common/PostViewModal/PostModal.tsx
  • Code Duplication · Duplicated block (16 lines × 2 locations) Frontend/src/components/ui/select.tsx
  • Code Duplication · Duplicated block with local edits (15 matched lines × 2 locations) Backend/src/infrastructure/controllers/user/chat/getChatListController.ts
  • Code Duplication · Duplicated block with local edits (15 matched lines × 2 locations) Backend/src/infrastructure/controllers/user/music/getCreatePostMusicDataController.ts
  • Code Duplication · Duplicated block with local edits (15 matched lines × 2 locations) Backend/src/infrastructure/controllers/user/search/searchController.ts
  • Code Duplication · Duplicated block with local edits (15 matched lines × 2 locations) Backend/src/infrastructure/controllers/user/user/cretePostGetUserDataController.ts
  • Code Duplication · Duplicated block (15 lines × 4 locations) Frontend/src/components/admin/music/AddMusicForm.tsx
  • Code Duplication · Duplicated block (15 lines × 4 locations) Frontend/src/components/chats/message-type/SharePostMessage.tsx
  • Code Duplication · Duplicated block (15 lines × 2 locations) Frontend/src/components/chats/message-type/TextMessage.tsx
  • Code Duplication · Duplicated block (14 lines × 3 locations) Backend/src/application/repositories/user/implements/friendsRepository.ts
  • Code Duplication · Duplicated block (14 lines × 3 locations) Backend/src/application/useCases/admin/music/listAndUnlistMusicByAdmin.ts
  • Code Duplication · Duplicated block (14 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (14 lines × 2 locations) Backend/src/infrastructure/controllers/admin/admin/getDashboardDataController.ts
  • Code Duplication · Duplicated block (14 lines × 2 locations) Frontend/src/components/admin/music/AddMusicForm.tsx
  • Code Duplication · Duplicated block (14 lines × 2 locations) Frontend/src/components/admin/profile/AdminProfileDetials.tsx
  • Code Duplication · Duplicated block (14 lines × 2 locations) Frontend/src/components/chats/ChatInbox.tsx
  • Code Duplication · Duplicated block (14 lines × 2 locations) Frontend/src/components/common/PostViewModal/PostModal.tsx
  • Code Duplication · Duplicated block (14 lines × 2 locations) Frontend/src/components/common/PostViewModal/PostModal.tsx
  • Code Duplication · Duplicated block (13 lines × 2 locations) Backend/src/application/providers/awsS3Storage.ts
  • Code Duplication · Duplicated block (13 lines × 2 locations) Backend/src/application/providers/nodeMailer.ts
  • Code Duplication · Duplicated block (13 lines × 2 locations) Backend/src/application/repositories/user/implements/chatRepository.ts
  • Code Duplication · Duplicated block (13 lines × 2 locations) Backend/src/application/repositories/user/implements/commentRepository.ts
  • Code Duplication · Duplicated block (13 lines × 2 locations) Backend/src/application/repositories/user/implements/likeRepository.ts
  • Code Duplication · Duplicated block (13 lines × 2 locations) Backend/src/application/repositories/user/implements/notificationRepository.ts
  • Code Duplication · Duplicated block (13 lines × 2 locations) Backend/src/application/repositories/user/implements/postRepository.ts
  • Code Duplication · Duplicated block (13 lines × 16 locations) Backend/src/application/useCases/admin/admin/getDashboardData.ts
  • Code Duplication · Duplicated block (13 lines × 2 locations) Backend/src/application/useCases/user/user/followingAndFollower.ts
  • Code Duplication · Duplicated block (13 lines × 3 locations) Backend/src/infrastructure/controllers/user/post/checkingHasUserLikedCommentController.ts
  • Code Duplication · Duplicated block (13 lines × 10 locations) Backend/src/infrastructure/controllers/user/post/deletePostController.ts
  • Code Duplication · Duplicated block (13 lines × 2 locations) Frontend/src/components/admin/subscription/SubscriptionDetials.tsx
  • Code Duplication · Duplicated block (13 lines × 2 locations) Frontend/src/components/create-post/ChangePost.tsx
  • Code Duplication · Duplicated block (12 lines × 2 locations) Backend/src/application/repositories/user/implements/commentRepository.ts
  • Code Duplication · Duplicated block (12 lines × 3 locations) Backend/src/application/repositories/user/implements/friendsRepository.ts
  • Code Duplication · Duplicated block (12 lines × 2 locations) Backend/src/application/repositories/user/implements/postRepository.ts
  • Code Duplication · Duplicated block (12 lines × 2 locations) Backend/src/application/repositories/user/implements/userRepository.ts
  • Code Duplication · Duplicated block (12 lines × 4 locations) Backend/src/application/useCases/user/user/followUser.ts
  • Code Duplication · Duplicated block with local edits (12 matched lines × 2 locations) Backend/src/infrastructure/controllers/admin/admin/editAdminController.ts
  • Code Duplication · Duplicated block (12 lines × 2 locations) Backend/src/infrastructure/controllers/admin/admin/editAdminPasswordController.ts
  • Code Duplication · Duplicated block (12 lines × 2 locations) Backend/src/infrastructure/controllers/admin/music/createMusicController.ts
  • Code Duplication · Duplicated block (12 lines × 2 locations) Backend/src/infrastructure/controllers/admin/subscription/createSubscriptionController.ts
  • Code Duplication · Duplicated block (12 lines × 2 locations) Backend/src/infrastructure/controllers/user/user/checkUserByUsernameController.ts
  • Code Duplication · Duplicated block (12 lines × 3 locations) Frontend/src/apis/api/userApi.ts
  • Code Duplication · Duplicated block (12 lines × 2 locations) Frontend/src/components/admin/post/PostDetialsTable.tsx
  • Code Duplication · Duplicated block (12 lines × 2 locations) Frontend/src/components/authentication/OtpForm.tsx
  • Code Duplication · Duplicated block (12 lines × 2 locations) Frontend/src/components/authentication/SignUpForm.tsx
  • Code Duplication · Duplicated block (12 lines × 4 locations) Frontend/src/components/calls/CallModal.tsx
Rebuild cost: about €26,000 · Estimate
Cost to rebuild€8,600 to €43,000, for 144 to 457 hours of work, about 0.2 person-years for one engineer
Difficulty of the problemStandard, 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 31. 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.
SizeMedium: 27,770 lines of product code

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

Top priorities

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

1
Resolve the 1 No automated tests finding(s) in Code Coverage.
Raises the score by about 14 points · Low effort · Code Coverage
2
Resolve the 1 No tests found finding(s) in Test Distribution.
Raises the score by about 14 points · Low effort · Test Distribution
3
Resolve the 9 Deprecated finding(s) in Dependency Hygiene — start with package.json (9).
Raises the score by about 11 points · Low effort · Dependency Hygiene

Diagnosis: what the measurements show together

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

Where the investment is most exposed · Value at risk
This code would cost about €26,000 to build again, about 0.2 person-years of work. Its weakest lens is Production Readiness, at 14 (Critical). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 1 No automated tests finding(s) in Code Coverage. Of all the actions in this report, it raises the score most for the work it takes: about 14 points for low effort, because it clears the 1 Code Coverage findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 4.7 out of 10. Code at that level is slower to change than clean code, and Watchdog estimates the extra work at 8% to 19% on every change.
How this is estimated: It rests on an assumption of Watchdog's own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Cohesion (LCOM4)
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.

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

297 modules, with 363 dependencies between them. Every module uses only modules listed above it, so there are no loops.

The table shows the 40 modules with the most connections; 257 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 Backend.src.application.providers.awsS3Storage2 Backend.src.application.providers.nodeMailer3 Backend.src.application.providers.passwordHasher4 Backend.src.application.providers.tokenManager5 Backend.src.application.repositories.admin.implements.adminRepository6 Backend.src.application.repositories.admin.implements.musicRepository7 Backend.src.application.repositories.user.implements.chatRepository8 Backend.src.application.repositories.user.implements.commentRepository9 Backend.src.application.repositories.user.implements.friendsRepository10 Backend.src.application.repositories.user.implements.likeRepository11 Backend.src.application.repositories.user.implements.messageRepository12 Backend.src.application.repositories.user.implements.notificationRepository13 Backend.src.application.repositories.user.implements.otpRepository14 Backend.src.application.repositories.user.implements.paymentRepository15 Backend.src.application.repositories.user.implements.postRepository16 Backend.src.application.repositories.user.implements.searchHistoryRepository17 Backend.src.application.repositories.user.implements.userMoreDataRepository18 Backend.src.infrastructure.controllers.interfaces.IControllerHandler19 Backend.src.infrastructure.database.models.subscription20 Backend.src.infrastructure.database.models.userModel21 Backend.src.application.interface.post22 Backend.src.application.repositories.admin.implements.subscriptionRepository23 Backend.src.application.repositories.user.implements.userRepository24 Backend.src.application.useCases.user.post.deleteCommentOrReply25 Backend.src.application.useCases.user.post.likeOrUnlikeComment26 Backend.src.application.useCases.user.post.loadingPagePost27 Backend.src.application.repositories.user.implements.storyRepository28 Backend.src.application.useCases.admin.admin.getDashboardData29 Backend.src.application.useCases.user.authentication.googleAuthenticateUser30 Backend.src.application.useCases.user.authentication.otpSend31 Backend.src.application.useCases.user.chat.fileMessage32 Backend.src.application.useCases.user.chat.sendShareMessaege33 Backend.src.application.useCases.user.post.commentPost34 Backend.src.application.useCases.user.post.createPost35 Backend.src.application.useCases.user.post.deletePost36 Backend.src.application.useCases.user.post.getLikedPostData37 Backend.src.application.useCases.user.post.replyComment38 Backend.src.application.useCases.user.post.userPostData39 Backend.src.application.useCases.user.user.updateUserData40 Frontend.src.types.profile.profile
1 Backend.src.application.providers.awsS3Storage
2 Backend.src.application.providers.nodeMailer
3 Backend.src.application.providers.passwordHasher
4 Backend.src.application.providers.tokenManager
5 Backend.src.application.repositories.admin.implements.adminRepository
6 Backend.src.application.repositories.admin.implements.musicRepository
7 Backend.src.application.repositories.user.implements.chatRepository
8 Backend.src.application.repositories.user.implements.commentRepository
9 Backend.src.application.repositories.user.implements.friendsRepository
10 Backend.src.application.repositories.user.implements.likeRepository
11 Backend.src.application.repositories.user.implements.messageRepository
12 Backend.src.application.repositories.user.implements.notificationRepository
13 Backend.src.application.repositories.user.implements.otpRepository
14 Backend.src.application.repositories.user.implements.paymentRepository
15 Backend.src.application.repositories.user.implements.postRepository
16 Backend.src.application.repositories.user.implements.searchHistoryRepository
17 Backend.src.application.repositories.user.implements.userMoreDataRepository
18 Backend.src.infrastructure.controllers.interfaces.IControllerHandler
19 Backend.src.infrastructure.database.models.subscription
20 Backend.src.infrastructure.database.models.userModel
21 Backend.src.application.interface.post3
22 Backend.src.application.repositories.admin.implements.subscriptionRepository1
23 Backend.src.application.repositories.user.implements.userRepository1
24 Backend.src.application.useCases.user.post.deleteCommentOrReply1111
25 Backend.src.application.useCases.user.post.likeOrUnlikeComment1111
26 Backend.src.application.useCases.user.post.loadingPagePost1111
27 Backend.src.application.repositories.user.implements.storyRepository1
28 Backend.src.application.useCases.admin.admin.getDashboardData1111
29 Backend.src.application.useCases.user.authentication.googleAuthenticateUser111
30 Backend.src.application.useCases.user.authentication.otpSend1111
31 Backend.src.application.useCases.user.chat.fileMessage1111
32 Backend.src.application.useCases.user.chat.sendShareMessaege1111
33 Backend.src.application.useCases.user.post.commentPost1111
34 Backend.src.application.useCases.user.post.createPost1111
35 Backend.src.application.useCases.user.post.deletePost1111111
36 Backend.src.application.useCases.user.post.getLikedPostData1111
37 Backend.src.application.useCases.user.post.replyComment1111
38 Backend.src.application.useCases.user.post.userPostData1111
39 Backend.src.application.useCases.user.user.updateUserData1111
40 Frontend.src.types.profile.profile1
Uses a module listed above itPart of a loopThe module itself
1 Backend.src.application.providers.awsS3Storage2 Backend.src.application.providers.nodeMailer3 Backend.src.application.providers.passwordHasher4 Backend.src.application.providers.tokenManager5 Backend.src.application.repositories.admin.implements.adminRepository6 Backend.src.application.repositories.admin.implements.musicRepository7 Backend.src.application.repositories.user.implements.chatRepository8 Backend.src.application.repositories.user.implements.commentRepository9 Backend.src.application.repositories.user.implements.friendsRepository10 Backend.src.application.repositories.user.implements.likeRepository11 Backend.src.application.repositories.user.implements.messageRepository12 Backend.src.application.repositories.user.implements.notificationRepository13 Backend.src.application.repositories.user.implements.otpRepository14 Backend.src.application.repositories.user.implements.paymentRepository15 Backend.src.application.repositories.user.implements.postRepository16 Backend.src.application.repositories.user.implements.searchHistoryRepository17 Backend.src.application.repositories.user.implements.userMoreDataRepository18 Backend.src.infrastructure.controllers.interfaces.IControllerHandler19 Backend.src.infrastructure.database.models.subscription20 Backend.src.infrastructure.database.models.userModel21 Backend.src.application.interface.post22 Backend.src.application.repositories.admin.implements.subscriptionRepository23 Backend.src.application.repositories.user.implements.userRepository24 Backend.src.application.useCases.user.post.deleteCommentOrReply25 Backend.src.application.useCases.user.post.likeOrUnlikeComment26 Backend.src.application.useCases.user.post.loadingPagePost27 Backend.src.application.repositories.user.implements.storyRepository28 Backend.src.application.useCases.admin.admin.getDashboardData29 Backend.src.application.useCases.user.authentication.googleAuthenticateUser30 Backend.src.application.useCases.user.authentication.otpSend31 Backend.src.application.useCases.user.chat.fileMessage32 Backend.src.application.useCases.user.chat.sendShareMessaege33 Backend.src.application.useCases.user.post.commentPost34 Backend.src.application.useCases.user.post.createPost35 Backend.src.application.useCases.user.post.deletePost36 Backend.src.application.useCases.user.post.getLikedPostData37 Backend.src.application.useCases.user.post.replyComment38 Backend.src.application.useCases.user.post.userPostData39 Backend.src.application.useCases.user.user.updateUserData40 Frontend.src.types.profile.profileBackend.src.application.providers.awsS3Storage1Backend.src.application.providers.nodeMailer2Backend.src.application.providers.passwordHasher3Backend.src.application.providers.tokenManager4Backend.src.application.repositories.admin.implements.adminRepository5Backend.src.application.repositories.admin.implements.musicRepository6Backend.src.application.repositories.user.implements.chatRepository7Backend.src.application.repositories.user.implements.commentRepository8Backend.src.application.repositories.user.implements.friendsRepository9Backend.src.application.repositories.user.implements.likeRepository10Backend.src.application.repositories.user.implements.messageRepository11Backend.src.application.repositories.user.implements.notificationRepository12Backend.src.application.repositories.user.implements.otpRepository13Backend.src.application.repositories.user.implements.paymentRepository14Backend.src.application.repositories.user.implements.postRepository15Backend.src.application.repositories.user.implements.searchHistoryRepository16Backend.src.application.repositories.user.implements.userMoreDataRepository17Backend.src.infrastructure.controllers.interfaces.IControllerHandler18Backend.src.infrastructure.database.models.subscription19Backend.src.infrastructure.database.models.userModel20Backend.src.application.interface.post21Backend.src.application.repositories.admin.implements.subscriptionRepository22Backend.src.application.repositories.user.implements.userRepository23Backend.src.application.useCases.user.post.deleteCommentOrReply24Backend.src.application.useCases.user.post.likeOrUnlikeComment25Backend.src.application.useCases.user.post.loadingPagePost26Backend.src.application.repositories.user.implements.storyRepository27Backend.src.application.useCases.admin.admin.getDashboardData28Backend.src.application.useCases.user.authentication.googleAuthenticateUser29Backend.src.application.useCases.user.authentication.otpSend30Backend.src.application.useCases.user.chat.fileMessage31Backend.src.application.useCases.user.chat.sendShareMessaege32Backend.src.application.useCases.user.post.commentPost33Backend.src.application.useCases.user.post.createPost34Backend.src.application.useCases.user.post.deletePost35Backend.src.application.useCases.user.post.getLikedPostData36Backend.src.application.useCases.user.post.replyComment37Backend.src.application.useCases.user.post.userPostData38Backend.src.application.useCases.user.user.updateUserData39Frontend.src.types.profile.profile403111111111111111111111111111111111111111111111111111111111111111111+257 more modules (most-connected shown)

At a glance — Code Health · 56% · Adequate · gated by D1, D2, D3 ·

The Good
D17 · TypeScript Explicit Debt 10.0 GD1 · Repo Unfinished & placeholder code 10.0 IC1 · Repo Incompleteness & stubs 7.3 R1 · React / TS Type Safety 10.0 R2 · React / TS Cyclomatic Complexity 8.0 R3 · React / TS Large Files 9.4 R7 · React / TS Dead Code 9.5 X1 · Repo Async correctness 7.5 X12 · Repo Unreachable branch 10.0 X13 · Repo Undrained process stream 10.0 X16 · Repo Unfloored truncation loop 10.0 X18 · Repo Disposal-pattern correctness 10.0 X19 · Repo Unrestored process-global state 10.0 X21 · Repo Side-effecting pattern guard 10.0 X22 · Repo Contradicted release guard 10.0 X23 · Repo Unguarded diagnostic materialisation 10.0 X25 · Repo Inert configuration knob 10.0 X28 · Repo Index access outside its own emptiness guard 10.0 X29 · Repo Per-element action decided by a fixed element 10.0 X3 · Repo Exception handling 10.0 X30 · Repo Support guard that admits what it rejects 10.0 X5 · Repo Nullable reference types 9.3
The Bad
R10 · React / TS Code Duplication 6.3
The Ugly
D1 · TypeScript Cyclomatic Complexity 2.0 D2 · TypeScript Cognitive Complexity 2.0 D3 · TypeScript God Classes 2.4 X2 · Repo Cancellation propagation 4.0

At a glance — Architecture · 57% · Adequate · gated by D26, R11 ·

The Good
D5 · TypeScript Coupling 10.0 D6 · TypeScript Cohesion (LCOM4) 10.0 D35 · TypeScript Change Coupling 9.8 AX10 · Repo Code composition 7.8 AX3 · Repo Project dependency cycles 10.0 AX5 · Repo Architecture & structure 10.0 AX6 · Repo Interface segregation 9.7 AX7 · Repo Slice cohesion 10.0
The Bad
R9 · React / TS Circular Imports 6.4
The Ugly
D26 · TypeScript Project Cohesion 0.0 R11 · React / TS Import Boundaries 0.0

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

The Good
D15 · TypeScript Churn × Complexity Hotspots 10.0 D19 · TypeScript Documentation Quality 8.0 D21 · TypeScript Naming Consistency 10.0 D34 · TypeScript Knowledge Freshness 10.0 M1 · Repo Documentation (README) 7.7 M3 · Repo Folder & project structure 8.0 M4 · Repo Documentation accuracy 9.0
The Ugly
D20 · TypeScript ADR Quality 0.0 M2 · Repo Architecture documentation 0.0

At a glance — Readiness · 14% · Critical · gated by D8, D9, R4, P1, P2, P3 ·

The Good
D13 · TypeScript Secret Scanning 10.0 D14 · TypeScript License Compliance 10.0 P10 · Repo Library API & versioning 10.0 P4 · Repo Deployment & Rollback 8.0 R8 · React / TS Dependency Hygiene 9.0
The Bad
D12 · TypeScript Dependency Hygiene 5.0 R5 · React / TS Dependency Freshness 5.0 R6 · React / TS Tooling 6.6
The Ugly
D8 · TypeScript Code Coverage 0.0 P1 · Repo CI/CD gates 0.0 P2 · Repo Observability 0.0 P3 · Repo Security & performance tooling 0.0 R4 · React / TS Test Coverage 0.0

At a glance — Security · 45% · Weak · gated by D29, D30, C1 ·

The Good
D28 · TypeScript Secrets (history) 10.0 D43 · TypeScript Malicious Dependencies 10.0 C2 · Repo Access Controls 7.0 X14 · Repo Bypassable address classification 10.0 X15 · Repo Unvalidated length from an untrusted reader 10.0 X17 · Repo Uncapped recursion over a caller-supplied document 10.0
The Bad
C4 · Repo Data Retention 6.5 S1 · Repo Web-Security Posture 6.0 X24 · Repo Document value interpolated into markup unescaped 5.0
The Ugly
D29 · TypeScript Static Analysis (SAST) 3.9 D30 · TypeScript Dependency Vulnerabilities 0.0 C1 · Repo Data Protection 1.0

At a glance — Domain Modelling · — · — ·

The Good
DM9 · Repo Scattered domain decisions 10.0

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

The Good
AC3 · Repo Page structure 7.8 AC5 · Repo ARIA correctness 10.0
The Bad
AC1 · Repo Text alternatives 5.1
The Ugly
AC2 · Repo Forms & labels 4.4 AC4 · Repo Keyboard semantics 1.6 AC6 · Repo Visual & motion safety 2.6 AC7 · Repo A11y enforcement 4.0

At a glance — Performance · 100% · Exemplary ·

The Good
PF3 · Repo Async & latency hygiene 10.0

Security & Compliance — OWASP Top-10 mapping

Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).

OWASP categoryFindingsSeverity
A03:2025 — Software Supply Chain Failures74High / Critical
A05:2025 — Injection18Medium

Roadmap

First, establish a CI workflow that builds and runs tests on every push or pull request to ensure immediate feedback. Next, address the lack of automated testing by resolving the single code coverage gap and adding missing tests to improve distribution. Finally, clean up dependencies by removing nine deprecated packages and updating eight outdated npm packages, starting with package.json.

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

Do thisHelpsEffortDimension
Resolve the 1 No automated tests finding(s) in Code Coverage.+14.1 ptsLowCode Coverage
Resolve the 1 No tests found finding(s) in Test Distribution.+14.1 ptsLowTest Distribution
Resolve the 9 Deprecated finding(s) in Dependency Hygiene — start with package.json (9).+11.4 ptsLowDependency Hygiene
Resolve the 8 Outdated (npm) finding(s) in Dependency Hygiene — start with package.json (8).+10.7 ptsLowDependency Hygiene
Add a CI workflow that builds and runs the test suite on every push/PR.+2.6 ptsMediumCI/CD gates
Adopt pino (or winston) and log at meaningful points in the services you run.+2.6 ptsMediumObservability
Run what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.+2.6 ptsMediumSecurity & performance tooling
Add tests that import the unreached modules (directly or through their public entry).+2.6 ptsMediumTest Coverage

File quality

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

FileScoreBandWorst signal
REDACTED0.0SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED0.0SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED5.8MixedStatic Analysis (SAST): Medium: REDACTED
Frontend/src/components/chats/ChatDetials.tsx5.9MixedCyclomatic Complexity: ChatDetials.ChatDetials (cyclomatic 61)
Frontend/package.json6.1MixedDependency Hygiene: Deprecated: @fortawesome/react-fontawesome
REDACTED6.9MixedStatic Analysis (SAST): Medium: REDACTED
Backend/package.json6.9MixedDependency Hygiene: Deprecated: uuid
Frontend/src/components/common/PostViewModal/PostModal.tsx7.1MixedCyclomatic Complexity: PostModal.PostModal (cyclomatic 165)
Frontend/src/components/calls/VideoAudioCall.tsx7.4MixedCyclomatic Complexity: VideoAudioCall.VideoAudioCall (cyclomatic 68)
Frontend/src/components/chats/ChatInbox.tsx7.4MixedCyclomatic Complexity: ChatInbox.ChatsInbox (cyclomatic 66)
Frontend/src/components/home/Posts.tsx7.4MixedCyclomatic Complexity: Posts.Posts (cyclomatic 63)
Frontend/src/components/common/FollowDetialsModal.tsx7.4MixedCyclomatic Complexity: FollowDetialsModal.FollowDetialsModal (cyclomatic 62)
Frontend/src/components/reel/ReelsDetials.tsx7.4MixedCyclomatic Complexity: ReelsDetials.ReelsDetials (cyclomatic 56)
Frontend/src/components/notification/NotificationDetials.tsx7.4MixedCyclomatic Complexity: NotificationDetials.NotificationDetials (cyclomatic 47)
Frontend/src/components/create-post/CreatePostBody.tsx7.4MixedCyclomatic Complexity: CreatePostBody.CreatePostBody (cyclomatic 45)
Frontend/src/components/admin/post/PostDetialsTable.tsx7.4MixedCyclomatic Complexity: PostDetialsTable.PostDetialsTable (cyclomatic 38)
Frontend/src/components/search/SearchDetials.tsx7.4MixedCyclomatic Complexity: SearchDetials.SearchDetials (cyclomatic 38)
Frontend/src/components/user-profiles/UserProfileDetials.tsx7.4MixedCyclomatic Complexity: UserProfileDetials.UserProfileDetials (cyclomatic 37)
Frontend/src/components/admin/music/MusicDetialsTable.tsx7.4MixedCyclomatic Complexity: MusicDetialsTable.MusicDetialsTable (cyclomatic 36)
Frontend/src/components/create-post/ChangePost.tsx7.4MixedCyclomatic Complexity: ChangePost.ChangePost (cyclomatic 34)

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

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

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

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

Could not be resolved — 9

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

Methodology & how to trust this report

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

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

What we checked — 82 dimensions across the health lenses
D1D2D3D5D6D8D9D12D13D14D15D17D19D20D21D26D28D29D30D34D35D43AC1AC2AC3AC4AC5AC6AC7AX10AX3AX5AX6AX7C1C2C4DM9GD1IC1M1M2M3M4P1P10P2P3P4PF3R1R10R11R2R3R4R5R6R7R8R9S1X1X12X13X14X15X16X17X18X19X2X21X22X23X24X25X28X29X3X30X5

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, 535 of 608 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, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — 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
Watchdog 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 · trivySecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3✓ deterministic
LLM (sampled · advisory)Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurementLocal LLM◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 01a16473-f0b3-7c4d-9417-571224da2933.

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.

  • 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-contributor repository — bus factor is not applicable (1 contributor(s) across 288 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
  • D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (Backend/package.json), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
  • D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
  • D44 Platform End-of-Life — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
  • AC2 Forms & labels — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 63 further occurrence(s) are not listed individually; the score already reflects all 103.
  • AC4 Keyboard semantics — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 97 further occurrence(s) are not listed individually; the score already reflects all 137.
  • AC6 Visual & motion safety — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 22 further occurrence(s) are not listed individually; the score already reflects all 62.
  • AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (dev). the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence.
  • DM9 Scattered domain decisions — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Arm two tells a construction that PRODUCES a measurement from one that merely passes it along, and this repository's frontend does not compute that fact. A measurement built independently in two places would not appear above.
  • R10 Code Duplication — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 196 further occurrence(s) are not listed individually; the score already reflects all 236.
  • R11 Import Boundaries — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 105 further occurrence(s) are not listed individually; the score already reflects all 145.
  • X4 Structured logging — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.

Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.

Limitations & what we did not check

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

Per-dimension blind spots

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

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D8 Code Coverage: Coverage is measured by building and running the test suite inside Watchdog's isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
  • 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.
  • D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
  • D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
  • D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
  • D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • 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.
  • C4 Data Retention: This control is scored from in-repo evidence only — its real-world effectiveness, exercised only at runtime, is outside a static scan.
  • M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".

The LLM boundary

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

Dimensions

D1 · Cyclomatic Complexity2.0 / 10Critical✓ Tool-verified

What it measures: How tangled the control flow is — methods with many branches are hard to test and change.

Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.

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

40 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was PostModal.PostModal at 165.

PostModal.PostModal (cyclomatic 165)Frontend/src/components/common/PostViewModal/PostModal.tsx:56
VideoAudioCall.VideoAudioCall (cyclomatic 68)Frontend/src/components/calls/VideoAudioCall.tsx:15
ChatInbox.ChatsInbox (cyclomatic 66)Frontend/src/components/chats/ChatInbox.tsx:26
Posts.Posts (cyclomatic 63)Frontend/src/components/home/Posts.tsx:21
FollowDetialsModal.FollowDetialsModal (cyclomatic 62)Frontend/src/components/common/FollowDetialsModal.tsx:11

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

What to do

  1. Bring the 1 body over 120 down to 120 or less in Cyclomatic Complexity — start with PostModal.PostModal (cyclomatic 165). — Refactoring it lifts Cyclomatic Complexity from 2.0 to about 2.6/10.
  2. Stand up a CI pipeline, then gate Cyclomatic Complexity in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D2 · Cognitive Complexity2.0 / 10Critical✓ Tool-verified

What it measures: How hard the code is for a person to follow, beyond raw branching.

Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.

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

47 method(s) exceeded the cognitive complexity threshold of 15; the worst was ChatInbox.ChatsInbox at 116.

ChatInbox.ChatsInbox (cognitive 116)Frontend/src/components/chats/ChatInbox.tsx:26
VideoAudioCall.VideoAudioCall (cognitive 95)Frontend/src/components/calls/VideoAudioCall.tsx:15
Posts.Posts (cognitive 92)Frontend/src/components/home/Posts.tsx:21
ReelsDetials.ReelsDetials (cognitive 74)Frontend/src/components/reel/ReelsDetials.tsx:20
ChatDetials.ChatDetials (cognitive 66)Frontend/src/components/chats/ChatDetials.tsx:26

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

What to do

  1. Bring the 5 bodies over 60 down to 60 or less in Cognitive Complexity — start with ChatInbox.ChatsInbox (cognitive 116), VideoAudioCall.VideoAudioCall (cognitive 95), Posts.Posts (cognitive 92). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 5 together lifts Cognitive Complexity from 2.0 to about 3.8/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
  2. Stand up a CI pipeline, then gate Cognitive Complexity in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D3 · God Classes2.4 / 10Critical✓ Tool-verified

What it measures: Over-large classes that try to do too much ("god classes").

Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.

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

47 god class(es) detected.

FunctionTooLong: PostModal.PostModal · ×45Frontend/src/components/common/PostViewModal/PostModal.tsx:56
ClassTooLong: PostModalFrontend/src/components/common/PostViewModal/PostModal.tsx:1
FileTooLong: PostViewModal/PostModal.tsxFrontend/src/components/common/PostViewModal/PostModal.tsx

What to do

  1. Resolve the 45 FunctionTooLong finding(s) in God Classes — start with Sidebar.tsx (2), SignInForm.tsx (2), PostModal.tsx. — One of this dimension's main actionable groups (45 warning-level).
  2. Resolve the 1 ClassTooLong finding(s) in God Classes — start with PostModal.tsx. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 FileTooLong finding(s) in God Classes — start with PostModal.tsx. — One of this dimension's main actionable groups (1 warning-level).
  4. Stand up a CI pipeline, then gate God Classes in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

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

2 production modules (npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence.

✓ 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 3 classes have LCOM4 above 3.

✓ On the Gold path — maintain.

Detailed fixes: d6_recommendation.md.

D8 · Code Coverage0.0 / 10Critical✓ Tool-verified

What it measures: How much of the code is actually exercised by tests.

Method: Coverage from coverlet runs or committed reports (Cobertura/OpenCover/lcov), computed per-file with structured exclusions for generated, trivial, and glue code. When the suite can't be built/run in-image AND no report is committed, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.

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

No automated tests — no test code was found in this repository.

No automated tests

What to do

  1. Resolve the 1 No automated tests finding(s) in Code Coverage. — One of this dimension's main actionable groups (1 issue-level).
  2. Stand up a CI pipeline, then gate Code Coverage in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

D9 · Test Distribution0.0 / 10Critical✓ 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 0.0 / 10 · rule-coverage 100% · ceiling Documented

No test suite found.

No tests found

What to do

  1. Resolve the 1 No tests found finding(s) in Test Distribution. — One of this dimension's main actionable groups (1 recommendation-level).

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

D12 · Dependency Hygiene5.0 / 10Adequate✓ Tool-verified

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

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

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

61 outdated direct production npm dependency(ies) of 68 graded, 0 pinning defect(s), across 2 package.json (2 of them the product) and 2 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 8 direct dependency(ies) — production, development or optional — are marked DEPRECATED by their publisher (the registry's per-version mark, or the lockfile's copy of it when the registry could not be asked); deprecated transitive packages are listed but not charged. Whether any is UNMAINTAINED is not graded — the registry publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, and the frontend dependency lens (R8) answers it in this same run. Known CVEs in this dependency graph are D30's question, read from the manifest there.

Deprecated: uuid · ×9Backend/package.json:32
Outdated (npm): @fortawesome/react-fontawesome · ×8Frontend/package.json:18
Outdated (npm): @aws-sdk/client-rekognition · ×53

What to do

  1. Resolve the 9 Deprecated finding(s) in Dependency Hygiene — start with package.json (9). — One of this dimension's main actionable groups (9 warning-level).
  2. Resolve the 8 Outdated (npm) finding(s) in Dependency Hygiene — start with package.json (8). — One of this dimension's main actionable groups (8 recommendation-level).
  3. Stand up a CI pipeline, then gate Dependency Hygiene in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

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

What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.

Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.

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

Secret scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.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 68 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 68 production dependency(ies) this repository's committed lockfile resolves, across 2 product package.json manifest(s). Its 39 `devDependencies` declaration(s) are excluded: a consumer installs none of them. ★ DEPTH: this is the DIRECT production set the lockfile resolves, NOT the transitive closure — only one of the four lock dialects this pass reads states a full graph, so a banned licence pulled in only by a dependency's OWN dependencies is outside this verdict, exactly as the JVM arm's declaration-site verdict is. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. This repository publishes itself under ISC, which is its own choice and is not judged here.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

D15 · Churn × Complexity Hotspots10.0 / 10Exemplary✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Documented

No churn × complexity hotspots in the window.

✓ On the Gold path — maintain.

Detailed fixes: d15_recommendation.md.

D17 · Explicit Debt10.0 / 10Exemplary○ Nothing flagged

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

0 deducted task-comment markers across 27770 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.

✓ On the Gold path — maintain.

Detailed fixes: d17_recommendation.md.

D19 · Documentation QualityStrong◐ Sampled · advisory

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

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

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

The root README is clear and complete for a project: it states what Instant is ('a dynamic social media platform'), lists features with bolded headings (user profiles/verification, post management, live chat/calls, notifications, friend suggestions, story management, admin panel), shows the tech stack, and gives installation steps. The Frontend README is an internal directory README and does not qualify as repository-level documentation.

What to do

  1. Improve Documentation Quality — currently 8.0/10. — The root README is clear and complete for a project: it states what Instant is ('a dynamic social media platform'), lists features with bolded headings (user profiles/verification, post management, live chat/calls, notifications, friend suggestions, story management, admin panel), shows the tech stack, and gives installation steps. The Frontend README is an internal directory README and does not qualify as repository-level documentation.

Detailed fixes: d19_recommendation.md.

D20 · ADR Quality0.0 / 10Critical✓ Tool-verified

What it measures: Whether architecture decisions are recorded well (context, decision, consequences).

Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.

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

No architecture decision records were found.

No ADRs found

What to do

  1. Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).

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

D21 · Naming ConsistencyExemplary◐ Sampled · advisory

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

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

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

0 naming inconsistencies across 0 sampled symbols.

✓ On the Gold path — maintain.

Detailed fixes: d21_recommendation.md.

D26 · Project Cohesion0.0 / 10Critical✓ Tool-verified

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

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

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

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

Projects may be oversized for their cohesion

What to do

  1. Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — 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.

D28 · Secrets (history)10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.

Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.

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

gitleaks scanned the full history AND the current working tree and found no secrets.

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

D29 · Static Analysis (SAST)3.9 / 10Weak✓ 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 3.9 / 10 · rule-coverage 100% · ceiling Documented

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

REDACTED
REDACTED

What to do

  1. Resolve the 11 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (9), REDACTED, REDACTED. — One of this dimension's main actionable groups (11 warning-level).
  2. Resolve the 7 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (7 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.

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

74 finding(s): 10 critical, 33 high, 23 medium, 8 low.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 33 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (33). — One of this dimension's main actionable groups (33 issue-level).
  2. Resolve the 21 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (21). — One of this dimension's main actionable groups (21 warning-level).
  3. Resolve the 10 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (10). — 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.

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 111 of the 435 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.8 / 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.8 / 10 · rule-coverage 100% · ceiling Documented

Strongest change-coupling: ChatDetials.tsx↔ChatInbox.tsx 73%; SignInForm.tsx↔SignUpForm.tsx 70%; App.tsx↔SignInForm.tsx 60%

Change coupling: ChatDetials.tsx ↔ ChatInbox.tsxFrontend/src/components/chats/ChatDetials.tsx:1
Change coupling clique: App.tsx, SignInForm.tsx, SignUpForm.tsxFrontend/src/App.tsx

What to do

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

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

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

Frontend & cross-cutting dimensions

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

AC1 · Text alternatives5.1 / 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.

  • Video with no captions <track> offers no captions. This player's source is set at runtime, so there is no caption file to author here: give the player a way to carry captions — accept a track/captions URL alongside the media and render a <track kind="captions"> when one is supplied — and capture that asset wherever the media enters the product (upload, import or generation). (×14) — Frontend/src/components/admin/post/PostDetialsTable.tsx:157, Frontend/src/components/admin/post/PostDetialsTable.tsx:243, Frontend/src/components/chats/ChatDetials.tsx:359, …
  • An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. (×4) — Frontend/src/components/common/FollowDetialsModal.tsx:144, Frontend/src/components/common/FriendSuggetion.tsx:90, Frontend/src/components/notification/NotificationDetials.tsx:175, …

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.4 / 10Weak✓ 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 only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label. (×16) — Frontend/src/components/admin/authentication/SignInForm.tsx:74, Frontend/src/components/admin/authentication/SignInForm.tsx:82, Frontend/src/components/admin/music/MusicDetialsTable.tsx:242, …
  • This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. (×2) — Frontend/src/components/admin/music/AddMusicForm.tsx:341, Frontend/src/components/admin/music/MusicDetialsTable.tsx:343
  • A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one). (×5) — Frontend/src/components/admin/music/MusicDetialsTable.tsx:250, Frontend/src/components/admin/post/PostDetialsTable.tsx:183, Frontend/src/components/admin/profile/AdminProfileDetials.tsx:145, …
  • This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. (×4) — Frontend/src/components/admin/music/MusicDetialsTable.tsx:258, Frontend/src/components/admin/post/PostDetialsTable.tsx:191, Frontend/src/components/admin/subscription/SubscriptionDetials.tsx:111, …
  • This <video> 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. — Frontend/src/components/admin/post/PostDetialsTable.tsx:243
  • This <label> has no htmlFor 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 htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id. (×5) — Frontend/src/components/admin/profile/AdminProfileChangePassword.tsx:82, Frontend/src/components/admin/profile/AdminProfileChangePassword.tsx:111, Frontend/src/components/admin/profile/AdminProfileChangePassword.tsx:140, …
  • This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×7) — Frontend/src/components/admin/profile/AdminProfileChangePassword.tsx:86, Frontend/src/components/admin/profile/AdminProfileChangePassword.tsx:115, Frontend/src/components/admin/profile/AdminProfileChangePassword.tsx:144, …

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 structure7.8 / 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. This document's body is only the mount point <div id="root">, so there is no content here to wrap — render the <main> from the component mounted into it. — Frontend/index.html:2

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.6 / 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".

  • A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler. (×37) — Frontend/src/components/admin/authentication/SignInForm.tsx:89, Frontend/src/components/admin/common/Sidebar.tsx:74, Frontend/src/components/admin/common/Sidebar.tsx:137, …
  • A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabIndex={0}. (×3) — Frontend/src/components/chats/ChatDetials.tsx:347, Frontend/src/components/chats/ChatDetials.tsx:427, Frontend/src/components/chats/ChatDetials.tsx:430

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 safety2.6 / 10Weak✓ 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.

  • <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). (×27) — Frontend/src/components/admin/authentication/SignInForm.tsx:74, Frontend/src/components/admin/authentication/SignInForm.tsx:82, Frontend/src/components/admin/music/AddMusicForm.tsx:302, …
  • <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). (×8) — Frontend/src/components/admin/music/MusicDetialsTable.tsx:250, Frontend/src/components/admin/post/PostDetialsTable.tsx:183, Frontend/src/components/admin/subscription/SubscriptionDetials.tsx:103, …
  • <select> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). (×2) — Frontend/src/components/admin/subscription/AddSubscriptionForm.tsx:91, Frontend/src/components/admin/subscription/SubscriptionActions.tsx:126
  • <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:. (×2) — Frontend/src/components/calls/VideoAudioCall.tsx:347, Frontend/src/components/calls/VideoAudioCall.tsx:418
  • <div> moves — its inline style sets `transition: width 100ms linear` — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:. — Frontend/src/components/chats/AudioRecoding.tsx:143

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 / 10Weak✓ 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-jsx-a11y) 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 132 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.

What to do

  • Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y, 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.
AX10 · Code composition7.8 / 10Strong✓ Tool-verified

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

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

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

What to do

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

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

  • `IPostRepository` declares 23 required operations: `createPost`, `getAllPostCount`, `findUserPostData`, `findUserTaggedPosts`, `findLikedPostData`, `handleLikes`, `updateCommentCount`, `findPostById`, `findPostByIdWithUserData`, `findPostByIdWithUserData1`, `deletePost`, `getUserPostCount`, `updatePost`, `reportPost`, `archiveToggle`, `findUserArchivedPost`, `findUserReelsPost`, `findReelById`, `findPostsOfFriendAndNonWatched`, `findPostsOfNonFriendAndNonWatched`, `findPostOfWatched`, `findPostOfFollowedUserWached`, `getPostData`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — Backend/src/application/repositories/user/interfaces/IPostRepository.ts:4
  • `IUserRepository` declares 21 required operations: `findById`, `findById1`, `findByEmail`, `findByUsernameAndEmail`, `findByUsername`, `findByUsernameEdit`, `createUser`, `getAllUsers`, `findUsersByUserIds`, `userPasswordChange`, `updateUser`, `getUserData`, `blockAndUnBlockUser`, `find10UserBySearch`, `findUsers`, `findUserDataWithIdInArray`, `changeUserOnlineStatus`, `updateVerification`, `setVerificationStatusFalse`, `findSearchUsers`, `findUsersByIds`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — Backend/src/application/repositories/user/interfaces/IUserRepository.ts:5

What to do

  • Split fat interfaces into focused role-interfaces so clients depend only on what they use.
AX7 · Slice cohesion10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether feature slices stay independent (no direct cross-slice references) — the discipline that makes vertical-slice architecture pay off.

Method: Roslyn scan (vertical-slice gated): feature slices resolved from namespaces (.Features.*, .Slices.*) or project names; cross-slice type references detected. Deterministic, traceable.

C1 · Data Protection1.0 / 10Critical✓ Tool-verified

Other · Security — Whether sensitive data is encrypted at rest and in transit and keys are vaulted.

Method: Roslyn plus filesystem scan: encryption presence (EF ColumnEncryption, key-vault references, HTTPS enforcement) and key-derivation KDF detection. Deterministic.

What to do

  • Strengthen data-at-rest protection: vault your keys (AWS KMS / Secrets Manager, Azure Key Vault, GCP KMS / Secret Manager, HashiCorp Vault) and encrypt the most sensitive columns (typeorm-encrypted, prisma-field-encryption, mongoose-field-encryption or MongoDB CSFLE) — partial coverage still leaves gaps.
  • Enforce HTTPS (serve through https.createServer / NestJS httpsOptions, or redirect plain HTTP with express-sslify behind your TLS terminator) so data in transit is always encrypted.
C2 · Access Controls7.0 / 10Strong✓ Tool-verified

Other · Security — Whether access is authorized by default — a framework authorization attribute/decorator or policy, or imperative guard methods (throw-on-violation) called from handlers.

Method: Roslyn scan: [Authorize] usage and authorization policies, plus imperative throw-on-violation guard methods detected via syntax. Deterministic.

  • Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect.

What to do

  • Name the access rules — roles/permissions declared once (a @Roles/@Permissions decorator with its guard, a CASL ability, a casbin model, or Supabase CREATE POLICY) and consulted where access is checked, so the rule set is reviewable and testable on its own.
C4 · Data Retention6.5 / 10Adequate✓ Tool-verified

Other · Security — Whether data has a defined lifetime — retention periods, TTLs, cleanup jobs (storage limitation).

Method: Roslyn scan: retention/TTL configuration presence in schema; CascadeDelete detected but not scored as retention control. Deterministic, gated by PII presence.

  • A retention mechanism is present, but the data-lifecycle is not yet complete — missing: a scheduled purge / cleanup job (a cron task that deletes rows past their retention — purgeExpired… / deleteOld…), a documented retention period / data-expiry.

What to do

  • Complete the data-lifecycle story: an expiry limit (a declared maximum age for the stored data — a retention-age setting, or a store-level TTL where your storage offers one), a scheduled purge/cleanup job that enforces it, and a documented retention period covering the personal data.
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.

GD1 · Unfinished & placeholder code10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Unreviewed-generation residue in this repository's JavaScript/TypeScript: functions whose whole body still throws a "not implemented" error, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings and JSX of non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.

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

IC1 · Incompleteness & stubs7.3 / 10Strong✓ Tool-verified

Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's JavaScript/TypeScript: functions that only throw a "not implemented" error, functions that take inputs and return a constant or do nothing, async functions that never await, dead `if (false)` branches, and skeleton classes most of whose methods are holes.

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

  • `adminAuthMiddleware` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — Backend/src/infrastructure/middlewares/adminAuthMiddleware.ts:8
  • The `if` and its `else` contain the same statements, so no input can make the condition matter. Implement the distinction that was intended, or drop the branch and keep the body. (×5) — Frontend/src/components/chats/message-type/SharePostMessage.tsx:24, Frontend/src/components/notification/NotificationDetials.tsx:139, Frontend/src/components/post/PostSingle.tsx:42, …

What to do

  • Remove the dead code that still moves this score: delete dead if(false) branches and either do the real async work or drop the async keyword from fake-async functions.
M1 · Documentation (README)7.7 / 10Strong✓ 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

  • 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 1 of 2 project(s) that lack one — worth up to 1 pts.
M2 · Architecture documentation0.0 / 10Critical✓ Tool-verified

Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.

Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.

  • No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
  • No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.

What to do

  • Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
  • Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure8.0 / 10Strong✓ 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.

What to do

  • Start a test surface where your build system looks for one (tests/, test/, spec/, or your ecosystem's test source set) — the separation follows from putting the first tests in the right place.
M4 · Documentation accuracy9.0 / 10Exemplary◐ Sampled · advisory

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

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

P1 · CI/CD gates0.0 / 10Critical✓ Tool-verified

Readiness · Readiness — Whether an automated pipeline builds and tests every change.

Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.

  • No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.

What to do

  • Add a CI workflow that builds and runs the test suite on every push/PR.
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged

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

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

P2 · Observability0.0 / 10Critical✓ 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.

  • No logging call was found in the 431 JavaScript/TypeScript production file(s) this check read across 2 module(s). Each was searched for its ecosystem's logging libraries (JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.

What to do

  • Adopt pino (or winston) and log at meaningful points in the services you run.
  • Consider OpenTelemetry tracing/metrics (@opentelemetry/sdk-node) and a health-check endpoint (@godaddy/terminus or a /health route) for operability.
P3 · Security & performance tooling0.0 / 10Critical✓ Tool-verified

Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).

Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.

  • No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.

What to do

  • Run what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
  • Enable Dependabot/Renovate or a dependency-review gate.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback8.0 / 10Strong✓ 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.

  • The release 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 the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.

What to do

  • Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
PF3 · Async & latency hygiene10.0 / 10Exemplary✓ Tool-verified

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

Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from the language model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, 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.

R1 · Type Safety10.0 / 10Exemplary✓ Tool-verified

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

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

R10 · Code Duplication6.3 / 10Adequate✓ 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.

  • 52 duplicated blocks under Frontend/src/components/ have copies in at least two of the sibling directories admin, authentication, calls, chats, common, create-post (+9 more sibling(s) not listed) — 42 of them are reported below, and 10 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 52 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 52 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 52 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. — Frontend/src/components/common/PostViewModal/PostEditModal.tsx:20
  • 19 duplicated blocks under Backend/src/infrastructure/controllers/user/ have copies in at least two of the sibling directories authentication, chat, music, post, search, story (+1 more sibling(s) not listed) — 16 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 19 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 19 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 19 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. — Backend/src/infrastructure/controllers/user/post/checkingHasUserLikedPostController.ts:9
  • 14 duplicated blocks under Frontend/src/components/admin/ have copies in at least two of the sibling directories dashboard, music, post, subscription, users — 13 of them are reported below, and 1 is 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 14 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 14 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 14 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. — Frontend/src/components/admin/music/MusicDetialsTable.tsx:30
  • 10 duplicated blocks under Backend/src/application/useCases/user/ have copies in at least two of the sibling directories authentication, chat, post, search, story, subscription (+1 more sibling(s) not listed) — 3 of them are reported below, and 7 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. — Backend/src/application/useCases/user/authentication/resetPassword.ts:6
  • 10 duplicated blocks under Backend/src/infrastructure/controllers/ have copies in at least two of the sibling directories admin, user — 9 of them are reported below, and 1 is 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. — Backend/src/infrastructure/controllers/admin/authentication/refreshTokenAdminController.ts:9
  • 9 duplicated blocks under Backend/src/application/repositories/ have copies in at least two of the sibling directories admin, user — 5 of them are reported below, and 4 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 9 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 9 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 9 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. — Backend/src/application/repositories/admin/implements/musicRepository.ts:36
  • 8 duplicated blocks under Backend/src/application/useCases/ have copies in at least two of the sibling directories admin, user — 5 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 8 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 8 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 8 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. — Backend/src/application/useCases/admin/authentication/handleAdminRefreshToken.ts:5
  • 7 duplicated blocks under Backend/src/application/useCases/admin/ have copies in at least two of the sibling directories admin, authentication, music, post, subscription, user — 5 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 7 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 7 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 7 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — Backend/src/application/useCases/admin/admin/editAdmin.ts:6
  • Frontend/src/components/common/PostViewModal/PostEditModal.tsx:20 · Frontend/src/components/create-post/CreatePostFormSubmit.tsx:19 — the two spans are one implementation copied and then locally edited — 753 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. — Frontend/src/components/common/PostViewModal/PostEditModal.tsx:20
  • Frontend/src/components/admin/music/MusicDetialsTable.tsx:30 · Frontend/src/components/admin/subscription/SubscriptionDetials.tsx:20 — the two spans are one implementation copied and then locally edited — 1010 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. — Frontend/src/components/admin/music/MusicDetialsTable.tsx:30
  • Frontend/src/components/profile/ProfilePostSection.tsx:160 · Frontend/src/components/user-profiles/UserProfilePostSection.tsx:158 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — Frontend/src/components/profile/ProfilePostSection.tsx:160
  • Frontend/src/components/admin/common/Sidebar.tsx:44 · Frontend/src/components/common/Sidebar.tsx:94 — the two spans are one implementation copied and then locally edited — 666 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. — Frontend/src/components/admin/common/Sidebar.tsx:44
  • Frontend/src/components/authentication/SignInForm.tsx:14 · Frontend/src/components/authentication/SignUpForm.tsx:12 — the two spans are one implementation copied and then locally edited — 570 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. — Frontend/src/components/authentication/SignInForm.tsx:14
  • Frontend/src/components/admin/music/MusicDetialsTable.tsx:103 · Frontend/src/components/create-post/CreatePostMusic.tsx:30 — the two spans are one implementation copied and then locally edited — 517 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. — Frontend/src/components/admin/music/MusicDetialsTable.tsx:103
  • Frontend/src/components/explore/ExploreDetials.tsx:94 · Frontend/src/components/profile/ProfilePostSection.tsx:160 · Frontend/src/components/user-profiles/UserProfilePostSection.tsx:158 — the 3 copies are spread across 3 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — Frontend/src/components/explore/ExploreDetials.tsx:94
  • Frontend/src/components/admin/music/MusicAction.tsx:94 · Frontend/src/components/admin/subscription/SubscriptionActions.tsx:85 — the two spans are one implementation copied and then locally edited — 425 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. — Frontend/src/components/admin/music/MusicAction.tsx:94
  • Frontend/src/components/admin/music/MusicDetialsTable.tsx:52 · Frontend/src/components/admin/users/UserDetialsTable.tsx:51 — the two spans are one implementation copied and then locally edited — 386 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. — Frontend/src/components/admin/music/MusicDetialsTable.tsx:52
  • Frontend/src/components/admin/subscription/AddSubscriptionForm.tsx:77 · Frontend/src/components/admin/subscription/SubscriptionActions.tsx:112 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — Frontend/src/components/admin/subscription/AddSubscriptionForm.tsx:77
  • Frontend/src/components/common/PostViewModal/PostModal.tsx:1136 · Frontend/src/components/common/PostViewModal/PostModal.tsx:1320 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — Frontend/src/components/common/PostViewModal/PostModal.tsx:1136
  • Frontend/src/components/authentication/ForgotPasswordForm.tsx:33 · Frontend/src/components/authentication/ResetPasswordForm.tsx:49 — the two spans are one implementation copied and then locally edited — 252 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. — Frontend/src/components/authentication/ForgotPasswordForm.tsx:33
  • Frontend/src/components/ui/dropdown-menu.tsx:129 · Frontend/src/components/ui/menubar.tsx:160 — 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. — Frontend/src/components/ui/dropdown-menu.tsx:129
  • Frontend/src/components/admin/post/PostDetialsTable.tsx:164 · Frontend/src/components/admin/users/UserDetialsTable.tsx:155 — 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. — Frontend/src/components/admin/post/PostDetialsTable.tsx:164
  • Frontend/src/components/common/Sidebar.tsx:191 · Frontend/src/components/common/svg/Reel.tsx:11 — 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. — Frontend/src/components/common/Sidebar.tsx:191
  • Frontend/src/validations/authValidations.ts:3 · Frontend/src/validations/authValidations.ts:98 — the two spans are one implementation copied and then locally edited — 248 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. — Frontend/src/validations/authValidations.ts:3
  • Frontend/src/components/admin/post/PostDetialsTable.tsx:266 · Frontend/src/components/admin/users/UserDetialsTable.tsx:266 — 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. — Frontend/src/components/admin/post/PostDetialsTable.tsx:266
  • Frontend/src/components/admin/music/AddMusicForm.tsx:264 · Frontend/src/components/admin/music/MusicAction.tsx:162 — 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. — Frontend/src/components/admin/music/AddMusicForm.tsx:264
  • Frontend/src/components/ui/dropdown-menu.tsx:21 · Frontend/src/components/ui/menubar.tsx:49 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of MODULE-LEVEL DECLARATIONS — bindings the module declares and exports — rather than statements with a call site. Do not read this as an extract-a-helper row: a call expression cannot stand where a declaration was, and putting one there would delete the names themselves, which are what the rest of the codebase imports. What actually repeats here is the INITIALISER — the same expression shape written once per binding. So give that expression one name (a small helper the initialisers call, or a shared base value they are each derived from) and keep every binding under the name it already has. Where the run is an enumeration — one binding per distinct thing, differing precisely in the thing each one names — the repetition IS the enumeration and collapsing it would delete entries; consider instead whether the set belongs in one exported table the individual names are read out of. Reported because the copies drift apart the first time only one of them is edited. — Frontend/src/components/ui/dropdown-menu.tsx:21
  • Frontend/src/components/common/PostViewModal/PostReportModal.tsx:39 · Frontend/src/components/common/PostViewModal/PostShareModal.tsx:22 — the two spans are one implementation copied and then locally edited — 162 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. — Frontend/src/components/common/PostViewModal/PostReportModal.tsx:39
  • Frontend/src/components/profile/ProfileDetials.tsx:39 · Frontend/src/components/user-profiles/UserProfileDetials.tsx:138 — the two spans are one implementation copied and then locally edited — 227 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. — Frontend/src/components/profile/ProfileDetials.tsx:39
  • Frontend/src/apis/interceptors/adminInterceptors.ts:6 · Frontend/src/apis/interceptors/interceptors.ts:7 — 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. — Frontend/src/apis/interceptors/adminInterceptors.ts:6
  • Frontend/src/components/common/FollowDetialsModal.tsx:32 · Frontend/src/components/common/FriendSuggetion.tsx:21 — the two spans are one implementation copied and then locally edited — 229 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. — Frontend/src/components/common/FollowDetialsModal.tsx:32
  • Frontend/src/components/admin/post/PostDetialsTable.tsx:92 · Frontend/src/components/admin/users/UserDetialsTable.tsx:60 — 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. — Frontend/src/components/admin/post/PostDetialsTable.tsx:92
  • Frontend/src/components/admin/profile/AdminProfileDetials.tsx:35 · Frontend/src/components/profile/EditProfileForm.tsx:51 — 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. — Frontend/src/components/admin/profile/AdminProfileDetials.tsx:35
  • Frontend/src/components/admin/authentication/SignInForm.tsx:59 · Frontend/src/components/authentication/SignInForm.tsx:61 — 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. — Frontend/src/components/admin/authentication/SignInForm.tsx:59
  • Frontend/src/components/common/PostViewModal/PostEditModal.tsx:163 · Frontend/src/components/common/PostViewModal/PostEditModal.tsx:200 — 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. — Frontend/src/components/common/PostViewModal/PostEditModal.tsx:163
  • Backend/src/infrastructure/database/models/postModel.ts:29 · Backend/src/infrastructure/database/models/storyModal.ts:24 — the 2 copies are spread across 2 files, and what repeats is a LIST OF ENTRIES rather than behaviour — the same entries written out more than once. Extract them into one shared, exported constant and spread that constant into each site, rather than into a function the sites call: a list like this often lives in declarative metadata (a decorator's options object, a static configuration table) that a build step must be able to read statically, where a function call is not allowed. Adding an entry to one copy and not the other is the failure this prevents. — Backend/src/infrastructure/database/models/postModel.ts:29
  • Frontend/src/components/common/PostViewModal/PostModal.tsx:338 · Frontend/src/helperFuntions/dateFormat.ts:1 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — Frontend/src/components/common/PostViewModal/PostModal.tsx:338
  • Backend/src/application/useCases/user/post/explorePost.ts:6 · Backend/src/application/useCases/user/post/filterReels.ts:7 — the two spans are one implementation copied and then locally edited — 299 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. — Backend/src/application/useCases/user/post/explorePost.ts:6
  • Backend/src/infrastructure/middlewares/adminAuthMiddleware.ts:6 · Backend/src/infrastructure/middlewares/authMiddleware.ts:8 — the two spans are one implementation copied and then locally edited — 237 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. — Backend/src/infrastructure/middlewares/adminAuthMiddleware.ts:6
  • Frontend/src/components/admin/music/AddMusicForm.tsx:156 · Frontend/src/components/admin/music/MusicAction.tsx:121 — 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. — Frontend/src/components/admin/music/AddMusicForm.tsx:156

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 Boundaries0.0 / 10Critical✓ 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.

  • Backend/src/application/interface/post.ts:2 imports Backend/src/infrastructure/database/models/userModel.ts against the layered-src rules. — Backend/src/application/interface/post.ts:2
  • Backend/src/application/providers/awsS3Storage.ts:7 imports Backend/src/infrastructure/configs/aswS3.ts against the layered-src rules. — Backend/src/application/providers/awsS3Storage.ts:7
  • Backend/src/application/providers/nodeMailer.ts:7 imports Backend/src/infrastructure/configs/nodeEmailerConfig.ts against the layered-src rules. — Backend/src/application/providers/nodeMailer.ts:7
  • Backend/src/application/repositories/admin/implements/adminRepository.ts:1 imports Backend/src/infrastructure/database/models/adminModel.ts against the layered-src rules. — Backend/src/application/repositories/admin/implements/adminRepository.ts:1
  • Backend/src/application/repositories/admin/implements/musicRepository.ts:1 imports Backend/src/infrastructure/database/models/musicModal.ts against the layered-src rules. — Backend/src/application/repositories/admin/implements/musicRepository.ts:1
  • Backend/src/application/repositories/admin/implements/subscriptionRepository.ts:1 imports Backend/src/infrastructure/database/models/subscription.ts against the layered-src rules. — Backend/src/application/repositories/admin/implements/subscriptionRepository.ts:1
  • Backend/src/application/repositories/admin/interfaces/IAdminRepository.ts:1 imports Backend/src/infrastructure/database/models/adminModel.ts against the layered-src rules. — Backend/src/application/repositories/admin/interfaces/IAdminRepository.ts:1
  • Backend/src/application/repositories/admin/interfaces/IMusicRepository.ts:1 imports Backend/src/infrastructure/database/models/musicModal.ts against the layered-src rules. — Backend/src/application/repositories/admin/interfaces/IMusicRepository.ts:1
  • Backend/src/application/repositories/admin/interfaces/ISubscriptionRepository.ts:1 imports Backend/src/infrastructure/database/models/subscription.ts against the layered-src rules. — Backend/src/application/repositories/admin/interfaces/ISubscriptionRepository.ts:1
  • Backend/src/application/repositories/user/implements/chatRepository.ts:2 imports Backend/src/infrastructure/database/models/chatModal.ts against the layered-src rules. — Backend/src/application/repositories/user/implements/chatRepository.ts:2
  • Backend/src/application/repositories/user/implements/commentRepository.ts:1 imports Backend/src/infrastructure/database/models/commentModel.ts against the layered-src rules. — Backend/src/application/repositories/user/implements/commentRepository.ts:1
  • Backend/src/application/repositories/user/implements/friendsRepository.ts:1 imports Backend/src/infrastructure/database/models/friendsModal.ts against the layered-src rules. — Backend/src/application/repositories/user/implements/friendsRepository.ts:1
  • Backend/src/application/repositories/user/implements/likeRepository.ts:1 imports Backend/src/infrastructure/database/models/likeModel.ts against the layered-src rules. — Backend/src/application/repositories/user/implements/likeRepository.ts:1
  • Backend/src/application/repositories/user/implements/messageRepository.ts:1 imports Backend/src/infrastructure/database/models/messageModal.ts against the layered-src rules. — Backend/src/application/repositories/user/implements/messageRepository.ts:1
  • Backend/src/application/repositories/user/implements/notificationRepository.ts:1 imports Backend/src/infrastructure/database/models/notificationModal.ts against the layered-src rules. — Backend/src/application/repositories/user/implements/notificationRepository.ts:1
  • Backend/src/application/repositories/user/implements/otpRepository.ts:1 imports Backend/src/infrastructure/database/models/otpVerificationModel.ts against the layered-src rules. — Backend/src/application/repositories/user/implements/otpRepository.ts:1
  • Backend/src/application/repositories/user/implements/paymentRepository.ts:1 imports Backend/src/infrastructure/database/models/paymentModal.ts against the layered-src rules. — Backend/src/application/repositories/user/implements/paymentRepository.ts:1
  • Backend/src/application/repositories/user/implements/postRepository.ts:1 imports Backend/src/infrastructure/database/models/postModel.ts against the layered-src rules. — Backend/src/application/repositories/user/implements/postRepository.ts:1
  • Backend/src/application/repositories/user/implements/searchHistoryRepository.ts:1 imports Backend/src/infrastructure/database/models/searchHistoryModel.ts against the layered-src rules. — Backend/src/application/repositories/user/implements/searchHistoryRepository.ts:1
  • Backend/src/application/repositories/user/implements/storyRepository.ts:1 imports Backend/src/infrastructure/database/models/storyModal.ts against the layered-src rules. — Backend/src/application/repositories/user/implements/storyRepository.ts:1
  • Backend/src/application/repositories/user/implements/userMoreDataRepository.ts:1 imports Backend/src/infrastructure/database/models/userMoreDataModal.ts against the layered-src rules. — Backend/src/application/repositories/user/implements/userMoreDataRepository.ts:1
  • Backend/src/application/repositories/user/implements/userRepository.ts:2 imports Backend/src/infrastructure/database/models/userModel.ts against the layered-src rules. — Backend/src/application/repositories/user/implements/userRepository.ts:2
  • Backend/src/application/repositories/user/interfaces/IChatRepository.ts:2 imports Backend/src/infrastructure/database/models/chatModal.ts against the layered-src rules. — Backend/src/application/repositories/user/interfaces/IChatRepository.ts:2
  • Backend/src/application/repositories/user/interfaces/ICommentRepository.ts:1 imports Backend/src/infrastructure/database/models/commentModel.ts against the layered-src rules. — Backend/src/application/repositories/user/interfaces/ICommentRepository.ts:1
  • Backend/src/application/repositories/user/interfaces/IFriendsRepository.ts:1 imports Backend/src/infrastructure/database/models/friendsModal.ts against the layered-src rules. — Backend/src/application/repositories/user/interfaces/IFriendsRepository.ts:1
  • Backend/src/application/repositories/user/interfaces/IMessageRepository.ts:1 imports Backend/src/infrastructure/database/models/messageModal.ts against the layered-src rules. — Backend/src/application/repositories/user/interfaces/IMessageRepository.ts:1
  • Backend/src/application/repositories/user/interfaces/INotificationRepository.ts:1 imports Backend/src/infrastructure/database/models/notificationModal.ts against the layered-src rules. — Backend/src/application/repositories/user/interfaces/INotificationRepository.ts:1
  • Backend/src/application/repositories/user/interfaces/IOtpRepository.ts:1 imports Backend/src/infrastructure/database/models/otpVerificationModel.ts against the layered-src rules. — Backend/src/application/repositories/user/interfaces/IOtpRepository.ts:1
  • Backend/src/application/repositories/user/interfaces/IPaymentRepository.ts:1 imports Backend/src/infrastructure/database/models/paymentModal.ts against the layered-src rules. — Backend/src/application/repositories/user/interfaces/IPaymentRepository.ts:1
  • Backend/src/application/repositories/user/interfaces/IPostRepository.ts:1 imports Backend/src/infrastructure/database/models/postModel.ts against the layered-src rules. — Backend/src/application/repositories/user/interfaces/IPostRepository.ts:1
  • Backend/src/application/repositories/user/interfaces/ISearchHistoryRepository.ts:1 imports Backend/src/infrastructure/database/models/searchHistoryModel.ts against the layered-src rules. — Backend/src/application/repositories/user/interfaces/ISearchHistoryRepository.ts:1
  • Backend/src/application/repositories/user/interfaces/IStoryRepository.ts:1 imports Backend/src/infrastructure/database/models/storyModal.ts against the layered-src rules. — Backend/src/application/repositories/user/interfaces/IStoryRepository.ts:1
  • Backend/src/application/repositories/user/interfaces/IUserMoreDataRepository.ts:1 imports Backend/src/infrastructure/database/models/userMoreDataModal.ts against the layered-src rules. — Backend/src/application/repositories/user/interfaces/IUserMoreDataRepository.ts:1
  • Backend/src/application/repositories/user/interfaces/IUserRepository.ts:2 imports Backend/src/infrastructure/database/models/userModel.ts against the layered-src rules. — Backend/src/application/repositories/user/interfaces/IUserRepository.ts:2
  • Backend/src/application/useCases/admin/admin/editAdmin.ts:1 imports Backend/src/infrastructure/constants/messages.ts against the layered-src rules. — Backend/src/application/useCases/admin/admin/editAdmin.ts:1
  • Backend/src/application/useCases/admin/admin/editAdmin.ts:2 imports Backend/src/infrastructure/database/models/adminModel.ts against the layered-src rules. — Backend/src/application/useCases/admin/admin/editAdmin.ts:2
  • Backend/src/application/useCases/admin/admin/editAdminPassword.ts:1 imports Backend/src/infrastructure/constants/messages.ts against the layered-src rules. — Backend/src/application/useCases/admin/admin/editAdminPassword.ts:1
  • Backend/src/application/useCases/admin/admin/getAdminData.ts:1 imports Backend/src/infrastructure/constants/messages.ts against the layered-src rules. — Backend/src/application/useCases/admin/admin/getAdminData.ts:1
  • Backend/src/application/useCases/admin/admin/getAdminData.ts:2 imports Backend/src/infrastructure/database/models/adminModel.ts against the layered-src rules. — Backend/src/application/useCases/admin/admin/getAdminData.ts:2
  • Backend/src/application/useCases/admin/authentication/authenticateAdmin.ts:1 imports Backend/src/infrastructure/constants/messages.ts against the layered-src rules. — Backend/src/application/useCases/admin/authentication/authenticateAdmin.ts:1

What to do

  • Fix the listed violations: respect the layer/slice order — import only through a slice's public index and never upward into a higher layer (144 rows); import through the target package's declared public entry rather than a deep path into its internals or a relative path into its directory (1 row).
R2 · Cyclomatic Complexity8.0 / 10Strong✓ Tool-verified

React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.

Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.

  • CreatePostBody has cyclomatic complexity 37 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — Frontend/src/components/create-post/CreatePostBody.tsx:20
  • PostModal has cyclomatic complexity 36 and cognitive complexity 34; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — Frontend/src/components/common/PostViewModal/PostModal.tsx:56
  • createRoutes has cyclomatic complexity 34 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — Frontend/src/routes/createRoutes.tsx:35
  • VideoAudioCall has cyclomatic complexity 32 and cognitive complexity 30; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — Frontend/src/components/calls/VideoAudioCall.tsx:15
  • (anonymous) has cyclomatic complexity 28 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — Frontend/src/components/admin/post/PostDetialsTable.tsx:48
  • CreatePostFilters has cyclomatic complexity 27 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — Frontend/src/components/create-post/CreatePostFilters.tsx:16
  • ChatsInbox has cyclomatic complexity 22 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — Frontend/src/components/chats/ChatInbox.tsx:26
  • (anonymous) has cyclomatic complexity 22 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — Frontend/src/components/chats/ChatInbox.tsx:436
  • handleInputChange has cyclomatic complexity 21 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — Frontend/src/components/create-post/SelectAspectRatio.tsx:95
  • (anonymous) has cyclomatic complexity 21 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — Frontend/src/components/common/FollowDetialsModal.tsx:135
  • Sidebar has cyclomatic complexity 19 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — Frontend/src/components/common/Sidebar.tsx:56
  • ProfilePostSection has cyclomatic complexity 19 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — Frontend/src/components/profile/ProfilePostSection.tsx:26
  • (anonymous) has cyclomatic complexity 17 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — Frontend/src/components/home/Posts.tsx:274
  • execute has cyclomatic complexity 17 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — Backend/src/application/useCases/user/chat/sendMessage.ts:18
  • TagUser has cyclomatic complexity 16 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — Frontend/src/components/create-post/TagUser.tsx:26
  • ChatDetials has cyclomatic complexity 15 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — Frontend/src/components/chats/ChatDetials.tsx:26
  • CreatePostFormSubmit has cyclomatic complexity 15 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — Frontend/src/components/create-post/CreatePostFormSubmit.tsx:13
  • UserProfileDetials has cyclomatic complexity 15 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — Frontend/src/components/user-profiles/UserProfileDetials.tsx:19
  • (anonymous) has cyclomatic complexity 15 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — Frontend/src/components/common/PostViewModal/PostModal.tsx:1032
  • timeSince has cyclomatic complexity 14 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — Frontend/src/components/common/PostViewModal/PostModal.tsx:338

What to do

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

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

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

  • Frontend/src/components/common/PostViewModal/PostModal.tsx has 1557 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — Frontend/src/components/common/PostViewModal/PostModal.tsx:1
  • Frontend/src/components/chats/ChatInbox.tsx has 498 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — Frontend/src/components/chats/ChatInbox.tsx:1
  • Frontend/src/components/calls/VideoAudioCall.tsx has 442 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — Frontend/src/components/calls/VideoAudioCall.tsx:1
  • Frontend/src/components/common/Sidebar.tsx has 422 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — Frontend/src/components/common/Sidebar.tsx:1
  • Frontend/src/components/home/Posts.tsx has 413 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — Frontend/src/components/home/Posts.tsx:1
  • Frontend/src/components/chats/ChatDetials.tsx has 408 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — Frontend/src/components/chats/ChatDetials.tsx: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.0 / 10Critical✓ Tool-verified

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

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

  • 0% of 396 production file(s) reachable from 0 test file(s) via the import graph — 'production' here is the RESIDUE: every source file left once tests, tooling, generated output, config, declarations and declaration-only modules, fixture corpora, type fixtures, behaviour-free data modules, re-export barrels, registration/constant data modules and service workers are set aside, so the percentage is taken over a smaller denominator than the workspace's file count

What to do

  • Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness5.0 / 10Adequate✓ 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.

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

What to do

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

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

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

  • test ✗ · lint ✓ · typecheck ✓ — read from this repository's package.json 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 a test runner (vitest / jest / playwright) as package.json scripts and run them in CI.
R7 · Dead Code9.5 / 10Exemplary✓ Tool-verified

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

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

  • Unreachable from the 5 application, 7 tooling and 0 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 (5 application, 7 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×5) — Frontend/src/components/ui/mode-toggle.tsx, Frontend/src/helperFuntions/convertBlobUrlToBase64.ts, Frontend/src/components/ui/slider.tsx, …
  • Nothing imports this binding — it is safe to review for removal. (×5) — Frontend/src/context/SocketContext.ts:6, Frontend/src/redux/store/store.ts:37, Frontend/src/redux/store/store.ts:40, …
  • This private field is assigned but never read: every reference in its class is a plain assignment, no string key or test reads it by name, and the instance never escapes as a whole (so nothing serialises or destructures it). The value it holds is dead state — read it where it was meant to take effect, or remove the field and its assignments. (×2) — Backend/src/application/useCases/user/story/createStory.ts:13, Backend/src/application/useCases/user/user/removeUser.ts:12

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 Hygiene9.0 / 10Exemplary✓ 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.

  • Declared in Frontend/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. (×2)

What to do

  • Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports6.4 / 10Adequate✓ 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.

  • Backend/src/application/useCases/user/chat/sendMessage.ts → Backend/src/infrastructure/service/socketService.ts → Backend/src/application/useCases/user/chat/sendMessage.ts (one verified cycle inside a mutually-dependent group of 3 files) — Backend/src/application/useCases/user/chat/sendMessage.ts:3
  • Frontend/src/apis/apiClient.ts → Frontend/src/apis/interceptors/adminInterceptors.ts → Frontend/src/apis/apiClient.ts (one verified cycle inside a mutually-dependent group of 3 files) — Frontend/src/apis/apiClient.ts:7

What to do

  • Break each cycle by extracting the shared piece into a module both sides can import.
S1 · Web-Security Posture6.0 / 10Adequate✓ Tool-verified

Other · Security — Read from this repository's JavaScript/TypeScript source: cryptographic hygiene (weak hash or cipher, key material fixed in the source) and outbound TLS (certificate validation, protocol version) — facts about code that hold whether or not it serves anything itself. This repository commits the configuration that serves its own HTTP surface, so that configuration was read in full for the security response headers it sets. The server controls — HTTPS enforcement, HSTS, cookie flags, input validation — are NOT assessed for JavaScript/TypeScript: each is scored as an absence, an absence is only reportable over the production HTTP server, and in this ecosystem the file that opens the port is build output or a framework launcher rather than a file in the source tree. Their absence here is not a finding about this repository. Its Node HTTP listeners were read for HTTPS enforcement alone — TLS served, a redirect to https:// or HSTS, or a TLS-terminating proxy configuration committed beside the server — each judged per server package.

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

  • None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `vercel.json` configures this repository's static hosting, including its response headers, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.) — Frontend/vercel.json:1
  • `server.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.) — Backend/src/presentation/settings/server.ts:73

What to do

  • Set security response headers on the surface this repository serves: an `add_header` directive per header in the nginx/Caddy/Apache config, a `_headers` / `vercel.json` / `netlify.toml` entry for a static host, or `helmet()` in the HTTP server. `Content-Security-Policy` is the one that pays for itself first — it is what contains an injected script once one reaches the page — followed by `X-Content-Type-Options: nosniff` and a frame policy (`X-Frame-Options: DENY`, or CSP `frame-ancestors`). Where the app is served from a build container, the header configuration belongs in the image beside the built assets, so it ships with them rather than depending on where it lands.
  • Enforce HTTPS on each listed server: serve TLS itself, or redirect plain requests to `https://` and send `Strict-Transport-Security` (`helmet()` does by default) behind the TLS-terminating proxy — and commit that proxy's configuration beside the service. A server only this machine reaches should bind `127.0.0.1`.
X1 · Async correctness7.5 / 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.

  • `forEach` ignores what its callback returns, so the Promise each `async` call returns is dropped: nothing can await it, the code after this loop runs before any of the awaited work has finished (a function that `await`s around this loop still returns early), and a rejection is never handled — in Node.js an unhandled rejection terminates the process by default, and in a browser it is lost. Iterate with `for (const item of items) { await … }` when the work must run in order, or `await Promise.all(items.map(async (item) => { … }))` when it may run concurrently, so the enclosing function finishes only when the work does and its failures reach the caller. Where firing and forgetting is genuinely intended, make the callback's whole body a `try { … } catch (e) { … }` that handles the failure, so it cannot escape. (×8) — Backend/src/application/useCases/user/chat/sendShareMessaege.ts:29, Backend/src/application/useCases/user/post/replyComment.ts:47, Backend/src/application/useCases/user/post/deletePost.ts:45, …

What to do

  • `async` callback passed to `forEach`
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 propagation4.0 / 10Weak✓ Tool-verified

Other · Code Health — Whether async functions that make a cancellable request accept or pass on an AbortSignal (adoption curve).

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

  • Only 0/1 async functions that make a cancellable request (fetch, axios, ky, ofetch) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
  • `convertBlobUrlToBase64` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — Frontend/src/helperFuntions/convertBlobUrlToBase64.ts:1

What to do

  • Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
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.

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 unescaped5.0 / 10Adequate✓ Tool-verified

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

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

  • `(userData?.bio??"").replace(/\n/g,"<br />")` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×2) — Frontend/src/components/profile/ProfileDetials.tsx:88, Frontend/src/components/user-profiles/UserProfileDetials.tsx:215

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.

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 handling10.0 / 10Exemplary○ Nothing flagged

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.

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.

X5 · Nullable reference types9.3 / 10Exemplary✓ Tool-verified

Other · Code Health — Whether strict null checking is enabled and not undermined by heavy `!` assertion — TypeScript's `strictNullChecks` (which `strict` turns on) is what makes `string` exclude `null` and `undefined`, and the postfix `!` is the operator that silences it.

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

  • ~1.6 `!` null assertions per 1k TypeScript source lines — 50 assertion(s) across the 30839 source line(s) of the 430 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: Backend/src/presentation/settings/server.ts (17), Backend/src/application/providers/tokenManager.ts (6), Backend/src/infrastructure/configs/aswS3.ts (4). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.

What to do

  • The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).

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 Health56%Adequate — gated by D1, D2, D3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture57%Adequate — gated by D26, R11Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity53%Adequate — gated by M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness14%Critical — gated by D8, D9, R4, P1, P2, P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security45%Weak — gated by D29, D30, C1Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Accessibility37%Weak — gated by AC4, AC6Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance100%ExemplaryStrongest area.
Unscored — 1 check(s) recorded observations but carry no score

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

  • X10 Duplicated predicate — 10 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for

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

  • C3 Audit Trail — Repo shows no audit-logging mechanism (an audit-log table or model, an ORM write hook that records changes — a TypeORM/MikroORM subscriber, a Sequelize or Mongoose hook, Prisma middleware — or a change-history plugin such as mongoose-history or sequelize-paper-trail) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
  • C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
  • P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 53 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.

  • AX1 Captive dependencies — Not applicable: this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
  • AX2 Stateful singletons — Not applicable: TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
  • AX4 Dependency direction — not applicable to a vertical-slice architecture (the inward-dependency rule is for layered/clean styles)
  • AX8 Test isolation — no test/production split to check
  • AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXR1 Runtime accessibility — the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
  • D10 Test Quality — No tests were found in the analyzed repository to assess for quality.
  • D11 Test Reliability — No test suite was found to re-run, so reliability couldn't be assessed. Two searches produced that zero and both came back empty: the classifier that reads the loaded workspace recognised no suite it could run, and a walk of the source on disk — which covers the JS/TS `*.test.*` and `*.spec.*` conventions and probes for a Pester suite — found no test source in any other ecosystem either. Neither search reaches a suite that is missing from the loaded workspace and carries no name either walk recognises, so this is 'no suite found by those two searches', not a verdict that the repository has none.
  • D16 Bus Factor — single-contributor repository — bus factor is not applicable
  • D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
  • D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
  • D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D24 Comment Value — No inline comments to assess — comment value is not applicable here.
  • D25 ADR Conformance — no ADRs to check
  • D27 Navigability — D27 reads resolved call sites in the languages it reads only — this repository's production source is .tsx, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
  • D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
  • D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
  • 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.
  • D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
  • D4 Code Duplication — This repository's production source (.ts, .tsx) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication.
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
  • D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
  • DM1 Aggregate boundaries — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
  • DM10 One transaction, one aggregate — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
  • DM2 Strongly-typed ids — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
  • DM3 Integration-event coupling — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
  • DM4 Rich vs anemic model — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
  • DM5 Encapsulated state — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
  • DM6 Domain ↔ infrastructure boundary — this TypeScript/JavaScript repository maps no type to a persistence framework (TypeORM/Prisma/MikroORM/Sequelize/Mongoose), so DM6's domain↔infrastructure fusion read has no population to be taken over
  • DM7 Repository granularity — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
  • ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
  • ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • P12 CI test-gate honesty — no CI workflow found
  • P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the JavaScript/TypeScript source (service entry point: Backend/src/presentation/settings/server.ts:25 (express()))
  • P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
  • P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `vitest --coverage`, `jest --coverage`, `bun test --coverage --coverage-reporter=lcov`, or `nyc`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
  • PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
  • PF2 Allocation hygiene — Not applicable: TypeScript/JavaScript runs on a garbage-collected runtime that gives a program no allocation-control idiom to choose on a hot path — no pools, stack allocation or value types — so allocation awareness is not something this code can be rated on.
  • SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
  • X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
  • X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

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

Critical — 124 finding(s)
D30 · Dependency Vulnerabilities · High CVE · ×33
  • 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
  • + 8 more in this group — see findings.md.
AC2 · Forms & labels · <input> without a programmatic label · ×21
  • <input> without a programmatic label Frontend/src/components/admin/authentication/SignInForm.tsx:74 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label Frontend/src/components/admin/authentication/SignInForm.tsx:82 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label Frontend/src/components/admin/music/MusicDetialsTable.tsx:242 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label Frontend/src/components/admin/post/PostDetialsTable.tsx:175 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label Frontend/src/components/admin/profile/AdminProfileChangePassword.tsx:86 — This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label Frontend/src/components/admin/profile/AdminProfileChangePassword.tsx:115 — This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label Frontend/src/components/admin/profile/AdminProfileChangePassword.tsx:144 — This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label Frontend/src/components/admin/profile/AdminProfileDetials.tsx:195 — This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label Frontend/src/components/admin/profile/AdminProfileDetials.tsx:211 — This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label Frontend/src/components/admin/subscription/AddSubscriptionForm.tsx:105 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label Frontend/src/components/admin/subscription/SubscriptionActions.tsx:140 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label Frontend/src/components/admin/subscription/SubscriptionDetials.tsx:95 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label Frontend/src/components/admin/users/UserDetialsTable.tsx:166 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label Frontend/src/components/authentication/ForgotPasswordForm.tsx: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 htmlFor>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label Frontend/src/components/authentication/OtpForm.tsx:125 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label Frontend/src/components/authentication/ResetPasswordForm.tsx:77 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label Frontend/src/components/authentication/ResetPasswordForm.tsx:100 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label Frontend/src/components/authentication/SignInForm.tsx: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 htmlFor>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label Frontend/src/components/authentication/SignInForm.tsx:84 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label Frontend/src/components/authentication/SignUpForm.tsx: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 htmlFor>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label Frontend/src/components/authentication/SignUpForm.tsx: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 htmlFor>, a wrapping <label>, or aria-label.
AC4 · Keyboard semantics · Click handler on a non-interactive <th> · ×15
  • Click handler on a non-interactive <th> Frontend/src/components/admin/music/MusicDetialsTable.tsx:290 — 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 <th> Frontend/src/components/admin/music/MusicDetialsTable.tsx:292 — 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 <th> Frontend/src/components/admin/post/PostDetialsTable.tsx:222 — 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 <th> Frontend/src/components/admin/post/PostDetialsTable.tsx:223 — 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 <th> Frontend/src/components/admin/post/PostDetialsTable.tsx:224 — 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 <th> Frontend/src/components/admin/post/PostDetialsTable.tsx:225 — 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 <th> Frontend/src/components/admin/post/PostDetialsTable.tsx:226 — 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 <th> Frontend/src/components/admin/post/PostDetialsTable.tsx:227 — 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 <th> Frontend/src/components/admin/post/PostDetialsTable.tsx:228 — 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 <th> Frontend/src/components/admin/subscription/SubscriptionDetials.tsx:142 — 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 <th> Frontend/src/components/admin/subscription/SubscriptionDetials.tsx:145 — 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 <th> Frontend/src/components/admin/users/UserDetialsTable.tsx:213 — 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 <th> Frontend/src/components/admin/users/UserDetialsTable.tsx:214 — 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 <th> Frontend/src/components/admin/users/UserDetialsTable.tsx:215 — 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 <th> Frontend/src/components/admin/users/UserDetialsTable.tsx:217 — 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 · Click handler on a non-interactive <span> · ×10
  • Click handler on a non-interactive <span> Frontend/src/components/admin/authentication/SignInForm.tsx:89 — 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> Frontend/src/components/admin/profile/AdminProfileChangePassword.tsx:94 — 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> Frontend/src/components/admin/profile/AdminProfileChangePassword.tsx:123 — 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> Frontend/src/components/admin/profile/AdminProfileChangePassword.tsx:152 — 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> Frontend/src/components/authentication/OtpForm.tsx:147 — 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> Frontend/src/components/authentication/ResetPasswordForm.tsx:84 — 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> Frontend/src/components/authentication/ResetPasswordForm.tsx:107 — 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> Frontend/src/components/authentication/SignInForm.tsx:91 — 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> Frontend/src/components/authentication/SignUpForm.tsx:108 — 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> Frontend/src/components/authentication/SignUpForm.tsx:131 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
D30 · Dependency Vulnerabilities · Critical CVE · ×10
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AC4 · Keyboard semantics · Click handler on a non-interactive <div> · ×8
  • Click handler on a non-interactive <div> Frontend/src/components/admin/common/Sidebar.tsx:157 — 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> Frontend/src/components/chats/ChatDetials.tsx:347 — A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabIndex={0}.
  • Click handler on a non-interactive <div> Frontend/src/components/chats/ChatDetials.tsx:427 — A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabIndex={0}.
  • Click handler on a non-interactive <div> Frontend/src/components/chats/ChatDetials.tsx:430 — A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabIndex={0}.
  • Click handler on a non-interactive <div> Frontend/src/components/chats/ChatInbox.tsx:248 — 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> Frontend/src/components/chats/ChatInbox.tsx:377 — 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> Frontend/src/components/chats/ChatInbox.tsx:437 — 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> Frontend/src/components/chats/ChatInbox.tsx:492 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
AC2 · Forms & labels · <button> with no accessible text · ×5
  • <button> with no accessible text Frontend/src/components/admin/music/MusicDetialsTable.tsx:250 — A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
  • <button> with no accessible text Frontend/src/components/admin/post/PostDetialsTable.tsx:183 — A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
  • <button> with no accessible text Frontend/src/components/admin/profile/AdminProfileDetials.tsx:145 — A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
  • <button> with no accessible text Frontend/src/components/admin/subscription/SubscriptionDetials.tsx:103 — A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
  • <button> with no accessible text Frontend/src/components/admin/users/UserDetialsTable.tsx:174 — A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
AC2 · Forms & labels · <label> that labels no control · ×5
  • <label> that labels no control Frontend/src/components/admin/profile/AdminProfileChangePassword.tsx:82 — This <label> has no htmlFor 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 htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control Frontend/src/components/admin/profile/AdminProfileChangePassword.tsx:111 — This <label> has no htmlFor 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 htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control Frontend/src/components/admin/profile/AdminProfileChangePassword.tsx:140 — This <label> has no htmlFor 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 htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control Frontend/src/components/admin/profile/AdminProfileDetials.tsx:192 — This <label> has no htmlFor 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 htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control Frontend/src/components/admin/profile/AdminProfileDetials.tsx:208 — This <label> has no htmlFor 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 htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
AC1 · Text alternatives · <img> without a text alternative · ×4
  • <img> without a text alternative Frontend/src/components/common/FollowDetialsModal.tsx:144 — 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 Frontend/src/components/common/FriendSuggetion.tsx:90 — 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 Frontend/src/components/notification/NotificationDetials.tsx:175 — 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 Frontend/src/components/search/SearchDetials.tsx:183 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
AC4 · Keyboard semantics · Click handler on a non-interactive <img> · ×4
  • Click handler on a non-interactive <img> Frontend/src/components/admin/common/Sidebar.tsx:137 — 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 <img> Frontend/src/components/admin/music/MusicDetialsTable.tsx:301 — 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 <img> Frontend/src/components/admin/post/PostDetialsTable.tsx:238 — 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 <img> Frontend/src/components/admin/users/UserDetialsTable.tsx:225 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
AC2 · Forms & labels · <select> without a programmatic label · ×2
  • <select> without a programmatic label Frontend/src/components/admin/subscription/AddSubscriptionForm.tsx:91 — This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <select> without a programmatic label Frontend/src/components/admin/subscription/SubscriptionActions.tsx:126 — This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC4 · Keyboard semantics · Click handler on a non-interactive <h1> · ×2
  • Click handler on a non-interactive <h1> Frontend/src/components/admin/common/Sidebar.tsx:74 — 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 <h1> Frontend/src/components/chats/ChatInbox.tsx:218 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
R9 · Circular Imports · Import cycle (2 files) · ×2
  • Import cycle (2 files) Backend/src/application/useCases/user/chat/sendMessage.ts:3 — Backend/src/application/useCases/user/chat/sendMessage.ts → Backend/src/infrastructure/service/socketService.ts → Backend/src/application/useCases/user/chat/sendMessage.ts (one verified cycle inside a mutually-dependent group of 3 files)
  • Import cycle (2 files) Frontend/src/apis/apiClient.ts:7 — Frontend/src/apis/apiClient.ts → Frontend/src/apis/interceptors/adminInterceptors.ts → Frontend/src/apis/apiClient.ts (one verified cycle inside a mutually-dependent group of 3 files)
AC2 · Forms & labels · Custom control with no accessible name on <video> · ×1
  • Custom control with no accessible name on <video> Frontend/src/components/admin/post/PostDetialsTable.tsx:243 — This <video> 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 <video> · ×1
  • Click handler on a non-interactive <video> Frontend/src/components/admin/post/PostDetialsTable.tsx:243 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
D8 · Code Coverage · No automated tests · ×1
  • No automated tests — No automated tests — no test code was found in this repository. Untested code is the largest single risk to changing it safely. Start with the code you change most often: add a suite in a framework a runner can collect (Vitest, Jest, Mocha, or the runtime's built-in runner (`node --test`, `bun test`, `deno test`)), and run it in CI so the gap cannot reopen.
Serious — 383 finding(s)
D3 · God Classes · FunctionTooLong · ×45
  • FunctionTooLong: PostModal.PostModal Frontend/src/components/common/PostViewModal/PostModal.tsx:56 — FunctionTooLong — PostModal runs 1268 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1168 over it, 12.68× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: ChatInbox.ChatsInbox Frontend/src/components/chats/ChatInbox.tsx:26 — FunctionTooLong — ChatsInbox runs 412 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 312 over it, 4.12× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: VideoAudioCall.VideoAudioCall Frontend/src/components/calls/VideoAudioCall.tsx:15 — FunctionTooLong — VideoAudioCall runs 351 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 251 over it, 3.51× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: Sidebar.Sidebar Frontend/src/components/common/Sidebar.tsx:56 — FunctionTooLong — Sidebar runs 348 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 248 over it, 3.48× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: Posts.Posts Frontend/src/components/home/Posts.tsx:21 — FunctionTooLong — Posts runs 316 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 216 over it, 3.16× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: ChatDetials.ChatDetials Frontend/src/components/chats/ChatDetials.tsx:26 — FunctionTooLong — ChatDetials runs 312 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 212 over it, 3.12× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: MusicDetialsTable.MusicDetialsTable Frontend/src/components/admin/music/MusicDetialsTable.tsx:28 — FunctionTooLong — MusicDetialsTable runs 311 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 211 over it, 3.11× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: AddMusicForm.AddMusicForm Frontend/src/components/admin/music/AddMusicForm.tsx:19 — FunctionTooLong — AddMusicForm runs 309 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 209 over it, 3.09× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: ReelsDetials.ReelsDetials Frontend/src/components/reel/ReelsDetials.tsx:20 — FunctionTooLong — ReelsDetials runs 290 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 190 over it, 2.90× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: NotificationDetials.NotificationDetials Frontend/src/components/notification/NotificationDetials.tsx:23 — FunctionTooLong — NotificationDetials runs 280 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 180 over it, 2.80× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: UserProfilePostSection.UserProfilePostSection Frontend/src/components/user-profiles/UserProfilePostSection.tsx:19 — FunctionTooLong — UserProfilePostSection runs 272 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 172 over it, 2.72× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: EditProfileForm.EditProfileForm Frontend/src/components/profile/EditProfileForm.tsx:21 — FunctionTooLong — EditProfileForm runs 258 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 158 over it, 2.58× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: ProfilePostSection.ProfilePostSection Frontend/src/components/profile/ProfilePostSection.tsx:26 — FunctionTooLong — ProfilePostSection runs 257 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 157 over it, 2.57× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: AdminProfileDetials.AdminProfileDetails Frontend/src/components/admin/profile/AdminProfileDetials.tsx:11 — FunctionTooLong — AdminProfileDetails runs 247 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 147 over it, 2.47× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: CreatePostFormSubmit.CreatePostFormSubmit Frontend/src/components/create-post/CreatePostFormSubmit.tsx:13 — FunctionTooLong — CreatePostFormSubmit runs 240 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 140 over it, 2.40× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: PostDetialsTable.PostDetialsTable Frontend/src/components/admin/post/PostDetialsTable.tsx:31 — FunctionTooLong — PostDetialsTable runs 232 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 132 over it, 2.32× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: UserDetialsTable.UserDetialsTable Frontend/src/components/admin/users/UserDetialsTable.tsx:32 — FunctionTooLong — UserDetialsTable runs 232 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 132 over it, 2.32× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: PostEditModal.PostEditModal Frontend/src/components/common/PostViewModal/PostEditModal.tsx:13 — FunctionTooLong — PostEditModal runs 223 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 123 over it, 2.23× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: PostModalActions.PostModalActions Frontend/src/components/common/PostViewModal/PostModalActions.tsx:12 — FunctionTooLong — PostModalActions runs 215 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 115 over it, 2.15× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: SelectAspectRatio.SelectAspectRatioAndUplaod Frontend/src/components/create-post/SelectAspectRatio.tsx:27 — FunctionTooLong — SelectAspectRatioAndUplaod runs 212 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 112 over it, 2.12× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: ChangePost.ChangePost Frontend/src/components/create-post/ChangePost.tsx:26 — FunctionTooLong — ChangePost runs 204 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 104 over it, 2.04× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: CreatePostMusic.CreatePostMusic Frontend/src/components/create-post/CreatePostMusic.tsx:16 — FunctionTooLong — CreatePostMusic runs 199 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 99 over it, 1.99× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: TagUser.TagUser Frontend/src/components/create-post/TagUser.tsx:26 — FunctionTooLong — TagUser runs 196 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 96 over it, 1.96× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: CreatePostBody.CreatePostBody Frontend/src/components/create-post/CreatePostBody.tsx:20 — FunctionTooLong — CreatePostBody runs 179 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 79 over it, 1.79× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: SubscriptionDetials.SubscriptionDetials Frontend/src/components/admin/subscription/SubscriptionDetials.tsx:19 — FunctionTooLong — SubscriptionDetials runs 164 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 64 over it, 1.64× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • + 20 more in this group — see findings.md.
R11 · Import Boundaries · Boundary violation [layered · ×40
  • Boundary violation [layered:upward-import] Backend/src/application/interface/post.ts:2 — Backend/src/application/interface/post.ts:2 imports Backend/src/infrastructure/database/models/userModel.ts against the layered-src rules.
  • Boundary violation [layered:upward-import] Backend/src/application/providers/awsS3Storage.ts:7 — Backend/src/application/providers/awsS3Storage.ts:7 imports Backend/src/infrastructure/configs/aswS3.ts against the layered-src rules.
  • Boundary violation [layered:upward-import] Backend/src/application/providers/nodeMailer.ts:7 — Backend/src/application/providers/nodeMailer.ts:7 imports Backend/src/infrastructure/configs/nodeEmailerConfig.ts against the layered-src rules.
  • Boundary violation [layered:upward-import] Backend/src/application/repositories/admin/implements/adminRepository.ts:1 — Backend/src/application/repositories/admin/implements/adminRepository.ts:1 imports Backend/src/infrastructure/database/models/adminModel.ts against the layered-src rules.
  • Boundary violation [layered:upward-import] Backend/src/application/repositories/admin/implements/musicRepository.ts:1 — Backend/src/application/repositories/admin/implements/musicRepository.ts:1 imports Backend/src/infrastructure/database/models/musicModal.ts against the layered-src rules.
  • Boundary violation [layered:upward-import] Backend/src/application/repositories/admin/implements/subscriptionRepository.ts:1 — Backend/src/application/repositories/admin/implements/subscriptionRepository.ts:1 imports Backend/src/infrastructure/database/models/subscription.ts against the layered-src rules.
  • Boundary violation [layered:upward-import] Backend/src/application/repositories/admin/interfaces/IAdminRepository.ts:1 — Backend/src/application/repositories/admin/interfaces/IAdminRepository.ts:1 imports Backend/src/infrastructure/database/models/adminModel.ts against the layered-src rules.
  • Boundary violation [layered:upward-import] Backend/src/application/repositories/admin/interfaces/IMusicRepository.ts:1 — Backend/src/application/repositories/admin/interfaces/IMusicRepository.ts:1 imports Backend/src/infrastructure/database/models/musicModal.ts against the layered-src rules.
  • Boundary violation [layered:upward-import] Backend/src/application/repositories/admin/interfaces/ISubscriptionRepository.ts:1 — Backend/src/application/repositories/admin/interfaces/ISubscriptionRepository.ts:1 imports Backend/src/infrastructure/database/models/subscription.ts against the layered-src rules.
  • Boundary violation [layered:upward-import] Backend/src/application/repositories/user/implements/chatRepository.ts:2 — Backend/src/application/repositories/user/implements/chatRepository.ts:2 imports Backend/src/infrastructure/database/models/chatModal.ts against the layered-src rules.
  • Boundary violation [layered:upward-import] Backend/src/application/repositories/user/implements/commentRepository.ts:1 — Backend/src/application/repositories/user/implements/commentRepository.ts:1 imports Backend/src/infrastructure/database/models/commentModel.ts against the layered-src rules.
  • Boundary violation [layered:upward-import] Backend/src/application/repositories/user/implements/friendsRepository.ts:1 — Backend/src/application/repositories/user/implements/friendsRepository.ts:1 imports Backend/src/infrastructure/database/models/friendsModal.ts against the layered-src rules.
  • Boundary violation [layered:upward-import] Backend/src/application/repositories/user/implements/likeRepository.ts:1 — Backend/src/application/repositories/user/implements/likeRepository.ts:1 imports Backend/src/infrastructure/database/models/likeModel.ts against the layered-src rules.
  • Boundary violation [layered:upward-import] Backend/src/application/repositories/user/implements/messageRepository.ts:1 — Backend/src/application/repositories/user/implements/messageRepository.ts:1 imports Backend/src/infrastructure/database/models/messageModal.ts against the layered-src rules.
  • Boundary violation [layered:upward-import] Backend/src/application/repositories/user/implements/notificationRepository.ts:1 — Backend/src/application/repositories/user/implements/notificationRepository.ts:1 imports Backend/src/infrastructure/database/models/notificationModal.ts against the layered-src rules.
  • Boundary violation [layered:upward-import] Backend/src/application/repositories/user/implements/otpRepository.ts:1 — Backend/src/application/repositories/user/implements/otpRepository.ts:1 imports Backend/src/infrastructure/database/models/otpVerificationModel.ts against the layered-src rules.
  • Boundary violation [layered:upward-import] Backend/src/application/repositories/user/implements/paymentRepository.ts:1 — Backend/src/application/repositories/user/implements/paymentRepository.ts:1 imports Backend/src/infrastructure/database/models/paymentModal.ts against the layered-src rules.
  • Boundary violation [layered:upward-import] Backend/src/application/repositories/user/implements/postRepository.ts:1 — Backend/src/application/repositories/user/implements/postRepository.ts:1 imports Backend/src/infrastructure/database/models/postModel.ts against the layered-src rules.
  • Boundary violation [layered:upward-import] Backend/src/application/repositories/user/implements/searchHistoryRepository.ts:1 — Backend/src/application/repositories/user/implements/searchHistoryRepository.ts:1 imports Backend/src/infrastructure/database/models/searchHistoryModel.ts against the layered-src rules.
  • Boundary violation [layered:upward-import] Backend/src/application/repositories/user/implements/storyRepository.ts:1 — Backend/src/application/repositories/user/implements/storyRepository.ts:1 imports Backend/src/infrastructure/database/models/storyModal.ts against the layered-src rules.
  • Boundary violation [layered:upward-import] Backend/src/application/repositories/user/implements/userMoreDataRepository.ts:1 — Backend/src/application/repositories/user/implements/userMoreDataRepository.ts:1 imports Backend/src/infrastructure/database/models/userMoreDataModal.ts against the layered-src rules.
  • Boundary violation [layered:upward-import] Backend/src/application/repositories/user/implements/userRepository.ts:2 — Backend/src/application/repositories/user/implements/userRepository.ts:2 imports Backend/src/infrastructure/database/models/userModel.ts against the layered-src rules.
  • Boundary violation [layered:upward-import] Backend/src/application/repositories/user/interfaces/IChatRepository.ts:2 — Backend/src/application/repositories/user/interfaces/IChatRepository.ts:2 imports Backend/src/infrastructure/database/models/chatModal.ts against the layered-src rules.
  • Boundary violation [layered:upward-import] Backend/src/application/repositories/user/interfaces/ICommentRepository.ts:1 — Backend/src/application/repositories/user/interfaces/ICommentRepository.ts:1 imports Backend/src/infrastructure/database/models/commentModel.ts against the layered-src rules.
  • Boundary violation [layered:upward-import] Backend/src/application/repositories/user/interfaces/IFriendsRepository.ts:1 — Backend/src/application/repositories/user/interfaces/IFriendsRepository.ts:1 imports Backend/src/infrastructure/database/models/friendsModal.ts against the layered-src rules.
  • + 15 more in this group — see findings.md.
AC6 · Visual & motion safety · Focus outline removed inline · ×37
  • Focus outline removed inline Frontend/src/components/admin/authentication/SignInForm.tsx:74 — <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
  • Focus outline removed inline Frontend/src/components/admin/authentication/SignInForm.tsx:82 — <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
  • Focus outline removed inline Frontend/src/components/admin/music/AddMusicForm.tsx:302 — <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
  • Focus outline removed inline Frontend/src/components/admin/music/MusicAction.tsx:200 — <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
  • Focus outline removed inline Frontend/src/components/admin/music/MusicDetialsTable.tsx:242 — <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
  • Focus outline removed inline Frontend/src/components/admin/music/MusicDetialsTable.tsx:250 — <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
  • Focus outline removed inline Frontend/src/components/admin/post/PostDetialsTable.tsx:175 — <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
  • Focus outline removed inline Frontend/src/components/admin/post/PostDetialsTable.tsx:183 — <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
  • Focus outline removed inline Frontend/src/components/admin/profile/AdminProfileChangePassword.tsx:86 — <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
  • Focus outline removed inline Frontend/src/components/admin/profile/AdminProfileChangePassword.tsx:115 — <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
  • Focus outline removed inline Frontend/src/components/admin/profile/AdminProfileChangePassword.tsx:144 — <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
  • Focus outline removed inline Frontend/src/components/admin/subscription/AddSubscriptionForm.tsx:91 — <select> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
  • Focus outline removed inline Frontend/src/components/admin/subscription/AddSubscriptionForm.tsx:105 — <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
  • Focus outline removed inline Frontend/src/components/admin/subscription/AddSubscriptionForm.tsx:120 — <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
  • Focus outline removed inline Frontend/src/components/admin/subscription/SubscriptionActions.tsx:126 — <select> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
  • Focus outline removed inline Frontend/src/components/admin/subscription/SubscriptionActions.tsx:140 — <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
  • Focus outline removed inline Frontend/src/components/admin/subscription/SubscriptionActions.tsx:155 — <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
  • Focus outline removed inline Frontend/src/components/admin/subscription/SubscriptionDetials.tsx:95 — <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
  • Focus outline removed inline Frontend/src/components/admin/subscription/SubscriptionDetials.tsx:103 — <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
  • Focus outline removed inline Frontend/src/components/admin/users/UserDetialsTable.tsx:166 — <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
  • Focus outline removed inline Frontend/src/components/admin/users/UserDetialsTable.tsx:174 — <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
  • Focus outline removed inline Frontend/src/components/authentication/ForgotPasswordForm.tsx:66 — <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
  • Focus outline removed inline Frontend/src/components/authentication/ForgotPasswordForm.tsx:74 — <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
  • Focus outline removed inline Frontend/src/components/authentication/GoogleAuth.tsx:55 — <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
  • Focus outline removed inline Frontend/src/components/authentication/OtpForm.tsx:125 — <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
  • + 12 more in this group — see findings.md.
D30 · Dependency Vulnerabilities · Medium CVE · ×21
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AC1 · Text alternatives · <video> without a captions track · ×14
  • <video> without a captions track Frontend/src/components/admin/post/PostDetialsTable.tsx:157 — Video with no captions <track> offers no captions. This player's source is set at runtime, so there is no caption file to author here: give the player a way to carry captions — accept a track/captions URL alongside the media and render a <track kind="captions"> when one is supplied — and capture that asset wherever the media enters the product (upload, import or generation).
  • <video> without a captions track Frontend/src/components/admin/post/PostDetialsTable.tsx:243 — Video with no captions <track> offers no captions. This player's source is set at runtime, so there is no caption file to author here: give the player a way to carry captions — accept a track/captions URL alongside the media and render a <track kind="captions"> when one is supplied — and capture that asset wherever the media enters the product (upload, import or generation).
  • <video> without a captions track Frontend/src/components/chats/ChatDetials.tsx:359 — Video with no captions <track> offers no captions. This player's source is set at runtime, so there is no caption file to author here: give the player a way to carry captions — accept a track/captions URL alongside the media and render a <track kind="captions"> when one is supplied — and capture that asset wherever the media enters the product (upload, import or generation).
  • <video> without a captions track Frontend/src/components/chats/message-type/FileMessage.tsx:49 — Video with no captions <track> offers no captions. This player's source is set at runtime, so there is no caption file to author here: give the player a way to carry captions — accept a track/captions URL alongside the media and render a <track kind="captions"> when one is supplied — and capture that asset wherever the media enters the product (upload, import or generation).
  • <video> without a captions track Frontend/src/components/chats/message-type/SharePostMessage.tsx:116 — Video with no captions <track> offers no captions. This player's source is set at runtime, so there is no caption file to author here: give the player a way to carry captions — accept a track/captions URL alongside the media and render a <track kind="captions"> when one is supplied — and capture that asset wherever the media enters the product (upload, import or generation).
  • <video> without a captions track Frontend/src/components/common/PostViewModal/PostModal.tsx:839 — Video with no captions <track> offers no captions. This player's source is set at runtime, so there is no caption file to author here: give the player a way to carry captions — accept a track/captions URL alongside the media and render a <track kind="captions"> when one is supplied — and capture that asset wherever the media enters the product (upload, import or generation).
  • <video> without a captions track Frontend/src/components/common/StoryModal/StoryModal.tsx:105 — Video with no captions <track> offers no captions. This player's source is set at runtime, so there is no caption file to author here: give the player a way to carry captions — accept a track/captions URL alongside the media and render a <track kind="captions"> when one is supplied — and capture that asset wherever the media enters the product (upload, import or generation).
  • <video> without a captions track Frontend/src/components/common/ViewFile.tsx:23 — Video with no captions <track> offers no captions. This player's source is set at runtime, so there is no caption file to author here: give the player a way to carry captions — accept a track/captions URL alongside the media and render a <track kind="captions"> when one is supplied — and capture that asset wherever the media enters the product (upload, import or generation).
  • <video> without a captions track Frontend/src/components/create-post/ChangePost.tsx:185 — Video with no captions <track> offers no captions. This player's source is set at runtime, so there is no caption file to author here: give the player a way to carry captions — accept a track/captions URL alongside the media and render a <track kind="captions"> when one is supplied — and capture that asset wherever the media enters the product (upload, import or generation).
  • <video> without a captions track Frontend/src/components/create-post/CreatePostBody.tsx:146 — Video with no captions <track> offers no captions. This player's source is set at runtime, so there is no caption file to author here: give the player a way to carry captions — accept a track/captions URL alongside the media and render a <track kind="captions"> when one is supplied — and capture that asset wherever the media enters the product (upload, import or generation).
  • <video> without a captions track Frontend/src/components/create-post/TagUser.tsx:166 — Video with no captions <track> offers no captions. This player's source is set at runtime, so there is no caption file to author here: give the player a way to carry captions — accept a track/captions URL alongside the media and render a <track kind="captions"> when one is supplied — and capture that asset wherever the media enters the product (upload, import or generation).
  • <video> without a captions track Frontend/src/components/explore/ExploreDetials.tsx:126 — Video with no captions <track> offers no captions. This player's source is set at runtime, so there is no caption file to author here: give the player a way to carry captions — accept a track/captions URL alongside the media and render a <track kind="captions"> when one is supplied — and capture that asset wherever the media enters the product (upload, import or generation).
  • <video> without a captions track Frontend/src/components/profile/ProfilePostSection.tsx:192 — Video with no captions <track> offers no captions. This player's source is set at runtime, so there is no caption file to author here: give the player a way to carry captions — accept a track/captions URL alongside the media and render a <track kind="captions"> when one is supplied — and capture that asset wherever the media enters the product (upload, import or generation).
  • <video> without a captions track Frontend/src/components/user-profiles/UserProfilePostSection.tsx:194 — Video with no captions <track> offers no captions. This player's source is set at runtime, so there is no caption file to author here: give the player a way to carry captions — accept a track/captions URL alongside the media and render a <track kind="captions"> when one is supplied — and capture that asset wherever the media enters the product (upload, import or generation).
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D12 · Dependency Hygiene · Deprecated · ×9
  • Deprecated: uuid Backend/package.json:32 — uuid 10.0.0, declared in Backend/package.json, is marked deprecated by its publisher: "uuid@10 and below is no longer supported. For ESM codebases, update to uuid@latest. For CommonJS codebases, use uuid@11 (but be aware this version will likely be deprecated in 2028).". Replace it with the package or version that message names, or record why this one must stay.
  • Deprecated: eslint Backend/package.json:47 — eslint 9.14.0, declared in Backend/package.json, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
  • Deprecated: @fortawesome/react-fontawesome Frontend/package.json:18 — @fortawesome/react-fontawesome 0.2.2, declared in Frontend/package.json, is marked deprecated by its publisher: "v0.2.x is no longer supported. Unless you are still using FontAwesome 5, please update to v3.1.1 or greater.". Replace it with the package or version that message names, or record why this one must stay.
  • Deprecated: @nextui-org/modal Frontend/package.json:21 — @nextui-org/modal 2.0.39, declared in Frontend/package.json, is marked deprecated by its publisher: "This package has been deprecated. Please use @heroui/modal instead.". Replace it with the package or version that message names, or record why this one must stay.
  • Deprecated: @nextui-org/react Frontend/package.json:22 — @nextui-org/react 2.4.6, declared in Frontend/package.json, is marked deprecated by its publisher: "This package has been deprecated. Please use @heroui/react instead.". Replace it with the package or version that message names, or record why this one must stay.
  • Deprecated: react-beautiful-dnd Frontend/package.json:48 — react-beautiful-dnd 13.1.1, declared in Frontend/package.json, is marked deprecated by its publisher: "react-beautiful-dnd is now deprecated. Context and options: https://github.com/atlassian/react-beautiful-dnd/issues/2672". Replace it with the package or version that message names, or record why this one must stay.
  • Deprecated: recharts Frontend/package.json:56 — recharts 2.15.1, declared in Frontend/package.json, is marked deprecated by its publisher: "1.x and 2.x branches are no longer active. Bump to Recharts v3 to receive latest features and bugfixes. See https://github.com/recharts/recharts/wiki/3.0-migration-guide". Replace it with the package or version that message names, or record why this one must stay.
  • Deprecated: @types/date-fns Frontend/package.json:66 — @types/date-fns 2.6.3, declared in Frontend/package.json, is marked deprecated by its publisher: "This is a stub types definition. date-fns provides its own type definitions, so you do not need this installed.". Replace it with the package or version that message names, or record why this one must stay.
  • Deprecated: eslint Frontend/package.json:74 — eslint 9.9.1, declared in Frontend/package.json, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
X1 · Async correctness · `async` callback passed to `forEach` · ×8
  • `async` callback passed to `forEach` Backend/src/application/useCases/user/chat/sendShareMessaege.ts:29 — `forEach` ignores what its callback returns, so the Promise each `async` call returns is dropped: nothing can await it, the code after this loop runs before any of the awaited work has finished (a function that `await`s around this loop still returns early), and a rejection is never handled — in Node.js an unhandled rejection terminates the process by default, and in a browser it is lost. Iterate with `for (const item of items) { await … }` when the work must run in order, or `await Promise.all(items.map(async (item) => { … }))` when it may run concurrently, so the enclosing function finishes only when the work does and its failures reach the caller. Where firing and forgetting is genuinely intended, make the callback's whole body a `try { … } catch (e) { … }` that handles the failure, so it cannot escape.
  • `async` callback passed to `forEach` Backend/src/application/useCases/user/post/replyComment.ts:47 — `forEach` ignores what its callback returns, so the Promise each `async` call returns is dropped: nothing can await it, the code after this loop runs before any of the awaited work has finished (a function that `await`s around this loop still returns early), and a rejection is never handled — in Node.js an unhandled rejection terminates the process by default, and in a browser it is lost. Iterate with `for (const item of items) { await … }` when the work must run in order, or `await Promise.all(items.map(async (item) => { … }))` when it may run concurrently, so the enclosing function finishes only when the work does and its failures reach the caller. Where firing and forgetting is genuinely intended, make the callback's whole body a `try { … } catch (e) { … }` that handles the failure, so it cannot escape.
  • `async` callback passed to `forEach` Backend/src/application/useCases/user/post/deletePost.ts:45 — `forEach` ignores what its callback returns, so the Promise each `async` call returns is dropped: nothing can await it, the code after this loop runs before any of the awaited work has finished (a function that `await`s around this loop still returns early), and a rejection is never handled — in Node.js an unhandled rejection terminates the process by default, and in a browser it is lost. Iterate with `for (const item of items) { await … }` when the work must run in order, or `await Promise.all(items.map(async (item) => { … }))` when it may run concurrently, so the enclosing function finishes only when the work does and its failures reach the caller. Where firing and forgetting is genuinely intended, make the callback's whole body a `try { … } catch (e) { … }` that handles the failure, so it cannot escape.
  • `async` callback passed to `forEach` Backend/src/application/useCases/user/post/deleteCommentOrReply.ts:31 — `forEach` ignores what its callback returns, so the Promise each `async` call returns is dropped: nothing can await it, the code after this loop runs before any of the awaited work has finished (a function that `await`s around this loop still returns early), and a rejection is never handled — in Node.js an unhandled rejection terminates the process by default, and in a browser it is lost. Iterate with `for (const item of items) { await … }` when the work must run in order, or `await Promise.all(items.map(async (item) => { … }))` when it may run concurrently, so the enclosing function finishes only when the work does and its failures reach the caller. Where firing and forgetting is genuinely intended, make the callback's whole body a `try { … } catch (e) { … }` that handles the failure, so it cannot escape.
  • `async` callback passed to `forEach` Backend/src/application/useCases/user/post/createPost.ts:64 — `forEach` ignores what its callback returns, so the Promise each `async` call returns is dropped: nothing can await it, the code after this loop runs before any of the awaited work has finished (a function that `await`s around this loop still returns early), and a rejection is never handled — in Node.js an unhandled rejection terminates the process by default, and in a browser it is lost. Iterate with `for (const item of items) { await … }` when the work must run in order, or `await Promise.all(items.map(async (item) => { … }))` when it may run concurrently, so the enclosing function finishes only when the work does and its failures reach the caller. Where firing and forgetting is genuinely intended, make the callback's whole body a `try { … } catch (e) { … }` that handles the failure, so it cannot escape.
  • `async` callback passed to `forEach` Backend/src/application/useCases/user/post/commentPost.ts:44 — `forEach` ignores what its callback returns, so the Promise each `async` call returns is dropped: nothing can await it, the code after this loop runs before any of the awaited work has finished (a function that `await`s around this loop still returns early), and a rejection is never handled — in Node.js an unhandled rejection terminates the process by default, and in a browser it is lost. Iterate with `for (const item of items) { await … }` when the work must run in order, or `await Promise.all(items.map(async (item) => { … }))` when it may run concurrently, so the enclosing function finishes only when the work does and its failures reach the caller. Where firing and forgetting is genuinely intended, make the callback's whole body a `try { … } catch (e) { … }` that handles the failure, so it cannot escape.
  • `async` callback passed to `forEach` Frontend/src/components/common/PostViewModal/PostModal.tsx:635 — `forEach` ignores what its callback returns, so the Promise each `async` call returns is dropped: nothing can await it, the code after this loop runs before any of the awaited work has finished (a function that `await`s around this loop still returns early), and a rejection is never handled — in Node.js an unhandled rejection terminates the process by default, and in a browser it is lost. Iterate with `for (const item of items) { await … }` when the work must run in order, or `await Promise.all(items.map(async (item) => { … }))` when it may run concurrently, so the enclosing function finishes only when the work does and its failures reach the caller. Where firing and forgetting is genuinely intended, make the callback's whole body a `try { … } catch (e) { … }` that handles the failure, so it cannot escape.
  • `async` callback passed to `forEach` Frontend/src/components/home/Posts.tsx:97 — `forEach` ignores what its callback returns, so the Promise each `async` call returns is dropped: nothing can await it, the code after this loop runs before any of the awaited work has finished (a function that `await`s around this loop still returns early), and a rejection is never handled — in Node.js an unhandled rejection terminates the process by default, and in a browser it is lost. Iterate with `for (const item of items) { await … }` when the work must run in order, or `await Promise.all(items.map(async (item) => { … }))` when it may run concurrently, so the enclosing function finishes only when the work does and its failures reach the caller. Where firing and forgetting is genuinely intended, make the callback's whole body a `try { … } catch (e) { … }` that handles the failure, so it cannot escape.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
IC1 · Incompleteness & stubs · Both branches are identical · ×5
  • Both branches are identical — the condition decides nothing Frontend/src/components/chats/message-type/SharePostMessage.tsx:24 — The `if` and its `else` contain the same statements, so no input can make the condition matter. Implement the distinction that was intended, or drop the branch and keep the body.
  • Both branches are identical — the condition decides nothing Frontend/src/components/notification/NotificationDetials.tsx:139 — The `if` and its `else` contain the same statements, so no input can make the condition matter. Implement the distinction that was intended, or drop the branch and keep the body.
  • Both branches are identical — the condition decides nothing Frontend/src/components/post/PostSingle.tsx:42 — The `if` and its `else` contain the same statements, so no input can make the condition matter. Implement the distinction that was intended, or drop the branch and keep the body.
  • Both branches are identical — the condition decides nothing Frontend/src/components/reel/ReelsDetials.tsx:249 — The `if` and its `else` contain the same statements, so no input can make the condition matter. Implement the distinction that was intended, or drop the branch and keep the body.
  • Both branches are identical — the condition decides nothing Frontend/src/components/user-profiles/UserProfileDetials.tsx:94 — The `if` and its `else` contain the same statements, so no input can make the condition matter. Implement the distinction that was intended, or drop the branch and keep the body.
AC2 · Forms & labels · <Select> field component without a label · ×4
  • <Select> field component without a label Frontend/src/components/admin/music/MusicDetialsTable.tsx:258 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <Select> field component without a label Frontend/src/components/admin/post/PostDetialsTable.tsx:191 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <Select> field component without a label Frontend/src/components/admin/subscription/SubscriptionDetials.tsx:111 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <Select> field component without a label Frontend/src/components/admin/users/UserDetialsTable.tsx:182 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
AC6 · Visual & motion safety · Animation without a prefers-reduced-motion guard · ×3
  • Animation without a prefers-reduced-motion guard Frontend/src/components/calls/VideoAudioCall.tsx:347 — <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
  • Animation without a prefers-reduced-motion guard Frontend/src/components/calls/VideoAudioCall.tsx:418 — <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
  • Animation without a prefers-reduced-motion guard Frontend/src/components/chats/AudioRecoding.tsx:143 — <div> moves — its inline style sets `transition: width 100ms linear` — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
AC2 · Forms & labels · <Slider> field component without a label · ×2
  • <Slider> field component without a label Frontend/src/components/admin/music/AddMusicForm.tsx:341 — This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <Slider> field component without a label Frontend/src/components/admin/music/MusicDetialsTable.tsx:343 — This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
D30 · Dependency Vulnerabilities · Medium vulnerability · ×2
  • REDACTED
  • REDACTED
R10 · Code Duplication · Duplicated block (41 lines × 2 locations) · ×2
  • Duplicated block (41 lines × 2 locations) Frontend/src/components/admin/music/AddMusicForm.tsx:264 — Frontend/src/components/admin/music/AddMusicForm.tsx:264 · Frontend/src/components/admin/music/MusicAction.tsx:162 — 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 (41 lines × 2 locations) Frontend/src/components/ui/dropdown-menu.tsx:21 — Frontend/src/components/ui/dropdown-menu.tsx:21 · Frontend/src/components/ui/menubar.tsx:49 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of MODULE-LEVEL DECLARATIONS — bindings the module declares and exports — rather than statements with a call site. Do not read this as an extract-a-helper row: a call expression cannot stand where a declaration was, and putting one there would delete the names themselves, which are what the rest of the codebase imports. What actually repeats here is the INITIALISER — the same expression shape written once per binding. So give that expression one name (a small helper the initialisers call, or a shared base value they are each derived from) and keep every binding under the name it already has. Where the run is an enumeration — one binding per distinct thing, differing precisely in the thing each one names — the repetition IS the enumeration and collapsing it would delete entries; consider instead whether the set belongs in one exported table the individual names are read out of. Reported because the copies drift apart the first time only one of them is edited.
R10 · Code Duplication · Duplicated block with local edits (38 matched lines × 2 locations) · ×2
  • Duplicated block with local edits (38 matched lines × 2 locations) Frontend/src/components/common/PostViewModal/PostReportModal.tsx:39 — Frontend/src/components/common/PostViewModal/PostReportModal.tsx:39 · Frontend/src/components/common/PostViewModal/PostShareModal.tsx:22 — the two spans are one implementation copied and then locally edited — 162 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 (38 matched lines × 2 locations) Frontend/src/components/profile/ProfileDetials.tsx:39 — Frontend/src/components/profile/ProfileDetials.tsx:39 · Frontend/src/components/user-profiles/UserProfileDetials.tsx:138 — the two spans are one implementation copied and then locally edited — 227 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 (33 lines × 2 locations) · ×2
  • Duplicated block (33 lines × 2 locations) Frontend/src/components/admin/post/PostDetialsTable.tsx:92 — Frontend/src/components/admin/post/PostDetialsTable.tsx:92 · Frontend/src/components/admin/users/UserDetialsTable.tsx:60 — 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 (33 lines × 2 locations) Frontend/src/components/admin/profile/AdminProfileDetials.tsx:35 — Frontend/src/components/admin/profile/AdminProfileDetials.tsx:35 · Frontend/src/components/profile/EditProfileForm.tsx:51 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R10 · Code Duplication · Duplicated block (32 lines × 2 locations) · ×2
  • Duplicated block (32 lines × 2 locations) Frontend/src/components/admin/authentication/SignInForm.tsx:59 — Frontend/src/components/admin/authentication/SignInForm.tsx:59 · Frontend/src/components/authentication/SignInForm.tsx:61 — 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 (32 lines × 2 locations) Frontend/src/components/common/PostViewModal/PostEditModal.tsx:163 — Frontend/src/components/common/PostViewModal/PostEditModal.tsx:163 · Frontend/src/components/common/PostViewModal/PostEditModal.tsx:200 — 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 (31 lines × 2 locations) · ×2
  • Duplicated block (31 lines × 2 locations) Backend/src/infrastructure/database/models/postModel.ts:29 — Backend/src/infrastructure/database/models/postModel.ts:29 · Backend/src/infrastructure/database/models/storyModal.ts:24 — the 2 copies are spread across 2 files, and what repeats is a LIST OF ENTRIES rather than behaviour — the same entries written out more than once. Extract them into one shared, exported constant and spread that constant into each site, rather than into a function the sites call: a list like this often lives in declarative metadata (a decorator's options object, a static configuration table) that a build step must be able to read statically, where a function call is not allowed. Adding an entry to one copy and not the other is the failure this prevents.
  • Duplicated block (31 lines × 2 locations) Frontend/src/components/common/PostViewModal/PostModal.tsx:338 — Frontend/src/components/common/PostViewModal/PostModal.tsx:338 · Frontend/src/helperFuntions/dateFormat.ts:1 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R10 · Code Duplication · Duplicated block with local edits (30 matched lines × 2 locations) · ×2
  • Duplicated block with local edits (30 matched lines × 2 locations) Backend/src/application/useCases/user/post/explorePost.ts:6 — Backend/src/application/useCases/user/post/explorePost.ts:6 · Backend/src/application/useCases/user/post/filterReels.ts:7 — the two spans are one implementation copied and then locally edited — 299 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 (30 matched lines × 2 locations) Backend/src/infrastructure/middlewares/adminAuthMiddleware.ts:6 — Backend/src/infrastructure/middlewares/adminAuthMiddleware.ts:6 · Backend/src/infrastructure/middlewares/authMiddleware.ts:8 — the two spans are one implementation copied and then locally edited — 237 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.
X24 · Document value interpolated into markup unescaped · Untrusted text written into markup unescaped · ×2
  • Untrusted text written into markup unescaped Frontend/src/components/profile/ProfileDetials.tsx:88 — `(userData?.bio??"").replace(/\n/g,"<br />")` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped Frontend/src/components/user-profiles/UserProfileDetials.tsx:215 — `(userData?.bio??"").replace(/\n/g,"<br />")` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
AC3 · Page structure · Page without a main landmark · ×1
  • Page without a main landmark Frontend/index.html:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="root">, so there is no content here to wrap — render the <main> from the component mounted into it.
AC7 · A11y enforcement · Accessibility enforcement below the top rung · ×1
  • Accessibility enforcement below the top rung — No accessibility enforcement found — no a11y linter (eslint-plugin-jsx-a11y) 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 132 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.
D1 · Cyclomatic Complexity · PostModal.PostModal (cyclomatic 165) · ×1
  • PostModal.PostModal (cyclomatic 165) Frontend/src/components/common/PostViewModal/PostModal.tsx:56 — PostModal.PostModal has cyclomatic complexity 165 (threshold 15). Of this number, 36 points are the body's own statements and 129 belong to 42 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · VideoAudioCall.VideoAudioCall (cyclomatic 68) · ×1
  • VideoAudioCall.VideoAudioCall (cyclomatic 68) Frontend/src/components/calls/VideoAudioCall.tsx:15 — VideoAudioCall.VideoAudioCall has cyclomatic complexity 68 (threshold 15). Of this number, 32 points are the body's own statements and 36 belong to 20 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · ChatInbox.ChatsInbox (cyclomatic 66) · ×1
  • ChatInbox.ChatsInbox (cyclomatic 66) Frontend/src/components/chats/ChatInbox.tsx:26 — ChatInbox.ChatsInbox has cyclomatic complexity 66 (threshold 15). Of this number, 22 points are the body's own statements and 44 belong to 9 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · Posts.Posts (cyclomatic 63) · ×1
  • Posts.Posts (cyclomatic 63) Frontend/src/components/home/Posts.tsx:21 — Posts.Posts has cyclomatic complexity 63 (threshold 15). Most of this is not in the body itself: 4 of the 63 points are its own statements and the rest belongs to 18 function items inside it that branch (a function literal at line 274, a function literal at line 97, fetchPostData, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · FollowDetialsModal.FollowDetialsModal (cyclomatic 62) · ×1
  • FollowDetialsModal.FollowDetialsModal (cyclomatic 62) Frontend/src/components/common/FollowDetialsModal.tsx:11 — FollowDetialsModal.FollowDetialsModal has cyclomatic complexity 62 (threshold 15). Most of this is not in the body itself: 3 of the 62 points are its own statements and the rest belongs to 12 function items inside it that branch (a function literal at line 135, a function literal at line 19, handleUnfollow, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · ChatDetials.ChatDetials (cyclomatic 61) · ×1
  • ChatDetials.ChatDetials (cyclomatic 61) Frontend/src/components/chats/ChatDetials.tsx:26 — ChatDetials.ChatDetials has cyclomatic complexity 61 (threshold 15). Of this number, 19 points are the body's own statements and 42 belong to 14 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · ReelsDetials.ReelsDetials (cyclomatic 56) · ×1
  • ReelsDetials.ReelsDetials (cyclomatic 56) Frontend/src/components/reel/ReelsDetials.tsx:20 — ReelsDetials.ReelsDetials has cyclomatic complexity 56 (threshold 15). Most of this is not in the body itself: 3 of the 56 points are its own statements and the rest belongs to 18 function items inside it that branch (a function literal at line 290, a function literal at line 158, fetchReels, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · NotificationDetials.NotificationDetials (cyclomatic 47) · ×1
  • NotificationDetials.NotificationDetials (cyclomatic 47) Frontend/src/components/notification/NotificationDetials.tsx:23 — NotificationDetials.NotificationDetials has cyclomatic complexity 47 (threshold 15). Most of this is not in the body itself: 12 of the 47 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 169, handleFollow, renderNotifications, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · CreatePostBody.CreatePostBody (cyclomatic 45) · ×1
  • CreatePostBody.CreatePostBody (cyclomatic 45) Frontend/src/components/create-post/CreatePostBody.tsx:20 — CreatePostBody.CreatePostBody has cyclomatic complexity 45 (threshold 15). Of this number, 37 points are the body's own statements and 8 belong to 5 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · PostDetialsTable.PostDetialsTable (cyclomatic 38) · ×1
  • PostDetialsTable.PostDetialsTable (cyclomatic 38) Frontend/src/components/admin/post/PostDetialsTable.tsx:31 — PostDetialsTable.PostDetialsTable has cyclomatic complexity 38 (threshold 15). Most of this is not in the body itself: 9 of the 38 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 48, a function literal at line 144, a function literal at line 232, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · SearchDetials.SearchDetials (cyclomatic 38) · ×1
  • SearchDetials.SearchDetials (cyclomatic 38) Frontend/src/components/search/SearchDetials.tsx:13 — SearchDetials.SearchDetials has cyclomatic complexity 38 (threshold 15). Most of this is not in the body itself: 4 of the 38 points are its own statements and the rest belongs to 8 function items inside it that branch (fetchSearchHistory, fetchSearchData, handleClickSeach, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · UserProfileDetials.UserProfileDetials (cyclomatic 37) · ×1
  • UserProfileDetials.UserProfileDetials (cyclomatic 37) Frontend/src/components/user-profiles/UserProfileDetials.tsx:19 — UserProfileDetials.UserProfileDetials has cyclomatic complexity 37 (threshold 15). Of this number, 16 points are the body's own statements and 21 belong to 8 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · MusicDetialsTable.MusicDetialsTable (cyclomatic 36) · ×1
  • MusicDetialsTable.MusicDetialsTable (cyclomatic 36) Frontend/src/components/admin/music/MusicDetialsTable.tsx:28 — MusicDetialsTable.MusicDetialsTable has cyclomatic complexity 36 (threshold 15). Most of this is not in the body itself: 9 of the 36 points are its own statements and the rest belongs to 13 function items inside it that branch (a function literal at line 296, a function literal at line 50, handlePlayPause, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · createRoutes.createRoutes (cyclomatic 34) · ×1
  • createRoutes.createRoutes (cyclomatic 34) Frontend/src/routes/createRoutes.tsx:35 — createRoutes.createRoutes has cyclomatic complexity 34 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · ChangePost.ChangePost (cyclomatic 34) · ×1
  • ChangePost.ChangePost (cyclomatic 34) Frontend/src/components/create-post/ChangePost.tsx:26 — ChangePost.ChangePost has cyclomatic complexity 34 (threshold 15). Most of this is not in the body itself: 15 of the 34 points are its own statements and the rest belongs to 5 function items inside it that branch (handleInputChange, a function literal at line 151, handleCroppedImage, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · AddMusicForm.AddMusicForm (cyclomatic 31) · ×1
  • AddMusicForm.AddMusicForm (cyclomatic 31) Frontend/src/components/admin/music/AddMusicForm.tsx:19 — AddMusicForm.AddMusicForm has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 1 of the 31 points is its own statement and the rest belongs to 11 function items inside it that branch (handleSubmit, a function literal at line 267, handleFileChange, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · ProfilePostSection.ProfilePostSection (cyclomatic 31) · ×1
  • ProfilePostSection.ProfilePostSection (cyclomatic 31) Frontend/src/components/profile/ProfilePostSection.tsx:26 — ProfilePostSection.ProfilePostSection has cyclomatic complexity 31 (threshold 15). Of this number, 19 points are the body's own statements and 12 belong to 4 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · UserDetialsTable.UserDetialsTable (cyclomatic 30) · ×1
  • UserDetialsTable.UserDetialsTable (cyclomatic 30) Frontend/src/components/admin/users/UserDetialsTable.tsx:32 — UserDetialsTable.UserDetialsTable has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 9 of the 30 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 49, a function literal at line 221, handleAction, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · Sidebar.Sidebar (cyclomatic 30) · ×1
  • Sidebar.Sidebar (cyclomatic 30) Frontend/src/components/common/Sidebar.tsx:56 — Sidebar.Sidebar has cyclomatic complexity 30 (threshold 15). Of this number, 19 points are the body's own statements and 11 belong to 5 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · CreatePostFilters.CreatePostFilters (cyclomatic 29) · ×1
  • CreatePostFilters.CreatePostFilters (cyclomatic 29) Frontend/src/components/create-post/CreatePostFilters.tsx:16 — CreatePostFilters.CreatePostFilters has cyclomatic complexity 29 (threshold 15). Of this number, 27 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · TagUser.TagUser (cyclomatic 29) · ×1
  • TagUser.TagUser (cyclomatic 29) Frontend/src/components/create-post/TagUser.tsx:26 — TagUser.TagUser has cyclomatic complexity 29 (threshold 15). Of this number, 16 points are the body's own statements and 13 belong to 8 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · AdminProfileDetials.AdminProfileDetails (cyclomatic 28) · ×1
  • AdminProfileDetials.AdminProfileDetails (cyclomatic 28) Frontend/src/components/admin/profile/AdminProfileDetials.tsx:11 — AdminProfileDetials.AdminProfileDetails has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 12 of the 28 points are its own statements and the rest belongs to 4 function items inside it that branch (handleSubmit, handleProfileUpload, handleChangePassword, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · CreatePostFormSubmit.CreatePostFormSubmit (cyclomatic 26) · ×1
  • CreatePostFormSubmit.CreatePostFormSubmit (cyclomatic 26) Frontend/src/components/create-post/CreatePostFormSubmit.tsx:13 — CreatePostFormSubmit.CreatePostFormSubmit has cyclomatic complexity 26 (threshold 15). Of this number, 15 points are the body's own statements and 11 belong to 3 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · CreatePostMusic.CreatePostMusic (cyclomatic 25) · ×1
  • CreatePostMusic.CreatePostMusic (cyclomatic 25) Frontend/src/components/create-post/CreatePostMusic.tsx:16 — CreatePostMusic.CreatePostMusic has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 9 of the 25 points are its own statements and the rest belongs to 6 function items inside it that branch (handlePlayPause, fetchMusic, a function literal at line 99, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · MusicAction.MusicAction (cyclomatic 24) · ×1
  • MusicAction.MusicAction (cyclomatic 24) Frontend/src/components/admin/music/MusicAction.tsx:28 — MusicAction.MusicAction has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 2 of the 24 points are its own statements and the rest belongs to 6 function items inside it that branch (handleSubmit, handleAction, handleImageUpload, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · OtpForm.Otp (cyclomatic 24) · ×1
  • OtpForm.Otp (cyclomatic 24) Frontend/src/components/authentication/OtpForm.tsx:11 — OtpForm.Otp has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 11 of the 24 points are its own statements and the rest belongs to 4 function items inside it that branch (handleFormSubmit, handleResend, a function literal at line 19, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · FriendSuggetion.FriendSuggetion (cyclomatic 24) · ×1
  • FriendSuggetion.FriendSuggetion (cyclomatic 24) Frontend/src/components/common/FriendSuggetion.tsx:9 — FriendSuggetion.FriendSuggetion has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 2 of the 24 points are its own statements and the rest belongs to 7 function items inside it that branch (handleFollow, handleUnfollow, a function literal at line 80, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · SelectAspectRatio.SelectAspectRatioAndUplaod · ×1
  • SelectAspectRatio.SelectAspectRatioAndUplaod::handleInputChange (cyclomatic 24) Frontend/src/components/create-post/SelectAspectRatio.tsx:95 — SelectAspectRatio.SelectAspectRatioAndUplaod::handleInputChange has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · CallModal.CallModal (cyclomatic 23) · ×1
  • CallModal.CallModal (cyclomatic 23) Frontend/src/components/calls/CallModal.tsx:16 — CallModal.CallModal has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 9 of the 23 points are its own statements and the rest belongs to 6 function items inside it that branch (fetchUserData, fetchChatData, a function literal at line 59, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · ExploreDetials.ExploreDetials (cyclomatic 23) · ×1
  • ExploreDetials.ExploreDetials (cyclomatic 23) Frontend/src/components/explore/ExploreDetials.tsx:12 — ExploreDetials.ExploreDetials has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 4 of the 23 points are its own statements and the rest belongs to 7 function items inside it that branch (fetchPostData, a function literal at line 94, a function literal at line 45, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · EditProfileForm.EditProfileForm (cyclomatic 22) · ×1
  • EditProfileForm.EditProfileForm (cyclomatic 22) Frontend/src/components/profile/EditProfileForm.tsx:21 — EditProfileForm.EditProfileForm has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 7 of the 22 points are its own statements and the rest belongs to 4 function items inside it that branch (handleFormSubmit, handleProfileUpload, a function literal at line 105, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · UserProfilePostSection.UserProfilePostSection (cyclomatic 22) · ×1
  • UserProfilePostSection.UserProfilePostSection (cyclomatic 22) Frontend/src/components/user-profiles/UserProfilePostSection.tsx:19 — UserProfilePostSection.UserProfilePostSection has cyclomatic complexity 22 (threshold 15). Of this number, 11 points are the body's own statements and 11 belong to 5 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · SubscriptionDetials.SubscriptionDetials (cyclomatic 21) · ×1
  • SubscriptionDetials.SubscriptionDetials (cyclomatic 21) Frontend/src/components/admin/subscription/SubscriptionDetials.tsx:19 — SubscriptionDetials.SubscriptionDetials has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 9 of the 21 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 48, a function literal at line 149, a function literal at line 32, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · VerificationContent.VerificationContent (cyclomatic 19) · ×1
  • VerificationContent.VerificationContent (cyclomatic 19) Frontend/src/components/verification/VerificationContent.tsx:11 — VerificationContent.VerificationContent has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 3 of the 19 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 18, handlePayment, a function literal at line 76, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · sendMessage.execute (cyclomatic 17) · ×1
  • sendMessage.execute (cyclomatic 17) Backend/src/application/useCases/user/chat/sendMessage.ts:18 — sendMessage.execute has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · AudioRecoding.AudioRecorder (cyclomatic 17) · ×1
  • AudioRecoding.AudioRecorder (cyclomatic 17) Frontend/src/components/chats/AudioRecoding.tsx:5 — AudioRecoding.AudioRecorder has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 7 of the 17 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 23, stopRecording, a function literal at line 50, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · PostModalActions.PostModalActions (cyclomatic 17) · ×1
  • PostModalActions.PostModalActions (cyclomatic 17) Frontend/src/components/common/PostViewModal/PostModalActions.tsx:12 — PostModalActions.PostModalActions has cyclomatic complexity 17 (threshold 15). Of this number, 9 points are the body's own statements and 8 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · Sidebar.Sidebar (cyclomatic 16) · ×1
  • Sidebar.Sidebar (cyclomatic 16) Frontend/src/components/admin/common/Sidebar.tsx:39 — Sidebar.Sidebar has cyclomatic complexity 16 (threshold 15). Of this number, 11 points are the body's own statements and 5 belong to 2 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · SubscriptionActions.SubscriptionActions (cyclomatic 16) · ×1
  • SubscriptionActions.SubscriptionActions (cyclomatic 16) Frontend/src/components/admin/subscription/SubscriptionActions.tsx:29 — SubscriptionActions.SubscriptionActions has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 2 of the 16 points are its own statements and the rest belongs to 4 function items inside it that branch (handleAction, handleSubmit, a function literal at line 115, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · PostEditModal.PostEditModal (cyclomatic 16) · ×1
  • PostEditModal.PostEditModal (cyclomatic 16) Frontend/src/components/common/PostViewModal/PostEditModal.tsx:13 — PostEditModal.PostEditModal has cyclomatic complexity 16 (threshold 15). Of this number, 9 points are the body's own statements and 7 belong to 3 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · ChatInbox.ChatsInbox (cognitive 116) · ×1
  • ChatInbox.ChatsInbox (cognitive 116) Frontend/src/components/chats/ChatInbox.tsx:26 — ChatInbox.ChatsInbox has cognitive complexity 116 (threshold 15). Drivers by points: ternaries 27 (71 pts), if/else 17 (24 pts), boolean chains 18, error handling 3 (nesting depth added 51). Of this number, 32 points are the body's own statements and 84 belong to 9 function items inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · VideoAudioCall.VideoAudioCall (cognitive 95) · ×1
  • VideoAudioCall.VideoAudioCall (cognitive 95) Frontend/src/components/calls/VideoAudioCall.tsx:15 — VideoAudioCall.VideoAudioCall has cognitive complexity 95 (threshold 15). Drivers by points: if/else 30 (40 pts), ternaries 13 (36 pts), boolean chains 18, error handling 1 (nesting depth added 33). Of this number, 46 points are the body's own statements and 49 belong to 20 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Posts.Posts (cognitive 92) · ×1
  • Posts.Posts (cognitive 92) Frontend/src/components/home/Posts.tsx:21 — Posts.Posts has cognitive complexity 92 (threshold 15). Drivers by points: if/else 37 (52 pts), boolean chains 22, ternaries 9 (15 pts), error handling 3 (nesting depth added 21). Most of this is not in the body itself: 3 of the 92 points are its own statements and the rest belongs to 18 function items inside it that branch (a function literal at line 97, a function literal at line 274, fetchPostData, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · ReelsDetials.ReelsDetials (cognitive 74) · ×1
  • ReelsDetials.ReelsDetials (cognitive 74) Frontend/src/components/reel/ReelsDetials.tsx:20 — ReelsDetials.ReelsDetials has cognitive complexity 74 (threshold 15). Drivers by points: if/else 37 (47 pts), boolean chains 17, ternaries 7 (8 pts), error handling 2 (nesting depth added 11). Most of this is not in the body itself: 2 of the 74 points are its own statements and the rest belongs to 18 function items inside it that branch (a function literal at line 158, a function literal at line 290, a function literal at line 127, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · ChatDetials.ChatDetials (cognitive 66) · ×1
  • ChatDetials.ChatDetials (cognitive 66) Frontend/src/components/chats/ChatDetials.tsx:26 — ChatDetials.ChatDetials has cognitive complexity 66 (threshold 15). Drivers by points: if/else 20 (27 pts), ternaries 10 (18 pts), boolean chains 17, error handling 2 (3 pts), loops 1 (nesting depth added 16). Of this number, 22 points are the body's own statements and 44 belong to 14 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FollowDetialsModal.FollowDetialsModal (cognitive 53) · ×1
  • FollowDetialsModal.FollowDetialsModal (cognitive 53) Frontend/src/components/common/FollowDetialsModal.tsx:11 — FollowDetialsModal.FollowDetialsModal has cognitive complexity 53 (threshold 15). Drivers by points: boolean chains 22, if/else 14 (19 pts), ternaries 6 (7 pts), error handling 5 (nesting depth added 6). Most of this is not in the body itself: 2 of the 53 points are its own statements and the rest belongs to 12 function items inside it that branch (a function literal at line 19, handleUnfollow, handleFollow, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · ProfilePostSection.ProfilePostSection (cognitive 52) · ×1
  • ProfilePostSection.ProfilePostSection (cognitive 52) Frontend/src/components/profile/ProfilePostSection.tsx:26 — ProfilePostSection.ProfilePostSection has cognitive complexity 52 (threshold 15). Drivers by points: ternaries 13 (35 pts), if/else 8 (9 pts), boolean chains 8 (nesting depth added 23). Of this number, 37 points are the body's own statements and 15 belong to 4 function items inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · SearchDetials.SearchDetials (cognitive 48) · ×1
  • SearchDetials.SearchDetials (cognitive 48) Frontend/src/components/search/SearchDetials.tsx:13 — SearchDetials.SearchDetials has cognitive complexity 48 (threshold 15). Drivers by points: boolean chains 21, if/else 15 (21 pts), error handling 5, ternaries 1 (nesting depth added 6). Most of this is not in the body itself: 3 of the 48 points are its own statements and the rest belongs to 8 function items inside it that branch (fetchSearchHistory, fetchSearchData, handleClickSeach, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · AddMusicForm.AddMusicForm (cognitive 41) · ×1
  • AddMusicForm.AddMusicForm (cognitive 41) Frontend/src/components/admin/music/AddMusicForm.tsx:19 — AddMusicForm.AddMusicForm has cognitive complexity 41 (threshold 15). Drivers by points: if/else 21 (28 pts), boolean chains 6, ternaries 5 (6 pts), error handling 1 (nesting depth added 8). None of this is in the body itself: all 41 points belong to 11 function items inside it that branch (handleSubmit, handleFileChange, handleImageUpload, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · MusicDetialsTable.MusicDetialsTable (cognitive 41) · ×1
  • MusicDetialsTable.MusicDetialsTable (cognitive 41) Frontend/src/components/admin/music/MusicDetialsTable.tsx:28 — MusicDetialsTable.MusicDetialsTable has cognitive complexity 41 (threshold 15). Drivers by points: if/else 13 (18 pts), ternaries 10 (15 pts), boolean chains 7, error handling 1 (nesting depth added 10). Most of this is not in the body itself: 8 of the 41 points are its own statements and the rest belongs to 13 function items inside it that branch (handlePlayPause, a function literal at line 296, a function literal at line 81, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · PostDetialsTable.PostDetialsTable (cognitive 41) · ×1
  • PostDetialsTable.PostDetialsTable (cognitive 41) Frontend/src/components/admin/post/PostDetialsTable.tsx:31 — PostDetialsTable.PostDetialsTable has cognitive complexity 41 (threshold 15). Drivers by points: ternaries 11 (17 pts), if/else 14 (16 pts), boolean chains 7, error handling 1 (nesting depth added 8). Most of this is not in the body itself: 8 of the 41 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 48, a function literal at line 144, a function literal at line 232, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · CreatePostBody.CreatePostBody (cognitive 40) · ×1
  • CreatePostBody.CreatePostBody (cognitive 40) Frontend/src/components/create-post/CreatePostBody.tsx:20 — CreatePostBody.CreatePostBody has cognitive complexity 40 (threshold 15). Drivers by points: boolean chains 20, ternaries 9 (12 pts), if/else 6 (7 pts), error handling 1 (nesting depth added 4). Of this number, 30 points are the body's own statements and 10 belong to 5 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · NotificationDetials.NotificationDetials (cognitive 40) · ×1
  • NotificationDetials.NotificationDetials (cognitive 40) Frontend/src/components/notification/NotificationDetials.tsx:23 — NotificationDetials.NotificationDetials has cognitive complexity 40 (threshold 15). Drivers by points: boolean chains 19, if/else 17 (19 pts), error handling 2 (nesting depth added 2). Most of this is not in the body itself: 7 of the 40 points are its own statements and the rest belongs to 8 function items inside it that branch (handleFollow, fetchNotificationData, renderNotifications, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · CreatePostFormSubmit.CreatePostFormSubmit (cognitive 39) · ×1
  • CreatePostFormSubmit.CreatePostFormSubmit (cognitive 39) Frontend/src/components/create-post/CreatePostFormSubmit.tsx:13 — CreatePostFormSubmit.CreatePostFormSubmit has cognitive complexity 39 (threshold 15). Drivers by points: ternaries 15 (32 pts), if/else 4, boolean chains 2, error handling 1 (nesting depth added 17). Of this number, 18 points are the body's own statements and 21 belong to 3 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SelectAspectRatio.SelectAspectRatioAndUplaod · ×1
  • SelectAspectRatio.SelectAspectRatioAndUplaod::handleInputChange (cognitive 39) Frontend/src/components/create-post/SelectAspectRatio.tsx:95 — SelectAspectRatio.SelectAspectRatioAndUplaod::handleInputChange has cognitive complexity 39 (threshold 15). Drivers by points: if/else 11 (17 pts), ternaries 4 (12 pts), boolean chains 10 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CreatePostMusic.CreatePostMusic (cognitive 37) · ×1
  • CreatePostMusic.CreatePostMusic (cognitive 37) Frontend/src/components/create-post/CreatePostMusic.tsx:16 — CreatePostMusic.CreatePostMusic has cognitive complexity 37 (threshold 15). Drivers by points: if/else 14 (22 pts), boolean chains 8, ternaries 3 (6 pts), error handling 1 (nesting depth added 11). Most of this is not in the body itself: 8 of the 37 points are its own statements and the rest belongs to 6 function items inside it that branch (handlePlayPause, a function literal at line 99, fetchMusic, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · UserProfilePostSection.UserProfilePostSection (cognitive 36) · ×1
  • UserProfilePostSection.UserProfilePostSection (cognitive 36) Frontend/src/components/user-profiles/UserProfilePostSection.tsx:19 — UserProfilePostSection.UserProfilePostSection has cognitive complexity 36 (threshold 15). Drivers by points: ternaries 8 (19 pts), if/else 8 (10 pts), boolean chains 7 (nesting depth added 13). Of this number, 19 points are the body's own statements and 17 belong to 5 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · UserProfileDetials.UserProfileDetials (cognitive 36) · ×1
  • UserProfileDetials.UserProfileDetials (cognitive 36) Frontend/src/components/user-profiles/UserProfileDetials.tsx:19 — UserProfileDetials.UserProfileDetials has cognitive complexity 36 (threshold 15). Drivers by points: if/else 15 (19 pts), boolean chains 14, error handling 3 (nesting depth added 4). Most of this is not in the body itself: 8 of the 36 points are its own statements and the rest belongs to 8 function items inside it that branch (handleMessageBtn, fetchUserData, handleFollowUser, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · ChangePost.ChangePost (cognitive 35) · ×1
  • ChangePost.ChangePost (cognitive 35) Frontend/src/components/create-post/ChangePost.tsx:26 — ChangePost.ChangePost has cognitive complexity 35 (threshold 15). Drivers by points: boolean chains 13, if/else 9 (12 pts), ternaries 5 (9 pts), error handling 1 (nesting depth added 7). Most of this is not in the body itself: 9 of the 35 points are its own statements and the rest belongs to 5 function items inside it that branch (handleInputChange, a function literal at line 151, handleCroppedImage, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · AdminProfileDetials.AdminProfileDetails (cognitive 34) · ×1
  • AdminProfileDetials.AdminProfileDetails (cognitive 34) Frontend/src/components/admin/profile/AdminProfileDetials.tsx:11 — AdminProfileDetials.AdminProfileDetails has cognitive complexity 34 (threshold 15). Drivers by points: ternaries 10 (13 pts), if/else 9 (12 pts), boolean chains 8, error handling 1 (nesting depth added 6). Most of this is not in the body itself: 9 of the 34 points are its own statements and the rest belongs to 4 function items inside it that branch (handleChangePassword, handleProfileUpload, handleSubmit, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · CallModal.CallModal (cognitive 34) · ×1
  • CallModal.CallModal (cognitive 34) Frontend/src/components/calls/CallModal.tsx:16 — CallModal.CallModal has cognitive complexity 34 (threshold 15). Drivers by points: if/else 14 (18 pts), ternaries 6 (8 pts), boolean chains 6, error handling 2 (nesting depth added 6). Most of this is not in the body itself: 10 of the 34 points are its own statements and the rest belongs to 6 function items inside it that branch (fetchUserData, fetchChatData, a function literal at line 59, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · Sidebar.Sidebar (cognitive 34) · ×1
  • Sidebar.Sidebar (cognitive 34) Frontend/src/components/common/Sidebar.tsx:56 — Sidebar.Sidebar has cognitive complexity 34 (threshold 15). Drivers by points: boolean chains 14, if/else 7 (9 pts), ternaries 9, error handling 2 (nesting depth added 2). Of this number, 18 points are the body's own statements and 16 belong to 5 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · createRoutes.createRoutes (cognitive 33) · ×1
  • createRoutes.createRoutes (cognitive 33) Frontend/src/routes/createRoutes.tsx:35 — createRoutes.createRoutes has cognitive complexity 33 (threshold 15). Drivers by points: ternaries 33. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · UserDetialsTable.UserDetialsTable (cognitive 33) · ×1
  • UserDetialsTable.UserDetialsTable (cognitive 33) Frontend/src/components/admin/users/UserDetialsTable.tsx:32 — UserDetialsTable.UserDetialsTable has cognitive complexity 33 (threshold 15). Drivers by points: ternaries 13 (21 pts), if/else 6, boolean chains 4, error handling 2 (nesting depth added 8). Most of this is not in the body itself: 8 of the 33 points are its own statements and the rest belongs to 10 function items inside it that branch (handleAction, a function literal at line 221, a function literal at line 49, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · FriendSuggetion.FriendSuggetion (cognitive 33) · ×1
  • FriendSuggetion.FriendSuggetion (cognitive 33) Frontend/src/components/common/FriendSuggetion.tsx:9 — FriendSuggetion.FriendSuggetion has cognitive complexity 33 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 11, ternaries 5 (7 pts), error handling 3 (nesting depth added 6). Most of this is not in the body itself: 1 of the 33 points is its own statement and the rest belongs to 7 function items inside it that branch (handleFollow, handleUnfollow, a function literal at line 15, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · MusicAction.MusicAction (cognitive 30) · ×1
  • MusicAction.MusicAction (cognitive 30) Frontend/src/components/admin/music/MusicAction.tsx:28 — MusicAction.MusicAction has cognitive complexity 30 (threshold 15). Drivers by points: if/else 13 (16 pts), boolean chains 6, ternaries 5 (6 pts), error handling 2 (nesting depth added 4). Most of this is not in the body itself: 1 of the 30 points is its own statement and the rest belongs to 6 function items inside it that branch (handleSubmit, handleImageUpload, handleAction, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · PostModal.PostModal (cognitive 30) · ×1
  • PostModal.PostModal (cognitive 30) Frontend/src/components/common/PostViewModal/PostModal.tsx:56 — PostModal.PostModal has cognitive complexity 30 (threshold 15). Drivers by points: if/else 75 (93 pts), boolean chains 64, ternaries 20 (29 pts), error handling 8 (9 pts) (nesting depth added 28). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level. This shape REPEATS in the file: one other method here (PostModal.PostModal::timeSince) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · OtpForm.Otp (cognitive 27) · ×1
  • OtpForm.Otp (cognitive 27) Frontend/src/components/authentication/OtpForm.tsx:11 — OtpForm.Otp has cognitive complexity 27 (threshold 15). Drivers by points: if/else 8 (10 pts), ternaries 9, boolean chains 6, error handling 2 (nesting depth added 2). Most of this is not in the body itself: 10 of the 27 points are its own statements and the rest belongs to 4 function items inside it that branch (handleFormSubmit, handleResend, a function literal at line 19, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · ExploreDetials.ExploreDetials (cognitive 27) · ×1
  • ExploreDetials.ExploreDetials (cognitive 27) Frontend/src/components/explore/ExploreDetials.tsx:12 — ExploreDetials.ExploreDetials has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 12, error handling 1, ternaries 1 (nesting depth added 2). Most of this is not in the body itself: 3 of the 27 points are its own statements and the rest belongs to 7 function items inside it that branch (fetchPostData, a function literal at line 45, a function literal at line 94, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · EditProfileForm.EditProfileForm (cognitive 26) · ×1
  • EditProfileForm.EditProfileForm (cognitive 26) Frontend/src/components/profile/EditProfileForm.tsx:21 — EditProfileForm.EditProfileForm has cognitive complexity 26 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 9, ternaries 3, error handling 1 (nesting depth added 3). Most of this is not in the body itself: 6 of the 26 points are its own statements and the rest belongs to 4 function items inside it that branch (handleFormSubmit, handleProfileUpload, a function literal at line 105, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · UserPostData.execute (cognitive 25) · ×1
  • UserPostData.execute (cognitive 25) Backend/src/application/useCases/user/post/userPostData.ts:20 — UserPostData.execute has cognitive complexity 25 (threshold 15). Drivers by points: if/else 5 (14 pts), loops 4 (10 pts), boolean chains 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TagUser.TagUser (cognitive 24) · ×1
  • TagUser.TagUser (cognitive 24) Frontend/src/components/create-post/TagUser.tsx:26 — TagUser.TagUser has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 10, if/else 7, ternaries 5, error handling 2. Of this number, 12 points are the body's own statements and 12 belong to 8 function items inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · FollowUser.execute (cognitive 22) · ×1
  • FollowUser.execute (cognitive 22) Backend/src/application/useCases/user/user/followUser.ts:21 — FollowUser.execute has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (15 pts), ternaries 2 (7 pts) (nesting depth added 13). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · VerificationContent.VerificationContent (cognitive 22) · ×1
  • VerificationContent.VerificationContent (cognitive 22) Frontend/src/components/verification/VerificationContent.tsx:11 — VerificationContent.VerificationContent has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 9, if/else 5 (7 pts), ternaries 4, error handling 2 (nesting depth added 2). Most of this is not in the body itself: 2 of the 22 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 18, handlePayment, a function literal at line 76, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · FileMessage.execute (cognitive 20) · ×1
  • FileMessage.execute (cognitive 20) Backend/src/application/useCases/user/chat/fileMessage.ts:22 — FileMessage.execute has cognitive complexity 20 (threshold 15). Drivers by points: if/else 12 (17 pts), boolean chains 2, ternaries 1 (nesting depth added 5). Of this number, 14 points are the body's own statements and 6 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SubscriptionActions.SubscriptionActions (cognitive 19) · ×1
  • SubscriptionActions.SubscriptionActions (cognitive 19) Frontend/src/components/admin/subscription/SubscriptionActions.tsx:29 — SubscriptionActions.SubscriptionActions has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (8 pts), boolean chains 5, ternaries 4, error handling 2 (nesting depth added 2). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to 4 function items inside it that branch (handleAction, handleSubmit, a function literal at line 115, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · SubscriptionDetials.SubscriptionDetials (cognitive 19) · ×1
  • SubscriptionDetials.SubscriptionDetials (cognitive 19) Frontend/src/components/admin/subscription/SubscriptionDetials.tsx:19 — SubscriptionDetials.SubscriptionDetials has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 7 (11 pts), if/else 4, boolean chains 3, error handling 1 (nesting depth added 4). Most of this is not in the body itself: 8 of the 19 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 48, a function literal at line 149, a function literal at line 32, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · PostModalActions.PostModalActions (cognitive 19) · ×1
  • PostModalActions.PostModalActions (cognitive 19) Frontend/src/components/common/PostViewModal/PostModalActions.tsx:12 — PostModalActions.PostModalActions has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 8, if/else 4 (6 pts), ternaries 2 (3 pts), error handling 2 (nesting depth added 3). Most of this is not in the body itself: 7 of the 19 points are its own statements and the rest belongs to 2 function items inside it that branch (handleDeletePost, handleArchivePost). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · SharePostModal.SharePostModal (cognitive 19) · ×1
  • SharePostModal.SharePostModal (cognitive 19) Frontend/src/components/common/SharePostModal.tsx:14 — SharePostModal.SharePostModal has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 5 (8 pts), boolean chains 5, if/else 4 (5 pts), error handling 1 (nesting depth added 4). Most of this is not in the body itself: 3 of the 19 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 20, a function literal at line 104, toggleSelection, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · PostModal.PostModal · ×1
  • PostModal.PostModal::timeSince (cognitive 19) Frontend/src/components/common/PostViewModal/PostModal.tsx:338 — PostModal.PostModal::timeSince has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 5 (10 pts), if/else 9 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (PostModal.PostModal) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · StoryModal.StoryModal (cognitive 19) · ×1
  • StoryModal.StoryModal (cognitive 19) Frontend/src/components/common/StoryModal/StoryModal.tsx:9 — StoryModal.StoryModal has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 4, ternaries 4 (nesting depth added 4). Most of this is not in the body itself: 7 of the 19 points are its own statements and the rest belongs to 3 function items inside it that branch (goToPrevStory, goToNextStory, a function literal at line 68). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · dateFormat.timeSince (cognitive 19) · ×1
  • dateFormat.timeSince (cognitive 19) Frontend/src/helperFuntions/dateFormat.ts:1 — dateFormat.timeSince has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 5 (10 pts), if/else 9 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Sidebar.Sidebar (cognitive 17) · ×1
  • Sidebar.Sidebar (cognitive 17) Frontend/src/components/admin/common/Sidebar.tsx:39 — Sidebar.Sidebar has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 8, ternaries 5, if/else 2 (3 pts), error handling 1 (nesting depth added 1). Of this number, 10 points are the body's own statements and 7 belong to 2 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · ResetPasswordForm.ResetPasswordForm (cognitive 17) · ×1
  • ResetPasswordForm.ResetPasswordForm (cognitive 17) Frontend/src/components/authentication/ResetPasswordForm.tsx:12 — ResetPasswordForm.ResetPasswordForm has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 8 (10 pts), if/else 3 (4 pts), boolean chains 2, error handling 1 (nesting depth added 3). Of this number, 10 points are the body's own statements and 7 belong to one function item inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · SignUpForm.SignUpForm (cognitive 17) · ×1
  • SignUpForm.SignUpForm (cognitive 17) Frontend/src/components/authentication/SignUpForm.tsx:12 — SignUpForm.SignUpForm has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 8 (10 pts), if/else 3 (4 pts), boolean chains 2, error handling 1 (nesting depth added 3). Of this number, 10 points are the body's own statements and 7 belong to one function item inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · PostEditModal.PostEditModal (cognitive 17) · ×1
  • PostEditModal.PostEditModal (cognitive 17) Frontend/src/components/common/PostViewModal/PostEditModal.tsx:13 — PostEditModal.PostEditModal has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 8, if/else 3 (4 pts), boolean chains 3, error handling 2 (nesting depth added 1). Most of this is not in the body itself: 8 of the 17 points are its own statements and the rest belongs to 3 function items inside it that branch (a function literal at line 46, handleOutsideClick, handleSharePost). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · LikeOrUnlikeComment.execute (cognitive 16) · ×1
  • LikeOrUnlikeComment.execute (cognitive 16) Backend/src/application/useCases/user/post/likeOrUnlikeComment.ts:21 — LikeOrUnlikeComment.execute has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 5 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D3 · God Classes · ClassTooLong · ×1
  • ClassTooLong: PostModal Frontend/src/components/common/PostViewModal/PostModal.tsx:1 — ClassTooLong — 1268 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 868 over it, 3.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D3 · God Classes · FileTooLong · ×1
  • FileTooLong: PostViewModal/PostModal.tsx Frontend/src/components/common/PostViewModal/PostModal.tsx — FileTooLong — 1322 significant lines (blank, comment-only and punctuation-only lines excluded), about 96% of them inside a single declaration: PostModal (56-1618). The bar is 500 significant lines; this is 822 over it, 2.64× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
D35 · Change Coupling · Change coupling · ×1
  • Change coupling: ChatDetials.tsx ↔ ChatInbox.tsx Frontend/src/components/chats/ChatDetials.tsx:1 — `Frontend/src/components/chats/ChatDetials.tsx` and `Frontend/src/components/chats/ChatInbox.tsx` change together 73% of the time (8 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `8b3a4008` fix: bug in video call and audio call some minor change; `f7786dad` Add callEnd socket event to notify user when the call has ended; `076185dd` Add callText message type and dynamic frontend rendering — run `git show` on any of them.
D35 · Change Coupling · Change coupling clique · ×1
  • Change coupling clique: App.tsx, SignInForm.tsx, SignUpForm.tsx Frontend/src/App.tsx — 3 files — `Frontend/src/App.tsx`, `Frontend/src/components/authentication/SignInForm.tsx`, `Frontend/src/components/authentication/SignUpForm.tsx` — all change together with no explicit dependency: a fully-connected co-change clique, not 3 separate couplings. They share one concern (thin parallel siblings over a common abstraction), so extract the shared part into ONE unit and the whole clique's coupling clears at once — you do not need to break each pair individually.
IC1 · Incompleteness & stubs · Fake-async · ×1
  • Fake-async — async method never awaits Backend/src/infrastructure/middlewares/adminAuthMiddleware.ts:8 — `adminAuthMiddleware` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
P1 · CI/CD gates · No CI pipeline · ×1
  • No CI pipeline — No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
P2 · Observability · No structured logging · ×1
  • No structured logging — No logging call was found in the 431 JavaScript/TypeScript production file(s) this check read across 2 module(s). Each was searched for its ecosystem's logging libraries (JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
R10 · Code Duplication · Duplication concentrated across 15 sibling directories (52 clone groups) · ×1
  • Duplication concentrated across 15 sibling directories (52 clone groups) Frontend/src/components/common/PostViewModal/PostEditModal.tsx:20 — 52 duplicated blocks under Frontend/src/components/ have copies in at least two of the sibling directories admin, authentication, calls, chats, common, create-post (+9 more sibling(s) not listed) — 42 of them are reported below, and 10 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 52 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 52 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 52 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 7 sibling directories (19 clone groups) · ×1
  • Duplication concentrated across 7 sibling directories (19 clone groups) Backend/src/infrastructure/controllers/user/post/checkingHasUserLikedPostController.ts:9 — 19 duplicated blocks under Backend/src/infrastructure/controllers/user/ have copies in at least two of the sibling directories authentication, chat, music, post, search, story (+1 more sibling(s) not listed) — 16 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 19 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 19 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 19 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 5 sibling directories (14 clone groups) · ×1
  • Duplication concentrated across 5 sibling directories (14 clone groups) Frontend/src/components/admin/music/MusicDetialsTable.tsx:30 — 14 duplicated blocks under Frontend/src/components/admin/ have copies in at least two of the sibling directories dashboard, music, post, subscription, users — 13 of them are reported below, and 1 is 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 14 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 14 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 14 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 7 sibling directories (10 clone groups) · ×1
  • Duplication concentrated across 7 sibling directories (10 clone groups) Backend/src/application/useCases/user/authentication/resetPassword.ts:6 — 10 duplicated blocks under Backend/src/application/useCases/user/ have copies in at least two of the sibling directories authentication, chat, post, search, story, subscription (+1 more sibling(s) not listed) — 3 of them are reported below, and 7 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 · Duplication concentrated across 2 sibling directories (10 clone groups) · ×1
  • Duplication concentrated across 2 sibling directories (10 clone groups) Backend/src/infrastructure/controllers/admin/authentication/refreshTokenAdminController.ts:9 — 10 duplicated blocks under Backend/src/infrastructure/controllers/ have copies in at least two of the sibling directories admin, user — 9 of them are reported below, and 1 is 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 · Duplication concentrated across 2 sibling directories (9 clone groups) · ×1
  • Duplication concentrated across 2 sibling directories (9 clone groups) Backend/src/application/repositories/admin/implements/musicRepository.ts:36 — 9 duplicated blocks under Backend/src/application/repositories/ have copies in at least two of the sibling directories admin, user — 5 of them are reported below, and 4 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 9 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 9 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 9 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 2 sibling directories (8 clone groups) · ×1
  • Duplication concentrated across 2 sibling directories (8 clone groups) Backend/src/application/useCases/admin/authentication/handleAdminRefreshToken.ts:5 — 8 duplicated blocks under Backend/src/application/useCases/ have copies in at least two of the sibling directories admin, user — 5 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 8 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 8 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 8 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 6 sibling directories (7 clone groups) · ×1
  • Duplication concentrated across 6 sibling directories (7 clone groups) Backend/src/application/useCases/admin/admin/editAdmin.ts:6 — 7 duplicated blocks under Backend/src/application/useCases/admin/ have copies in at least two of the sibling directories admin, authentication, music, post, subscription, user — 5 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 7 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 7 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 7 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplicated block with local edits (162 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (162 matched lines × 2 locations) Frontend/src/components/common/PostViewModal/PostEditModal.tsx:20 — Frontend/src/components/common/PostViewModal/PostEditModal.tsx:20 · Frontend/src/components/create-post/CreatePostFormSubmit.tsx:19 — the two spans are one implementation copied and then locally edited — 753 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block with local edits (157 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (157 matched lines × 2 locations) Frontend/src/components/admin/music/MusicDetialsTable.tsx:30 — Frontend/src/components/admin/music/MusicDetialsTable.tsx:30 · Frontend/src/components/admin/subscription/SubscriptionDetials.tsx:20 — the two spans are one implementation copied and then locally edited — 1010 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 (140 lines × 2 locations) · ×1
  • Duplicated block (140 lines × 2 locations) Frontend/src/components/profile/ProfilePostSection.tsx:160 — Frontend/src/components/profile/ProfilePostSection.tsx:160 · Frontend/src/components/user-profiles/UserProfilePostSection.tsx:158 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
R10 · Code Duplication · Duplicated block with local edits (135 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (135 matched lines × 2 locations) Frontend/src/components/admin/common/Sidebar.tsx:44 — Frontend/src/components/admin/common/Sidebar.tsx:44 · Frontend/src/components/common/Sidebar.tsx:94 — the two spans are one implementation copied and then locally edited — 666 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block with local edits (103 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (103 matched lines × 2 locations) Frontend/src/components/authentication/SignInForm.tsx:14 — Frontend/src/components/authentication/SignInForm.tsx:14 · Frontend/src/components/authentication/SignUpForm.tsx:12 — the two spans are one implementation copied and then locally edited — 570 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block with local edits (100 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (100 matched lines × 2 locations) Frontend/src/components/admin/music/MusicDetialsTable.tsx:103 — Frontend/src/components/admin/music/MusicDetialsTable.tsx:103 · Frontend/src/components/create-post/CreatePostMusic.tsx:30 — the two spans are one implementation copied and then locally edited — 517 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (97 lines × 3 locations) · ×1
  • Duplicated block (97 lines × 3 locations) Frontend/src/components/explore/ExploreDetials.tsx:94 — Frontend/src/components/explore/ExploreDetials.tsx:94 · Frontend/src/components/profile/ProfilePostSection.tsx:160 · Frontend/src/components/user-profiles/UserProfilePostSection.tsx:158 — the 3 copies are spread across 3 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
R10 · Code Duplication · Duplicated block with local edits (86 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (86 matched lines × 2 locations) Frontend/src/components/admin/music/MusicAction.tsx:94 — Frontend/src/components/admin/music/MusicAction.tsx:94 · Frontend/src/components/admin/subscription/SubscriptionActions.tsx:85 — the two spans are one implementation copied and then locally edited — 425 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block with local edits (66 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (66 matched lines × 2 locations) Frontend/src/components/admin/music/MusicDetialsTable.tsx:52 — Frontend/src/components/admin/music/MusicDetialsTable.tsx:52 · Frontend/src/components/admin/users/UserDetialsTable.tsx:51 — the two spans are one implementation copied and then locally edited — 386 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 (66 lines × 2 locations) · ×1
  • Duplicated block (66 lines × 2 locations) Frontend/src/components/admin/subscription/AddSubscriptionForm.tsx:77 — Frontend/src/components/admin/subscription/AddSubscriptionForm.tsx:77 · Frontend/src/components/admin/subscription/SubscriptionActions.tsx:112 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
R10 · Code Duplication · Duplicated block (60 lines × 2 locations) · ×1
  • Duplicated block (60 lines × 2 locations) Frontend/src/components/common/PostViewModal/PostModal.tsx:1136 — Frontend/src/components/common/PostViewModal/PostModal.tsx:1136 · Frontend/src/components/common/PostViewModal/PostModal.tsx:1320 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
R10 · Code Duplication · Duplicated block with local edits (59 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (59 matched lines × 2 locations) Frontend/src/components/authentication/ForgotPasswordForm.tsx:33 — Frontend/src/components/authentication/ForgotPasswordForm.tsx:33 · Frontend/src/components/authentication/ResetPasswordForm.tsx:49 — the two spans are one implementation copied and then locally edited — 252 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 (54 lines × 2 locations) · ×1
  • Duplicated block (54 lines × 2 locations) Frontend/src/components/ui/dropdown-menu.tsx:129 — Frontend/src/components/ui/dropdown-menu.tsx:129 · Frontend/src/components/ui/menubar.tsx:160 — 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 (53 lines × 2 locations) · ×1
  • Duplicated block (53 lines × 2 locations) Frontend/src/components/admin/post/PostDetialsTable.tsx:164 — Frontend/src/components/admin/post/PostDetialsTable.tsx:164 · Frontend/src/components/admin/users/UserDetialsTable.tsx:155 — 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 (48 lines × 2 locations) · ×1
  • Duplicated block (48 lines × 2 locations) Frontend/src/components/common/Sidebar.tsx:191 — Frontend/src/components/common/Sidebar.tsx:191 · Frontend/src/components/common/svg/Reel.tsx:11 — 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 (44 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (44 matched lines × 2 locations) Frontend/src/validations/authValidations.ts:3 — Frontend/src/validations/authValidations.ts:3 · Frontend/src/validations/authValidations.ts:98 — the two spans are one implementation copied and then locally edited — 248 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 (43 lines × 2 locations) · ×1
  • Duplicated block (43 lines × 2 locations) Frontend/src/components/admin/post/PostDetialsTable.tsx:266 — Frontend/src/components/admin/post/PostDetialsTable.tsx:266 · Frontend/src/components/admin/users/UserDetialsTable.tsx:266 — 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 (37 lines × 2 locations) · ×1
  • Duplicated block (37 lines × 2 locations) Frontend/src/apis/interceptors/adminInterceptors.ts:6 — Frontend/src/apis/interceptors/adminInterceptors.ts:6 · Frontend/src/apis/interceptors/interceptors.ts:7 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
R10 · Code Duplication · Duplicated block with local edits (35 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (35 matched lines × 2 locations) Frontend/src/components/common/FollowDetialsModal.tsx:32 — Frontend/src/components/common/FollowDetialsModal.tsx:32 · Frontend/src/components/common/FriendSuggetion.tsx:21 — the two spans are one implementation copied and then locally edited — 229 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 (30 lines × 2 locations) · ×1
  • Duplicated block (30 lines × 2 locations) Frontend/src/components/admin/music/AddMusicForm.tsx:156 — Frontend/src/components/admin/music/AddMusicForm.tsx:156 · Frontend/src/components/admin/music/MusicAction.tsx:121 — 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.
R2 · Cyclomatic Complexity · Complex function CreatePostBody (cyclomatic 37, cognitive 29) · ×1
  • Complex function CreatePostBody (cyclomatic 37, cognitive 29) Frontend/src/components/create-post/CreatePostBody.tsx:20 — CreatePostBody has cyclomatic complexity 37 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function PostModal (cyclomatic 36, cognitive 34) · ×1
  • Complex function PostModal (cyclomatic 36, cognitive 34) Frontend/src/components/common/PostViewModal/PostModal.tsx:56 — PostModal has cyclomatic complexity 36 and cognitive complexity 34; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function createRoutes (cyclomatic 34, cognitive 33) · ×1
  • Complex function createRoutes (cyclomatic 34, cognitive 33) Frontend/src/routes/createRoutes.tsx:35 — createRoutes has cyclomatic complexity 34 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function VideoAudioCall (cyclomatic 32, cognitive 30) · ×1
  • Complex function VideoAudioCall (cyclomatic 32, cognitive 30) Frontend/src/components/calls/VideoAudioCall.tsx:15 — VideoAudioCall has cyclomatic complexity 32 and cognitive complexity 30; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 28, cognitive 33) · ×1
  • Complex function (anonymous) (cyclomatic 28, cognitive 33) Frontend/src/components/admin/post/PostDetialsTable.tsx:48 — (anonymous) has cyclomatic complexity 28 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function CreatePostFilters (cyclomatic 27, cognitive 21) · ×1
  • Complex function CreatePostFilters (cyclomatic 27, cognitive 21) Frontend/src/components/create-post/CreatePostFilters.tsx:16 — CreatePostFilters has cyclomatic complexity 27 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function ChatsInbox (cyclomatic 22, cognitive 20) · ×1
  • Complex function ChatsInbox (cyclomatic 22, cognitive 20) Frontend/src/components/chats/ChatInbox.tsx:26 — ChatsInbox has cyclomatic complexity 22 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 22, cognitive 18) · ×1
  • Complex function (anonymous) (cyclomatic 22, cognitive 18) Frontend/src/components/chats/ChatInbox.tsx:436 — (anonymous) has cyclomatic complexity 22 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function handleInputChange (cyclomatic 21, cognitive 32) · ×1
  • Complex function handleInputChange (cyclomatic 21, cognitive 32) Frontend/src/components/create-post/SelectAspectRatio.tsx:95 — handleInputChange has cyclomatic complexity 21 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 21, cognitive 17) · ×1
  • Complex function (anonymous) (cyclomatic 21, cognitive 17) Frontend/src/components/common/FollowDetialsModal.tsx:135 — (anonymous) has cyclomatic complexity 21 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function Sidebar (cyclomatic 19, cognitive 18) · ×1
  • Complex function Sidebar (cyclomatic 19, cognitive 18) Frontend/src/components/common/Sidebar.tsx:56 — Sidebar has cyclomatic complexity 19 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function ProfilePostSection (cyclomatic 19, cognitive 16) · ×1
  • Complex function ProfilePostSection (cyclomatic 19, cognitive 16) Frontend/src/components/profile/ProfilePostSection.tsx:26 — ProfilePostSection has cyclomatic complexity 19 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 17, cognitive 16) · ×1
  • Complex function (anonymous) (cyclomatic 17, cognitive 16) Frontend/src/components/home/Posts.tsx:274 — (anonymous) has cyclomatic complexity 17 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function execute (cyclomatic 17, cognitive 15) · ×1
  • Complex function execute (cyclomatic 17, cognitive 15) Backend/src/application/useCases/user/chat/sendMessage.ts:18 — execute has cyclomatic complexity 17 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function TagUser (cyclomatic 16, cognitive 12) · ×1
  • Complex function TagUser (cyclomatic 16, cognitive 12) Frontend/src/components/create-post/TagUser.tsx:26 — TagUser has cyclomatic complexity 16 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function ChatDetials (cyclomatic 15, cognitive 14) · ×1
  • Complex function ChatDetials (cyclomatic 15, cognitive 14) Frontend/src/components/chats/ChatDetials.tsx:26 — ChatDetials has cyclomatic complexity 15 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function CreatePostFormSubmit (cyclomatic 15, cognitive 14) · ×1
  • Complex function CreatePostFormSubmit (cyclomatic 15, cognitive 14) Frontend/src/components/create-post/CreatePostFormSubmit.tsx:13 — CreatePostFormSubmit has cyclomatic complexity 15 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function UserProfileDetials (cyclomatic 15, cognitive 14) · ×1
  • Complex function UserProfileDetials (cyclomatic 15, cognitive 14) Frontend/src/components/user-profiles/UserProfileDetials.tsx:19 — UserProfileDetials has cyclomatic complexity 15 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 15, cognitive 13) · ×1
  • Complex function (anonymous) (cyclomatic 15, cognitive 13) Frontend/src/components/common/PostViewModal/PostModal.tsx:1032 — (anonymous) has cyclomatic complexity 15 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function timeSince (cyclomatic 14, cognitive 19) · ×1
  • Complex function timeSince (cyclomatic 14, cognitive 19) Frontend/src/components/common/PostViewModal/PostModal.tsx:338 — timeSince has cyclomatic complexity 14 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files · Frontend/src/components/common/PostViewModal/PostModal.tsx · ×1
  • Frontend/src/components/common/PostViewModal/PostModal.tsx: 1557 lines of code Frontend/src/components/common/PostViewModal/PostModal.tsx:1 — Frontend/src/components/common/PostViewModal/PostModal.tsx has 1557 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 · Frontend/src/components/chats/ChatInbox.tsx · ×1
  • Frontend/src/components/chats/ChatInbox.tsx: 498 lines of code Frontend/src/components/chats/ChatInbox.tsx:1 — Frontend/src/components/chats/ChatInbox.tsx has 498 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 · Frontend/src/components/calls/VideoAudioCall.tsx · ×1
  • Frontend/src/components/calls/VideoAudioCall.tsx: 442 lines of code Frontend/src/components/calls/VideoAudioCall.tsx:1 — Frontend/src/components/calls/VideoAudioCall.tsx has 442 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 · Frontend/src/components/common/Sidebar.tsx · ×1
  • Frontend/src/components/common/Sidebar.tsx: 422 lines of code Frontend/src/components/common/Sidebar.tsx:1 — Frontend/src/components/common/Sidebar.tsx has 422 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 · Frontend/src/components/home/Posts.tsx · ×1
  • Frontend/src/components/home/Posts.tsx: 413 lines of code Frontend/src/components/home/Posts.tsx:1 — Frontend/src/components/home/Posts.tsx has 413 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 · Frontend/src/components/chats/ChatDetials.tsx · ×1
  • Frontend/src/components/chats/ChatDetials.tsx: 408 lines of code Frontend/src/components/chats/ChatDetials.tsx:1 — Frontend/src/components/chats/ChatDetials.tsx has 408 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R4 · Test Coverage · Test Coverage · ×1
  • Test Coverage — 0% of 396 production file(s) reachable from 0 test file(s) via the import graph — 'production' here is the RESIDUE: every source file left once tests, tooling, generated output, config, declarations and declaration-only modules, fixture corpora, type fixtures, behaviour-free data modules, re-export barrels, registration/constant data modules and service workers are set aside, so the percentage is taken over a smaller denominator than the workspace's file count
R5 · Dependency Freshness · Dependency Freshness · ×1
  • Dependency Freshness — 50 outdated package(s); JS/npm CVEs scored in D30
R6 · Tooling · No test script · ×1
  • No test script — test ✗ · lint ✓ · typecheck ✓ — read from this repository's package.json 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 (~37 LoC) · ×1
  • Dead file (~37 LoC) Frontend/src/components/ui/mode-toggle.tsx — no import path from any entry point (5 application, 7 tooling, 0 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 (~30 LoC) · ×1
  • Dead file (~30 LoC) Frontend/src/helperFuntions/convertBlobUrlToBase64.ts — no import path from any entry point (5 application, 7 tooling, 0 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 (~26 LoC) · ×1
  • Dead file (~26 LoC) Frontend/src/components/ui/slider.tsx — no import path from any entry point (5 application, 7 tooling, 0 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 (~13 LoC) · ×1
  • Dead file (~13 LoC) Frontend/src/pages/user/Chats.tsx — no import path from any entry point (5 application, 7 tooling, 0 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 (~10 LoC) · ×1
  • Dead file (~10 LoC) Backend/src/infrastructure/configs/rateLimit.ts — no import path from any entry point (5 application, 7 tooling, 0 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 'cropperjs' · ×1
  • Unused dependency 'cropperjs' — Declared in Frontend/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 'react-cropper' · ×1
  • Unused dependency 'react-cropper' — Declared in Frontend/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.
X2 · Cancellation propagation · Async function without AbortSignal · ×1
  • Async function without AbortSignal: convertBlobUrlToBase64 Frontend/src/helperFuntions/convertBlobUrlToBase64.ts:1 — `convertBlobUrlToBase64` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Minor — 48 finding(s)
X10 · Duplicated predicate · Duplicated predicate · ×10
  • Duplicated predicate Backend/src/application/useCases/user/chat/fileMessage.ts:45 — `!userChat?.members.includes(userId) && !userChat?.members.includes(chatId)` appears character-identically in 2 files — Backend/src/application/useCases/user/chat/fileMessage.ts, Backend/src/application/useCases/user/chat/sendMessage.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate Frontend/src/components/admin/music/MusicDetialsTable.tsx:162 — `currentlyPlayingIndex !== null && currentlyPlayingIndex !== musicId` appears character-identically in 2 files — Frontend/src/components/admin/music/MusicDetialsTable.tsx, Frontend/src/components/create-post/CreatePostMusic.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate Frontend/src/components/common/PostViewModal/PostEditModal.tsx:30 — `emojiPickerRef.current && !emojiPickerRef.current.contains(event.target as Node)` appears character-identically in 3 files — Frontend/src/components/common/PostViewModal/PostEditModal.tsx, Frontend/src/components/common/PostViewModal/PostModal.tsx, Frontend/src/components/create-post/CreatePostFormSubmit.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate Frontend/src/components/explore/ExploreDetials.tsx:46 — `entries[0].isIntersecting && page < totalPage` appears character-identically in 2 files — Frontend/src/components/explore/ExploreDetials.tsx, Frontend/src/components/home/Posts.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate Frontend/src/components/admin/authentication/SignInForm.tsx:50 — `error instanceof AxiosError && error.response` appears character-identically in 38 files — Frontend/src/components/admin/authentication/SignInForm.tsx, Frontend/src/components/admin/common/Sidebar.tsx, Frontend/src/components/admin/music/AddMusicForm.tsx, Frontend/src/components/admin/music/MusicAction.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate Frontend/src/components/admin/authentication/SignInForm.tsx:52 — `error.response.data?.error || "An error occurred"` appears character-identically in 38 files — Frontend/src/components/admin/authentication/SignInForm.tsx, Frontend/src/components/admin/common/Sidebar.tsx, Frontend/src/components/admin/music/AddMusicForm.tsx, Frontend/src/components/admin/music/MusicAction.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate Frontend/src/components/explore/ExploreDetials.tsx:112 — `item.post[0].type === "video" || item.post[0].type === 'reel'` appears character-identically in 3 files — Frontend/src/components/explore/ExploreDetials.tsx, Frontend/src/components/profile/ProfilePostSection.tsx, Frontend/src/components/user-profiles/UserProfilePostSection.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate Frontend/src/components/explore/ExploreDetials.tsx:48 — `newPosts.post && newPosts.post.length > 0` appears character-identically in 2 files — Frontend/src/components/explore/ExploreDetials.tsx, Frontend/src/components/home/Posts.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate Frontend/src/apis/interceptors/adminInterceptors.ts:27 — `originalRequest && error.response?.status === 401 && !originalRequest._retry` appears character-identically in 2 files — Frontend/src/apis/interceptors/adminInterceptors.ts, Frontend/src/apis/interceptors/interceptors.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate Backend/src/infrastructure/middlewares/adminAuthMiddleware.ts:17 — `parts.length !== 2 || parts[0] !== "Bearer"` appears character-identically in 2 files — Backend/src/infrastructure/middlewares/adminAuthMiddleware.ts, Backend/src/infrastructure/middlewares/authMiddleware.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
D12 · Dependency Hygiene · Outdated (npm) · ×8
  • Outdated (npm): @fortawesome/react-fontawesome Frontend/package.json:18 — @fortawesome/react-fontawesome is pinned at 0.2.2; registry.npmjs.org publishes 3.5.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @mui/icons-material Frontend/package.json:19 — @mui/icons-material is pinned at 6.1.1; registry.npmjs.org publishes 9.5.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @mui/material Frontend/package.json:20 — @mui/material is pinned at 6.1.1; registry.npmjs.org publishes 9.5.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @stripe/stripe-js Frontend/package.json:34 — @stripe/stripe-js is pinned at 5.6.0; registry.npmjs.org publishes 10.1.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): firebase Frontend/package.json:43 — firebase is pinned at 10.13.1; registry.npmjs.org publishes 13.1.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): nodemailer Backend/package.json:28 — nodemailer is pinned at 6.9.14; registry.npmjs.org publishes 10.2.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): stripe Backend/package.json:31 — stripe is pinned at 17.6.0; registry.npmjs.org publishes 23.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): uuid Backend/package.json:32 — uuid is pinned at 10.0.0; registry.npmjs.org publishes 14.0.3 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
D30 · Dependency Vulnerabilities · Low CVE · ×8
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AX6 · Interface segregation · Fat interface · ×2
  • Fat interface: IPostRepository (23 required operations) Backend/src/application/repositories/user/interfaces/IPostRepository.ts:4 — `IPostRepository` declares 23 required operations: `createPost`, `getAllPostCount`, `findUserPostData`, `findUserTaggedPosts`, `findLikedPostData`, `handleLikes`, `updateCommentCount`, `findPostById`, `findPostByIdWithUserData`, `findPostByIdWithUserData1`, `deletePost`, `getUserPostCount`, `updatePost`, `reportPost`, `archiveToggle`, `findUserArchivedPost`, `findUserReelsPost`, `findReelById`, `findPostsOfFriendAndNonWatched`, `findPostsOfNonFriendAndNonWatched`, `findPostOfWatched`, `findPostOfFollowedUserWached`, `getPostData`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: IUserRepository (21 required operations) Backend/src/application/repositories/user/interfaces/IUserRepository.ts:5 — `IUserRepository` declares 21 required operations: `findById`, `findById1`, `findByEmail`, `findByUsernameAndEmail`, `findByUsername`, `findByUsernameEdit`, `createUser`, `getAllUsers`, `findUsersByUserIds`, `userPasswordChange`, `updateUser`, `getUserData`, `blockAndUnBlockUser`, `find10UserBySearch`, `findUsers`, `findUserDataWithIdInArray`, `changeUserOnlineStatus`, `updateVerification`, `setVerificationStatusFalse`, `findSearchUsers`, `findUsersByIds`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
C2 · Access Controls · No named authorization policies · ×1
  • No named authorization policies — Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect.
C4 · Data Retention · Partial data-retention evidence · ×1
  • Partial data-retention evidence — A retention mechanism is present, but the data-lifecycle is not yet complete — missing: a scheduled purge / cleanup job (a cron task that deletes rows past their retention — purgeExpired… / deleteOld…), a documented retention period / data-expiry.
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1
  • Projects may be oversized for their cohesion — 2 of 2 project(s) overshoot their size bounds, lowering Project Cohesion to 0.0/10. The most over is `Frontend` (18473 LoC, 192 module-visible types across 47 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D9 · Test Distribution · No tests found · ×1
  • No tests found — No test suite could be collected — no discoverable tests to count. If this repository does test, wiring the suite to a framework a runner can collect (Vitest, Jest, Mocha, or the runtime's built-in runner (`node --test`, `bun test`, `deno test`)) is what makes it countable here; a pipeline step that invokes a runner is not evidence on its own, because a runner over an empty suite passes. Tests written as plain executables or shell/PowerShell harnesses are not collectible this way and are not scored here.
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
M2 · Architecture documentation · No architecture diagram/doc · ×1
  • No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST — No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
P4 · Deployment & Rollback · No release approval gate · ×1
  • No release approval gate — The release 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 the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
R7 · Dead Code · Unused export 'useSocket' · ×1
  • Unused export 'useSocket' Frontend/src/context/SocketContext.ts:6 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'persister' · ×1
  • Unused export 'persister' Frontend/src/redux/store/store.ts:37 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'AppDispatch' · ×1
  • Unused export 'AppDispatch' Frontend/src/redux/store/store.ts:40 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'ChatDataHeader' · ×1
  • Unused export 'ChatDataHeader' Frontend/src/types/chat/chat.ts:35 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'PostLowerSectionComponentProps' · ×1
  • Unused export 'PostLowerSectionComponentProps' Frontend/src/types/home/postLowerSection.ts:1 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Write-only private field 'notificationRepository' · ×1
  • Write-only private field 'notificationRepository' Backend/src/application/useCases/user/story/createStory.ts:13 — This private field is assigned but never read: every reference in its class is a plain assignment, no string key or test reads it by name, and the instance never escapes as a whole (so nothing serialises or destructures it). The value it holds is dead state — read it where it was meant to take effect, or remove the field and its assignments.
R7 · Dead Code · Write-only private field 'UserMoreDataRepository' · ×1
  • Write-only private field 'UserMoreDataRepository' Backend/src/application/useCases/user/user/removeUser.ts:12 — This private field is assigned but never read: every reference in its class is a plain assignment, no string key or test reads it by name, and the instance never escapes as a whole (so nothing serialises or destructures it). The value it holds is dead state — read it where it was meant to take effect, or remove the field and its assignments.
S1 · Web-Security Posture · No security response headers detected · ×1
  • No security response headers detected Frontend/vercel.json:1 — None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `vercel.json` configures this repository's static hosting, including its response headers, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.)
S1 · Web-Security Posture · No app-layer HTTPS enforcement detected · ×1
  • No app-layer HTTPS enforcement detected Backend/src/presentation/settings/server.ts:73 — `server.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.)
X2 · Cancellation propagation · Not all async functions that make a request accept an AbortSignal · ×1
  • Not all async functions that make a request accept an AbortSignal — Only 0/1 async functions that make a cancellable request (fetch, axios, ky, ofetch) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
X5 · Nullable reference types · Null assertions (`!`) reduce the strict null checking score · ×1
  • Null assertions (`!`) reduce the strict null checking score — ~1.6 `!` null assertions per 1k TypeScript source lines — 50 assertion(s) across the 30839 source line(s) of the 430 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: Backend/src/presentation/settings/server.ts (17), Backend/src/application/providers/tokenManager.ts (6), Backend/src/infrastructure/configs/aswS3.ts (4). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.
Minor — 53 finding(s)
D12 · Dependency Hygiene · Outdated (npm) · ×53
  • Outdated (npm): @aws-sdk/client-rekognition — @aws-sdk/client-rekognition is pinned at 3.665.0; registry.npmjs.org publishes 3.1155.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @aws-sdk/client-s3 — @aws-sdk/client-s3 is pinned at 3.637.0; registry.npmjs.org publishes 3.1155.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @aws-sdk/s3-request-presigner — @aws-sdk/s3-request-presigner is pinned at 3.637.0; registry.npmjs.org publishes 3.1155.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @emotion/react — @emotion/react is pinned at 11.13.3; registry.npmjs.org publishes 11.14.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @emotion/styled — @emotion/styled is pinned at 11.13.0; registry.npmjs.org publishes 11.14.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @fontsource/roboto — @fontsource/roboto is pinned at 5.1.0; registry.npmjs.org publishes 5.3.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @fortawesome/free-regular-svg-icons — @fortawesome/free-regular-svg-icons is pinned at 6.6.0; registry.npmjs.org publishes 7.3.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @fortawesome/free-solid-svg-icons — @fortawesome/free-solid-svg-icons is pinned at 6.6.0; registry.npmjs.org publishes 7.3.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @nextui-org/modal — @nextui-org/modal is pinned at 2.0.39; registry.npmjs.org publishes 2.2.7 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @nextui-org/react — @nextui-org/react is pinned at 2.4.6; registry.npmjs.org publishes 2.6.11 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @radix-ui/react-alert-dialog — @radix-ui/react-alert-dialog is pinned at 1.1.1; registry.npmjs.org publishes 1.2.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @radix-ui/react-dropdown-menu — @radix-ui/react-dropdown-menu is pinned at 2.1.1; registry.npmjs.org publishes 2.2.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @radix-ui/react-icons — @radix-ui/react-icons is pinned at 1.3.0; registry.npmjs.org publishes 1.3.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @radix-ui/react-label — @radix-ui/react-label is pinned at 2.1.0; registry.npmjs.org publishes 2.1.17 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @radix-ui/react-menubar — @radix-ui/react-menubar is pinned at 1.1.1; registry.npmjs.org publishes 1.2.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @radix-ui/react-radio-group — @radix-ui/react-radio-group is pinned at 1.2.1; registry.npmjs.org publishes 1.5.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @radix-ui/react-select — @radix-ui/react-select is pinned at 2.1.1; registry.npmjs.org publishes 2.4.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @radix-ui/react-slider — @radix-ui/react-slider is pinned at 1.2.1; registry.npmjs.org publishes 1.6.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @radix-ui/react-slot — @radix-ui/react-slot is pinned at 1.1.0; registry.npmjs.org publishes 1.5.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @radix-ui/react-tabs — @radix-ui/react-tabs is pinned at 1.1.0; registry.npmjs.org publishes 1.2.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @reduxjs/toolkit — @reduxjs/toolkit is pinned at 2.2.7; registry.npmjs.org publishes 2.13.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @zegocloud/zego-uikit-prebuilt — @zegocloud/zego-uikit-prebuilt is pinned at 2.14.1-beta; registry.npmjs.org publishes 2.18.5 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): axios — axios is pinned at 1.7.7; registry.npmjs.org publishes 1.20.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): bcryptjs — bcryptjs is pinned at 2.4.3; registry.npmjs.org publishes 3.0.3 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): class-variance-authority — class-variance-authority is pinned at 0.7.0; registry.npmjs.org publishes 0.7.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • + 28 more in this group — see findings.md.

Appendix B — Reproduction & audit trail

Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-534ba31ceeeb4875a0afce0b6957f4a9/history.json --exit-code 0 --source .1artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-534ba31ceeeb4875a0afce0b6957f4a9/tree.json --exit-code 0 --source .0artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off .18artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update74artifacts/raw/trivy-fs.json
D31 · IaC & Container Securitytrivy—trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.0—
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.0—
D36 · Supply-chain Provenance & Signingprovenance—provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.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-update0artifacts/raw/trivy-fs.json

Run 01a16473-f0b3-7c4d-9417-571224da2933 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Issues: 124 · Warnings: 383 · Recommendations: 48 · Info: 53 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 22-10-2026 @ 16:31 UTC.

Downloadable artifacts

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

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