Executive summary
mpanaryin/job_scope is rated At risk because critical security findings are open. 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 44 out of 100, which the At risk rating leaves unchanged. We judged it as a template or a sample, against a lower bar.
Production Readiness, at 28, is the weakest lens and counts most in the score. The best first step is replacing each retired release, worth about 7 points. Adding an automated build and test pipeline would lift Production Readiness itself, worth about 5 points. Raising Production Readiness to 52 would lift the score to about 52.
Three known security holes in the packages the code depends on can be used by attackers. Three settings leave the servers or containers unsafe, and one package carries licence risk. Updating the vulnerable packages, correcting the unsafe settings and replacing or clearing the banned-licence packages would close these risks. The page that blocks zooming needs the zoom block removed.
The product code is 5,009 lines, about €6,700 to rebuild.
If Production Readiness rose from 28 to 52, the lowest score rated Strong, the score would rise from 44 to about 52.
New since the last survey: 1 finding
- Visual & motion safety · Low contrast colour pair in CSS (4.2:1) static/css/prism-themes/prism-vsc-dark-plus.css
Fixed since the last survey: 37 findings
- Visual & motion safety · Animation without a prefers-reduced-motion guard static/css/animate.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard static/css/animate.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard static/css/animate.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard static/css/animate.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard static/css/animate.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard static/css/animate.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard static/css/animate.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard static/css/animate.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard static/css/animate.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard static/css/animate.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard static/css/animate.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard static/css/animate.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard static/css/animate.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard static/css/animate.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard static/css/animate.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard static/css/animate.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard static/css/animate.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard static/css/animate.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard static/css/animate.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard static/css/animate.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard static/css/animate.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard static/css/animate.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard static/css/animate.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard static/css/animate.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard static/css/animate.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard static/css/animate.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard static/css/animate.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard static/css/animate.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard static/css/animate.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard static/css/animate.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard static/css/animate.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard static/css/animate.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard static/css/animate.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard static/css/animate.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard static/css/animate.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard static/css/animate.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard static/css/animate.css
Rebuild cost: about €6,700 · Estimate
| Cost to rebuild | €2,200 to €11,000, for 37 to 118 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | High, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 44. 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: 5,009 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 auth.domain.interfaces.token_provider | 2 auth.infrastructure.transports.base | 3 core.domain.entities | 4 core.domain.exceptions.exceptions | 5 crud.base | 6 db.base | 7 integrations.infrastructure.http.interfaces | 8 users.domain.interfaces.password_hasher | 9 vacancies.domain.interfaces.vacancy_source_client | 10 auth.domain.entities | 11 auth.presentation.dtos | 12 crud.router | 13 integrations.infrastructure.external_api.headhunter.schemas.request | 14 integrations.infrastructure.external_api.headhunter.schemas.response | 15 integrations.infrastructure.http.services.api_client | 16 users.domain.dtos | 17 users.domain.entities | 18 users.infrastructure.db.orm | 19 vacancies.domain.entities | 20 vacancies.domain.interfaces.vacancy_repo | 21 auth.domain.interfaces.token_auth | 22 auth.domain.interfaces.token_storage | 23 integrations.infrastructure.external_api.headhunter.adapter | 24 integrations.infrastructure.external_api.mappers.helpers | 25 users.domain.interfaces.user_repo | 26 users.infrastructure.db.crud | 27 vacancies.domain.dtos | 28 vacancies.domain.interfaces.vacancy_search_repo | 29 vacancies.domain.interfaces.vacancy_uow | 30 auth.infrastructure.services.jwt | 31 auth.infrastructure.services.redis_token_storage | 32 users.domain.interfaces.user_uow | 33 users.infrastructure.db.repositories | 34 vacancies.application.mappers.vacancies | 35 vacancies.application.use_cases | 36 vacancies.infrastructure.elastic.repositories | 37 auth.application.use_cases | 38 auth.presentation | 39 users.application.use_cases | 40 users.presentation |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 auth.domain.interfaces.token_provider | ||||||||||||||||||||||||||||||||||||||||
| 2 auth.infrastructure.transports.base | ||||||||||||||||||||||||||||||||||||||||
| 3 core.domain.entities | ||||||||||||||||||||||||||||||||||||||||
| 4 core.domain.exceptions.exceptions | ||||||||||||||||||||||||||||||||||||||||
| 5 crud.base | ||||||||||||||||||||||||||||||||||||||||
| 6 db.base | ||||||||||||||||||||||||||||||||||||||||
| 7 integrations.infrastructure.http.interfaces | ||||||||||||||||||||||||||||||||||||||||
| 8 users.domain.interfaces.password_hasher | ||||||||||||||||||||||||||||||||||||||||
| 9 vacancies.domain.interfaces.vacancy_source_client | ||||||||||||||||||||||||||||||||||||||||
| 10 auth.domain.entities | 2 | |||||||||||||||||||||||||||||||||||||||
| 11 auth.presentation.dtos | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 crud.router | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 integrations.infrastructure.external_api.headhunter.schemas.request | 4 | |||||||||||||||||||||||||||||||||||||||
| 14 integrations.infrastructure.external_api.headhunter.schemas.response | 16 | |||||||||||||||||||||||||||||||||||||||
| 15 integrations.infrastructure.http.services.api_client | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 users.domain.dtos | 3 | |||||||||||||||||||||||||||||||||||||||
| 17 users.domain.entities | 3 | |||||||||||||||||||||||||||||||||||||||
| 18 users.infrastructure.db.orm | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 vacancies.domain.entities | 12 | |||||||||||||||||||||||||||||||||||||||
| 20 vacancies.domain.interfaces.vacancy_repo | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 auth.domain.interfaces.token_auth | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 22 auth.domain.interfaces.token_storage | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 integrations.infrastructure.external_api.headhunter.adapter | 1 | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 24 integrations.infrastructure.external_api.mappers.helpers | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 25 users.domain.interfaces.user_repo | 3 | |||||||||||||||||||||||||||||||||||||||
| 26 users.infrastructure.db.crud | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 27 vacancies.domain.dtos | 3 | 2 | ||||||||||||||||||||||||||||||||||||||
| 28 vacancies.domain.interfaces.vacancy_search_repo | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 29 vacancies.domain.interfaces.vacancy_uow | 1 | |||||||||||||||||||||||||||||||||||||||
| 30 auth.infrastructure.services.jwt | 2 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 31 auth.infrastructure.services.redis_token_storage | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 32 users.domain.interfaces.user_uow | 1 | |||||||||||||||||||||||||||||||||||||||
| 33 users.infrastructure.db.repositories | 3 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 34 vacancies.application.mappers.vacancies | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 35 vacancies.application.use_cases | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 36 vacancies.infrastructure.elastic.repositories | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 37 auth.application.use_cases | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 38 auth.presentation | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 39 users.application.use_cases | 1 | 2 | 3 | 4 | ||||||||||||||||||||||||||||||||||||
| 40 users.presentation | 2 | 1 |
10→3 auth.domain.entities uses core.domain.entities✕
- Connections
- 2 pairs of types, where a type in auth.domain.entities uses a type in core.domain.entities.
- The types involved
backend.src.auth.domain.entities.AnonymousUser→backend.src.core.domain.entities.CustomModelbackend.src.auth.domain.entities.TokenData→backend.src.core.domain.entities.CustomModel
- Direction
- auth.domain.entities uses core.domain.entities, so a change to core.domain.entities can break auth.domain.entities, while a change to auth.domain.entities can't break core.domain.entities.
- Position
- Below the diagonal: auth.domain.entities uses a module listed above it, which is the healthy direction.
11→3 auth.presentation.dtos uses core.domain.entities✕
- Connections
- 1 pair of types, where a type in auth.presentation.dtos uses a type in core.domain.entities.
- The types involved
backend.src.auth.presentation.dtos.AuthUserDTO→backend.src.core.domain.entities.CustomModel
- Direction
- auth.presentation.dtos uses core.domain.entities, so a change to core.domain.entities can break auth.presentation.dtos, while a change to auth.presentation.dtos can't break core.domain.entities.
- Position
- Below the diagonal: auth.presentation.dtos uses a module listed above it, which is the healthy direction.
12→5 crud.router uses crud.base✕
- Connections
- 1 pair of types, where a type in crud.router uses a type in crud.base.
- The types involved
backend.src.crud.router.CRUDRouter→backend.src.crud.base.CRUDBase
- Direction
- crud.router uses crud.base, so a change to crud.base can break crud.router, while a change to crud.router can't break crud.base.
- Position
- Below the diagonal: crud.router uses a module listed above it, which is the healthy direction.
13→3 integrations.infrastructure.external_api.headhunter.schemas.request uses core.domain.entities✕
- Connections
- 4 pairs of types, where a type in integrations.infrastructure.external_api.headhunter.schemas.request uses a type in core.domain.entities.
- The types involved
backend.src.integrations.infrastructure.external_api.headhunter.schemas.request.HHAccessApplicationTokenParams→backend.src.core.domain.entities.CustomModelbackend.src.integrations.infrastructure.external_api.headhunter.schemas.request.HHAccessUserTokenParams→backend.src.core.domain.entities.CustomModelbackend.src.integrations.infrastructure.external_api.headhunter.schemas.request.HHRefreshTokenParams→backend.src.core.domain.entities.CustomModelbackend.src.integrations.infrastructure.external_api.headhunter.schemas.request.HHVacancySearchParams→backend.src.core.domain.entities.CustomModel
- Direction
- integrations.infrastructure.external_api.headhunter.schemas.request uses core.domain.entities, so a change to core.domain.entities can break integrations.infrastructure.external_api.headhunter.schemas.request, while a change to integrations.infrastructure.external_api.headhunter.schemas.request can't break core.domain.entities.
- Position
- Below the diagonal: integrations.infrastructure.external_api.headhunter.schemas.request uses a module listed above it, which is the healthy direction.
14→3 integrations.infrastructure.external_api.headhunter.schemas.response uses core.domain.entities✕
- Connections
- 16 pairs of types, where a type in integrations.infrastructure.external_api.headhunter.schemas.response uses a type in core.domain.entities.
- The types involved
backend.src.integrations.infrastructure.external_api.headhunter.schemas.response.HHAddress→backend.src.core.domain.entities.CustomModelbackend.src.integrations.infrastructure.external_api.headhunter.schemas.response.HHArea→backend.src.core.domain.entities.CustomModelbackend.src.integrations.infrastructure.external_api.headhunter.schemas.response.HHArgument→backend.src.core.domain.entities.CustomModelbackend.src.integrations.infrastructure.external_api.headhunter.schemas.response.HHClusterGroup→backend.src.core.domain.entities.CustomModelbackend.src.integrations.infrastructure.external_api.headhunter.schemas.response.HHEmployer→backend.src.core.domain.entities.CustomModelbackend.src.integrations.infrastructure.external_api.headhunter.schemas.response.HHEmployment→backend.src.core.domain.entities.CustomModelbackend.src.integrations.infrastructure.external_api.headhunter.schemas.response.HHExperience→backend.src.core.domain.entities.CustomModelbackend.src.integrations.infrastructure.external_api.headhunter.schemas.response.HHLogoUrl→backend.src.core.domain.entities.CustomModelbackend.src.integrations.infrastructure.external_api.headhunter.schemas.response.HHMetroStation→backend.src.core.domain.entities.CustomModelbackend.src.integrations.infrastructure.external_api.headhunter.schemas.response.HHProfessionalRole→backend.src.core.domain.entities.CustomModelbackend.src.integrations.infrastructure.external_api.headhunter.schemas.response.HHSalary→backend.src.core.domain.entities.CustomModelbackend.src.integrations.infrastructure.external_api.headhunter.schemas.response.HHSchedule→backend.src.core.domain.entities.CustomModelbackend.src.integrations.infrastructure.external_api.headhunter.schemas.response.HHSnippet→backend.src.core.domain.entities.CustomModelbackend.src.integrations.infrastructure.external_api.headhunter.schemas.response.HHType→backend.src.core.domain.entities.CustomModelbackend.src.integrations.infrastructure.external_api.headhunter.schemas.response.HHVacancy→backend.src.core.domain.entities.CustomModelbackend.src.integrations.infrastructure.external_api.headhunter.schemas.response.HHVacancyResponse→backend.src.core.domain.entities.CustomModel
- Direction
- integrations.infrastructure.external_api.headhunter.schemas.response uses core.domain.entities, so a change to core.domain.entities can break integrations.infrastructure.external_api.headhunter.schemas.response, while a change to integrations.infrastructure.external_api.headhunter.schemas.response can't break core.domain.entities.
- Position
- Below the diagonal: integrations.infrastructure.external_api.headhunter.schemas.response uses a module listed above it, which is the healthy direction.
15→7 integrations.infrastructure.http.services.api_client uses integrations.infrastructure.http.interfaces✕
- Connections
- 1 pair of types, where a type in integrations.infrastructure.http.services.api_client uses a type in integrations.infrastructure.http.interfaces.
- The types involved
backend.src.integrations.infrastructure.http.services.api_client.APIClientService→backend.src.integrations.infrastructure.http.interfaces.IAsyncHttpClient
- Direction
- integrations.infrastructure.http.services.api_client uses integrations.infrastructure.http.interfaces, so a change to integrations.infrastructure.http.interfaces can break integrations.infrastructure.http.services.api_client, while a change to integrations.infrastructure.http.services.api_client can't break integrations.infrastructure.http.interfaces.
- Position
- Below the diagonal: integrations.infrastructure.http.services.api_client uses a module listed above it, which is the healthy direction.
16→3 users.domain.dtos uses core.domain.entities✕
- Connections
- 3 pairs of types, where a type in users.domain.dtos uses a type in core.domain.entities.
- The types involved
backend.src.users.domain.dtos.UserCreateDTO→backend.src.core.domain.entities.CustomModelbackend.src.users.domain.dtos.UserReadDTO→backend.src.core.domain.entities.CustomModelbackend.src.users.domain.dtos.UserUpdateDTO→backend.src.core.domain.entities.CustomModel
- Direction
- users.domain.dtos uses core.domain.entities, so a change to core.domain.entities can break users.domain.dtos, while a change to users.domain.dtos can't break core.domain.entities.
- Position
- Below the diagonal: users.domain.dtos uses a module listed above it, which is the healthy direction.
17→3 users.domain.entities uses core.domain.entities✕
- Connections
- 3 pairs of types, where a type in users.domain.entities uses a type in core.domain.entities.
- The types involved
backend.src.users.domain.entities.User→backend.src.core.domain.entities.CustomModelbackend.src.users.domain.entities.UserCreate→backend.src.core.domain.entities.CustomModelbackend.src.users.domain.entities.UserUpdate→backend.src.core.domain.entities.CustomModel
- Direction
- users.domain.entities uses core.domain.entities, so a change to core.domain.entities can break users.domain.entities, while a change to users.domain.entities can't break core.domain.entities.
- Position
- Below the diagonal: users.domain.entities uses a module listed above it, which is the healthy direction.
18→6 users.infrastructure.db.orm uses db.base✕
- Connections
- 1 pair of types, where a type in users.infrastructure.db.orm uses a type in db.base.
- The types involved
backend.src.users.infrastructure.db.orm.UserDB→backend.src.db.base.Base
- Direction
- users.infrastructure.db.orm uses db.base, so a change to db.base can break users.infrastructure.db.orm, while a change to users.infrastructure.db.orm can't break db.base.
- Position
- Below the diagonal: users.infrastructure.db.orm uses a module listed above it, which is the healthy direction.
19→3 vacancies.domain.entities uses core.domain.entities✕
- Connections
- 12 pairs of types, where a type in vacancies.domain.entities uses a type in core.domain.entities.
- The types involved
backend.src.vacancies.domain.entities.Address→backend.src.core.domain.entities.CustomModelbackend.src.vacancies.domain.entities.Area→backend.src.core.domain.entities.CustomModelbackend.src.vacancies.domain.entities.Employer→backend.src.core.domain.entities.CustomModelbackend.src.vacancies.domain.entities.Employment→backend.src.core.domain.entities.CustomModelbackend.src.vacancies.domain.entities.Experience→backend.src.core.domain.entities.CustomModelbackend.src.vacancies.domain.entities.MetroStation→backend.src.core.domain.entities.CustomModelbackend.src.vacancies.domain.entities.ProfessionalRole→backend.src.core.domain.entities.CustomModelbackend.src.vacancies.domain.entities.Salary→backend.src.core.domain.entities.CustomModelbackend.src.vacancies.domain.entities.Schedule→backend.src.core.domain.entities.CustomModelbackend.src.vacancies.domain.entities.Type→backend.src.core.domain.entities.CustomModelbackend.src.vacancies.domain.entities.Vacancy→backend.src.core.domain.entities.CustomModelbackend.src.vacancies.domain.entities.VacancySearchQuery→backend.src.core.domain.entities.CustomModel
- Direction
- vacancies.domain.entities uses core.domain.entities, so a change to core.domain.entities can break vacancies.domain.entities, while a change to vacancies.domain.entities can't break core.domain.entities.
- Position
- Below the diagonal: vacancies.domain.entities uses a module listed above it, which is the healthy direction.
20→3 vacancies.domain.interfaces.vacancy_repo uses core.domain.entities✕
- Connections
- 1 pair of types, where a type in vacancies.domain.interfaces.vacancy_repo uses a type in core.domain.entities.
- The types involved
backend.src.vacancies.domain.interfaces.vacancy_repo.IVacancyRepository→backend.src.core.domain.entities.BulkResult
- Direction
- vacancies.domain.interfaces.vacancy_repo uses core.domain.entities, so a change to core.domain.entities can break vacancies.domain.interfaces.vacancy_repo, while a change to vacancies.domain.interfaces.vacancy_repo can't break core.domain.entities.
- Position
- Below the diagonal: vacancies.domain.interfaces.vacancy_repo uses a module listed above it, which is the healthy direction.
21→1 auth.domain.interfaces.token_auth uses auth.domain.interfaces.token_provider✕
- Connections
- 1 pair of types, where a type in auth.domain.interfaces.token_auth uses a type in auth.domain.interfaces.token_provider.
- The types involved
backend.src.auth.domain.interfaces.token_auth.ITokenAuth→backend.src.auth.domain.interfaces.token_provider.ITokenProvider
- Direction
- auth.domain.interfaces.token_auth uses auth.domain.interfaces.token_provider, so a change to auth.domain.interfaces.token_provider can break auth.domain.interfaces.token_auth, while a change to auth.domain.interfaces.token_auth can't break auth.domain.interfaces.token_provider.
- Position
- Below the diagonal: auth.domain.interfaces.token_auth uses a module listed above it, which is the healthy direction.
21→10 auth.domain.interfaces.token_auth uses auth.domain.entities✕
- Connections
- 1 pair of types, where a type in auth.domain.interfaces.token_auth uses a type in auth.domain.entities.
- The types involved
backend.src.auth.domain.interfaces.token_auth.ITokenAuth→backend.src.auth.domain.entities.TokenType
- Direction
- auth.domain.interfaces.token_auth uses auth.domain.entities, so a change to auth.domain.entities can break auth.domain.interfaces.token_auth, while a change to auth.domain.interfaces.token_auth can't break auth.domain.entities.
- Position
- Below the diagonal: auth.domain.interfaces.token_auth uses a module listed above it, which is the healthy direction.
21→17 auth.domain.interfaces.token_auth uses users.domain.entities✕
- Connections
- 1 pair of types, where a type in auth.domain.interfaces.token_auth uses a type in users.domain.entities.
- The types involved
backend.src.auth.domain.interfaces.token_auth.ITokenAuth→backend.src.users.domain.entities.User
- Direction
- auth.domain.interfaces.token_auth uses users.domain.entities, so a change to users.domain.entities can break auth.domain.interfaces.token_auth, while a change to auth.domain.interfaces.token_auth can't break users.domain.entities.
- Position
- Below the diagonal: auth.domain.interfaces.token_auth uses a module listed above it, which is the healthy direction.
22→10 auth.domain.interfaces.token_storage uses auth.domain.entities✕
- Connections
- 1 pair of types, where a type in auth.domain.interfaces.token_storage uses a type in auth.domain.entities.
- The types involved
backend.src.auth.domain.interfaces.token_storage.ITokenStorage→backend.src.auth.domain.entities.TokenData
- Direction
- auth.domain.interfaces.token_storage uses auth.domain.entities, so a change to auth.domain.entities can break auth.domain.interfaces.token_storage, while a change to auth.domain.interfaces.token_storage can't break auth.domain.entities.
- Position
- Below the diagonal: auth.domain.interfaces.token_storage uses a module listed above it, which is the healthy direction.
23→7 integrations.infrastructure.external_api.headhunter.adapter uses integrations.infrastructure.http.interfaces✕
- Connections
- 1 pair of types, where a type in integrations.infrastructure.external_api.headhunter.adapter uses a type in integrations.infrastructure.http.interfaces.
- The types involved
backend.src.integrations.infrastructure.external_api.headhunter.adapter.HeadHunterAdapter→backend.src.integrations.infrastructure.http.interfaces.IAsyncHttpClient
- Direction
- integrations.infrastructure.external_api.headhunter.adapter uses integrations.infrastructure.http.interfaces, so a change to integrations.infrastructure.http.interfaces can break integrations.infrastructure.external_api.headhunter.adapter, while a change to integrations.infrastructure.external_api.headhunter.adapter can't break integrations.infrastructure.http.interfaces.
- Position
- Below the diagonal: integrations.infrastructure.external_api.headhunter.adapter uses a module listed above it, which is the healthy direction.
23→9 integrations.infrastructure.external_api.headhunter.adapter uses vacancies.domain.interfaces.vacancy_source_client✕
- Connections
- 1 pair of types, where a type in integrations.infrastructure.external_api.headhunter.adapter uses a type in vacancies.domain.interfaces.vacancy_source_client.
- The types involved
backend.src.integrations.infrastructure.external_api.headhunter.adapter.HeadHunterAdapter→backend.src.vacancies.domain.interfaces.vacancy_source_client.IVacancySourceClient
- Direction
- integrations.infrastructure.external_api.headhunter.adapter uses vacancies.domain.interfaces.vacancy_source_client, so a change to vacancies.domain.interfaces.vacancy_source_client can break integrations.infrastructure.external_api.headhunter.adapter, while a change to integrations.infrastructure.external_api.headhunter.adapter can't break vacancies.domain.interfaces.vacancy_source_client.
- Position
- Below the diagonal: integrations.infrastructure.external_api.headhunter.adapter uses a module listed above it, which is the healthy direction.
23→13 integrations.infrastructure.external_api.headhunter.adapter uses integrations.infrastructure.external_api.headhunter.schemas.request✕
- Connections
- 1 pair of types, where a type in integrations.infrastructure.external_api.headhunter.adapter uses a type in integrations.infrastructure.external_api.headhunter.schemas.request.
- The types involved
backend.src.integrations.infrastructure.external_api.headhunter.adapter.HeadHunterAdapter→backend.src.integrations.infrastructure.external_api.headhunter.schemas.request.HHVacancySearchParams
- Direction
- integrations.infrastructure.external_api.headhunter.adapter uses integrations.infrastructure.external_api.headhunter.schemas.request, so a change to integrations.infrastructure.external_api.headhunter.schemas.request can break integrations.infrastructure.external_api.headhunter.adapter, while a change to integrations.infrastructure.external_api.headhunter.adapter can't break integrations.infrastructure.external_api.headhunter.schemas.request.
- Position
- Below the diagonal: integrations.infrastructure.external_api.headhunter.adapter uses a module listed above it, which is the healthy direction.
23→14 integrations.infrastructure.external_api.headhunter.adapter uses integrations.infrastructure.external_api.headhunter.schemas.response✕
- Connections
- 1 pair of types, where a type in integrations.infrastructure.external_api.headhunter.adapter uses a type in integrations.infrastructure.external_api.headhunter.schemas.response.
- The types involved
backend.src.integrations.infrastructure.external_api.headhunter.adapter.HeadHunterAdapter→backend.src.integrations.infrastructure.external_api.headhunter.schemas.response.HHVacancyResponse
- Direction
- integrations.infrastructure.external_api.headhunter.adapter uses integrations.infrastructure.external_api.headhunter.schemas.response, so a change to integrations.infrastructure.external_api.headhunter.schemas.response can break integrations.infrastructure.external_api.headhunter.adapter, while a change to integrations.infrastructure.external_api.headhunter.adapter can't break integrations.infrastructure.external_api.headhunter.schemas.response.
- Position
- Below the diagonal: integrations.infrastructure.external_api.headhunter.adapter uses a module listed above it, which is the healthy direction.
23→15 integrations.infrastructure.external_api.headhunter.adapter uses integrations.infrastructure.http.services.api_client✕
- Connections
- 2 pairs of types, where a type in integrations.infrastructure.external_api.headhunter.adapter uses a type in integrations.infrastructure.http.services.api_client.
- The types involved
backend.src.integrations.infrastructure.external_api.headhunter.adapter.HeadHunterAdapter→backend.src.integrations.infrastructure.http.services.api_client.APIClientServicebackend.src.integrations.infrastructure.external_api.headhunter.adapter.HeadHunterAdapter→backend.src.integrations.infrastructure.http.services.api_client.AuthType
- Direction
- integrations.infrastructure.external_api.headhunter.adapter uses integrations.infrastructure.http.services.api_client, so a change to integrations.infrastructure.http.services.api_client can break integrations.infrastructure.external_api.headhunter.adapter, while a change to integrations.infrastructure.external_api.headhunter.adapter can't break integrations.infrastructure.http.services.api_client.
- Position
- Below the diagonal: integrations.infrastructure.external_api.headhunter.adapter uses a module listed above it, which is the healthy direction.
24→14 integrations.infrastructure.external_api.mappers.helpers uses integrations.infrastructure.external_api.headhunter.schemas.response✕
- Connections
- 1 pair of types, where a type in integrations.infrastructure.external_api.mappers.helpers uses a type in integrations.infrastructure.external_api.headhunter.schemas.response.
- The types involved
backend.src.integrations.infrastructure.external_api.mappers.helpers.HHVacancyToDomainMapper→backend.src.integrations.infrastructure.external_api.headhunter.schemas.response.HHVacancy
- Direction
- integrations.infrastructure.external_api.mappers.helpers uses integrations.infrastructure.external_api.headhunter.schemas.response, so a change to integrations.infrastructure.external_api.headhunter.schemas.response can break integrations.infrastructure.external_api.mappers.helpers, while a change to integrations.infrastructure.external_api.mappers.helpers can't break integrations.infrastructure.external_api.headhunter.schemas.response.
- Position
- Below the diagonal: integrations.infrastructure.external_api.mappers.helpers uses a module listed above it, which is the healthy direction.
24→19 integrations.infrastructure.external_api.mappers.helpers uses vacancies.domain.entities✕
- Connections
- 2 pairs of types, where a type in integrations.infrastructure.external_api.mappers.helpers uses a type in vacancies.domain.entities.
- The types involved
backend.src.integrations.infrastructure.external_api.mappers.helpers.HHVacancyToDomainMapper→backend.src.vacancies.domain.entities.Vacancybackend.src.integrations.infrastructure.external_api.mappers.helpers.HHVacancyToDomainMapper→backend.src.vacancies.domain.entities.VacancySource
- Direction
- integrations.infrastructure.external_api.mappers.helpers uses vacancies.domain.entities, so a change to vacancies.domain.entities can break integrations.infrastructure.external_api.mappers.helpers, while a change to integrations.infrastructure.external_api.mappers.helpers can't break vacancies.domain.entities.
- Position
- Below the diagonal: integrations.infrastructure.external_api.mappers.helpers uses a module listed above it, which is the healthy direction.
25→17 users.domain.interfaces.user_repo uses users.domain.entities✕
- Connections
- 3 pairs of types, where a type in users.domain.interfaces.user_repo uses a type in users.domain.entities.
- The types involved
backend.src.users.domain.interfaces.user_repo.IUserRepository→backend.src.users.domain.entities.Userbackend.src.users.domain.interfaces.user_repo.IUserRepository→backend.src.users.domain.entities.UserCreatebackend.src.users.domain.interfaces.user_repo.IUserRepository→backend.src.users.domain.entities.UserUpdate
- Direction
- users.domain.interfaces.user_repo uses users.domain.entities, so a change to users.domain.entities can break users.domain.interfaces.user_repo, while a change to users.domain.interfaces.user_repo can't break users.domain.entities.
- Position
- Below the diagonal: users.domain.interfaces.user_repo uses a module listed above it, which is the healthy direction.
26→5 users.infrastructure.db.crud uses crud.base✕
- Connections
- 1 pair of types, where a type in users.infrastructure.db.crud uses a type in crud.base.
- The types involved
backend.src.users.infrastructure.db.crud.UserService→backend.src.crud.base.CRUDBase
- Direction
- users.infrastructure.db.crud uses crud.base, so a change to crud.base can break users.infrastructure.db.crud, while a change to users.infrastructure.db.crud can't break crud.base.
- Position
- Below the diagonal: users.infrastructure.db.crud uses a module listed above it, which is the healthy direction.
26→18 users.infrastructure.db.crud uses users.infrastructure.db.orm✕
- Connections
- 1 pair of types, where a type in users.infrastructure.db.crud uses a type in users.infrastructure.db.orm.
- The types involved
backend.src.users.infrastructure.db.crud.UserService→backend.src.users.infrastructure.db.orm.UserDB
- Direction
- users.infrastructure.db.crud uses users.infrastructure.db.orm, so a change to users.infrastructure.db.orm can break users.infrastructure.db.crud, while a change to users.infrastructure.db.crud can't break users.infrastructure.db.orm.
- Position
- Below the diagonal: users.infrastructure.db.crud uses a module listed above it, which is the healthy direction.
27→3 vacancies.domain.dtos uses core.domain.entities✕
- Connections
- 3 pairs of types, where a type in vacancies.domain.dtos uses a type in core.domain.entities.
- The types involved
backend.src.vacancies.domain.dtos.VacancyCreateDTO→backend.src.core.domain.entities.CustomModelbackend.src.vacancies.domain.dtos.VacancyReadDTO→backend.src.core.domain.entities.CustomModelbackend.src.vacancies.domain.dtos.VacancyUpdateDTO→backend.src.core.domain.entities.CustomModel
- Direction
- vacancies.domain.dtos uses core.domain.entities, so a change to core.domain.entities can break vacancies.domain.dtos, while a change to vacancies.domain.dtos can't break core.domain.entities.
- Position
- Below the diagonal: vacancies.domain.dtos uses a module listed above it, which is the healthy direction.
27→19 vacancies.domain.dtos uses vacancies.domain.entities✕
- Connections
- 2 pairs of types, where a type in vacancies.domain.dtos uses a type in vacancies.domain.entities.
- The types involved
backend.src.vacancies.domain.dtos.VacancyCreateDTO→backend.src.vacancies.domain.entities.VacancySourcebackend.src.vacancies.domain.dtos.VacancyReadDTO→backend.src.vacancies.domain.entities.VacancySource
- Direction
- vacancies.domain.dtos uses vacancies.domain.entities, so a change to vacancies.domain.entities can break vacancies.domain.dtos, while a change to vacancies.domain.dtos can't break vacancies.domain.entities.
- Position
- Below the diagonal: vacancies.domain.dtos uses a module listed above it, which is the healthy direction.
28→3 vacancies.domain.interfaces.vacancy_search_repo uses core.domain.entities✕
- Connections
- 1 pair of types, where a type in vacancies.domain.interfaces.vacancy_search_repo uses a type in core.domain.entities.
- The types involved
backend.src.vacancies.domain.interfaces.vacancy_search_repo.IVacancySearchRepository→backend.src.core.domain.entities.BulkResult
- Direction
- vacancies.domain.interfaces.vacancy_search_repo uses core.domain.entities, so a change to core.domain.entities can break vacancies.domain.interfaces.vacancy_search_repo, while a change to vacancies.domain.interfaces.vacancy_search_repo can't break core.domain.entities.
- Position
- Below the diagonal: vacancies.domain.interfaces.vacancy_search_repo uses a module listed above it, which is the healthy direction.
28→19 vacancies.domain.interfaces.vacancy_search_repo uses vacancies.domain.entities✕
- Connections
- 1 pair of types, where a type in vacancies.domain.interfaces.vacancy_search_repo uses a type in vacancies.domain.entities.
- The types involved
backend.src.vacancies.domain.interfaces.vacancy_search_repo.IVacancySearchRepository→backend.src.vacancies.domain.entities.VacancySearchQuery
- Direction
- vacancies.domain.interfaces.vacancy_search_repo uses vacancies.domain.entities, so a change to vacancies.domain.entities can break vacancies.domain.interfaces.vacancy_search_repo, while a change to vacancies.domain.interfaces.vacancy_search_repo can't break vacancies.domain.entities.
- Position
- Below the diagonal: vacancies.domain.interfaces.vacancy_search_repo uses a module listed above it, which is the healthy direction.
29→20 vacancies.domain.interfaces.vacancy_uow uses vacancies.domain.interfaces.vacancy_repo✕
- Connections
- 1 pair of types, where a type in vacancies.domain.interfaces.vacancy_uow uses a type in vacancies.domain.interfaces.vacancy_repo.
- The types involved
backend.src.vacancies.domain.interfaces.vacancy_uow.IVacancyUnitOfWork→backend.src.vacancies.domain.interfaces.vacancy_repo.IVacancyRepository
- Direction
- vacancies.domain.interfaces.vacancy_uow uses vacancies.domain.interfaces.vacancy_repo, so a change to vacancies.domain.interfaces.vacancy_repo can break vacancies.domain.interfaces.vacancy_uow, while a change to vacancies.domain.interfaces.vacancy_uow can't break vacancies.domain.interfaces.vacancy_repo.
- Position
- Below the diagonal: vacancies.domain.interfaces.vacancy_uow uses a module listed above it, which is the healthy direction.
30→1 auth.infrastructure.services.jwt uses auth.domain.interfaces.token_provider✕
- Connections
- 2 pairs of types, where a type in auth.infrastructure.services.jwt uses a type in auth.domain.interfaces.token_provider.
- The types involved
backend.src.auth.infrastructure.services.jwt.JWTAuth→backend.src.auth.domain.interfaces.token_provider.ITokenProviderbackend.src.auth.infrastructure.services.jwt.JWTProvider→backend.src.auth.domain.interfaces.token_provider.ITokenProvider
- Direction
- auth.infrastructure.services.jwt uses auth.domain.interfaces.token_provider, so a change to auth.domain.interfaces.token_provider can break auth.infrastructure.services.jwt, while a change to auth.infrastructure.services.jwt can't break auth.domain.interfaces.token_provider.
- Position
- Below the diagonal: auth.infrastructure.services.jwt uses a module listed above it, which is the healthy direction.
30→10 auth.infrastructure.services.jwt uses auth.domain.entities✕
- Connections
- 2 pairs of types, where a type in auth.infrastructure.services.jwt uses a type in auth.domain.entities.
- The types involved
backend.src.auth.infrastructure.services.jwt.JWTAuth→backend.src.auth.domain.entities.TokenDatabackend.src.auth.infrastructure.services.jwt.JWTAuth→backend.src.auth.domain.entities.TokenType
- Direction
- auth.infrastructure.services.jwt uses auth.domain.entities, so a change to auth.domain.entities can break auth.infrastructure.services.jwt, while a change to auth.infrastructure.services.jwt can't break auth.domain.entities.
- Position
- Below the diagonal: auth.infrastructure.services.jwt uses a module listed above it, which is the healthy direction.
30→17 auth.infrastructure.services.jwt uses users.domain.entities✕
- Connections
- 1 pair of types, where a type in auth.infrastructure.services.jwt uses a type in users.domain.entities.
- The types involved
backend.src.auth.infrastructure.services.jwt.JWTAuth→backend.src.users.domain.entities.User
- Direction
- auth.infrastructure.services.jwt uses users.domain.entities, so a change to users.domain.entities can break auth.infrastructure.services.jwt, while a change to auth.infrastructure.services.jwt can't break users.domain.entities.
- Position
- Below the diagonal: auth.infrastructure.services.jwt uses a module listed above it, which is the healthy direction.
30→21 auth.infrastructure.services.jwt uses auth.domain.interfaces.token_auth✕
- Connections
- 1 pair of types, where a type in auth.infrastructure.services.jwt uses a type in auth.domain.interfaces.token_auth.
- The types involved
backend.src.auth.infrastructure.services.jwt.JWTAuth→backend.src.auth.domain.interfaces.token_auth.ITokenAuth
- Direction
- auth.infrastructure.services.jwt uses auth.domain.interfaces.token_auth, so a change to auth.domain.interfaces.token_auth can break auth.infrastructure.services.jwt, while a change to auth.infrastructure.services.jwt can't break auth.domain.interfaces.token_auth.
- Position
- Below the diagonal: auth.infrastructure.services.jwt uses a module listed above it, which is the healthy direction.
31→10 auth.infrastructure.services.redis_token_storage uses auth.domain.entities✕
- Connections
- 1 pair of types, where a type in auth.infrastructure.services.redis_token_storage uses a type in auth.domain.entities.
- The types involved
backend.src.auth.infrastructure.services.redis_token_storage.RedisTokenStorage→backend.src.auth.domain.entities.TokenData
- Direction
- auth.infrastructure.services.redis_token_storage uses auth.domain.entities, so a change to auth.domain.entities can break auth.infrastructure.services.redis_token_storage, while a change to auth.infrastructure.services.redis_token_storage can't break auth.domain.entities.
- Position
- Below the diagonal: auth.infrastructure.services.redis_token_storage uses a module listed above it, which is the healthy direction.
31→22 auth.infrastructure.services.redis_token_storage uses auth.domain.interfaces.token_storage✕
- Connections
- 1 pair of types, where a type in auth.infrastructure.services.redis_token_storage uses a type in auth.domain.interfaces.token_storage.
- The types involved
backend.src.auth.infrastructure.services.redis_token_storage.RedisTokenStorage→backend.src.auth.domain.interfaces.token_storage.ITokenStorage
- Direction
- auth.infrastructure.services.redis_token_storage uses auth.domain.interfaces.token_storage, so a change to auth.domain.interfaces.token_storage can break auth.infrastructure.services.redis_token_storage, while a change to auth.infrastructure.services.redis_token_storage can't break auth.domain.interfaces.token_storage.
- Position
- Below the diagonal: auth.infrastructure.services.redis_token_storage uses a module listed above it, which is the healthy direction.
32→25 users.domain.interfaces.user_uow uses users.domain.interfaces.user_repo✕
- Connections
- 1 pair of types, where a type in users.domain.interfaces.user_uow uses a type in users.domain.interfaces.user_repo.
- The types involved
backend.src.users.domain.interfaces.user_uow.IUserUnitOfWork→backend.src.users.domain.interfaces.user_repo.IUserRepository
- Direction
- users.domain.interfaces.user_uow uses users.domain.interfaces.user_repo, so a change to users.domain.interfaces.user_repo can break users.domain.interfaces.user_uow, while a change to users.domain.interfaces.user_uow can't break users.domain.interfaces.user_repo.
- Position
- Below the diagonal: users.domain.interfaces.user_uow uses a module listed above it, which is the healthy direction.
33→17 users.infrastructure.db.repositories uses users.domain.entities✕
- Connections
- 3 pairs of types, where a type in users.infrastructure.db.repositories uses a type in users.domain.entities.
- The types involved
backend.src.users.infrastructure.db.repositories.PGUserRepository→backend.src.users.domain.entities.Userbackend.src.users.infrastructure.db.repositories.PGUserRepository→backend.src.users.domain.entities.UserCreatebackend.src.users.infrastructure.db.repositories.PGUserRepository→backend.src.users.domain.entities.UserUpdate
- Direction
- users.infrastructure.db.repositories uses users.domain.entities, so a change to users.domain.entities can break users.infrastructure.db.repositories, while a change to users.infrastructure.db.repositories can't break users.domain.entities.
- Position
- Below the diagonal: users.infrastructure.db.repositories uses a module listed above it, which is the healthy direction.
33→18 users.infrastructure.db.repositories uses users.infrastructure.db.orm✕
- Connections
- 1 pair of types, where a type in users.infrastructure.db.repositories uses a type in users.infrastructure.db.orm.
- The types involved
backend.src.users.infrastructure.db.repositories.PGUserRepository→backend.src.users.infrastructure.db.orm.UserDB
- Direction
- users.infrastructure.db.repositories uses users.infrastructure.db.orm, so a change to users.infrastructure.db.orm can break users.infrastructure.db.repositories, while a change to users.infrastructure.db.repositories can't break users.infrastructure.db.orm.
- Position
- Below the diagonal: users.infrastructure.db.repositories uses a module listed above it, which is the healthy direction.
33→25 users.infrastructure.db.repositories uses users.domain.interfaces.user_repo✕
- Connections
- 1 pair of types, where a type in users.infrastructure.db.repositories uses a type in users.domain.interfaces.user_repo.
- The types involved
backend.src.users.infrastructure.db.repositories.PGUserRepository→backend.src.users.domain.interfaces.user_repo.IUserRepository
- Direction
- users.infrastructure.db.repositories uses users.domain.interfaces.user_repo, so a change to users.domain.interfaces.user_repo can break users.infrastructure.db.repositories, while a change to users.infrastructure.db.repositories can't break users.domain.interfaces.user_repo.
- Position
- Below the diagonal: users.infrastructure.db.repositories uses a module listed above it, which is the healthy direction.
34→19 vacancies.application.mappers.vacancies uses vacancies.domain.entities✕
- Connections
- 1 pair of types, where a type in vacancies.application.mappers.vacancies uses a type in vacancies.domain.entities.
- The types involved
backend.src.vacancies.application.mappers.vacancies.VacancyDomainToDTOMapper→backend.src.vacancies.domain.entities.Vacancy
- Direction
- vacancies.application.mappers.vacancies uses vacancies.domain.entities, so a change to vacancies.domain.entities can break vacancies.application.mappers.vacancies, while a change to vacancies.application.mappers.vacancies can't break vacancies.domain.entities.
- Position
- Below the diagonal: vacancies.application.mappers.vacancies uses a module listed above it, which is the healthy direction.
34→27 vacancies.application.mappers.vacancies uses vacancies.domain.dtos✕
- Connections
- 1 pair of types, where a type in vacancies.application.mappers.vacancies uses a type in vacancies.domain.dtos.
- The types involved
backend.src.vacancies.application.mappers.vacancies.VacancyDomainToDTOMapper→backend.src.vacancies.domain.dtos.VacancyCreateDTO
- Direction
- vacancies.application.mappers.vacancies uses vacancies.domain.dtos, so a change to vacancies.domain.dtos can break vacancies.application.mappers.vacancies, while a change to vacancies.application.mappers.vacancies can't break vacancies.domain.dtos.
- Position
- Below the diagonal: vacancies.application.mappers.vacancies uses a module listed above it, which is the healthy direction.
35→3 vacancies.application.use_cases uses core.domain.entities✕
- Connections
- 1 pair of types, where a type in vacancies.application.use_cases uses a type in core.domain.entities.
- The types involved
backend.src.vacancies.application.use_cases.vacancy_collector→backend.src.core.domain.entities.BulkResult
- Direction
- vacancies.application.use_cases uses core.domain.entities, so a change to core.domain.entities can break vacancies.application.use_cases, while a change to vacancies.application.use_cases can't break core.domain.entities.
- Position
- Below the diagonal: vacancies.application.use_cases uses a module listed above it, which is the healthy direction.
35→9 vacancies.application.use_cases uses vacancies.domain.interfaces.vacancy_source_client✕
- Connections
- 1 pair of types, where a type in vacancies.application.use_cases uses a type in vacancies.domain.interfaces.vacancy_source_client.
- The types involved
backend.src.vacancies.application.use_cases.vacancy_collector→backend.src.vacancies.domain.interfaces.vacancy_source_client.IVacancySourceClient
- Direction
- vacancies.application.use_cases uses vacancies.domain.interfaces.vacancy_source_client, so a change to vacancies.domain.interfaces.vacancy_source_client can break vacancies.application.use_cases, while a change to vacancies.application.use_cases can't break vacancies.domain.interfaces.vacancy_source_client.
- Position
- Below the diagonal: vacancies.application.use_cases uses a module listed above it, which is the healthy direction.
35→28 vacancies.application.use_cases uses vacancies.domain.interfaces.vacancy_search_repo✕
- Connections
- 1 pair of types, where a type in vacancies.application.use_cases uses a type in vacancies.domain.interfaces.vacancy_search_repo.
- The types involved
backend.src.vacancies.application.use_cases.vacancy_collector→backend.src.vacancies.domain.interfaces.vacancy_search_repo.IVacancySearchRepository
- Direction
- vacancies.application.use_cases uses vacancies.domain.interfaces.vacancy_search_repo, so a change to vacancies.domain.interfaces.vacancy_search_repo can break vacancies.application.use_cases, while a change to vacancies.application.use_cases can't break vacancies.domain.interfaces.vacancy_search_repo.
- Position
- Below the diagonal: vacancies.application.use_cases uses a module listed above it, which is the healthy direction.
35→29 vacancies.application.use_cases uses vacancies.domain.interfaces.vacancy_uow✕
- Connections
- 1 pair of types, where a type in vacancies.application.use_cases uses a type in vacancies.domain.interfaces.vacancy_uow.
- The types involved
backend.src.vacancies.application.use_cases.vacancy_collector→backend.src.vacancies.domain.interfaces.vacancy_uow.IVacancyUnitOfWork
- Direction
- vacancies.application.use_cases uses vacancies.domain.interfaces.vacancy_uow, so a change to vacancies.domain.interfaces.vacancy_uow can break vacancies.application.use_cases, while a change to vacancies.application.use_cases can't break vacancies.domain.interfaces.vacancy_uow.
- Position
- Below the diagonal: vacancies.application.use_cases uses a module listed above it, which is the healthy direction.
36→3 vacancies.infrastructure.elastic.repositories uses core.domain.entities✕
- Connections
- 1 pair of types, where a type in vacancies.infrastructure.elastic.repositories uses a type in core.domain.entities.
- The types involved
backend.src.vacancies.infrastructure.elastic.repositories.ESVacancySearchRepository→backend.src.core.domain.entities.BulkResult
- Direction
- vacancies.infrastructure.elastic.repositories uses core.domain.entities, so a change to core.domain.entities can break vacancies.infrastructure.elastic.repositories, while a change to vacancies.infrastructure.elastic.repositories can't break core.domain.entities.
- Position
- Below the diagonal: vacancies.infrastructure.elastic.repositories uses a module listed above it, which is the healthy direction.
36→19 vacancies.infrastructure.elastic.repositories uses vacancies.domain.entities✕
- Connections
- 1 pair of types, where a type in vacancies.infrastructure.elastic.repositories uses a type in vacancies.domain.entities.
- The types involved
backend.src.vacancies.infrastructure.elastic.repositories.ESVacancySearchRepository→backend.src.vacancies.domain.entities.VacancySearchQuery
- Direction
- vacancies.infrastructure.elastic.repositories uses vacancies.domain.entities, so a change to vacancies.domain.entities can break vacancies.infrastructure.elastic.repositories, while a change to vacancies.infrastructure.elastic.repositories can't break vacancies.domain.entities.
- Position
- Below the diagonal: vacancies.infrastructure.elastic.repositories uses a module listed above it, which is the healthy direction.
36→28 vacancies.infrastructure.elastic.repositories uses vacancies.domain.interfaces.vacancy_search_repo✕
- Connections
- 1 pair of types, where a type in vacancies.infrastructure.elastic.repositories uses a type in vacancies.domain.interfaces.vacancy_search_repo.
- The types involved
backend.src.vacancies.infrastructure.elastic.repositories.ESVacancySearchRepository→backend.src.vacancies.domain.interfaces.vacancy_search_repo.IVacancySearchRepository
- Direction
- vacancies.infrastructure.elastic.repositories uses vacancies.domain.interfaces.vacancy_search_repo, so a change to vacancies.domain.interfaces.vacancy_search_repo can break vacancies.infrastructure.elastic.repositories, while a change to vacancies.infrastructure.elastic.repositories can't break vacancies.domain.interfaces.vacancy_search_repo.
- Position
- Below the diagonal: vacancies.infrastructure.elastic.repositories uses a module listed above it, which is the healthy direction.
37→8 auth.application.use_cases uses users.domain.interfaces.password_hasher✕
- Connections
- 1 pair of types, where a type in auth.application.use_cases uses a type in users.domain.interfaces.password_hasher.
- The types involved
backend.src.auth.application.use_cases.authentication→backend.src.users.domain.interfaces.password_hasher.IPasswordHasher
- Direction
- auth.application.use_cases uses users.domain.interfaces.password_hasher, so a change to users.domain.interfaces.password_hasher can break auth.application.use_cases, while a change to auth.application.use_cases can't break users.domain.interfaces.password_hasher.
- Position
- Below the diagonal: auth.application.use_cases uses a module listed above it, which is the healthy direction.
37→17 auth.application.use_cases uses users.domain.entities✕
- Connections
- 1 pair of types, where a type in auth.application.use_cases uses a type in users.domain.entities.
- The types involved
backend.src.auth.application.use_cases.authentication→backend.src.users.domain.entities.User
- Direction
- auth.application.use_cases uses users.domain.entities, so a change to users.domain.entities can break auth.application.use_cases, while a change to auth.application.use_cases can't break users.domain.entities.
- Position
- Below the diagonal: auth.application.use_cases uses a module listed above it, which is the healthy direction.
37→21 auth.application.use_cases uses auth.domain.interfaces.token_auth✕
- Connections
- 1 pair of types, where a type in auth.application.use_cases uses a type in auth.domain.interfaces.token_auth.
- The types involved
backend.src.auth.application.use_cases.authentication→backend.src.auth.domain.interfaces.token_auth.ITokenAuth
- Direction
- auth.application.use_cases uses auth.domain.interfaces.token_auth, so a change to auth.domain.interfaces.token_auth can break auth.application.use_cases, while a change to auth.application.use_cases can't break auth.domain.interfaces.token_auth.
- Position
- Below the diagonal: auth.application.use_cases uses a module listed above it, which is the healthy direction.
37→32 auth.application.use_cases uses users.domain.interfaces.user_uow✕
- Connections
- 1 pair of types, where a type in auth.application.use_cases uses a type in users.domain.interfaces.user_uow.
- The types involved
backend.src.auth.application.use_cases.authentication→backend.src.users.domain.interfaces.user_uow.IUserUnitOfWork
- Direction
- auth.application.use_cases uses users.domain.interfaces.user_uow, so a change to users.domain.interfaces.user_uow can break auth.application.use_cases, while a change to auth.application.use_cases can't break users.domain.interfaces.user_uow.
- Position
- Below the diagonal: auth.application.use_cases uses a module listed above it, which is the healthy direction.
38→8 auth.presentation uses users.domain.interfaces.password_hasher✕
- Connections
- 1 pair of types, where a type in auth.presentation uses a type in users.domain.interfaces.password_hasher.
- The types involved
backend.src.auth.presentation.dependencies→backend.src.users.domain.interfaces.password_hasher.IPasswordHasher
- Direction
- auth.presentation uses users.domain.interfaces.password_hasher, so a change to users.domain.interfaces.password_hasher can break auth.presentation, while a change to auth.presentation can't break users.domain.interfaces.password_hasher.
- Position
- Below the diagonal: auth.presentation uses a module listed above it, which is the healthy direction.
38→11 auth.presentation uses auth.presentation.dtos✕
- Connections
- 1 pair of types, where a type in auth.presentation uses a type in auth.presentation.dtos.
- The types involved
backend.src.auth.presentation.api→backend.src.auth.presentation.dtos.AuthUserDTO
- Direction
- auth.presentation uses auth.presentation.dtos, so a change to auth.presentation.dtos can break auth.presentation, while a change to auth.presentation can't break auth.presentation.dtos.
- Position
- Below the diagonal: auth.presentation uses a module listed above it, which is the healthy direction.
38→16 auth.presentation uses users.domain.dtos✕
- Connections
- 1 pair of types, where a type in auth.presentation uses a type in users.domain.dtos.
- The types involved
backend.src.auth.presentation.api→backend.src.users.domain.dtos.UserReadDTO
- Direction
- auth.presentation uses users.domain.dtos, so a change to users.domain.dtos can break auth.presentation, while a change to auth.presentation can't break users.domain.dtos.
- Position
- Below the diagonal: auth.presentation uses a module listed above it, which is the healthy direction.
38→22 auth.presentation uses auth.domain.interfaces.token_storage✕
- Connections
- 1 pair of types, where a type in auth.presentation uses a type in auth.domain.interfaces.token_storage.
- The types involved
backend.src.auth.presentation.dependencies→backend.src.auth.domain.interfaces.token_storage.ITokenStorage
- Direction
- auth.presentation uses auth.domain.interfaces.token_storage, so a change to auth.domain.interfaces.token_storage can break auth.presentation, while a change to auth.presentation can't break auth.domain.interfaces.token_storage.
- Position
- Below the diagonal: auth.presentation uses a module listed above it, which is the healthy direction.
38→30 auth.presentation uses auth.infrastructure.services.jwt✕
- Connections
- 1 pair of types, where a type in auth.presentation uses a type in auth.infrastructure.services.jwt.
- The types involved
backend.src.auth.presentation.dependencies→backend.src.auth.infrastructure.services.jwt.JWTAuth
- Direction
- auth.presentation uses auth.infrastructure.services.jwt, so a change to auth.infrastructure.services.jwt can break auth.presentation, while a change to auth.presentation can't break auth.infrastructure.services.jwt.
- Position
- Below the diagonal: auth.presentation uses a module listed above it, which is the healthy direction.
39→8 users.application.use_cases uses users.domain.interfaces.password_hasher✕
- Connections
- 1 pair of types, where a type in users.application.use_cases uses a type in users.domain.interfaces.password_hasher.
- The types involved
backend.src.users.application.use_cases.user_registration→backend.src.users.domain.interfaces.password_hasher.IPasswordHasher
- Direction
- users.application.use_cases uses users.domain.interfaces.password_hasher, so a change to users.domain.interfaces.password_hasher can break users.application.use_cases, while a change to users.application.use_cases can't break users.domain.interfaces.password_hasher.
- Position
- Below the diagonal: users.application.use_cases uses a module listed above it, which is the healthy direction.
39→16 users.application.use_cases uses users.domain.dtos✕
- Connections
- 2 pairs of types, where a type in users.application.use_cases uses a type in users.domain.dtos.
- The types involved
backend.src.users.application.use_cases.user_registration→backend.src.users.domain.dtos.UserCreateDTObackend.src.users.application.use_cases.user_update→backend.src.users.domain.dtos.UserUpdateDTO
- Direction
- users.application.use_cases uses users.domain.dtos, so a change to users.domain.dtos can break users.application.use_cases, while a change to users.application.use_cases can't break users.domain.dtos.
- Position
- Below the diagonal: users.application.use_cases uses a module listed above it, which is the healthy direction.
39→17 users.application.use_cases uses users.domain.entities✕
- Connections
- 3 pairs of types, where a type in users.application.use_cases uses a type in users.domain.entities.
- The types involved
backend.src.users.application.use_cases.user_profile→backend.src.users.domain.entities.Userbackend.src.users.application.use_cases.user_registration→backend.src.users.domain.entities.Userbackend.src.users.application.use_cases.user_update→backend.src.users.domain.entities.User
- Direction
- users.application.use_cases uses users.domain.entities, so a change to users.domain.entities can break users.application.use_cases, while a change to users.application.use_cases can't break users.domain.entities.
- Position
- Below the diagonal: users.application.use_cases uses a module listed above it, which is the healthy direction.
39→32 users.application.use_cases uses users.domain.interfaces.user_uow✕
- Connections
- 4 pairs of types, where a type in users.application.use_cases uses a type in users.domain.interfaces.user_uow.
- The types involved
backend.src.users.application.use_cases.user_delete→backend.src.users.domain.interfaces.user_uow.IUserUnitOfWorkbackend.src.users.application.use_cases.user_profile→backend.src.users.domain.interfaces.user_uow.IUserUnitOfWorkbackend.src.users.application.use_cases.user_registration→backend.src.users.domain.interfaces.user_uow.IUserUnitOfWorkbackend.src.users.application.use_cases.user_update→backend.src.users.domain.interfaces.user_uow.IUserUnitOfWork
- Direction
- users.application.use_cases uses users.domain.interfaces.user_uow, so a change to users.domain.interfaces.user_uow can break users.application.use_cases, while a change to users.application.use_cases can't break users.domain.interfaces.user_uow.
- Position
- Below the diagonal: users.application.use_cases uses a module listed above it, which is the healthy direction.
40→16 users.presentation uses users.domain.dtos✕
- Connections
- 2 pairs of types, where a type in users.presentation uses a type in users.domain.dtos.
- The types involved
backend.src.users.presentation.api→backend.src.users.domain.dtos.UserCreateDTObackend.src.users.presentation.api→backend.src.users.domain.dtos.UserUpdateDTO
- Direction
- users.presentation uses users.domain.dtos, so a change to users.domain.dtos can break users.presentation, while a change to users.presentation can't break users.domain.dtos.
- Position
- Below the diagonal: users.presentation uses a module listed above it, which is the healthy direction.
40→32 users.presentation uses users.domain.interfaces.user_uow✕
- Connections
- 1 pair of types, where a type in users.presentation uses a type in users.domain.interfaces.user_uow.
- The types involved
backend.src.users.presentation.dependencies→backend.src.users.domain.interfaces.user_uow.IUserUnitOfWork
- Direction
- users.presentation uses users.domain.interfaces.user_uow, so a change to users.domain.interfaces.user_uow can break users.presentation, while a change to users.presentation can't break users.domain.interfaces.user_uow.
- Position
- Below the diagonal: users.presentation 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 — Domain Modelling
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A02:2025 — Security Misconfiguration | 24 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 5 | High / Critical |
Roadmap
Top priorities: Resolve the 1 Yanked release finding(s) in Dependency Hygiene; 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; Add a CI workflow that builds and runs the test suite on every push/PR.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 Yanked release finding(s) in Dependency Hygiene. | +6.7 pts | Low | Dependency Hygiene |
| Resolve the 1 Banned license finding(s) in License Compliance. | +4.5 pts | Low | License Compliance |
| 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. | +6.0 pts | Medium | Visual & motion safety |
| Add a CI workflow that builds and runs the test suite on every push/PR. | +5.4 pts | Medium | CI/CD gates |
| Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery. | +5.4 pts | Medium | DR & Backup |
| Enforce accessibility over your pages: run an accessibility checker (axe-core, pa11y or Lighthouse) against your HTML in CI and fail the build on new violations — these run as standalone tools without adding a package manifest. | +3.3 pts | Medium | A11y enforcement |
| Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh. | +2.6 pts | Medium | Page structure |
| Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding. | +2.0 pts | Medium | Deployment & Rollback |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 3.4 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.4 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 5.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 7.9 | Near-clean | IaC & Container Security: Medium IaC: REDACTED |
| tools/print_structure.py | 8.5 | Near-clean | Cognitive Complexity: print_structure.print_tree (cognitive 16) |
| backend/src/crud/base.py | 8.5 | Near-clean | Code Duplication: Duplicated block (14 lines × 2) |
| REDACTED | 8.6 | Near-clean | IaC & Container Security: Low IaC: REDACTED |
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 68 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.7, the weighted average across measured dimensions.
What we checked — 68 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, 81 of 115 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 · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.py) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (`coverage run -m pytest` then `coverage xml`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (`coverage run -m pytest` then `coverage xml`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.py) but the built-in reliability runner does not support this repository's ecosystem, so flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D15 Churn × Complexity Hotspots — measured, with a gap in what it reached — 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. Git history depth insufficient — this repository has 24 commit(s), too few for a reliable trend signal. The clone is complete, so there is no deeper history to fetch: the signal returns as the project accumulates history.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-contributor repository — bus factor is not applicable (1 contributor(s) across 24 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- 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.
- D24 Comment Value — 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's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D34 Knowledge Freshness — 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. Too few commits to judge knowledge freshness (24 commit(s) sampled).
- D35 Change Coupling — measured, with a gap in what it reached — 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. Git history depth insufficient — this repository has 24 commit(s), too few for a reliable change-coupling signal. The clone is complete, so there is no deeper history to fetch: the signal returns as the project accumulates history.
- AC6 Visual & motion safety — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 37 further occurrence(s) are not listed individually; the score already reflects all 77.
- AX6 Interface segregation — 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 is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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 DockerCompose (REDACTED). compose up failed (exit 14 — a file the compose project references is missing) — time="2026-11-08T00:27:32Z" level=warning msg="The \"DB_PORT\" variable is not set. Defaulting to a blank string." env file .env.dev not found: stat .env.dev: no such file or directory; runtime evidence skipped.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- DM8 Value-object opportunities — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- DM9 Scattered domain decisions — 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. Arm two tells a construction that PRODUCES a measurement from one that merely passes it along, and this repository's frontend does not compute that fact. A measurement built independently in two places would not appear above.
- GD1 Unfinished & placeholder code — 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, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Python is not read yet, 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.
- IC1 Incompleteness & stubs — 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, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Python is not read yet, 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.
- X16 Unfloored truncation loop — 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, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — 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, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X29 Per-element action decided by a fixed element — 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 (Vue and Svelte components included), Java, Rust, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, Rust, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X5 Nullable reference types — 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 MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Python is not read yet, 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.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- 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.
- D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
- 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 REDACTED, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- 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.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
1 method(s) exceeded the cognitive complexity threshold of 15; the worst was print_structure.print_tree at 16.
What to do
- Bring the 1 body over 15 down to 15 or less in Cognitive Complexity — start with print_structure.print_tree (cognitive 16). — Refactoring it lifts Cognitive Complexity from 9.9 to about 10.0/10.
- Stand up a CI pipeline, then gate Cognitive Complexity in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
1 duplicated block group(s) detected.
What to do
- Resolve the 1 Duplicated block (14 lines × 2) finding(s) in Code Duplication — start with base.py. — One of this dimension's main actionable groups (1 warning-level).
- Stand up a CI pipeline, then gate Code Duplication in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
2 production modules (source-import), 0 dependency cycle(s), 0 unstable depended-on module(s). No manifest declares this repository's modules, so the modules are its top-level source directories and the edges the imports between them; 0 module(s) off the main sequence.
D6 · Cohesion (LCOM4)
0 of 22 classes have LCOM4 above 3.
D12 · Dependency Hygiene
23 outdated, 1 yanked pinned Python distributions. Only EXACT pins are graded for currency: a floor or a range already installs the newest release it admits, so reporting one would report this repository for being current. Whether a deliberate upper cap has itself gone stale is a different and weaker question, and is not asked. Whether any distribution is UNMAINTAINED is not graded — PyPI publishes no maintenance status, and release age does not stand in for one. Lockfiles are not read (poetry.lock, uv.lock, Pipfile.lock, pdm.lock), so a lock-resolved install is outside this verdict. Known CVEs in this dependency graph are D30's question.
What to do
- Resolve the 1 Yanked release finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).
- Stand up a CI pipeline, then gate Dependency Hygiene in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
1 of 85 shipped Python distribution(s) use a banned license. Licences were resolved from PyPI over the distributions a consumer installs — this repository's 25 declared runtime requirement(s) closed transitively over each distribution's published `requires_dist` (60 reached that way). Requirements it states ONLY under an extra, a PEP 735 dependency group, a Poetry dev group or a dev-named requirements file are excluded: pip does not install any of them for a consumer. ★ This repository commits no dependency lockfile that this pass reads, so each licence is the one PyPI publishes for the distribution's CURRENT release rather than for a pinned version. 5 of them publish no licence on PyPI this pass can read; that is missing data, not a violation, and none of them is charged.
What to do
- Resolve the 1 Banned license finding(s) in License Compliance. — One of this dimension's main actionable groups (1 issue-level).
- Stand up a CI pipeline, then gate License Compliance in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
0 deducted task-comment markers across 5009 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.
D23 · Boundary Type-Coupling
No domain types leak across context boundaries (3 contexts). Contexts: db, users, vacancies.
D26 · Project Cohesion
1 of 2 build units (Make, Python) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
66 % of calls cross a namespace and 0 % go through an interface, but 85 % 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. semgrep hit a parse error in 1 file(s) — `backend/src/templates/login.html` (lines 1–3, lines 5–7, line 30, …) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
D30 · Dependency Vulnerabilities
5 finding(s): 1 critical, 2 high, 2 medium, 0 low.
What to do
- Resolve the 2 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 2 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
D31 · IaC & Container Security
24 finding(s): 0 critical, 3 high, 5 medium, 16 low.
What to do
- Resolve the 3 High IaC finding(s) in IaC & Container Security — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 16 Low IaC finding(s) in IaC & Container Security — start with REDACTED (14), REDACTED (2). — One of this dimension's main actionable groups (16 recommendation-level).
- Resolve the 5 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (4), REDACTED. — One of this dimension's main actionable groups (5 warning-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.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 25 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AC2 · Forms & labels
AC3 · Page structure
- user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta. — backend/src/templates/base.html:6
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.
AC6 · Visual & motion safety
- `:not(pre) > code[class*="language-"]` sets color: #db4c69 on background-color: #1e1e1e — 4.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — static/css/prism-themes/prism-vsc-dark-plus.css:46
- `.oval-btn:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — static/css/styles.css:182
- `#login-form *` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — static/css/styles.css:366
- `.bounce` moves (`animation-name: bounce`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — static/css/animate.css:53
- `.pulse` moves (`animation-name: pulse`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — static/css/animate.css:88
- `.rubberBand` moves (`animation-name: rubberBand`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — static/css/animate.css:122
- `.shake` moves (`animation-name: shake`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — static/css/animate.css:140
- `.headShake` moves (`animation-name: headShake`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — static/css/animate.css:171
- `.swing` moves (`animation-name: swing`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — static/css/animate.css:198
- `.tada` moves (`animation-name: tada`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — static/css/animate.css:224
- `.wobble` moves (`animation-name: wobble`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — static/css/animate.css:260
- `.jello` moves (`animation-name: jello`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — static/css/animate.css:298
- `.bounceIn` moves (`animation-name: bounceIn`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — static/css/animate.css:336
- `.bounceInDown` moves (`animation-name: bounceInDown`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — static/css/animate.css:368
- `.bounceInLeft` moves (`animation-name: bounceInLeft`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — static/css/animate.css:400
- `.bounceInRight` moves (`animation-name: bounceInRight`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — static/css/animate.css:432
- `.bounceInUp` moves (`animation-name: bounceInUp`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — static/css/animate.css:464
- `.bounceOut` moves (`animation-name: bounceOut`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — static/css/animate.css:484
- `.bounceOutDown` moves (`animation-name: bounceOutDown`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — static/css/animate.css:504
- `.bounceOutLeft` moves (`animation-name: bounceOutLeft`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — static/css/animate.css:520
- `.bounceOutRight` moves (`animation-name: bounceOutRight`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — static/css/animate.css:536
- `.bounceOutUp` moves (`animation-name: bounceOutUp`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — static/css/animate.css:556
- `.fadeInDown` moves (`animation-name: fadeInDown`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — static/css/animate.css:586
- `.fadeInDownBig` moves (`animation-name: fadeInDownBig`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — static/css/animate.css:602
- `.fadeInLeft` moves (`animation-name: fadeInLeft`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — static/css/animate.css:618
- `.fadeInLeftBig` moves (`animation-name: fadeInLeftBig`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — static/css/animate.css:634
- `.fadeInRight` moves (`animation-name: fadeInRight`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — static/css/animate.css:650
- `.fadeInRightBig` moves (`animation-name: fadeInRightBig`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — static/css/animate.css:666
- `.fadeInUp` moves (`animation-name: fadeInUp`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — static/css/animate.css:682
- `.fadeInUpBig` moves (`animation-name: fadeInUpBig`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — static/css/animate.css:698
- `.fadeOutDown` moves (`animation-name: fadeOutDown`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — static/css/animate.css:727
- `.fadeOutDownBig` moves (`animation-name: fadeOutDownBig`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — static/css/animate.css:742
- `.fadeOutLeft` moves (`animation-name: fadeOutLeft`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — static/css/animate.css:757
- `.fadeOutLeftBig` moves (`animation-name: fadeOutLeftBig`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — static/css/animate.css:772
- `.fadeOutRight` moves (`animation-name: fadeOutRight`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — static/css/animate.css:787
- `.fadeOutRightBig` moves (`animation-name: fadeOutRightBig`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — static/css/animate.css:802
- `.fadeOutUp` moves (`animation-name: fadeOutUp`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — static/css/animate.css:817
- `.fadeOutUpBig` moves (`animation-name: fadeOutUpBig`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — static/css/animate.css:832
- `.animated.flip` moves (`animation-name: flip`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — static/css/animate.css:865
- `.flipInX` moves (`animation-name: flipInX`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — static/css/animate.css:897
What to do
- Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AC7 · A11y enforcement
- No accessibility enforcement found — no automated accessibility check runs over your pages. Add an accessibility checker (axe-core, pa11y or Lighthouse) over your HTML in CI and fail the build on new violations. What was searched, so you can tell an absence from a miss: the 2 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
What to do
- Enforce accessibility over your pages: run an accessibility checker (axe-core, pa11y or Lighthouse) against your HTML in CI and fail the build on new violations — these run as standalone tools without adding a package manifest.
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX5 · Architecture & structure
C2 · Access Controls
- Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect.
What to do
- Name the access rules — DRF permission classes, django-guardian or django-rules permissions, a casbin or oso policy, or roles and permissions declared once — and consult them where access is checked (permission_classes, @permission_required, Depends), so the rule set is reviewable and testable on its own.
DM1 · Aggregate boundaries
DM10 · One transaction, one aggregate
DM11 · Constructible invalid state
DM12 · Ambient inputs in the domain
DM4 · Rich vs anemic model
- `UserDB` is an aggregate/entity with 6 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — backend/src/users/infrastructure/db/orm.py:7
- `VacancyDB` is an aggregate/entity with 22 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — backend/src/vacancies/infrastructure/db/orm.py:15
What to do
- Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services.
DM5 · Encapsulated state
DM6 · Domain ↔ infrastructure boundary
DM9 · Scattered domain decisions
- backend.src.vacancies.domain.entities.Vacancy's [source_id, source_name] are judged in backend.tests.fakes.vacancies.FakeSearchVacancyRepository, backend.tests.fakes.vacancies.FakeVacancyRepository — the same decision, restated. Every copy is a chance to drift, and copies drift silently because each one looks correct on its own. Move the judgement onto the type that owns the members and let the call sites ask it.
What to do
- Move each repeated judgement onto the type that owns the members it reads, so the rule has one home and cannot drift.
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.
P2 · Observability
What to do
- Consider OpenTelemetry tracing/metrics (opentelemetry-sdk) and a health-check endpoint (a /health route) for operability.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add bandit, `semgrep --config=p/python`, or CodeQL's python pack — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
What to do
- Run what this repository's stack ships: bandit, `semgrep --config=p/python`, or CodeQL's python pack — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
What to do
- Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P5 · DR & Backup
- A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
What to do
- Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.
P7 · Outbound HTTP resilience
P8 · Schema migrations
PF3 · Async & latency hygiene
S1 · Web-Security Posture
- `https://code.jquery.com/jquery-3.7.1.min.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. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. 3 such include(s) across the repository's markup. — backend/src/templates/base.html:22
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `REDACTED` builds the web-server image that serves this application, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.) — REDACTED:2
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.
- Set security response headers on the surface this repository serves: an `add_header` directive per header in the nginx/Caddy/Apache config, a `_headers` / `vercel.json` / `netlify.toml` entry for a static host, or `helmet()` in the HTTP server. `Content-Security-Policy` is the one that pays for itself first — it is what contains an injected script once one reaches the page — followed by `X-Content-Type-Options: nosniff` and a frame policy (`X-Frame-Options: DENY`, or CSP `frame-ancestors`). Where the app is served from a build container, the header configuration belongs in the image beside the built assets, so it ships with them rather than depending on where it lands.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X17 · Uncapped recursion over a caller-supplied document
X19 · Unrestored process-global state
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X3 · Exception handling
X30 · Support guard that admits what it rejects
X4 · Structured logging
- `debug` at line 78 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.debug("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.debug("order moved", order_id=order_id, status=status)` with structlog. — backend/src/integrations/infrastructure/http/aiohttp_client.py:78
- `debug` at line 96 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.debug("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.debug("order moved", order_id=order_id, status=status)` with structlog. — backend/src/integrations/infrastructure/http/aiohttp_client.py:96
- `debug` at line 114 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.debug("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.debug("order moved", order_id=order_id, status=status)` with structlog. — backend/src/integrations/infrastructure/http/aiohttp_client.py:114
- `debug` at line 131 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.debug("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.debug("order moved", order_id=order_id, status=status)` with structlog. — backend/src/integrations/infrastructure/http/aiohttp_client.py:131
- `debug` at line 150 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.debug("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.debug("order moved", order_id=order_id, status=status)` with structlog. — backend/src/integrations/infrastructure/http/aiohttp_client.py:150
What to do
- Interpolated log message defeats structured logging
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| 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 |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
| AC7 · A11y enforcement | enforcement — no page criterion | Enforcement posture (process) |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 75% | Adequate — gated by X4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 77% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 65% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 28% | Weak — gated by P1, P3, P5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 72% | Strong | Solid. |
| Domain Modelling | 80% | Adequate — gated by DM4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 40% | Adequate — gated by AC6 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Not evidenced — 4 control(s) we could not find positive evidence for
- C3 Audit Trail — Repo shows no audit-logging mechanism (an audit-log table or model — a class or table named for it — django-simple-history, django-auditlog, django-reversion, django-pghistory or SQLAlchemy-Continuum recording each change, or an event-sourced store beside one) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
- C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
- C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
- P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 58 check(s) not relevant to this codebase
- AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
- AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
- AX1 Captive dependencies — Not applicable: this repository's Python 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 — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads.
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — compose up failed (exit 14 — a file the compose project references is missing) — time="2026-11-08T00:27:32Z" level=warning msg="The \"DB_PORT\" variable is not set. Defaulting to a blank string." env file .env.dev not found: stat .env.dev: no such file or directory; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- D10 Test Quality — ~702 lines of test source are present (.py) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — no .py test runner
- D16 Bus Factor — single-contributor repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D19 Documentation Quality — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
- D20 ADR Quality — N/A — this repo declares itself a template / kata / sample / demo; a formal ADR log is deferred to a real application built from it.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Python not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .py, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- 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.
- D34 Knowledge Freshness — too few commits to judge knowledge freshness
- D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- D9 Test Distribution — Test source is present (.py) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so its unit/integration/BDD/E2E split couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
- DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
- 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
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks.
- P12 CI test-gate honesty — no CI workflow found
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (`coverage run -m pytest` then `coverage xml`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for a pytest-benchmark or pytest-codspeed dependency with tests taking the `benchmark` fixture, an asv.conf.json with its `time_`/`mem_`/`peakmem_` benchmarks, or a pyperf Runner, 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.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X16 Unfloored truncation loop — 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
- X18 Disposal-pattern correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X2 Cancellation propagation — no C# was loaded; this repository's Python was read, and no request in it can be cancelled by a caller — a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation
- 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.
- X29 Per-element action decided by a fixed element — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 8 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Viewport restricts zoom backend/src/templates/base.html:6
- Banned license: psycopg
- REDACTED
Serious — 56 finding(s)
- Animation without a prefers-reduced-motion guard static/css/animate.css:53
- Animation without a prefers-reduced-motion guard static/css/animate.css:88
- Animation without a prefers-reduced-motion guard static/css/animate.css:122
- Animation without a prefers-reduced-motion guard static/css/animate.css:140
- Animation without a prefers-reduced-motion guard static/css/animate.css:171
- Animation without a prefers-reduced-motion guard static/css/animate.css:198
- Animation without a prefers-reduced-motion guard static/css/animate.css:224
- Animation without a prefers-reduced-motion guard static/css/animate.css:260
- Animation without a prefers-reduced-motion guard static/css/animate.css:298
- Animation without a prefers-reduced-motion guard static/css/animate.css:336
- Animation without a prefers-reduced-motion guard static/css/animate.css:368
- Animation without a prefers-reduced-motion guard static/css/animate.css:400
- Animation without a prefers-reduced-motion guard static/css/animate.css:432
- Animation without a prefers-reduced-motion guard static/css/animate.css:464
- Animation without a prefers-reduced-motion guard static/css/animate.css:484
- Animation without a prefers-reduced-motion guard static/css/animate.css:504
- Animation without a prefers-reduced-motion guard static/css/animate.css:520
- Animation without a prefers-reduced-motion guard static/css/animate.css:536
- Animation without a prefers-reduced-motion guard static/css/animate.css:556
- Animation without a prefers-reduced-motion guard static/css/animate.css:586
- Animation without a prefers-reduced-motion guard static/css/animate.css:602
- Animation without a prefers-reduced-motion guard static/css/animate.css:618
- Animation without a prefers-reduced-motion guard static/css/animate.css:634
- Animation without a prefers-reduced-motion guard static/css/animate.css:650
- Animation without a prefers-reduced-motion guard static/css/animate.css:666
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Focus outline removed in CSS without a :focus replacement static/css/styles.css:182
- Focus outline removed in CSS without a :focus replacement static/css/styles.css:366
- REDACTED
- REDACTED
- Anemic entity: UserDB backend/src/users/infrastructure/db/orm.py:7
- Anemic entity: VacancyDB backend/src/vacancies/infrastructure/db/orm.py:15
- Low contrast colour pair in CSS (4.2:1) static/css/prism-themes/prism-vsc-dark-plus.css:46
- Accessibility enforcement below the top rung
- Yanked release: aiohttp
- print_structure.print_tree (cognitive 16) tools/print_structure.py:42
- Duplicated block (14 lines × 2) backend/src/crud/base.py:332
- No CI pipeline
- No DR/backup evidence
- Third-party script without Subresource Integrity backend/src/templates/base.html:22
Minor — 28 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Interpolated log message defeats structured logging backend/src/integrations/infrastructure/http/aiohttp_client.py:78
- Interpolated log message defeats structured logging backend/src/integrations/infrastructure/http/aiohttp_client.py:96
- Interpolated log message defeats structured logging backend/src/integrations/infrastructure/http/aiohttp_client.py:114
- Interpolated log message defeats structured logging backend/src/integrations/infrastructure/http/aiohttp_client.py:131
- Interpolated log message defeats structured logging backend/src/integrations/infrastructure/http/aiohttp_client.py:150
- No named authorization policies
- Projects may be oversized for their cohesion
- Rule about [source_id, source_name] decided in 2 places
- No ADRs
- No SAST
- No rollback/health safety
- No security response headers detected REDACTED:2
Minor — 23 finding(s)
- Outdated: aiosqlite
- Outdated: alembic
- Outdated: asgiref
- Outdated: asyncpg
- Outdated: bcrypt
- Outdated: celery
- Outdated: cryptography
- Outdated: elasticsearch
- Outdated: email-validator
- Outdated: fastapi
- Outdated: fastapi-storages
- Outdated: prometheus-fastapi-instrumentator
- Outdated: psycopg
- Outdated: pydantic-settings
- Outdated: pytest
- Outdated: pytest-asyncio
- Outdated: python-jose
- Outdated: python-json-logger
- Outdated: pytz
- Outdated: redis
- Outdated: sqladmin
- Outdated: uuid6
- Outdated: uvicorn
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-9f3e479938a3474c93225398adec1dde/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-9f3e479938a3474c93225398adec1dde/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 --exclude static/js . | 0 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 5 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 24 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 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 | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |