Executive summary
sudheerj/reactjs-interview-questions is rated At risk because critical security findings are open, all of them in the packages it uses. Its score is held back because we found no working pipeline that builds or tests changes to the code and no automated security scanning of the code, its secrets or its dependencies. It scores 52 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 38, is the weakest lens and counts most in the score. The best first step is adding an automated build and test pipeline, worth about 7 points. Adding tests for the code no test reaches comes next, worth about 5 points. Raising Production Readiness to 70 would lift the score to about 64.
Seventy-seven known security holes in the packages the code depends on can be used by attackers. Eight form fields can't be read by a screen reader, and two controls can't be used without a mouse. Updating the vulnerable packages, labelling the form fields and making the controls work with a keyboard would close these risks. The page that doesn't say its language needs its language set.
The product code is 3,612 lines, about €3,500 to rebuild.
If Production Readiness rose from 38 to 70, the lowest score rated Strong, the score would rise from 52 to about 64.
New since the last survey: 15 findings
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Visual & motion safety · Low contrast colour pair in CSS (4.4:1) coding-projects/autocomplete-app/src/App.css
Fixed since the last survey: 41 findings
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High vulnerability: REDACTED REDACTED
- Dependency Vulnerabilities · High vulnerability: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High vulnerability: REDACTED REDACTED
- Dependency Vulnerabilities · High vulnerability: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Test Coverage · No test reaches this file coding-hooks/src/hooks/05-useInterval/useInterval.ts
- Test Coverage · No test reaches this file coding-exercise/src/index.js
- Test Coverage · No test reaches this file coding-hooks/src/hooks/07-useFetch/useFetch.ts
- Test Coverage · No test reaches this file coding-projects/tree-view-app/src/components/Tree.tsx
- Test Coverage · No test reaches this file coding-hooks/src/hooks/02-useDebounce/useDebounce.ts
- Test Coverage · No test reaches this file coding-hooks/src/hooks/04-useToggle/App.tsx
- Test Coverage · No test reaches this file coding-hooks/src/hooks/06-useLocalStorage/App.tsx
- Test Coverage · No test reaches this file coding-hooks/src/hooks/06-useLocalStorage/useLocalStorage.ts
- Test Coverage · No test reaches this file coding-projects/data-table-app/src/components/SearchBar.tsx
- Test Coverage · No test reaches this file coding-projects/infinite-scroll-app/src/components/PostCard.tsx
- Test Coverage · No test reaches this file coding-projects/theme-switcher/src/components/ThemeSwitcher.tsx
- Test Coverage · No test reaches this file coding-projects/theme-switcher/src/main.tsx
- Test Coverage · No test reaches this file coding-projects/tree-view-app/src/App.tsx
- Test Coverage · No test reaches this file coding-projects/data-table-app/src/services/userService.ts
- Test Coverage · No test reaches this file coding-hooks/src/hooks/01-usePrevious/usePrevious.ts
- Test Coverage · No test reaches this file coding-hooks/src/hooks/04-useToggle/useToggle.ts
- Test Coverage · No test reaches this file coding-hooks/src/main.tsx
- Test Coverage · No test reaches this file coding-projects/accordion-app/src/main.tsx
- Test Coverage · No test reaches this file coding-projects/autocomplete-app/src/main.tsx
- Test Coverage · No test reaches this file coding-projects/carousel-app/src/main.tsx
- Test Coverage · No test reaches this file coding-projects/data-table-app/src/main.tsx
- Test Coverage · No test reaches this file coding-projects/hacker-news-jobs/src/main.tsx
- Test Coverage · No test reaches this file coding-projects/infinite-scroll-app/src/main.tsx
- Test Coverage · No test reaches this file coding-projects/nested-comments/src/main.tsx
- Test Coverage · No test reaches this file coding-projects/react-modal/src/main.tsx
- Test Coverage · No test reaches this file coding-projects/shopping-cart/src/main.tsx
- Test Coverage · No test reaches this file coding-projects/star-rating/src/main.tsx
- Test Coverage · No test reaches this file coding-projects/todo-app/src/main.tsx
- Test Coverage · No test reaches this file coding-projects/tree-view-app/src/main.tsx
- Test Coverage · No test reaches this file coding-projects/infinite-scroll-app/src/App.tsx
- Test Coverage · No test reaches this file coding-exercise/hooks/useDebounce.tsx
- Test Coverage · No test reaches this file coding-projects/carousel-app/src/components/Carousel.tsx
- A11y enforcement · Accessibility enforcement below the top rung
Rebuild cost: about €3,500 · Estimate
| Cost to rebuild | €1,200 to €5,900, for 20 to 62 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 52. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 3,612 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 coding-exercise.src | 2 coding-exercise.src.components | 3 coding-exercise.src.exercises.__template__ | 4 coding-exercise.src.exercises.exercise-01-state-batching | 5 coding-exercise.src.exercises.exercise-02-useeffect-dependencies | 6 coding-exercise.src.exercises.exercise-03-useCallback-memoization | 7 coding-exercise.src.exercises.exercise-04-custom-hooks | 8 coding-hooks.src | 9 coding-hooks.src.hooks.01-usePrevious | 10 coding-hooks.src.hooks.02-useDebounce | 11 coding-hooks.src.hooks.03-useDebounceCallback | 12 coding-hooks.src.hooks.04-useToggle | 13 coding-hooks.src.hooks.05-useInterval | 14 coding-projects.accordion-app.src.types.accordion | 15 coding-projects.data-table-app.src.components.DataTable | 16 coding-projects.data-table-app.src.components.Pagination | 17 coding-projects.data-table-app.src.components.SearchBar | 18 coding-projects.infinite-scroll-app.src.types.post | 19 coding-projects.nested-comments.src.components.Comment | 20 coding-projects.nested-comments.src.components.CommentForm | 21 coding-projects.nested-comments.src.components.CommentList | 22 coding-projects.react-modal.src.components.Modal | 23 coding-projects.shopping-cart.src.components.Cart | 24 coding-projects.shopping-cart.src.types.product | 25 coding-projects.star-rating.src.components.StarRating | 26 coding-projects.theme-switcher.src.context.ThemeContext | 27 coding-projects.tree-view-app.src.components.Tree | 28 coding-projects.tree-view-app.src.types.tree | 29 coding-projects.accordion-app.src.components | 30 coding-projects.data-table-app.src.components | 31 coding-projects.infinite-scroll-app.src.components.PostCard | 32 coding-projects.nested-comments.src.components | 33 coding-projects.react-modal.src.components | 34 coding-projects.shopping-cart.src.components.ProductCard | 35 coding-projects.star-rating.src.components | 36 coding-projects.theme-switcher.src.context | 37 coding-projects.tree-view-app.src.components.TreeNode | 38 coding-projects.infinite-scroll-app.src.components | 39 coding-projects.shopping-cart.src.components | 40 coding-projects.tree-view-app.src.components |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 coding-exercise.src | ||||||||||||||||||||||||||||||||||||||||
| 2 coding-exercise.src.components | ||||||||||||||||||||||||||||||||||||||||
| 3 coding-exercise.src.exercises.__template__ | ||||||||||||||||||||||||||||||||||||||||
| 4 coding-exercise.src.exercises.exercise-01-state-batching | ||||||||||||||||||||||||||||||||||||||||
| 5 coding-exercise.src.exercises.exercise-02-useeffect-dependencies | ||||||||||||||||||||||||||||||||||||||||
| 6 coding-exercise.src.exercises.exercise-03-useCallback-memoization | ||||||||||||||||||||||||||||||||||||||||
| 7 coding-exercise.src.exercises.exercise-04-custom-hooks | ||||||||||||||||||||||||||||||||||||||||
| 8 coding-hooks.src | ||||||||||||||||||||||||||||||||||||||||
| 9 coding-hooks.src.hooks.01-usePrevious | ||||||||||||||||||||||||||||||||||||||||
| 10 coding-hooks.src.hooks.02-useDebounce | ||||||||||||||||||||||||||||||||||||||||
| 11 coding-hooks.src.hooks.03-useDebounceCallback | ||||||||||||||||||||||||||||||||||||||||
| 12 coding-hooks.src.hooks.04-useToggle | ||||||||||||||||||||||||||||||||||||||||
| 13 coding-hooks.src.hooks.05-useInterval | ||||||||||||||||||||||||||||||||||||||||
| 14 coding-projects.accordion-app.src.types.accordion | ||||||||||||||||||||||||||||||||||||||||
| 15 coding-projects.data-table-app.src.components.DataTable | ||||||||||||||||||||||||||||||||||||||||
| 16 coding-projects.data-table-app.src.components.Pagination | ||||||||||||||||||||||||||||||||||||||||
| 17 coding-projects.data-table-app.src.components.SearchBar | ||||||||||||||||||||||||||||||||||||||||
| 18 coding-projects.infinite-scroll-app.src.types.post | ||||||||||||||||||||||||||||||||||||||||
| 19 coding-projects.nested-comments.src.components.Comment | ||||||||||||||||||||||||||||||||||||||||
| 20 coding-projects.nested-comments.src.components.CommentForm | ||||||||||||||||||||||||||||||||||||||||
| 21 coding-projects.nested-comments.src.components.CommentList | ||||||||||||||||||||||||||||||||||||||||
| 22 coding-projects.react-modal.src.components.Modal | ||||||||||||||||||||||||||||||||||||||||
| 23 coding-projects.shopping-cart.src.components.Cart | ||||||||||||||||||||||||||||||||||||||||
| 24 coding-projects.shopping-cart.src.types.product | ||||||||||||||||||||||||||||||||||||||||
| 25 coding-projects.star-rating.src.components.StarRating | ||||||||||||||||||||||||||||||||||||||||
| 26 coding-projects.theme-switcher.src.context.ThemeContext | ||||||||||||||||||||||||||||||||||||||||
| 27 coding-projects.tree-view-app.src.components.Tree | ||||||||||||||||||||||||||||||||||||||||
| 28 coding-projects.tree-view-app.src.types.tree | ||||||||||||||||||||||||||||||||||||||||
| 29 coding-projects.accordion-app.src.components | 2 | |||||||||||||||||||||||||||||||||||||||
| 30 coding-projects.data-table-app.src.components | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 31 coding-projects.infinite-scroll-app.src.components.PostCard | 1 | |||||||||||||||||||||||||||||||||||||||
| 32 coding-projects.nested-comments.src.components | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 33 coding-projects.react-modal.src.components | 1 | |||||||||||||||||||||||||||||||||||||||
| 34 coding-projects.shopping-cart.src.components.ProductCard | 1 | |||||||||||||||||||||||||||||||||||||||
| 35 coding-projects.star-rating.src.components | 1 | |||||||||||||||||||||||||||||||||||||||
| 36 coding-projects.theme-switcher.src.context | 1 | |||||||||||||||||||||||||||||||||||||||
| 37 coding-projects.tree-view-app.src.components.TreeNode | 1 | |||||||||||||||||||||||||||||||||||||||
| 38 coding-projects.infinite-scroll-app.src.components | 1 | |||||||||||||||||||||||||||||||||||||||
| 39 coding-projects.shopping-cart.src.components | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 40 coding-projects.tree-view-app.src.components | 1 | 1 |
29→14 coding-projects.accordion-app.src.components uses coding-projects.accordion-app.src.types.accordion✕
- Connections
- 2 pairs of types, where a type in coding-projects.accordion-app.src.components uses a type in coding-projects.accordion-app.src.types.accordion.
- The types involved
coding-projects.accordion-app.src.components.Accordion→coding-projects.accordion-app.src.types.accordion.AccordionPropscoding-projects.accordion-app.src.components.AccordionItem→coding-projects.accordion-app.src.types.accordion.AccordionItemProps
- Direction
- coding-projects.accordion-app.src.components uses coding-projects.accordion-app.src.types.accordion, so a change to coding-projects.accordion-app.src.types.accordion can break coding-projects.accordion-app.src.components, while a change to coding-projects.accordion-app.src.components can't break coding-projects.accordion-app.src.types.accordion.
- Position
- Below the diagonal: coding-projects.accordion-app.src.components uses a module listed above it, which is the healthy direction.
30→15 coding-projects.data-table-app.src.components uses coding-projects.data-table-app.src.components.DataTable✕
- Connections
- 1 pair of types, where a type in coding-projects.data-table-app.src.components uses a type in coding-projects.data-table-app.src.components.DataTable.
- The types involved
coding-projects.data-table-app.src.components.DataTable→coding-projects.data-table-app.src.components.DataTable.DataTableProps
- Direction
- coding-projects.data-table-app.src.components uses coding-projects.data-table-app.src.components.DataTable, so a change to coding-projects.data-table-app.src.components.DataTable can break coding-projects.data-table-app.src.components, while a change to coding-projects.data-table-app.src.components can't break coding-projects.data-table-app.src.components.DataTable.
- Position
- Below the diagonal: coding-projects.data-table-app.src.components uses a module listed above it, which is the healthy direction.
30→16 coding-projects.data-table-app.src.components uses coding-projects.data-table-app.src.components.Pagination✕
- Connections
- 1 pair of types, where a type in coding-projects.data-table-app.src.components uses a type in coding-projects.data-table-app.src.components.Pagination.
- The types involved
coding-projects.data-table-app.src.components.Pagination→coding-projects.data-table-app.src.components.Pagination.PaginationProps
- Direction
- coding-projects.data-table-app.src.components uses coding-projects.data-table-app.src.components.Pagination, so a change to coding-projects.data-table-app.src.components.Pagination can break coding-projects.data-table-app.src.components, while a change to coding-projects.data-table-app.src.components can't break coding-projects.data-table-app.src.components.Pagination.
- Position
- Below the diagonal: coding-projects.data-table-app.src.components uses a module listed above it, which is the healthy direction.
30→17 coding-projects.data-table-app.src.components uses coding-projects.data-table-app.src.components.SearchBar✕
- Connections
- 1 pair of types, where a type in coding-projects.data-table-app.src.components uses a type in coding-projects.data-table-app.src.components.SearchBar.
- The types involved
coding-projects.data-table-app.src.components.SearchBar→coding-projects.data-table-app.src.components.SearchBar.SearchBarProps
- Direction
- coding-projects.data-table-app.src.components uses coding-projects.data-table-app.src.components.SearchBar, so a change to coding-projects.data-table-app.src.components.SearchBar can break coding-projects.data-table-app.src.components, while a change to coding-projects.data-table-app.src.components can't break coding-projects.data-table-app.src.components.SearchBar.
- Position
- Below the diagonal: coding-projects.data-table-app.src.components uses a module listed above it, which is the healthy direction.
31→18 coding-projects.infinite-scroll-app.src.components.PostCard uses coding-projects.infinite-scroll-app.src.types.post✕
- Connections
- 1 pair of types, where a type in coding-projects.infinite-scroll-app.src.components.PostCard uses a type in coding-projects.infinite-scroll-app.src.types.post.
- The types involved
coding-projects.infinite-scroll-app.src.components.PostCard.PostCardProps→coding-projects.infinite-scroll-app.src.types.post.Post
- Direction
- coding-projects.infinite-scroll-app.src.components.PostCard uses coding-projects.infinite-scroll-app.src.types.post, so a change to coding-projects.infinite-scroll-app.src.types.post can break coding-projects.infinite-scroll-app.src.components.PostCard, while a change to coding-projects.infinite-scroll-app.src.components.PostCard can't break coding-projects.infinite-scroll-app.src.types.post.
- Position
- Below the diagonal: coding-projects.infinite-scroll-app.src.components.PostCard uses a module listed above it, which is the healthy direction.
32→19 coding-projects.nested-comments.src.components uses coding-projects.nested-comments.src.components.Comment✕
- Connections
- 1 pair of types, where a type in coding-projects.nested-comments.src.components uses a type in coding-projects.nested-comments.src.components.Comment.
- The types involved
coding-projects.nested-comments.src.components.Comment→coding-projects.nested-comments.src.components.Comment.CommentProps
- Direction
- coding-projects.nested-comments.src.components uses coding-projects.nested-comments.src.components.Comment, so a change to coding-projects.nested-comments.src.components.Comment can break coding-projects.nested-comments.src.components, while a change to coding-projects.nested-comments.src.components can't break coding-projects.nested-comments.src.components.Comment.
- Position
- Below the diagonal: coding-projects.nested-comments.src.components uses a module listed above it, which is the healthy direction.
32→20 coding-projects.nested-comments.src.components uses coding-projects.nested-comments.src.components.CommentForm✕
- Connections
- 1 pair of types, where a type in coding-projects.nested-comments.src.components uses a type in coding-projects.nested-comments.src.components.CommentForm.
- The types involved
coding-projects.nested-comments.src.components.CommentForm→coding-projects.nested-comments.src.components.CommentForm.CommentForm
- Direction
- coding-projects.nested-comments.src.components uses coding-projects.nested-comments.src.components.CommentForm, so a change to coding-projects.nested-comments.src.components.CommentForm can break coding-projects.nested-comments.src.components, while a change to coding-projects.nested-comments.src.components can't break coding-projects.nested-comments.src.components.CommentForm.
- Position
- Below the diagonal: coding-projects.nested-comments.src.components uses a module listed above it, which is the healthy direction.
32→21 coding-projects.nested-comments.src.components uses coding-projects.nested-comments.src.components.CommentList✕
- Connections
- 1 pair of types, where a type in coding-projects.nested-comments.src.components uses a type in coding-projects.nested-comments.src.components.CommentList.
- The types involved
coding-projects.nested-comments.src.components.CommentList→coding-projects.nested-comments.src.components.CommentList.CommentListProps
- Direction
- coding-projects.nested-comments.src.components uses coding-projects.nested-comments.src.components.CommentList, so a change to coding-projects.nested-comments.src.components.CommentList can break coding-projects.nested-comments.src.components, while a change to coding-projects.nested-comments.src.components can't break coding-projects.nested-comments.src.components.CommentList.
- Position
- Below the diagonal: coding-projects.nested-comments.src.components uses a module listed above it, which is the healthy direction.
33→22 coding-projects.react-modal.src.components uses coding-projects.react-modal.src.components.Modal✕
- Connections
- 1 pair of types, where a type in coding-projects.react-modal.src.components uses a type in coding-projects.react-modal.src.components.Modal.
- The types involved
coding-projects.react-modal.src.components.Modal→coding-projects.react-modal.src.components.Modal.ModalProps
- Direction
- coding-projects.react-modal.src.components uses coding-projects.react-modal.src.components.Modal, so a change to coding-projects.react-modal.src.components.Modal can break coding-projects.react-modal.src.components, while a change to coding-projects.react-modal.src.components can't break coding-projects.react-modal.src.components.Modal.
- Position
- Below the diagonal: coding-projects.react-modal.src.components uses a module listed above it, which is the healthy direction.
34→24 coding-projects.shopping-cart.src.components.ProductCard uses coding-projects.shopping-cart.src.types.product✕
- Connections
- 1 pair of types, where a type in coding-projects.shopping-cart.src.components.ProductCard uses a type in coding-projects.shopping-cart.src.types.product.
- The types involved
coding-projects.shopping-cart.src.components.ProductCard.ProductCardProps→coding-projects.shopping-cart.src.types.product.Product
- Direction
- coding-projects.shopping-cart.src.components.ProductCard uses coding-projects.shopping-cart.src.types.product, so a change to coding-projects.shopping-cart.src.types.product can break coding-projects.shopping-cart.src.components.ProductCard, while a change to coding-projects.shopping-cart.src.components.ProductCard can't break coding-projects.shopping-cart.src.types.product.
- Position
- Below the diagonal: coding-projects.shopping-cart.src.components.ProductCard uses a module listed above it, which is the healthy direction.
35→25 coding-projects.star-rating.src.components uses coding-projects.star-rating.src.components.StarRating✕
- Connections
- 1 pair of types, where a type in coding-projects.star-rating.src.components uses a type in coding-projects.star-rating.src.components.StarRating.
- The types involved
coding-projects.star-rating.src.components.StarRating→coding-projects.star-rating.src.components.StarRating.StarRatingProps
- Direction
- coding-projects.star-rating.src.components uses coding-projects.star-rating.src.components.StarRating, so a change to coding-projects.star-rating.src.components.StarRating can break coding-projects.star-rating.src.components, while a change to coding-projects.star-rating.src.components can't break coding-projects.star-rating.src.components.StarRating.
- Position
- Below the diagonal: coding-projects.star-rating.src.components uses a module listed above it, which is the healthy direction.
36→26 coding-projects.theme-switcher.src.context uses coding-projects.theme-switcher.src.context.ThemeContext✕
- Connections
- 1 pair of types, where a type in coding-projects.theme-switcher.src.context uses a type in coding-projects.theme-switcher.src.context.ThemeContext.
- The types involved
coding-projects.theme-switcher.src.context.ThemeContext→coding-projects.theme-switcher.src.context.ThemeContext.ThemeProviderProps
- Direction
- coding-projects.theme-switcher.src.context uses coding-projects.theme-switcher.src.context.ThemeContext, so a change to coding-projects.theme-switcher.src.context.ThemeContext can break coding-projects.theme-switcher.src.context, while a change to coding-projects.theme-switcher.src.context can't break coding-projects.theme-switcher.src.context.ThemeContext.
- Position
- Below the diagonal: coding-projects.theme-switcher.src.context uses a module listed above it, which is the healthy direction.
37→28 coding-projects.tree-view-app.src.components.TreeNode uses coding-projects.tree-view-app.src.types.tree✕
- Connections
- 1 pair of types, where a type in coding-projects.tree-view-app.src.components.TreeNode uses a type in coding-projects.tree-view-app.src.types.tree.
- The types involved
coding-projects.tree-view-app.src.components.TreeNode.TreeNodeProps→coding-projects.tree-view-app.src.types.tree.TreeNodeType
- Direction
- coding-projects.tree-view-app.src.components.TreeNode uses coding-projects.tree-view-app.src.types.tree, so a change to coding-projects.tree-view-app.src.types.tree can break coding-projects.tree-view-app.src.components.TreeNode, while a change to coding-projects.tree-view-app.src.components.TreeNode can't break coding-projects.tree-view-app.src.types.tree.
- Position
- Below the diagonal: coding-projects.tree-view-app.src.components.TreeNode uses a module listed above it, which is the healthy direction.
38→31 coding-projects.infinite-scroll-app.src.components uses coding-projects.infinite-scroll-app.src.components.PostCard✕
- Connections
- 1 pair of types, where a type in coding-projects.infinite-scroll-app.src.components uses a type in coding-projects.infinite-scroll-app.src.components.PostCard.
- The types involved
coding-projects.infinite-scroll-app.src.components.PostCard→coding-projects.infinite-scroll-app.src.components.PostCard.PostCardProps
- Direction
- coding-projects.infinite-scroll-app.src.components uses coding-projects.infinite-scroll-app.src.components.PostCard, so a change to coding-projects.infinite-scroll-app.src.components.PostCard can break coding-projects.infinite-scroll-app.src.components, while a change to coding-projects.infinite-scroll-app.src.components can't break coding-projects.infinite-scroll-app.src.components.PostCard.
- Position
- Below the diagonal: coding-projects.infinite-scroll-app.src.components uses a module listed above it, which is the healthy direction.
39→23 coding-projects.shopping-cart.src.components uses coding-projects.shopping-cart.src.components.Cart✕
- Connections
- 1 pair of types, where a type in coding-projects.shopping-cart.src.components uses a type in coding-projects.shopping-cart.src.components.Cart.
- The types involved
coding-projects.shopping-cart.src.components.Cart→coding-projects.shopping-cart.src.components.Cart.CartProps
- Direction
- coding-projects.shopping-cart.src.components uses coding-projects.shopping-cart.src.components.Cart, so a change to coding-projects.shopping-cart.src.components.Cart can break coding-projects.shopping-cart.src.components, while a change to coding-projects.shopping-cart.src.components can't break coding-projects.shopping-cart.src.components.Cart.
- Position
- Below the diagonal: coding-projects.shopping-cart.src.components uses a module listed above it, which is the healthy direction.
39→34 coding-projects.shopping-cart.src.components uses coding-projects.shopping-cart.src.components.ProductCard✕
- Connections
- 1 pair of types, where a type in coding-projects.shopping-cart.src.components uses a type in coding-projects.shopping-cart.src.components.ProductCard.
- The types involved
coding-projects.shopping-cart.src.components.ProductCard→coding-projects.shopping-cart.src.components.ProductCard.ProductCardProps
- Direction
- coding-projects.shopping-cart.src.components uses coding-projects.shopping-cart.src.components.ProductCard, so a change to coding-projects.shopping-cart.src.components.ProductCard can break coding-projects.shopping-cart.src.components, while a change to coding-projects.shopping-cart.src.components can't break coding-projects.shopping-cart.src.components.ProductCard.
- Position
- Below the diagonal: coding-projects.shopping-cart.src.components uses a module listed above it, which is the healthy direction.
40→27 coding-projects.tree-view-app.src.components uses coding-projects.tree-view-app.src.components.Tree✕
- Connections
- 1 pair of types, where a type in coding-projects.tree-view-app.src.components uses a type in coding-projects.tree-view-app.src.components.Tree.
- The types involved
coding-projects.tree-view-app.src.components.Tree→coding-projects.tree-view-app.src.components.Tree.TreeProps
- Direction
- coding-projects.tree-view-app.src.components uses coding-projects.tree-view-app.src.components.Tree, so a change to coding-projects.tree-view-app.src.components.Tree can break coding-projects.tree-view-app.src.components, while a change to coding-projects.tree-view-app.src.components can't break coding-projects.tree-view-app.src.components.Tree.
- Position
- Below the diagonal: coding-projects.tree-view-app.src.components uses a module listed above it, which is the healthy direction.
40→37 coding-projects.tree-view-app.src.components uses coding-projects.tree-view-app.src.components.TreeNode✕
- Connections
- 1 pair of types, where a type in coding-projects.tree-view-app.src.components uses a type in coding-projects.tree-view-app.src.components.TreeNode.
- The types involved
coding-projects.tree-view-app.src.components.TreeNode→coding-projects.tree-view-app.src.components.TreeNode.TreeNodeProps
- Direction
- coding-projects.tree-view-app.src.components uses coding-projects.tree-view-app.src.components.TreeNode, so a change to coding-projects.tree-view-app.src.components.TreeNode can break coding-projects.tree-view-app.src.components, while a change to coding-projects.tree-view-app.src.components can't break coding-projects.tree-view-app.src.components.TreeNode.
- Position
- Below the diagonal: coding-projects.tree-view-app.src.components uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 100 | High / Critical |
Roadmap
Top priorities: Add a CI workflow that builds and runs the test suite on every push/PR; Add tests that import the unreached modules (directly or through their public entry); Resolve the 1 No ADRs found finding(s) in ADR Quality — start with package.json.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Add a CI workflow that builds and runs the test suite on every push/PR. | +7.0 pts | Medium | CI/CD gates |
| Add tests that import the unreached modules (directly or through their public entry). | +5.4 pts | Medium | Test Coverage |
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with package.json. | +2.3 pts | Low | ADR Quality |
| Resolve the 8 Orphaned file finding(s) in Knowledge Freshness — start with Solution.js (5), Problem.js (2), ExerciseCard.js. | +1.9 pts | Low | Knowledge Freshness |
| Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. | +2.0 pts | Medium | Keyboard semantics |
| 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. | +2.0 pts | Medium | Architecture documentation |
| Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label. | +1.5 pts | Medium | Forms & labels |
| 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 `?`). | +1.2 pts | Medium | Nullable reference types |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 2.7 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 2.7 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 5.8 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 5.8 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 5.8 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 5.8 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 5.8 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 5.8 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 5.8 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 5.8 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 5.8 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 5.8 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 5.8 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| coding-projects/autocomplete-app/src/App.tsx | 8.5 | Near-clean | Cyclomatic Complexity: App.App (cyclomatic 18) |
| coding-exercise/src/exercises/exercise-03-useCallback-memoization/Solution.js | 8.5 | Near-clean | God Classes: FunctionTooLong: Solution.Solution |
| coding-exercise/src/exercises/exercise-04-custom-hooks/Solution.js | 8.5 | Near-clean | God Classes: FunctionTooLong: Solution.Solution |
| coding-exercise/src/exercises/exercise-02-useeffect-dependencies/Solution.js | 8.5 | Near-clean | God Classes: FunctionTooLong: Solution.Solution |
How the grades work
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.
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.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 58 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 58 dimensions across the health lenses
- 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, 217 of 230 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- 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. All 14 significant source file(s) were last meaningfully changed so long ago that no living knowledge remains — nothing since has been substantial enough to re-establish ownership (a broad, mechanical sweep that touches many files shallowly does not count, and neither does no activity at all). There is no concentration to measure, so the bus factor is not scored. This is not a clean bill: nobody currently holds working knowledge of this code (see D34 Knowledge Freshness). Counted over 13 of the 122 production source files in this repository: 108 are under the ~2,400-byte size floor this dimension measures over, and the remaining 1 have no attributable history left to measure.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 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: 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.
- D44 Platform End-of-Life — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This 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.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (start). the dev server (`npm run start`) exited before it served a page. Likely cause (the repository): package.json has no "start" script, so `npm run start` could not start the app. Last output: "npm error Missing script: "start" / npm error / npm error Did you mean one of these? / npm error npm star # Mark your favorite packages / npm error npm stars # View packages marked as favorites / npm error / npm error To see a list of scripts, run: / npm error npm run / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- R4 Test Coverage — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 32 further occurrence(s) are not listed individually; the score already reflects all 72.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala 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.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- 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.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our 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.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- 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 publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- 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.
- 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.
Dimensions
D1 · Cyclomatic Complexity
1 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was App.App at 18.
What to do
- Bring the 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with App.App (cyclomatic 18). — Refactoring it lifts Cyclomatic Complexity from 9.7 to about 10.0/10.
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
6 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 6 FunctionTooLong finding(s) in God Classes — start with Solution.js (4), App.tsx (2). — One of this dimension's main actionable groups (6 warning-level).
D5 · Coupling
15 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, with abstractness counted on 14 of the 15 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
D8 · Code Coverage
Line coverage 90.0%. Measured from the JavaScript/TypeScript suite (jest via `npm ci --ignore-scripts` in coding-projects/star-rating/).
D10 · Test Quality
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 5 tests.
D11 · Test Reliability
0 flaky across 1 measured tier(s). JavaScript/TypeScript (jest via `npm ci --ignore-scripts` in coding-projects/star-rating/ (4 tests)): measured (0 flaky).
D12 · Dependency Hygiene
4 outdated direct production npm dependency(ies) of 6 graded, 0 pinning defect(s), across 16 package.json (16 of them the product) and 17 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 0 direct dependency(ies) — production, development or optional — are marked DEPRECATED by their publisher (the registry's per-version mark, or the lockfile's copy of it when the registry could not be asked); deprecated transitive packages are listed but not charged. Whether any is UNMAINTAINED is not graded — the registry publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, and the frontend dependency lens (R8) answers it in this same run. Known CVEs in this dependency graph are D30's question, read from the manifest there.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 1110 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 1110 package(s) this repository's committed lockfile installs for a consumer — its 6 production, optional and peer dependency(ies), across 16 product package.json manifest(s), and everything those install in turn. Its 117 `devDependencies` declaration(s), and every package only they reach, are excluded: a consumer installs none of them. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
0 deducted task-comment markers across 1955 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.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 16 document(s) read across 16 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with package.json. — One of this dimension's main actionable groups (1 recommendation-level).
D24 · Comment Value
0 of 50 judged comments only repeat the code they sit on (0.0 %). 1 comment(s) in another language or script were not judged.
D26 · Project Cohesion
0 of 15 build units (npm) flagged as possibly oversized/incoherent.
D27 · Navigability
2 % of calls cross a namespace and 0 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
semgrep found no security issues.
D30 · Dependency Vulnerabilities
100 finding(s): 5 critical, 72 high, 16 medium, 7 low.
What to do
- Resolve the 68 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (51), REDACTED (17). — One of this dimension's main actionable groups (68 issue-level).
- Resolve the 5 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3), REDACTED (2). — One of this dimension's main actionable groups (5 issue-level).
- Resolve the 4 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (4 issue-level).
D34 · Knowledge Freshness
8 of 14 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is coding-exercise/src/exercises/exercise-04-custom-hooks/Solution.js. Counted over 14 of the 122 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 8 Orphaned file finding(s) in Knowledge Freshness — start with Solution.js (5), Problem.js (2), ExerciseCard.js. — One of this dimension's main actionable groups (8 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
Frontend & cross-cutting dimensions
AC1 · Text alternatives
AC2 · Forms & labels
- This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×4) — coding-hooks/src/hooks/02-useDebounce/App.tsx:13, coding-hooks/src/hooks/03-useDebounceCallback/App.tsx:20, coding-hooks/src/hooks/06-useLocalStorage/App.tsx:10, …
- 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. (×4) — coding-projects/autocomplete-app/src/App.tsx:88, coding-projects/data-table-app/src/components/SearchBar.tsx:8, coding-projects/nested-comments/src/components/CommentForm.tsx:23, …
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 structure
- The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). — coding-exercise/hooks/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 semantics
- 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}. — coding-projects/autocomplete-app/src/App.tsx:106
- A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler. — coding-projects/tree-view-app/src/components/TreeNode.tsx:22
What to do
- Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC5 · ARIA correctness
AC6 · Visual & motion safety
- `.loading, .no-results` sets color: #777 on background-color: white — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — coding-projects/autocomplete-app/src/App.css:73
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.
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
M1 · Documentation (README)
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
P1 · CI/CD gates
- 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.
P3 · Security & performance tooling
- 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.
- `package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — package.json:2
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.
PF3 · Async & latency hygiene
R1 · Type Safety
R10 · Code Duplication
- coding-projects/carousel-app/src/App.tsx:1 · coding-projects/hacker-news-jobs/src/App.tsx:1 — these 2 files are line-for-line copies of one another — 94 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — coding-projects/carousel-app/src/App.tsx:1
- coding-exercise/src/exercises/exercise-04-custom-hooks/Problem.js:32 · coding-exercise/src/exercises/exercise-04-custom-hooks/Problem.js:66 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — coding-exercise/src/exercises/exercise-04-custom-hooks/Problem.js:32
- coding-exercise/src/exercises/exercise-03-useCallback-memoization/Solution.js:27 · coding-exercise/src/exercises/exercise-03-useCallback-memoization/Solution.js:38 · coding-exercise/src/exercises/exercise-03-useCallback-memoization/Solution.js:49 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. — coding-exercise/src/exercises/exercise-03-useCallback-memoization/Solution.js:27
- coding-exercise/src/exercises/exercise-04-custom-hooks/Solution.js:111 · coding-exercise/src/exercises/exercise-04-custom-hooks/Solution.js:130 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — coding-exercise/src/exercises/exercise-04-custom-hooks/Solution.js:111
- coding-exercise/src/exercises/exercise-01-state-batching/Solution.js:52 · coding-exercise/src/exercises/exercise-01-state-batching/Solution.js:61 — 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. — coding-exercise/src/exercises/exercise-01-state-batching/Solution.js:52
- coding-exercise/src/exercises/exercise-03-useCallback-memoization/Solution.js:254 · coding-exercise/src/exercises/exercise-03-useCallback-memoization/Solution.js:259 — 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. — coding-exercise/src/exercises/exercise-03-useCallback-memoization/Solution.js:254
- coding-exercise/src/exercises/exercise-04-custom-hooks/Solution.js:287 · coding-exercise/src/exercises/exercise-04-custom-hooks/Solution.js:292 · coding-exercise/src/exercises/exercise-04-custom-hooks/Solution.js:297 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. — coding-exercise/src/exercises/exercise-04-custom-hooks/Solution.js:287
- coding-exercise/src/exercises/exercise-04-custom-hooks/Solution.js:296 · coding-exercise/src/exercises/exercise-04-custom-hooks/Solution.js:301 — 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. — coding-exercise/src/exercises/exercise-04-custom-hooks/Solution.js:296
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.
R2 · Cyclomatic Complexity
R3 · Large Files
R4 · Test Coverage
- No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×40) — coding-exercise/src/exercises/__template__/Solution.js:1, coding-exercise/src/serviceWorker.js:1, coding-projects/autocomplete-app/src/App.tsx:1, …
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness
R6 · Tooling
R7 · Dead Code
- Unreachable from the 16 application, 18 tooling and 3 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 (16 application, 18 tooling, 3 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (coding-exercise/src/exercises/__template__/index.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×2) — coding-exercise/src/exercises/__template__/Solution.js, coding-exercise/src/exercises/__template__/Problem.js
- no import path from any entry point (16 application, 18 tooling, 3 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 (×4) — coding-hooks/src/hooks/08-useThrottle/App.tsx, coding-exercise/src/exercises/__template__/index.js, coding-exercise/hooks/useDebounce.tsx, …
- no import path from any entry point (16 application, 18 tooling, 3 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (coding-hooks/src/hooks/08-useThrottle/App.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — coding-hooks/src/hooks/08-useThrottle/useThrottle.ts
- Nothing imports this binding — it is safe to review for removal. (×2) — coding-exercise/src/exercises/index.js:56, coding-exercise/src/serviceWorker.js:23
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 Hygiene
- Declared in coding-exercise/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.
- Declared in coding-projects/todo-app/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.
- Only test files import it (first: coding-exercise/src/App.test.js:2) — move it to devDependencies. — coding-exercise/package.json:7
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
S1 · Web-Security Posture
- `https://unpkg.com/react@18/umd/react.development.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. 3 such include(s) across the repository's markup. — coding-exercise/hooks/index.html:8
What to do
- Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
X1 · Async correctness
X12 · Unreachable branch
X2 · Cancellation propagation
- Only 1/2 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
- `getUsers` 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 })`. — coding-projects/data-table-app/src/services/userService.ts:4
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 guard
X3 · Exception handling
X5 · Nullable reference types
- 1/29 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
- ~6.1 `!` null assertions per 1k TypeScript source lines — 14 assertion(s) across the 2283 source line(s) of the 83 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: coding-hooks/src/main.tsx (1), coding-projects/accordion-app/src/main.tsx (1), coding-projects/autocomplete-app/src/main.tsx (1). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
What to do
- The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC1 · Text alternatives | 1.1.1, 1.2.2, 1.2.5 | Partial signal |
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC4 · Keyboard semantics | 2.1.1, 2.4.3 | Partial signal |
| AC5 · ARIA correctness | 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 63% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 98% | Exemplary | Solid. |
| Maturity | 63% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 38% | Weak — gated by R4, P1, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 89% | Strong | Solid. |
| Accessibility | 58% | Adequate — gated by AC4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 control(s) we could not find positive evidence for
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- 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 — 66 check(s) not relevant to this codebase
- AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — Not applicable: TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the dev server (`npm run start`) exited before it served a page. Likely cause (the repository): package.json has no "start" script, so `npm run start` could not start the app. Last output: "npm error Missing script: "start" / npm error / npm error Did you mean one of these? / npm error npm star # Mark your favorite packages / npm error npm stars # View packages marked as favorites / npm error / npm error To see a list of scripts, run: / npm error npm run / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no data at rest for these controls to protect. If it does persist personal data (through a hosted backend configured outside this repository, for instance), the controls belong to wherever that data is stored.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository stands up no server (no Express, Fastify, Koa, Hono, NestJS or similar app, no Next.js/SvelteKit/Nuxt server route, no edge function), creates no Supabase tables and talks to no hosted backend. Access control is therefore N/A here — a browser application or library is authorized by the server it calls, not by itself; a client-side route guard hides a page and authorizes nothing. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound. If it does (through a hosted backend configured outside this repository, for instance), the limit belongs wherever that data is stored.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over. If it does (through a hosted backend configured outside this repository, for instance), the rights are served wherever that data is stored.
- D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
- 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.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (224 declarations, no unit with a dominant convention).
- 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+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D25 ADR Conformance — no ADRs to check
- 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.
- 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
- D6 Cohesion (LCOM4) — No production classes were analyzable, so cohesion (LCOM4) was not measured (the solution likely failed to load or has no production code).
- 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 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- M4 Documentation accuracy — Not applicable: the 14 current-state document(s) make no claim of a kind M4 checks. 13 claim(s) of kinds M4 does not check were not checked (path 12, command argument 1); M4 checks only links and versions and artefact counts.
- P12 CI test-gate honesty — no CI workflow found
- P2 Observability — This repository's JavaScript/TypeScript source (15 module(s), 104 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage data present for 1 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X16 Unfloored truncation loop — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
- X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 88 finding(s)
- 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
- <input> without a programmatic label coding-hooks/src/hooks/02-useDebounce/App.tsx:13
- <input> without a programmatic label coding-hooks/src/hooks/03-useDebounceCallback/App.tsx:20
- <input> without a programmatic label coding-hooks/src/hooks/06-useLocalStorage/App.tsx:10
- <input> without a programmatic label coding-projects/autocomplete-app/src/App.tsx:88
- <input> without a programmatic label coding-projects/data-table-app/src/components/SearchBar.tsx:8
- <input> without a programmatic label coding-projects/nested-comments/src/components/CommentForm.tsx:23
- <input> without a programmatic label coding-projects/todo-app/src/components/TodoForm.tsx:21
- <input> without a programmatic label coding-projects/todo-app/src/components/TodoItem.tsx:38
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <html> without a lang coding-exercise/hooks/index.html:2
- Click handler on a non-interactive <li> coding-projects/autocomplete-app/src/App.tsx:106
- Click handler on a non-interactive <div> coding-projects/tree-view-app/src/components/TreeNode.tsx:22
Serious — 84 finding(s)
- No test reaches this file coding-exercise/src/exercises/__template__/Solution.js:1
- No test reaches this file coding-exercise/src/serviceWorker.js:1
- No test reaches this file coding-projects/autocomplete-app/src/App.tsx:1
- No test reaches this file coding-projects/carousel-app/src/App.tsx:1
- No test reaches this file coding-projects/hacker-news-jobs/src/App.tsx:1
- No test reaches this file coding-projects/infinite-scroll-app/src/components/InfinitePosts.tsx:1
- No test reaches this file coding-projects/data-table-app/src/App.tsx:1
- No test reaches this file coding-projects/shopping-cart/src/App.tsx:1
- No test reaches this file coding-projects/nested-comments/src/App.tsx:1
- No test reaches this file coding-hooks/src/App.tsx:1
- No test reaches this file coding-exercise/src/exercises/__template__/Problem.js:1
- No test reaches this file coding-projects/todo-app/src/components/TodoItem.tsx:1
- No test reaches this file coding-projects/react-modal/src/components/Modal.tsx:1
- No test reaches this file coding-projects/tree-view-app/src/components/TreeNode.tsx:1
- No test reaches this file coding-projects/todo-app/src/App.tsx:1
- No test reaches this file coding-projects/nested-comments/src/components/Comment.tsx:1
- No test reaches this file coding-projects/data-table-app/src/components/DataTable.tsx:1
- No test reaches this file coding-projects/shopping-cart/src/components/Cart.tsx:1
- No test reaches this file coding-projects/theme-switcher/src/context/ThemeContext.tsx:1
- No test reaches this file coding-hooks/src/hooks/03-useDebounceCallback/useDebounceCallback.ts:1
- No test reaches this file coding-projects/accordion-app/src/components/Accordion.tsx:1
- No test reaches this file coding-projects/accordion-app/src/components/AccordionItem.tsx:1
- No test reaches this file coding-projects/nested-comments/src/components/CommentForm.tsx:1
- No test reaches this file coding-hooks/src/hooks/03-useDebounceCallback/App.tsx:1
- No test reaches this file coding-projects/todo-app/src/components/TodoForm.tsx:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- FunctionTooLong: Solution.Solution coding-exercise/src/exercises/exercise-03-useCallback-memoization/Solution.js:59
- FunctionTooLong: Solution.Solution coding-exercise/src/exercises/exercise-04-custom-hooks/Solution.js:153
- FunctionTooLong: Solution.Solution coding-exercise/src/exercises/exercise-02-useeffect-dependencies/Solution.js:26
- FunctionTooLong: App.App coding-projects/carousel-app/src/App.tsx:7
- FunctionTooLong: App.App coding-projects/hacker-news-jobs/src/App.tsx:7
- FunctionTooLong: Solution.Solution coding-exercise/src/exercises/__template__/Solution.js:22
- Duplicated block (5 lines × 2 locations) coding-exercise/src/exercises/exercise-03-useCallback-memoization/Solution.js:254
- Duplicated block (5 lines × 2 locations) coding-exercise/src/exercises/exercise-04-custom-hooks/Solution.js:296
- Dead file (~0 LoC) coding-exercise/hooks/useDebounce.tsx
- Dead file (~0 LoC) coding-projects/carousel-app/src/components/Carousel.tsx
- Low contrast colour pair in CSS (4.4:1) coding-projects/autocomplete-app/src/App.css:73
- App.App (cyclomatic 18) coding-projects/autocomplete-app/src/App.tsx:5
- No CI pipeline
- Wholesale file copy (94 identical lines × 2 files) coding-projects/carousel-app/src/App.tsx:1
- Duplicated block (12 lines × 2 locations) coding-exercise/src/exercises/exercise-04-custom-hooks/Problem.js:32
- Duplicated block (9 lines × 3 locations) coding-exercise/src/exercises/exercise-03-useCallback-memoization/Solution.js:27
- Duplicated block (7 lines × 2 locations) coding-exercise/src/exercises/exercise-04-custom-hooks/Solution.js:111
- Duplicated block (6 lines × 2 locations) coding-exercise/src/exercises/exercise-01-state-batching/Solution.js:52
- Duplicated block (5 lines × 3 locations) coding-exercise/src/exercises/exercise-04-custom-hooks/Solution.js:287
- Dead file (~143 LoC) coding-exercise/src/exercises/__template__/Solution.js
- Dead file (~53 LoC) coding-exercise/src/exercises/__template__/Problem.js
- Dead file (~26 LoC) coding-hooks/src/hooks/08-useThrottle/App.tsx
- Dead file (~21 LoC) coding-hooks/src/hooks/08-useThrottle/useThrottle.ts
- Dead file (~2 LoC) coding-exercise/src/exercises/__template__/index.js
- Unused dependency '@testing-library/user-event'
- Unused dependency '@rolldown/binding-win32-x64-msvc'
- Third-party script without Subresource Integrity coding-exercise/hooks/index.html:8
- Async function without AbortSignal: getUsers coding-projects/data-table-app/src/services/userService.ts:4
Minor — 54 finding(s)
- Deprecated: @babel/plugin-proposal-class-properties REDACTED:544
- Deprecated: @babel/plugin-proposal-nullish-coalescing-operator REDACTED:578
- Deprecated: @babel/plugin-proposal-numeric-separator REDACTED:595
- Deprecated: @babel/plugin-proposal-optional-chaining REDACTED:612
- Deprecated: @babel/plugin-proposal-private-methods REDACTED:630
- Deprecated: @humanwhocodes/config-array REDACTED:2484
- Deprecated: @humanwhocodes/object-schema REDACTED:2512
- Deprecated: abab REDACTED:4217
- Deprecated: @babel/plugin-proposal-private-property-in-object REDACTED:5014
- Deprecated: domexception REDACTED:6664
- Deprecated: eslint REDACTED:7114
- Deprecated: glob REDACTED:8552
- Deprecated: inflight REDACTED:9207
- Deprecated: mkdirp REDACTED:11466
- Deprecated: q REDACTED:13581
- Deprecated: rimraf REDACTED:14283
- Deprecated: rollup-plugin-terser REDACTED:14314
- Deprecated: sourcemap-codec REDACTED:14986
- Deprecated: stable REDACTED:15029
- Deprecated: svgo REDACTED:15456
- Deprecated: uuid REDACTED:16442
- Deprecated: w3c-hr-time REDACTED:16481
- Deprecated: whatwg-encoding REDACTED:16766
- Deprecated: workbox-cacheable-response REDACTED:17052
- Deprecated: workbox-google-analytics REDACTED:17078
- Orphaned file coding-exercise/src/exercises/exercise-04-custom-hooks/Solution.js:1
- Orphaned file coding-exercise/src/exercises/exercise-03-useCallback-memoization/Solution.js:1
- Orphaned file coding-exercise/src/exercises/exercise-02-useeffect-dependencies/Solution.js:1
- Orphaned file coding-exercise/src/exercises/exercise-01-state-batching/Solution.js:1
- Orphaned file coding-exercise/src/exercises/exercise-04-custom-hooks/Problem.js:1
- Orphaned file coding-exercise/src/exercises/__template__/Solution.js:1
- Orphaned file coding-exercise/src/components/ExerciseCard.js:1
- Orphaned file coding-exercise/src/exercises/exercise-03-useCallback-memoization/Problem.js:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs found coding-projects/tree-view-app/package.json:7
- Orphaned files with no living knowledge
- No ADRs
- No SAST
- No dependency-update automation package.json:2
- Unused export 'default' coding-exercise/src/exercises/index.js:56
- Unused export 'register' coding-exercise/src/serviceWorker.js:23
- Test-only dependency '@testing-library/react' in production deps coding-exercise/package.json:7
- Not all async functions that make a request accept an AbortSignal
- Strict null checking is not enabled everywhere the repository type-checks
- Null assertions (`!`) override strict null checking
- Pending state with no failure state coding-hooks/src/hooks/07-useFetch/App.tsx:11
Minor — 4 finding(s)
- Outdated (npm): @testing-library/jest-dom
- Outdated (npm): @testing-library/user-event
- Outdated (npm): react
- Outdated (npm): react-dom
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-4f935e4cd25f4e41a8b1ebea3570d717/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-4f935e4cd25f4e41a8b1ebea3570d717/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 0 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 100 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D36 · Supply-chain Provenance & Signing | provenance | — | 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 Policy | disclosure | — | 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 Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |