Executive summary
gftf2011/clean-node-todolist is rated At risk because critical security findings are open, most of them in the build pipeline. Its score is held back because three passwords or keys sit in the current code and we found no logging, tracing or health checks in the code. It scores 48 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 28, is the weakest lens and counts most in the score. The best first step is replacing the three exposed passwords or keys and switching the old ones off, worth about 18 points. Having someone learn and document the nine files no active contributor knows comes next, worth about 5 points. Raising Production Readiness to 70 would lift the score to about 64.
Thirteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Four passwords or keys in the code's history and three in the code are open to anyone who can read the repository, and three secrets can leak from the build pipeline. Pinning each tool to an exact version, replacing each exposed password or key and limiting each secret to its own step would close these risks. The three unsafe settings in infrastructure or container files need changing to safe values.
The product code is 4,986 lines, about €15,000 to rebuild.
If Production Readiness rose from 28 to 70, the lowest score rated Strong, the score would rise from 48 to about 64.
Rebuild cost: about €15,000 · Estimate
| Cost to rebuild | €5,100 to €26,000, for 85 to 269 hours of work, about 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 48. 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: 4,986 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 app.contracts.bus | 2 app.contracts.controllers | 3 app.contracts.database | 4 app.contracts.handlers | 5 app.contracts.middlewares | 6 app.contracts.providers.decryption | 7 app.contracts.providers.encryption | 8 app.contracts.services.note | 9 app.contracts.services.user | 10 app.controllers.view-models.note | 11 app.errors.application | 12 domain.errors.domain | 13 domain.repositories.note | 14 domain.repositories.user | 15 shared.either | 16 app.controllers.template.graphql-controller | 17 app.controllers.template.http-controller | 18 app.handlers.create-access-token | 19 app.handlers.create-note | 20 app.handlers.create-user | 21 app.handlers.delete-note | 22 app.handlers.find-note | 23 app.handlers.find-notes-by-user-id | 24 app.handlers.find-user | 25 app.handlers.find-user-by-email | 26 app.handlers.is-note-finished | 27 app.handlers.password-match | 28 app.handlers.update-note | 29 app.handlers.verify-token | 30 app.controllers.graphql.create-note | 31 app.controllers.graphql.get-note | 32 app.controllers.graphql.get-notes-by-user-id | 33 app.controllers.graphql.update-finished-note | 34 app.controllers.graphql.update-note | 35 app.controllers.rest.create-note | 36 app.controllers.rest.get-note | 37 app.controllers.rest.get-notes-by-user-id | 38 app.controllers.rest.update-finished-note | 39 app.controllers.rest.update-note | 40 main.factories.app.handlers |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 app.contracts.bus | ||||||||||||||||||||||||||||||||||||||||
| 2 app.contracts.controllers | ||||||||||||||||||||||||||||||||||||||||
| 3 app.contracts.database | ||||||||||||||||||||||||||||||||||||||||
| 4 app.contracts.handlers | ||||||||||||||||||||||||||||||||||||||||
| 5 app.contracts.middlewares | ||||||||||||||||||||||||||||||||||||||||
| 6 app.contracts.providers.decryption | ||||||||||||||||||||||||||||||||||||||||
| 7 app.contracts.providers.encryption | ||||||||||||||||||||||||||||||||||||||||
| 8 app.contracts.services.note | ||||||||||||||||||||||||||||||||||||||||
| 9 app.contracts.services.user | ||||||||||||||||||||||||||||||||||||||||
| 10 app.controllers.view-models.note | ||||||||||||||||||||||||||||||||||||||||
| 11 app.errors.application | ||||||||||||||||||||||||||||||||||||||||
| 12 domain.errors.domain | ||||||||||||||||||||||||||||||||||||||||
| 13 domain.repositories.note | ||||||||||||||||||||||||||||||||||||||||
| 14 domain.repositories.user | ||||||||||||||||||||||||||||||||||||||||
| 15 shared.either | ||||||||||||||||||||||||||||||||||||||||
| 16 app.controllers.template.graphql-controller | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 app.controllers.template.http-controller | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 app.handlers.create-access-token | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 app.handlers.create-note | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 20 app.handlers.create-user | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 21 app.handlers.delete-note | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 22 app.handlers.find-note | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 23 app.handlers.find-notes-by-user-id | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 24 app.handlers.find-user | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 25 app.handlers.find-user-by-email | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 26 app.handlers.is-note-finished | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 27 app.handlers.password-match | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 app.handlers.update-note | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 29 app.handlers.verify-token | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 30 app.controllers.graphql.create-note | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 31 app.controllers.graphql.get-note | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 32 app.controllers.graphql.get-notes-by-user-id | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 33 app.controllers.graphql.update-finished-note | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 34 app.controllers.graphql.update-note | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 35 app.controllers.rest.create-note | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 36 app.controllers.rest.get-note | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 37 app.controllers.rest.get-notes-by-user-id | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 38 app.controllers.rest.update-finished-note | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 39 app.controllers.rest.update-note | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 40 main.factories.app.handlers | 12 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
16→2 app.controllers.template.graphql-controller uses app.contracts.controllers✕
- Connections
- 1 pair of types, where a type in app.controllers.template.graphql-controller uses a type in app.contracts.controllers.
- The types involved
src.app.controllers.template.graphql-controller.TemplateGraphqlController→src.app.contracts.controllers.Controller
- Direction
- app.controllers.template.graphql-controller uses app.contracts.controllers, so a change to app.contracts.controllers can break app.controllers.template.graphql-controller, while a change to app.controllers.template.graphql-controller can't break app.contracts.controllers.
- Position
- Below the diagonal: app.controllers.template.graphql-controller uses a module listed above it, which is the healthy direction.
17→2 app.controllers.template.http-controller uses app.contracts.controllers✕
- Connections
- 1 pair of types, where a type in app.controllers.template.http-controller uses a type in app.contracts.controllers.
- The types involved
src.app.controllers.template.http-controller.TemplateHttpController→src.app.contracts.controllers.Controller
- Direction
- app.controllers.template.http-controller uses app.contracts.controllers, so a change to app.contracts.controllers can break app.controllers.template.http-controller, while a change to app.controllers.template.http-controller can't break app.contracts.controllers.
- Position
- Below the diagonal: app.controllers.template.http-controller uses a module listed above it, which is the healthy direction.
18→4 app.handlers.create-access-token uses app.contracts.handlers✕
- Connections
- 1 pair of types, where a type in app.handlers.create-access-token uses a type in app.contracts.handlers.
- The types involved
src.app.handlers.create-access-token.CreateAccessTokenHandler→src.app.contracts.handlers.Handler
- Direction
- app.handlers.create-access-token uses app.contracts.handlers, so a change to app.contracts.handlers can break app.handlers.create-access-token, while a change to app.handlers.create-access-token can't break app.contracts.handlers.
- Position
- Below the diagonal: app.handlers.create-access-token uses a module listed above it, which is the healthy direction.
19→4 app.handlers.create-note uses app.contracts.handlers✕
- Connections
- 1 pair of types, where a type in app.handlers.create-note uses a type in app.contracts.handlers.
- The types involved
src.app.handlers.create-note.CreateNoteHandler→src.app.contracts.handlers.Handler
- Direction
- app.handlers.create-note uses app.contracts.handlers, so a change to app.contracts.handlers can break app.handlers.create-note, while a change to app.handlers.create-note can't break app.contracts.handlers.
- Position
- Below the diagonal: app.handlers.create-note uses a module listed above it, which is the healthy direction.
19→7 app.handlers.create-note uses app.contracts.providers.encryption✕
- Connections
- 1 pair of types, where a type in app.handlers.create-note uses a type in app.contracts.providers.encryption.
- The types involved
src.app.handlers.create-note.CreateNoteHandler→src.app.contracts.providers.encryption.EncryptionProvider
- Direction
- app.handlers.create-note uses app.contracts.providers.encryption, so a change to app.contracts.providers.encryption can break app.handlers.create-note, while a change to app.handlers.create-note can't break app.contracts.providers.encryption.
- Position
- Below the diagonal: app.handlers.create-note uses a module listed above it, which is the healthy direction.
19→13 app.handlers.create-note uses domain.repositories.note✕
- Connections
- 1 pair of types, where a type in app.handlers.create-note uses a type in domain.repositories.note.
- The types involved
src.app.handlers.create-note.CreateNoteHandler→src.domain.repositories.note.NoteRepository
- Direction
- app.handlers.create-note uses domain.repositories.note, so a change to domain.repositories.note can break app.handlers.create-note, while a change to app.handlers.create-note can't break domain.repositories.note.
- Position
- Below the diagonal: app.handlers.create-note uses a module listed above it, which is the healthy direction.
20→4 app.handlers.create-user uses app.contracts.handlers✕
- Connections
- 1 pair of types, where a type in app.handlers.create-user uses a type in app.contracts.handlers.
- The types involved
src.app.handlers.create-user.CreateUserHandler→src.app.contracts.handlers.Handler
- Direction
- app.handlers.create-user uses app.contracts.handlers, so a change to app.contracts.handlers can break app.handlers.create-user, while a change to app.handlers.create-user can't break app.contracts.handlers.
- Position
- Below the diagonal: app.handlers.create-user uses a module listed above it, which is the healthy direction.
20→7 app.handlers.create-user uses app.contracts.providers.encryption✕
- Connections
- 1 pair of types, where a type in app.handlers.create-user uses a type in app.contracts.providers.encryption.
- The types involved
src.app.handlers.create-user.CreateUserHandler→src.app.contracts.providers.encryption.EncryptionProvider
- Direction
- app.handlers.create-user uses app.contracts.providers.encryption, so a change to app.contracts.providers.encryption can break app.handlers.create-user, while a change to app.handlers.create-user can't break app.contracts.providers.encryption.
- Position
- Below the diagonal: app.handlers.create-user uses a module listed above it, which is the healthy direction.
20→14 app.handlers.create-user uses domain.repositories.user✕
- Connections
- 1 pair of types, where a type in app.handlers.create-user uses a type in domain.repositories.user.
- The types involved
src.app.handlers.create-user.CreateUserHandler→src.domain.repositories.user.UserRepository
- Direction
- app.handlers.create-user uses domain.repositories.user, so a change to domain.repositories.user can break app.handlers.create-user, while a change to app.handlers.create-user can't break domain.repositories.user.
- Position
- Below the diagonal: app.handlers.create-user uses a module listed above it, which is the healthy direction.
21→4 app.handlers.delete-note uses app.contracts.handlers✕
- Connections
- 1 pair of types, where a type in app.handlers.delete-note uses a type in app.contracts.handlers.
- The types involved
src.app.handlers.delete-note.DeleteNoteHandler→src.app.contracts.handlers.Handler
- Direction
- app.handlers.delete-note uses app.contracts.handlers, so a change to app.contracts.handlers can break app.handlers.delete-note, while a change to app.handlers.delete-note can't break app.contracts.handlers.
- Position
- Below the diagonal: app.handlers.delete-note uses a module listed above it, which is the healthy direction.
21→13 app.handlers.delete-note uses domain.repositories.note✕
- Connections
- 1 pair of types, where a type in app.handlers.delete-note uses a type in domain.repositories.note.
- The types involved
src.app.handlers.delete-note.DeleteNoteHandler→src.domain.repositories.note.NoteRepository
- Direction
- app.handlers.delete-note uses domain.repositories.note, so a change to domain.repositories.note can break app.handlers.delete-note, while a change to app.handlers.delete-note can't break domain.repositories.note.
- Position
- Below the diagonal: app.handlers.delete-note uses a module listed above it, which is the healthy direction.
22→4 app.handlers.find-note uses app.contracts.handlers✕
- Connections
- 1 pair of types, where a type in app.handlers.find-note uses a type in app.contracts.handlers.
- The types involved
src.app.handlers.find-note.FindNoteHandler→src.app.contracts.handlers.Handler
- Direction
- app.handlers.find-note uses app.contracts.handlers, so a change to app.contracts.handlers can break app.handlers.find-note, while a change to app.handlers.find-note can't break app.contracts.handlers.
- Position
- Below the diagonal: app.handlers.find-note uses a module listed above it, which is the healthy direction.
22→6 app.handlers.find-note uses app.contracts.providers.decryption✕
- Connections
- 1 pair of types, where a type in app.handlers.find-note uses a type in app.contracts.providers.decryption.
- The types involved
src.app.handlers.find-note.FindNoteHandler→src.app.contracts.providers.decryption.DecryptionProvider
- Direction
- app.handlers.find-note uses app.contracts.providers.decryption, so a change to app.contracts.providers.decryption can break app.handlers.find-note, while a change to app.handlers.find-note can't break app.contracts.providers.decryption.
- Position
- Below the diagonal: app.handlers.find-note uses a module listed above it, which is the healthy direction.
22→13 app.handlers.find-note uses domain.repositories.note✕
- Connections
- 1 pair of types, where a type in app.handlers.find-note uses a type in domain.repositories.note.
- The types involved
src.app.handlers.find-note.FindNoteHandler→src.domain.repositories.note.NoteRepository
- Direction
- app.handlers.find-note uses domain.repositories.note, so a change to domain.repositories.note can break app.handlers.find-note, while a change to app.handlers.find-note can't break domain.repositories.note.
- Position
- Below the diagonal: app.handlers.find-note uses a module listed above it, which is the healthy direction.
23→4 app.handlers.find-notes-by-user-id uses app.contracts.handlers✕
- Connections
- 1 pair of types, where a type in app.handlers.find-notes-by-user-id uses a type in app.contracts.handlers.
- The types involved
src.app.handlers.find-notes-by-user-id.FindNotesByUserIdHandler→src.app.contracts.handlers.Handler
- Direction
- app.handlers.find-notes-by-user-id uses app.contracts.handlers, so a change to app.contracts.handlers can break app.handlers.find-notes-by-user-id, while a change to app.handlers.find-notes-by-user-id can't break app.contracts.handlers.
- Position
- Below the diagonal: app.handlers.find-notes-by-user-id uses a module listed above it, which is the healthy direction.
23→6 app.handlers.find-notes-by-user-id uses app.contracts.providers.decryption✕
- Connections
- 1 pair of types, where a type in app.handlers.find-notes-by-user-id uses a type in app.contracts.providers.decryption.
- The types involved
src.app.handlers.find-notes-by-user-id.FindNotesByUserIdHandler→src.app.contracts.providers.decryption.DecryptionProvider
- Direction
- app.handlers.find-notes-by-user-id uses app.contracts.providers.decryption, so a change to app.contracts.providers.decryption can break app.handlers.find-notes-by-user-id, while a change to app.handlers.find-notes-by-user-id can't break app.contracts.providers.decryption.
- Position
- Below the diagonal: app.handlers.find-notes-by-user-id uses a module listed above it, which is the healthy direction.
23→13 app.handlers.find-notes-by-user-id uses domain.repositories.note✕
- Connections
- 1 pair of types, where a type in app.handlers.find-notes-by-user-id uses a type in domain.repositories.note.
- The types involved
src.app.handlers.find-notes-by-user-id.FindNotesByUserIdHandler→src.domain.repositories.note.NoteRepository
- Direction
- app.handlers.find-notes-by-user-id uses domain.repositories.note, so a change to domain.repositories.note can break app.handlers.find-notes-by-user-id, while a change to app.handlers.find-notes-by-user-id can't break domain.repositories.note.
- Position
- Below the diagonal: app.handlers.find-notes-by-user-id uses a module listed above it, which is the healthy direction.
24→4 app.handlers.find-user uses app.contracts.handlers✕
- Connections
- 1 pair of types, where a type in app.handlers.find-user uses a type in app.contracts.handlers.
- The types involved
src.app.handlers.find-user.FindUserHandler→src.app.contracts.handlers.Handler
- Direction
- app.handlers.find-user uses app.contracts.handlers, so a change to app.contracts.handlers can break app.handlers.find-user, while a change to app.handlers.find-user can't break app.contracts.handlers.
- Position
- Below the diagonal: app.handlers.find-user uses a module listed above it, which is the healthy direction.
24→6 app.handlers.find-user uses app.contracts.providers.decryption✕
- Connections
- 1 pair of types, where a type in app.handlers.find-user uses a type in app.contracts.providers.decryption.
- The types involved
src.app.handlers.find-user.FindUserHandler→src.app.contracts.providers.decryption.DecryptionProvider
- Direction
- app.handlers.find-user uses app.contracts.providers.decryption, so a change to app.contracts.providers.decryption can break app.handlers.find-user, while a change to app.handlers.find-user can't break app.contracts.providers.decryption.
- Position
- Below the diagonal: app.handlers.find-user uses a module listed above it, which is the healthy direction.
24→14 app.handlers.find-user uses domain.repositories.user✕
- Connections
- 1 pair of types, where a type in app.handlers.find-user uses a type in domain.repositories.user.
- The types involved
src.app.handlers.find-user.FindUserHandler→src.domain.repositories.user.UserRepository
- Direction
- app.handlers.find-user uses domain.repositories.user, so a change to domain.repositories.user can break app.handlers.find-user, while a change to app.handlers.find-user can't break domain.repositories.user.
- Position
- Below the diagonal: app.handlers.find-user uses a module listed above it, which is the healthy direction.
25→4 app.handlers.find-user-by-email uses app.contracts.handlers✕
- Connections
- 1 pair of types, where a type in app.handlers.find-user-by-email uses a type in app.contracts.handlers.
- The types involved
src.app.handlers.find-user-by-email.FindUserByEmailHandler→src.app.contracts.handlers.Handler
- Direction
- app.handlers.find-user-by-email uses app.contracts.handlers, so a change to app.contracts.handlers can break app.handlers.find-user-by-email, while a change to app.handlers.find-user-by-email can't break app.contracts.handlers.
- Position
- Below the diagonal: app.handlers.find-user-by-email uses a module listed above it, which is the healthy direction.
25→6 app.handlers.find-user-by-email uses app.contracts.providers.decryption✕
- Connections
- 1 pair of types, where a type in app.handlers.find-user-by-email uses a type in app.contracts.providers.decryption.
- The types involved
src.app.handlers.find-user-by-email.FindUserByEmailHandler→src.app.contracts.providers.decryption.DecryptionProvider
- Direction
- app.handlers.find-user-by-email uses app.contracts.providers.decryption, so a change to app.contracts.providers.decryption can break app.handlers.find-user-by-email, while a change to app.handlers.find-user-by-email can't break app.contracts.providers.decryption.
- Position
- Below the diagonal: app.handlers.find-user-by-email uses a module listed above it, which is the healthy direction.
25→7 app.handlers.find-user-by-email uses app.contracts.providers.encryption✕
- Connections
- 1 pair of types, where a type in app.handlers.find-user-by-email uses a type in app.contracts.providers.encryption.
- The types involved
src.app.handlers.find-user-by-email.FindUserByEmailHandler→src.app.contracts.providers.encryption.EncryptionProvider
- Direction
- app.handlers.find-user-by-email uses app.contracts.providers.encryption, so a change to app.contracts.providers.encryption can break app.handlers.find-user-by-email, while a change to app.handlers.find-user-by-email can't break app.contracts.providers.encryption.
- Position
- Below the diagonal: app.handlers.find-user-by-email uses a module listed above it, which is the healthy direction.
25→14 app.handlers.find-user-by-email uses domain.repositories.user✕
- Connections
- 1 pair of types, where a type in app.handlers.find-user-by-email uses a type in domain.repositories.user.
- The types involved
src.app.handlers.find-user-by-email.FindUserByEmailHandler→src.domain.repositories.user.UserRepository
- Direction
- app.handlers.find-user-by-email uses domain.repositories.user, so a change to domain.repositories.user can break app.handlers.find-user-by-email, while a change to app.handlers.find-user-by-email can't break domain.repositories.user.
- Position
- Below the diagonal: app.handlers.find-user-by-email uses a module listed above it, which is the healthy direction.
26→4 app.handlers.is-note-finished uses app.contracts.handlers✕
- Connections
- 1 pair of types, where a type in app.handlers.is-note-finished uses a type in app.contracts.handlers.
- The types involved
src.app.handlers.is-note-finished.IsNoteFinishedHandler→src.app.contracts.handlers.Handler
- Direction
- app.handlers.is-note-finished uses app.contracts.handlers, so a change to app.contracts.handlers can break app.handlers.is-note-finished, while a change to app.handlers.is-note-finished can't break app.contracts.handlers.
- Position
- Below the diagonal: app.handlers.is-note-finished uses a module listed above it, which is the healthy direction.
26→13 app.handlers.is-note-finished uses domain.repositories.note✕
- Connections
- 1 pair of types, where a type in app.handlers.is-note-finished uses a type in domain.repositories.note.
- The types involved
src.app.handlers.is-note-finished.IsNoteFinishedHandler→src.domain.repositories.note.NoteRepository
- Direction
- app.handlers.is-note-finished uses domain.repositories.note, so a change to domain.repositories.note can break app.handlers.is-note-finished, while a change to app.handlers.is-note-finished can't break domain.repositories.note.
- Position
- Below the diagonal: app.handlers.is-note-finished uses a module listed above it, which is the healthy direction.
27→4 app.handlers.password-match uses app.contracts.handlers✕
- Connections
- 1 pair of types, where a type in app.handlers.password-match uses a type in app.contracts.handlers.
- The types involved
src.app.handlers.password-match.PasswordMatchHandler→src.app.contracts.handlers.Handler
- Direction
- app.handlers.password-match uses app.contracts.handlers, so a change to app.contracts.handlers can break app.handlers.password-match, while a change to app.handlers.password-match can't break app.contracts.handlers.
- Position
- Below the diagonal: app.handlers.password-match uses a module listed above it, which is the healthy direction.
28→4 app.handlers.update-note uses app.contracts.handlers✕
- Connections
- 1 pair of types, where a type in app.handlers.update-note uses a type in app.contracts.handlers.
- The types involved
src.app.handlers.update-note.UpdateNoteHandler→src.app.contracts.handlers.Handler
- Direction
- app.handlers.update-note uses app.contracts.handlers, so a change to app.contracts.handlers can break app.handlers.update-note, while a change to app.handlers.update-note can't break app.contracts.handlers.
- Position
- Below the diagonal: app.handlers.update-note uses a module listed above it, which is the healthy direction.
28→7 app.handlers.update-note uses app.contracts.providers.encryption✕
- Connections
- 1 pair of types, where a type in app.handlers.update-note uses a type in app.contracts.providers.encryption.
- The types involved
src.app.handlers.update-note.UpdateNoteHandler→src.app.contracts.providers.encryption.EncryptionProvider
- Direction
- app.handlers.update-note uses app.contracts.providers.encryption, so a change to app.contracts.providers.encryption can break app.handlers.update-note, while a change to app.handlers.update-note can't break app.contracts.providers.encryption.
- Position
- Below the diagonal: app.handlers.update-note uses a module listed above it, which is the healthy direction.
28→13 app.handlers.update-note uses domain.repositories.note✕
- Connections
- 1 pair of types, where a type in app.handlers.update-note uses a type in domain.repositories.note.
- The types involved
src.app.handlers.update-note.UpdateNoteHandler→src.domain.repositories.note.NoteRepository
- Direction
- app.handlers.update-note uses domain.repositories.note, so a change to domain.repositories.note can break app.handlers.update-note, while a change to app.handlers.update-note can't break domain.repositories.note.
- Position
- Below the diagonal: app.handlers.update-note uses a module listed above it, which is the healthy direction.
29→4 app.handlers.verify-token uses app.contracts.handlers✕
- Connections
- 1 pair of types, where a type in app.handlers.verify-token uses a type in app.contracts.handlers.
- The types involved
src.app.handlers.verify-token.VerifyTokenHandler→src.app.contracts.handlers.Handler
- Direction
- app.handlers.verify-token uses app.contracts.handlers, so a change to app.contracts.handlers can break app.handlers.verify-token, while a change to app.handlers.verify-token can't break app.contracts.handlers.
- Position
- Below the diagonal: app.handlers.verify-token uses a module listed above it, which is the healthy direction.
29→15 app.handlers.verify-token uses shared.either✕
- Connections
- 1 pair of types, where a type in app.handlers.verify-token uses a type in shared.either.
- The types involved
src.app.handlers.verify-token.VerifyTokenHandler→src.shared.either.Either
- Direction
- app.handlers.verify-token uses shared.either, so a change to shared.either can break app.handlers.verify-token, while a change to app.handlers.verify-token can't break shared.either.
- Position
- Below the diagonal: app.handlers.verify-token uses a module listed above it, which is the healthy direction.
30→8 app.controllers.graphql.create-note uses app.contracts.services.note✕
- Connections
- 1 pair of types, where a type in app.controllers.graphql.create-note uses a type in app.contracts.services.note.
- The types involved
src.app.controllers.graphql.create-note.CreateNoteGraphqlController→src.app.contracts.services.note.NoteService
- Direction
- app.controllers.graphql.create-note uses app.contracts.services.note, so a change to app.contracts.services.note can break app.controllers.graphql.create-note, while a change to app.controllers.graphql.create-note can't break app.contracts.services.note.
- Position
- Below the diagonal: app.controllers.graphql.create-note uses a module listed above it, which is the healthy direction.
30→9 app.controllers.graphql.create-note uses app.contracts.services.user✕
- Connections
- 1 pair of types, where a type in app.controllers.graphql.create-note uses a type in app.contracts.services.user.
- The types involved
src.app.controllers.graphql.create-note.CreateNoteGraphqlController→src.app.contracts.services.user.UserService
- Direction
- app.controllers.graphql.create-note uses app.contracts.services.user, so a change to app.contracts.services.user can break app.controllers.graphql.create-note, while a change to app.controllers.graphql.create-note can't break app.contracts.services.user.
- Position
- Below the diagonal: app.controllers.graphql.create-note uses a module listed above it, which is the healthy direction.
30→10 app.controllers.graphql.create-note uses app.controllers.view-models.note✕
- Connections
- 1 pair of types, where a type in app.controllers.graphql.create-note uses a type in app.controllers.view-models.note.
- The types involved
src.app.controllers.graphql.create-note.CreateNoteGraphqlController→src.app.controllers.view-models.note.NoteViewModel
- Direction
- app.controllers.graphql.create-note uses app.controllers.view-models.note, so a change to app.controllers.view-models.note can break app.controllers.graphql.create-note, while a change to app.controllers.graphql.create-note can't break app.controllers.view-models.note.
- Position
- Below the diagonal: app.controllers.graphql.create-note uses a module listed above it, which is the healthy direction.
30→16 app.controllers.graphql.create-note uses app.controllers.template.graphql-controller✕
- Connections
- 1 pair of types, where a type in app.controllers.graphql.create-note uses a type in app.controllers.template.graphql-controller.
- The types involved
src.app.controllers.graphql.create-note.CreateNoteGraphqlController→src.app.controllers.template.graphql-controller.TemplateGraphqlController
- Direction
- app.controllers.graphql.create-note uses app.controllers.template.graphql-controller, so a change to app.controllers.template.graphql-controller can break app.controllers.graphql.create-note, while a change to app.controllers.graphql.create-note can't break app.controllers.template.graphql-controller.
- Position
- Below the diagonal: app.controllers.graphql.create-note uses a module listed above it, which is the healthy direction.
31→8 app.controllers.graphql.get-note uses app.contracts.services.note✕
- Connections
- 1 pair of types, where a type in app.controllers.graphql.get-note uses a type in app.contracts.services.note.
- The types involved
src.app.controllers.graphql.get-note.GetNoteGraphqlController→src.app.contracts.services.note.NoteService
- Direction
- app.controllers.graphql.get-note uses app.contracts.services.note, so a change to app.contracts.services.note can break app.controllers.graphql.get-note, while a change to app.controllers.graphql.get-note can't break app.contracts.services.note.
- Position
- Below the diagonal: app.controllers.graphql.get-note uses a module listed above it, which is the healthy direction.
31→9 app.controllers.graphql.get-note uses app.contracts.services.user✕
- Connections
- 1 pair of types, where a type in app.controllers.graphql.get-note uses a type in app.contracts.services.user.
- The types involved
src.app.controllers.graphql.get-note.GetNoteGraphqlController→src.app.contracts.services.user.UserService
- Direction
- app.controllers.graphql.get-note uses app.contracts.services.user, so a change to app.contracts.services.user can break app.controllers.graphql.get-note, while a change to app.controllers.graphql.get-note can't break app.contracts.services.user.
- Position
- Below the diagonal: app.controllers.graphql.get-note uses a module listed above it, which is the healthy direction.
31→10 app.controllers.graphql.get-note uses app.controllers.view-models.note✕
- Connections
- 1 pair of types, where a type in app.controllers.graphql.get-note uses a type in app.controllers.view-models.note.
- The types involved
src.app.controllers.graphql.get-note.GetNoteGraphqlController→src.app.controllers.view-models.note.NoteViewModel
- Direction
- app.controllers.graphql.get-note uses app.controllers.view-models.note, so a change to app.controllers.view-models.note can break app.controllers.graphql.get-note, while a change to app.controllers.graphql.get-note can't break app.controllers.view-models.note.
- Position
- Below the diagonal: app.controllers.graphql.get-note uses a module listed above it, which is the healthy direction.
31→16 app.controllers.graphql.get-note uses app.controllers.template.graphql-controller✕
- Connections
- 1 pair of types, where a type in app.controllers.graphql.get-note uses a type in app.controllers.template.graphql-controller.
- The types involved
src.app.controllers.graphql.get-note.GetNoteGraphqlController→src.app.controllers.template.graphql-controller.TemplateGraphqlController
- Direction
- app.controllers.graphql.get-note uses app.controllers.template.graphql-controller, so a change to app.controllers.template.graphql-controller can break app.controllers.graphql.get-note, while a change to app.controllers.graphql.get-note can't break app.controllers.template.graphql-controller.
- Position
- Below the diagonal: app.controllers.graphql.get-note uses a module listed above it, which is the healthy direction.
32→8 app.controllers.graphql.get-notes-by-user-id uses app.contracts.services.note✕
- Connections
- 1 pair of types, where a type in app.controllers.graphql.get-notes-by-user-id uses a type in app.contracts.services.note.
- The types involved
src.app.controllers.graphql.get-notes-by-user-id.GetNotesByUserIdGraphqlController→src.app.contracts.services.note.NoteService
- Direction
- app.controllers.graphql.get-notes-by-user-id uses app.contracts.services.note, so a change to app.contracts.services.note can break app.controllers.graphql.get-notes-by-user-id, while a change to app.controllers.graphql.get-notes-by-user-id can't break app.contracts.services.note.
- Position
- Below the diagonal: app.controllers.graphql.get-notes-by-user-id uses a module listed above it, which is the healthy direction.
32→9 app.controllers.graphql.get-notes-by-user-id uses app.contracts.services.user✕
- Connections
- 1 pair of types, where a type in app.controllers.graphql.get-notes-by-user-id uses a type in app.contracts.services.user.
- The types involved
src.app.controllers.graphql.get-notes-by-user-id.GetNotesByUserIdGraphqlController→src.app.contracts.services.user.UserService
- Direction
- app.controllers.graphql.get-notes-by-user-id uses app.contracts.services.user, so a change to app.contracts.services.user can break app.controllers.graphql.get-notes-by-user-id, while a change to app.controllers.graphql.get-notes-by-user-id can't break app.contracts.services.user.
- Position
- Below the diagonal: app.controllers.graphql.get-notes-by-user-id uses a module listed above it, which is the healthy direction.
32→16 app.controllers.graphql.get-notes-by-user-id uses app.controllers.template.graphql-controller✕
- Connections
- 1 pair of types, where a type in app.controllers.graphql.get-notes-by-user-id uses a type in app.controllers.template.graphql-controller.
- The types involved
src.app.controllers.graphql.get-notes-by-user-id.GetNotesByUserIdGraphqlController→src.app.controllers.template.graphql-controller.TemplateGraphqlController
- Direction
- app.controllers.graphql.get-notes-by-user-id uses app.controllers.template.graphql-controller, so a change to app.controllers.template.graphql-controller can break app.controllers.graphql.get-notes-by-user-id, while a change to app.controllers.graphql.get-notes-by-user-id can't break app.controllers.template.graphql-controller.
- Position
- Below the diagonal: app.controllers.graphql.get-notes-by-user-id uses a module listed above it, which is the healthy direction.
33→8 app.controllers.graphql.update-finished-note uses app.contracts.services.note✕
- Connections
- 1 pair of types, where a type in app.controllers.graphql.update-finished-note uses a type in app.contracts.services.note.
- The types involved
src.app.controllers.graphql.update-finished-note.UpdateFinishedNoteGraphqlController→src.app.contracts.services.note.NoteService
- Direction
- app.controllers.graphql.update-finished-note uses app.contracts.services.note, so a change to app.contracts.services.note can break app.controllers.graphql.update-finished-note, while a change to app.controllers.graphql.update-finished-note can't break app.contracts.services.note.
- Position
- Below the diagonal: app.controllers.graphql.update-finished-note uses a module listed above it, which is the healthy direction.
33→9 app.controllers.graphql.update-finished-note uses app.contracts.services.user✕
- Connections
- 1 pair of types, where a type in app.controllers.graphql.update-finished-note uses a type in app.contracts.services.user.
- The types involved
src.app.controllers.graphql.update-finished-note.UpdateFinishedNoteGraphqlController→src.app.contracts.services.user.UserService
- Direction
- app.controllers.graphql.update-finished-note uses app.contracts.services.user, so a change to app.contracts.services.user can break app.controllers.graphql.update-finished-note, while a change to app.controllers.graphql.update-finished-note can't break app.contracts.services.user.
- Position
- Below the diagonal: app.controllers.graphql.update-finished-note uses a module listed above it, which is the healthy direction.
33→10 app.controllers.graphql.update-finished-note uses app.controllers.view-models.note✕
- Connections
- 1 pair of types, where a type in app.controllers.graphql.update-finished-note uses a type in app.controllers.view-models.note.
- The types involved
src.app.controllers.graphql.update-finished-note.UpdateFinishedNoteGraphqlController→src.app.controllers.view-models.note.NoteViewModel
- Direction
- app.controllers.graphql.update-finished-note uses app.controllers.view-models.note, so a change to app.controllers.view-models.note can break app.controllers.graphql.update-finished-note, while a change to app.controllers.graphql.update-finished-note can't break app.controllers.view-models.note.
- Position
- Below the diagonal: app.controllers.graphql.update-finished-note uses a module listed above it, which is the healthy direction.
33→16 app.controllers.graphql.update-finished-note uses app.controllers.template.graphql-controller✕
- Connections
- 1 pair of types, where a type in app.controllers.graphql.update-finished-note uses a type in app.controllers.template.graphql-controller.
- The types involved
src.app.controllers.graphql.update-finished-note.UpdateFinishedNoteGraphqlController→src.app.controllers.template.graphql-controller.TemplateGraphqlController
- Direction
- app.controllers.graphql.update-finished-note uses app.controllers.template.graphql-controller, so a change to app.controllers.template.graphql-controller can break app.controllers.graphql.update-finished-note, while a change to app.controllers.graphql.update-finished-note can't break app.controllers.template.graphql-controller.
- Position
- Below the diagonal: app.controllers.graphql.update-finished-note uses a module listed above it, which is the healthy direction.
34→8 app.controllers.graphql.update-note uses app.contracts.services.note✕
- Connections
- 1 pair of types, where a type in app.controllers.graphql.update-note uses a type in app.contracts.services.note.
- The types involved
src.app.controllers.graphql.update-note.UpdateNoteGraphqlController→src.app.contracts.services.note.NoteService
- Direction
- app.controllers.graphql.update-note uses app.contracts.services.note, so a change to app.contracts.services.note can break app.controllers.graphql.update-note, while a change to app.controllers.graphql.update-note can't break app.contracts.services.note.
- Position
- Below the diagonal: app.controllers.graphql.update-note uses a module listed above it, which is the healthy direction.
34→9 app.controllers.graphql.update-note uses app.contracts.services.user✕
- Connections
- 1 pair of types, where a type in app.controllers.graphql.update-note uses a type in app.contracts.services.user.
- The types involved
src.app.controllers.graphql.update-note.UpdateNoteGraphqlController→src.app.contracts.services.user.UserService
- Direction
- app.controllers.graphql.update-note uses app.contracts.services.user, so a change to app.contracts.services.user can break app.controllers.graphql.update-note, while a change to app.controllers.graphql.update-note can't break app.contracts.services.user.
- Position
- Below the diagonal: app.controllers.graphql.update-note uses a module listed above it, which is the healthy direction.
34→10 app.controllers.graphql.update-note uses app.controllers.view-models.note✕
- Connections
- 1 pair of types, where a type in app.controllers.graphql.update-note uses a type in app.controllers.view-models.note.
- The types involved
src.app.controllers.graphql.update-note.UpdateNoteGraphqlController→src.app.controllers.view-models.note.NoteViewModel
- Direction
- app.controllers.graphql.update-note uses app.controllers.view-models.note, so a change to app.controllers.view-models.note can break app.controllers.graphql.update-note, while a change to app.controllers.graphql.update-note can't break app.controllers.view-models.note.
- Position
- Below the diagonal: app.controllers.graphql.update-note uses a module listed above it, which is the healthy direction.
34→16 app.controllers.graphql.update-note uses app.controllers.template.graphql-controller✕
- Connections
- 1 pair of types, where a type in app.controllers.graphql.update-note uses a type in app.controllers.template.graphql-controller.
- The types involved
src.app.controllers.graphql.update-note.UpdateNoteGraphqlController→src.app.controllers.template.graphql-controller.TemplateGraphqlController
- Direction
- app.controllers.graphql.update-note uses app.controllers.template.graphql-controller, so a change to app.controllers.template.graphql-controller can break app.controllers.graphql.update-note, while a change to app.controllers.graphql.update-note can't break app.controllers.template.graphql-controller.
- Position
- Below the diagonal: app.controllers.graphql.update-note uses a module listed above it, which is the healthy direction.
35→8 app.controllers.rest.create-note uses app.contracts.services.note✕
- Connections
- 1 pair of types, where a type in app.controllers.rest.create-note uses a type in app.contracts.services.note.
- The types involved
src.app.controllers.rest.create-note.CreateNoteHttpController→src.app.contracts.services.note.NoteService
- Direction
- app.controllers.rest.create-note uses app.contracts.services.note, so a change to app.contracts.services.note can break app.controllers.rest.create-note, while a change to app.controllers.rest.create-note can't break app.contracts.services.note.
- Position
- Below the diagonal: app.controllers.rest.create-note uses a module listed above it, which is the healthy direction.
35→9 app.controllers.rest.create-note uses app.contracts.services.user✕
- Connections
- 1 pair of types, where a type in app.controllers.rest.create-note uses a type in app.contracts.services.user.
- The types involved
src.app.controllers.rest.create-note.CreateNoteHttpController→src.app.contracts.services.user.UserService
- Direction
- app.controllers.rest.create-note uses app.contracts.services.user, so a change to app.contracts.services.user can break app.controllers.rest.create-note, while a change to app.controllers.rest.create-note can't break app.contracts.services.user.
- Position
- Below the diagonal: app.controllers.rest.create-note uses a module listed above it, which is the healthy direction.
35→10 app.controllers.rest.create-note uses app.controllers.view-models.note✕
- Connections
- 1 pair of types, where a type in app.controllers.rest.create-note uses a type in app.controllers.view-models.note.
- The types involved
src.app.controllers.rest.create-note.CreateNoteHttpController→src.app.controllers.view-models.note.NoteViewModel
- Direction
- app.controllers.rest.create-note uses app.controllers.view-models.note, so a change to app.controllers.view-models.note can break app.controllers.rest.create-note, while a change to app.controllers.rest.create-note can't break app.controllers.view-models.note.
- Position
- Below the diagonal: app.controllers.rest.create-note uses a module listed above it, which is the healthy direction.
35→17 app.controllers.rest.create-note uses app.controllers.template.http-controller✕
- Connections
- 1 pair of types, where a type in app.controllers.rest.create-note uses a type in app.controllers.template.http-controller.
- The types involved
src.app.controllers.rest.create-note.CreateNoteHttpController→src.app.controllers.template.http-controller.TemplateHttpController
- Direction
- app.controllers.rest.create-note uses app.controllers.template.http-controller, so a change to app.controllers.template.http-controller can break app.controllers.rest.create-note, while a change to app.controllers.rest.create-note can't break app.controllers.template.http-controller.
- Position
- Below the diagonal: app.controllers.rest.create-note uses a module listed above it, which is the healthy direction.
36→8 app.controllers.rest.get-note uses app.contracts.services.note✕
- Connections
- 1 pair of types, where a type in app.controllers.rest.get-note uses a type in app.contracts.services.note.
- The types involved
src.app.controllers.rest.get-note.GetNoteHttpController→src.app.contracts.services.note.NoteService
- Direction
- app.controllers.rest.get-note uses app.contracts.services.note, so a change to app.contracts.services.note can break app.controllers.rest.get-note, while a change to app.controllers.rest.get-note can't break app.contracts.services.note.
- Position
- Below the diagonal: app.controllers.rest.get-note uses a module listed above it, which is the healthy direction.
36→9 app.controllers.rest.get-note uses app.contracts.services.user✕
- Connections
- 1 pair of types, where a type in app.controllers.rest.get-note uses a type in app.contracts.services.user.
- The types involved
src.app.controllers.rest.get-note.GetNoteHttpController→src.app.contracts.services.user.UserService
- Direction
- app.controllers.rest.get-note uses app.contracts.services.user, so a change to app.contracts.services.user can break app.controllers.rest.get-note, while a change to app.controllers.rest.get-note can't break app.contracts.services.user.
- Position
- Below the diagonal: app.controllers.rest.get-note uses a module listed above it, which is the healthy direction.
36→10 app.controllers.rest.get-note uses app.controllers.view-models.note✕
- Connections
- 1 pair of types, where a type in app.controllers.rest.get-note uses a type in app.controllers.view-models.note.
- The types involved
src.app.controllers.rest.get-note.GetNoteHttpController→src.app.controllers.view-models.note.NoteViewModel
- Direction
- app.controllers.rest.get-note uses app.controllers.view-models.note, so a change to app.controllers.view-models.note can break app.controllers.rest.get-note, while a change to app.controllers.rest.get-note can't break app.controllers.view-models.note.
- Position
- Below the diagonal: app.controllers.rest.get-note uses a module listed above it, which is the healthy direction.
36→17 app.controllers.rest.get-note uses app.controllers.template.http-controller✕
- Connections
- 1 pair of types, where a type in app.controllers.rest.get-note uses a type in app.controllers.template.http-controller.
- The types involved
src.app.controllers.rest.get-note.GetNoteHttpController→src.app.controllers.template.http-controller.TemplateHttpController
- Direction
- app.controllers.rest.get-note uses app.controllers.template.http-controller, so a change to app.controllers.template.http-controller can break app.controllers.rest.get-note, while a change to app.controllers.rest.get-note can't break app.controllers.template.http-controller.
- Position
- Below the diagonal: app.controllers.rest.get-note uses a module listed above it, which is the healthy direction.
37→8 app.controllers.rest.get-notes-by-user-id uses app.contracts.services.note✕
- Connections
- 1 pair of types, where a type in app.controllers.rest.get-notes-by-user-id uses a type in app.contracts.services.note.
- The types involved
src.app.controllers.rest.get-notes-by-user-id.GetNotesByUserIdHttpController→src.app.contracts.services.note.NoteService
- Direction
- app.controllers.rest.get-notes-by-user-id uses app.contracts.services.note, so a change to app.contracts.services.note can break app.controllers.rest.get-notes-by-user-id, while a change to app.controllers.rest.get-notes-by-user-id can't break app.contracts.services.note.
- Position
- Below the diagonal: app.controllers.rest.get-notes-by-user-id uses a module listed above it, which is the healthy direction.
37→9 app.controllers.rest.get-notes-by-user-id uses app.contracts.services.user✕
- Connections
- 1 pair of types, where a type in app.controllers.rest.get-notes-by-user-id uses a type in app.contracts.services.user.
- The types involved
src.app.controllers.rest.get-notes-by-user-id.GetNotesByUserIdHttpController→src.app.contracts.services.user.UserService
- Direction
- app.controllers.rest.get-notes-by-user-id uses app.contracts.services.user, so a change to app.contracts.services.user can break app.controllers.rest.get-notes-by-user-id, while a change to app.controllers.rest.get-notes-by-user-id can't break app.contracts.services.user.
- Position
- Below the diagonal: app.controllers.rest.get-notes-by-user-id uses a module listed above it, which is the healthy direction.
37→17 app.controllers.rest.get-notes-by-user-id uses app.controllers.template.http-controller✕
- Connections
- 1 pair of types, where a type in app.controllers.rest.get-notes-by-user-id uses a type in app.controllers.template.http-controller.
- The types involved
src.app.controllers.rest.get-notes-by-user-id.GetNotesByUserIdHttpController→src.app.controllers.template.http-controller.TemplateHttpController
- Direction
- app.controllers.rest.get-notes-by-user-id uses app.controllers.template.http-controller, so a change to app.controllers.template.http-controller can break app.controllers.rest.get-notes-by-user-id, while a change to app.controllers.rest.get-notes-by-user-id can't break app.controllers.template.http-controller.
- Position
- Below the diagonal: app.controllers.rest.get-notes-by-user-id uses a module listed above it, which is the healthy direction.
38→8 app.controllers.rest.update-finished-note uses app.contracts.services.note✕
- Connections
- 1 pair of types, where a type in app.controllers.rest.update-finished-note uses a type in app.contracts.services.note.
- The types involved
src.app.controllers.rest.update-finished-note.UpdateFinishedNoteHttpController→src.app.contracts.services.note.NoteService
- Direction
- app.controllers.rest.update-finished-note uses app.contracts.services.note, so a change to app.contracts.services.note can break app.controllers.rest.update-finished-note, while a change to app.controllers.rest.update-finished-note can't break app.contracts.services.note.
- Position
- Below the diagonal: app.controllers.rest.update-finished-note uses a module listed above it, which is the healthy direction.
38→9 app.controllers.rest.update-finished-note uses app.contracts.services.user✕
- Connections
- 1 pair of types, where a type in app.controllers.rest.update-finished-note uses a type in app.contracts.services.user.
- The types involved
src.app.controllers.rest.update-finished-note.UpdateFinishedNoteHttpController→src.app.contracts.services.user.UserService
- Direction
- app.controllers.rest.update-finished-note uses app.contracts.services.user, so a change to app.contracts.services.user can break app.controllers.rest.update-finished-note, while a change to app.controllers.rest.update-finished-note can't break app.contracts.services.user.
- Position
- Below the diagonal: app.controllers.rest.update-finished-note uses a module listed above it, which is the healthy direction.
38→10 app.controllers.rest.update-finished-note uses app.controllers.view-models.note✕
- Connections
- 1 pair of types, where a type in app.controllers.rest.update-finished-note uses a type in app.controllers.view-models.note.
- The types involved
src.app.controllers.rest.update-finished-note.UpdateFinishedNoteHttpController→src.app.controllers.view-models.note.NoteViewModel
- Direction
- app.controllers.rest.update-finished-note uses app.controllers.view-models.note, so a change to app.controllers.view-models.note can break app.controllers.rest.update-finished-note, while a change to app.controllers.rest.update-finished-note can't break app.controllers.view-models.note.
- Position
- Below the diagonal: app.controllers.rest.update-finished-note uses a module listed above it, which is the healthy direction.
38→17 app.controllers.rest.update-finished-note uses app.controllers.template.http-controller✕
- Connections
- 1 pair of types, where a type in app.controllers.rest.update-finished-note uses a type in app.controllers.template.http-controller.
- The types involved
src.app.controllers.rest.update-finished-note.UpdateFinishedNoteHttpController→src.app.controllers.template.http-controller.TemplateHttpController
- Direction
- app.controllers.rest.update-finished-note uses app.controllers.template.http-controller, so a change to app.controllers.template.http-controller can break app.controllers.rest.update-finished-note, while a change to app.controllers.rest.update-finished-note can't break app.controllers.template.http-controller.
- Position
- Below the diagonal: app.controllers.rest.update-finished-note uses a module listed above it, which is the healthy direction.
39→8 app.controllers.rest.update-note uses app.contracts.services.note✕
- Connections
- 1 pair of types, where a type in app.controllers.rest.update-note uses a type in app.contracts.services.note.
- The types involved
src.app.controllers.rest.update-note.UpdateNoteHttpController→src.app.contracts.services.note.NoteService
- Direction
- app.controllers.rest.update-note uses app.contracts.services.note, so a change to app.contracts.services.note can break app.controllers.rest.update-note, while a change to app.controllers.rest.update-note can't break app.contracts.services.note.
- Position
- Below the diagonal: app.controllers.rest.update-note uses a module listed above it, which is the healthy direction.
39→9 app.controllers.rest.update-note uses app.contracts.services.user✕
- Connections
- 1 pair of types, where a type in app.controllers.rest.update-note uses a type in app.contracts.services.user.
- The types involved
src.app.controllers.rest.update-note.UpdateNoteHttpController→src.app.contracts.services.user.UserService
- Direction
- app.controllers.rest.update-note uses app.contracts.services.user, so a change to app.contracts.services.user can break app.controllers.rest.update-note, while a change to app.controllers.rest.update-note can't break app.contracts.services.user.
- Position
- Below the diagonal: app.controllers.rest.update-note uses a module listed above it, which is the healthy direction.
39→10 app.controllers.rest.update-note uses app.controllers.view-models.note✕
- Connections
- 1 pair of types, where a type in app.controllers.rest.update-note uses a type in app.controllers.view-models.note.
- The types involved
src.app.controllers.rest.update-note.UpdateNoteHttpController→src.app.controllers.view-models.note.NoteViewModel
- Direction
- app.controllers.rest.update-note uses app.controllers.view-models.note, so a change to app.controllers.view-models.note can break app.controllers.rest.update-note, while a change to app.controllers.rest.update-note can't break app.controllers.view-models.note.
- Position
- Below the diagonal: app.controllers.rest.update-note uses a module listed above it, which is the healthy direction.
39→17 app.controllers.rest.update-note uses app.controllers.template.http-controller✕
- Connections
- 1 pair of types, where a type in app.controllers.rest.update-note uses a type in app.controllers.template.http-controller.
- The types involved
src.app.controllers.rest.update-note.UpdateNoteHttpController→src.app.controllers.template.http-controller.TemplateHttpController
- Direction
- app.controllers.rest.update-note uses app.controllers.template.http-controller, so a change to app.controllers.template.http-controller can break app.controllers.rest.update-note, while a change to app.controllers.rest.update-note can't break app.controllers.template.http-controller.
- Position
- Below the diagonal: app.controllers.rest.update-note uses a module listed above it, which is the healthy direction.
40→3 main.factories.app.handlers uses app.contracts.database✕
- Connections
- 12 pairs of types, where a type in main.factories.app.handlers uses a type in app.contracts.database.
- The types involved
src.main.factories.app.handlers.create-access-token→src.app.contracts.database.DatabaseTransactionsrc.main.factories.app.handlers.create-note→src.app.contracts.database.DatabaseTransactionsrc.main.factories.app.handlers.create-user→src.app.contracts.database.DatabaseTransactionsrc.main.factories.app.handlers.delete-note→src.app.contracts.database.DatabaseTransactionsrc.main.factories.app.handlers.find-note→src.app.contracts.database.DatabaseTransactionsrc.main.factories.app.handlers.find-notes-by-user-id→src.app.contracts.database.DatabaseTransactionsrc.main.factories.app.handlers.find-user→src.app.contracts.database.DatabaseTransactionsrc.main.factories.app.handlers.find-user-by-email→src.app.contracts.database.DatabaseTransactionsrc.main.factories.app.handlers.is-note-finished→src.app.contracts.database.DatabaseTransactionsrc.main.factories.app.handlers.password-match→src.app.contracts.database.DatabaseTransactionsrc.main.factories.app.handlers.update-note→src.app.contracts.database.DatabaseTransactionsrc.main.factories.app.handlers.verify-token→src.app.contracts.database.DatabaseTransaction
- Direction
- main.factories.app.handlers uses app.contracts.database, so a change to app.contracts.database can break main.factories.app.handlers, while a change to main.factories.app.handlers can't break app.contracts.database.
- Position
- Below the diagonal: main.factories.app.handlers uses a module listed above it, which is the healthy direction.
40→18 main.factories.app.handlers uses app.handlers.create-access-token✕
- Connections
- 1 pair of types, where a type in main.factories.app.handlers uses a type in app.handlers.create-access-token.
- The types involved
src.main.factories.app.handlers.create-access-token→src.app.handlers.create-access-token.CreateAccessTokenHandler
- Direction
- main.factories.app.handlers uses app.handlers.create-access-token, so a change to app.handlers.create-access-token can break main.factories.app.handlers, while a change to main.factories.app.handlers can't break app.handlers.create-access-token.
- Position
- Below the diagonal: main.factories.app.handlers uses a module listed above it, which is the healthy direction.
40→19 main.factories.app.handlers uses app.handlers.create-note✕
- Connections
- 1 pair of types, where a type in main.factories.app.handlers uses a type in app.handlers.create-note.
- The types involved
src.main.factories.app.handlers.create-note→src.app.handlers.create-note.CreateNoteHandler
- Direction
- main.factories.app.handlers uses app.handlers.create-note, so a change to app.handlers.create-note can break main.factories.app.handlers, while a change to main.factories.app.handlers can't break app.handlers.create-note.
- Position
- Below the diagonal: main.factories.app.handlers uses a module listed above it, which is the healthy direction.
40→20 main.factories.app.handlers uses app.handlers.create-user✕
- Connections
- 1 pair of types, where a type in main.factories.app.handlers uses a type in app.handlers.create-user.
- The types involved
src.main.factories.app.handlers.create-user→src.app.handlers.create-user.CreateUserHandler
- Direction
- main.factories.app.handlers uses app.handlers.create-user, so a change to app.handlers.create-user can break main.factories.app.handlers, while a change to main.factories.app.handlers can't break app.handlers.create-user.
- Position
- Below the diagonal: main.factories.app.handlers uses a module listed above it, which is the healthy direction.
40→21 main.factories.app.handlers uses app.handlers.delete-note✕
- Connections
- 1 pair of types, where a type in main.factories.app.handlers uses a type in app.handlers.delete-note.
- The types involved
src.main.factories.app.handlers.delete-note→src.app.handlers.delete-note.DeleteNoteHandler
- Direction
- main.factories.app.handlers uses app.handlers.delete-note, so a change to app.handlers.delete-note can break main.factories.app.handlers, while a change to main.factories.app.handlers can't break app.handlers.delete-note.
- Position
- Below the diagonal: main.factories.app.handlers uses a module listed above it, which is the healthy direction.
40→22 main.factories.app.handlers uses app.handlers.find-note✕
- Connections
- 1 pair of types, where a type in main.factories.app.handlers uses a type in app.handlers.find-note.
- The types involved
src.main.factories.app.handlers.find-note→src.app.handlers.find-note.FindNoteHandler
- Direction
- main.factories.app.handlers uses app.handlers.find-note, so a change to app.handlers.find-note can break main.factories.app.handlers, while a change to main.factories.app.handlers can't break app.handlers.find-note.
- Position
- Below the diagonal: main.factories.app.handlers uses a module listed above it, which is the healthy direction.
40→23 main.factories.app.handlers uses app.handlers.find-notes-by-user-id✕
- Connections
- 1 pair of types, where a type in main.factories.app.handlers uses a type in app.handlers.find-notes-by-user-id.
- The types involved
src.main.factories.app.handlers.find-notes-by-user-id→src.app.handlers.find-notes-by-user-id.FindNotesByUserIdHandler
- Direction
- main.factories.app.handlers uses app.handlers.find-notes-by-user-id, so a change to app.handlers.find-notes-by-user-id can break main.factories.app.handlers, while a change to main.factories.app.handlers can't break app.handlers.find-notes-by-user-id.
- Position
- Below the diagonal: main.factories.app.handlers uses a module listed above it, which is the healthy direction.
40→24 main.factories.app.handlers uses app.handlers.find-user✕
- Connections
- 1 pair of types, where a type in main.factories.app.handlers uses a type in app.handlers.find-user.
- The types involved
src.main.factories.app.handlers.find-user→src.app.handlers.find-user.FindUserHandler
- Direction
- main.factories.app.handlers uses app.handlers.find-user, so a change to app.handlers.find-user can break main.factories.app.handlers, while a change to main.factories.app.handlers can't break app.handlers.find-user.
- Position
- Below the diagonal: main.factories.app.handlers uses a module listed above it, which is the healthy direction.
40→25 main.factories.app.handlers uses app.handlers.find-user-by-email✕
- Connections
- 1 pair of types, where a type in main.factories.app.handlers uses a type in app.handlers.find-user-by-email.
- The types involved
src.main.factories.app.handlers.find-user-by-email→src.app.handlers.find-user-by-email.FindUserByEmailHandler
- Direction
- main.factories.app.handlers uses app.handlers.find-user-by-email, so a change to app.handlers.find-user-by-email can break main.factories.app.handlers, while a change to main.factories.app.handlers can't break app.handlers.find-user-by-email.
- Position
- Below the diagonal: main.factories.app.handlers uses a module listed above it, which is the healthy direction.
40→26 main.factories.app.handlers uses app.handlers.is-note-finished✕
- Connections
- 1 pair of types, where a type in main.factories.app.handlers uses a type in app.handlers.is-note-finished.
- The types involved
src.main.factories.app.handlers.is-note-finished→src.app.handlers.is-note-finished.IsNoteFinishedHandler
- Direction
- main.factories.app.handlers uses app.handlers.is-note-finished, so a change to app.handlers.is-note-finished can break main.factories.app.handlers, while a change to main.factories.app.handlers can't break app.handlers.is-note-finished.
- Position
- Below the diagonal: main.factories.app.handlers uses a module listed above it, which is the healthy direction.
40→27 main.factories.app.handlers uses app.handlers.password-match✕
- Connections
- 1 pair of types, where a type in main.factories.app.handlers uses a type in app.handlers.password-match.
- The types involved
src.main.factories.app.handlers.password-match→src.app.handlers.password-match.PasswordMatchHandler
- Direction
- main.factories.app.handlers uses app.handlers.password-match, so a change to app.handlers.password-match can break main.factories.app.handlers, while a change to main.factories.app.handlers can't break app.handlers.password-match.
- Position
- Below the diagonal: main.factories.app.handlers uses a module listed above it, which is the healthy direction.
40→28 main.factories.app.handlers uses app.handlers.update-note✕
- Connections
- 1 pair of types, where a type in main.factories.app.handlers uses a type in app.handlers.update-note.
- The types involved
src.main.factories.app.handlers.update-note→src.app.handlers.update-note.UpdateNoteHandler
- Direction
- main.factories.app.handlers uses app.handlers.update-note, so a change to app.handlers.update-note can break main.factories.app.handlers, while a change to main.factories.app.handlers can't break app.handlers.update-note.
- Position
- Below the diagonal: main.factories.app.handlers uses a module listed above it, which is the healthy direction.
40→29 main.factories.app.handlers uses app.handlers.verify-token✕
- Connections
- 1 pair of types, where a type in main.factories.app.handlers uses a type in app.handlers.verify-token.
- The types involved
src.main.factories.app.handlers.verify-token→src.app.handlers.verify-token.VerifyTokenHandler
- Direction
- main.factories.app.handlers uses app.handlers.verify-token, so a change to app.handlers.verify-token can break main.factories.app.handlers, while a change to main.factories.app.handlers can't break app.handlers.verify-token.
- Position
- Below the diagonal: main.factories.app.handlers 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 — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 19 | High / Critical |
| A07:2025 — Authentication Failures | 8 | High / Critical |
| A02:2025 — Security Misconfiguration | 5 | High / Critical |
Roadmap
Top priorities: Resolve the 3 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (3); Adopt pino (or winston) and log at meaningful points in the services you run; Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 3 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (3). | +18.1 pts | Low | REDACTED Scanning |
| Resolve the 9 Orphaned file finding(s) in Knowledge Freshness — start with note.ts, jest.config.js, jest-integration.config.js. | +4.7 pts | Low | Knowledge Freshness |
| Adopt pino (or winston) and log at meaningful points in the services you run. | +4.8 pts | Medium | Observability |
| Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery. | +4.8 pts | Medium | DR & Backup |
| 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. | +3.7 pts | Medium | Architecture documentation |
| Improve Test Distribution — currently 8.2/10. | +2.8 pts | Medium | Test Distribution |
| Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. | +1.3 pts | Low | Knowledge Freshness |
| Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. | +1.0 pts | Low | Project Cohesion |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.5 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 0.9 | Slop | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 2.3 | Slop | IaC & Container Security: Critical IaC: REDACTED |
| REDACTED | 5.8 | Mixed | Secrets (history): REDACTED: REDACTED |
| .nvmrc | 7.9 | Mixed | Platform End-of-Life: End-of-life runtime: Node.js 18 |
| src/infra/database/postgres/postgres-transaction.ts | 8.5 | Near-clean | Code Coverage: Low coverage: src/infra/database/postgres/postgres-transaction.ts |
| tests/integration/infra/database/postgres/connection/pg-connection.test.ts | 8.5 | Near-clean | Test Quality: No assertions: should open and close database connection |
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 69 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 69 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, 132 of 147 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
- 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 reliability not included — the JavaScript/TypeScript suite (jest via `npm install --ignore-scripts` (no lockfile) in the repository root (468 tests)) did not finish re-running within its budget: too large to re-run within its budget.
- D12 Dependency Hygiene — 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. This repository's 1 package.json manifest(s) WERE read and their pinning discipline assessed; what went unanswered is the currency half, because answering it needs a lockfile resolved to CONCRETE versions and this repository commits none — a package.json states version RANGES, and a range names no particular release to be behind. So registry.npmjs.org was never asked, and there was nothing here for it to grade. This is a true statement about the repository and NOT a gap on our side: no lockfile reader we could write would find anything here to read, so there is no capability behind this row to build.
- D14 License Compliance — 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. Not scored — this repository declares package.json manifests but commits no lockfile this pass can resolve (npm, pnpm, yarn and bun each write a different one, and `bun.lockb` is a binary format with no published shape), so the set of packages it actually ships is not resolvable from the checkout: its declarations carry version RANGES, and grading whichever release happens to be newest today would be a verdict about a dependency graph this repository has not pinned. Commit the lock and this dimension grades its production dependencies against registry.npmjs.org. NOT a finding that this repository's licences are compliant: this dimension asserts nothing about its licensing in either direction.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. All 9 significant source file(s) were last meaningfully changed so long ago that no living knowledge remains — nothing since has been substantial enough to re-establish ownership (a broad, mechanical sweep that touches many files shallowly does not count, and neither does no activity at all). There is no concentration to measure, so the bus factor is not scored. This is not a clean bill: nobody currently holds working knowledge of this code (see D34 Knowledge Freshness). Counted over 9 of the 238 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
- 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: it declares a published package (package.json), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
- D30 Dependency Vulnerabilities — 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. The scanner produced no output at all, so no dependency was actually scanned. 1 of 2 declared ecosystem(s) (npm) WERE scanned and every vulnerability they reported is included in this result; osv was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that osv is free of known-vulnerable dependencies. osv: the scanner produced no output at all, so no dependency was actually scanned. This is reported as a measurement gap rather than a clean pass. osv-scanner documents exit 128 as "no package sources found" — but this scan only invoked it because the tree declares a source it supports (`pom.xml` and the resolved lockfiles among them), so the tool's report and this repository disagree. Check that those sources are reachable from the directory the scan ran in before concluding anything is missing. If this tree really does commit only range-pinned manifests, commit the lockfile your package manager produces — but only where your ecosystem HAS one and commits it: Maven has none at all (osv-scanner reads `pom.xml` directly) and Gradle writes one only under opt-in dependency locking, while a published Composer package and a published Dart library both deliberately exclude theirs. In those three, generate one in CI before the scan instead — a resolved dependency list or an SBOM fed to the scanner.
- D43 Malicious Dependencies — 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. The scanner produced no output at all, so no dependency was actually scanned. 1 of 2 declared ecosystem(s) (npm) WERE scanned and every vulnerability they reported is included in this result; osv was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that osv is free of known-vulnerable dependencies. osv: the scanner produced no output at all, so no dependency was actually scanned. This is reported as a measurement gap rather than a clean pass. osv-scanner documents exit 128 as "no package sources found" — but this scan only invoked it because the tree declares a source it supports (`pom.xml` and the resolved lockfiles among them), so the tool's report and this repository disagree. Check that those sources are reachable from the directory the scan ran in before concluding anything is missing. If this tree really does commit only range-pinned manifests, commit the lockfile your package manager produces — but only where your ecosystem HAS one and commits it: Maven has none at all (osv-scanner reads `pom.xml` directly) and Gradle writes one only under opt-in dependency locking, while a published Composer package and a published Dart library both deliberately exclude theirs. In those three, generate one in CI before the scan instead — a resolved dependency list or an SBOM fed to the scanner.
- 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 (docker/dev/docker-compose.yml). compose up failed (exit 17 — an image could not be built) — unable to prepare context: path "docker/dev/docker/dev/images/postgres" not found; 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. 'pg' is imported (src/infra/database/postgres/postgres-transaction.ts:1), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C3 Audit Trail — 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. 'pg' is imported (src/infra/database/postgres/postgres-transaction.ts:1), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C4 Data Retention — 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. 'pg' is imported (src/infra/database/postgres/postgres-transaction.ts:1), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C5 Data-Subject Rights — 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. 'pg' is imported (src/infra/database/postgres/postgres-transaction.ts:1), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- X2 Cancellation propagation — 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, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- 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.
- 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
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
0 god class(es) detected.
D6 · Cohesion (LCOM4)
0 of 47 classes have LCOM4 above 3.
D8 · Code Coverage
Line coverage 99.4% — 1 file(s) below 50%. Measured from the JavaScript/TypeScript suite (jest via `npm install --ignore-scripts` (no lockfile) in the repository root).
What to do
- Resolve the 1 Low coverage finding(s) in Code Coverage — start with postgres-transaction.ts. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Code Coverage in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
468 test methods: 382 unit, 20 integration, 0 BDD, 66 e2e. The JavaScript/TypeScript suite contributes 468 `it`/`test` case(s) across 90 test file(s) declaring at least one; its tier split is read from package names and paths only.
What to do
- Improve Test Distribution — currently 8.2/10. — 468 test methods: 382 unit, 20 integration, 0 BDD, 66 e2e. The JavaScript/TypeScript suite contributes 468 `it`/`test` case(s) across 90 test file(s) declaring at least one; its tier split is read from package names and paths only.
D10 · Test Quality
0 skipped, 1 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 468 tests.
What to do
- Resolve the 1 No assertions finding(s) in Test Quality — start with pg-connection.test.ts. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D13 · REDACTED Scanning
3 secret(s) detected.
What to do
- Resolve the 3 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
- Enforce REDACTED Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — 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 4986 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 1 document(s) read across 1 unit(s).
D26 · Project Cohesion
1 of 1 build units (npm) 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
84 % of calls cross a namespace and 31 % go through an interface, but 59 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
What to do
- Resolve the 1 High interface indirection finding(s) in Navigability. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 Scattered collaborators finding(s) in Navigability. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
4 finding(s): 0 critical, 4 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 4 REDACTED finding(s) in Secrets (history) — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
19 finding(s): 0 critical, 16 high, 3 medium, 0 low. 13 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens.
What to do
- Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).
- No action in Static Analysis (SAST) — all 13 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (13 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in the 1 ecosystem(s) that were scanned (npm). Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (npm), and the findings above are real and complete for them. osv was not scanned (osv: the scanner produced no output at all, so no dependency was actually scanned), so this is not the whole dependency surface and the result is reported at reduced confidence.
D31 · IaC & Container Security
5 finding(s): 2 critical, 1 high, 1 medium, 1 low.
What to do
- Resolve the 2 Critical IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 High IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Medium IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D34 · Knowledge Freshness
9 of 9 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/infra/repositories/note.ts. Counted over 9 of the 238 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 9 Orphaned file finding(s) in Knowledge Freshness — start with note.ts, jest.config.js, jest-integration.config.js. — One of this dimension's main actionable groups (9 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D43 · Malicious Dependencies
No known-vulnerable dependencies in the 1 ecosystem(s) that were scanned (npm). Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (npm), and the findings above are real and complete for them. osv was not scanned (osv: the scanner produced no output at all, so no dependency was actually scanned), so this is not the whole dependency surface and the result is reported at reduced confidence.
D44 · Platform End-of-Life
1 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 13 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.
What to do
- Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with .nvmrc. — One of this dimension's main actionable groups (1 warning-level).
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
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. — src/app/middlewares/utils/http.ts:14
What to do
- Name the access rules — roles/permissions declared once (a @Roles/@Permissions decorator with its guard, a CASL ability, a casbin model, or Supabase CREATE POLICY) and consulted where access is checked, so the rule set is reviewable and testable on its own.
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
M1 · Documentation (README)
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- No logging call was found in the 234 JavaScript/TypeScript production file(s) this check read across 1 module(s). Each was searched for its ecosystem's logging libraries (JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
What to do
- Adopt pino (or winston) and log at meaningful points in the services you run.
- Consider OpenTelemetry tracing/metrics (@opentelemetry/sdk-node) and a health-check endpoint (@godaddy/terminus or a /health route) for operability.
P3 · Security & performance tooling
- `package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — package.json:62
What to do
- 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.
P9 · Domain vs controller coverage
PF3 · Async & latency hygiene
R1 · Type Safety
What to do
- Migrate the remaining .js/.jsx files to TypeScript.
R10 · Code Duplication
- 7 duplicated blocks under src/app/ have copies in at least two of the sibling directories controllers, middlewares — 5 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 7 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 7 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 7 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/app/controllers/strategies/error-handler.ts:63
- src/infra/repositories/note.ts:97 · src/infra/repositories/user.ts:84 — the two spans are one implementation copied and then locally edited — 397 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/infra/repositories/note.ts:97
- src/infra/providers/decryption.ts:5 · src/infra/providers/encryption.ts:5 — the two spans are one implementation copied and then locally edited — 302 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/infra/providers/decryption.ts:5
- src/app/controllers/strategies/error-handler.ts:63 · src/app/middlewares/strategies/error-handler.ts:32 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/app/controllers/strategies/error-handler.ts:63
- src/app/controllers/rest/create-note.ts:12 · src/app/controllers/rest/update-note.ts:12 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/app/controllers/rest/create-note.ts:12
- src/infra/repositories/note.ts:268 · src/infra/repositories/user.ts:199 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/infra/repositories/note.ts:268
- src/app/controllers/rest/delete-note.ts:14 · src/app/controllers/rest/get-note.ts:11 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/app/controllers/rest/delete-note.ts:14
- src/app/controllers/rest/update-finished-note.ts:29 · src/app/controllers/rest/update-note.ts:35 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/app/controllers/rest/update-finished-note.ts:29
- src/infra/repositories/user.ts:21 · src/infra/repositories/user.ts:45 — all 2 copies are in the same file, and what repeats is a LIST OF ENTRIES rather than behaviour — the same entries written out more than once. Extract them into one shared, exported constant and spread that constant into each site, rather than into a function the sites call: a list like this often lives in declarative metadata (a decorator's options object, a static configuration table) that a build step must be able to read statically, where a function call is not allowed. Adding an entry to one copy and not the other is the failure this prevents. — src/infra/repositories/user.ts:21
- src/main/factories/app/handlers/find-note.ts:4 · src/main/factories/app/handlers/find-notes-by-user-id.ts:4 · src/main/factories/app/handlers/find-user-by-email.ts:6 · src/main/factories/app/handlers/find-user.ts:4 · +1 more site(s) not listed — the 5 copies are spread across 5 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/main/factories/app/handlers/find-note.ts:4
- src/domain/value-objects/description.ts:4 · src/domain/value-objects/title.ts:4 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — src/domain/value-objects/description.ts:4
- src/domain/value-objects/lastname.ts:5 · src/domain/value-objects/name.ts:5 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — src/domain/value-objects/lastname.ts:5
- src/infra/repositories/user.ts:94 · src/infra/repositories/user.ts:114 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/infra/repositories/user.ts:94
- src/app/controllers/graphql/update-finished-note.ts:9 · src/app/controllers/graphql/update-note.ts:10 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/app/controllers/graphql/update-finished-note.ts:9
- src/app/controllers/rest/create-note.ts:10 · src/app/controllers/rest/delete-note.ts:12 · src/app/controllers/rest/get-note.ts:9 · src/app/controllers/rest/get-notes-by-user-id.ts:9 · +2 more site(s) not listed — the 6 copies are spread across 6 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/app/controllers/rest/create-note.ts:10
- src/app/controllers/rest/sign-in.ts:21 · src/app/controllers/rest/sign-up.ts:29 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/app/controllers/rest/sign-in.ts:21
- src/app/controllers/decorators/database.ts:11 · src/app/middlewares/decorators/database.ts:11 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — src/app/controllers/decorators/database.ts:11
- src/app/controllers/graphql/create-note.ts:9 · src/app/controllers/graphql/get-note.ts:9 · src/app/controllers/graphql/get-notes-by-user-id.ts:9 · src/app/controllers/graphql/update-finished-note.ts:9 · +1 more site(s) not listed — the 5 copies are spread across 5 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/app/controllers/graphql/create-note.ts:9
- src/app/controllers/template/graphql-controller.ts:10 · src/app/middlewares/template/graphql-middleware.ts:9 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/app/controllers/template/graphql-controller.ts:10
- src/infra/repositories/note.ts:66 · src/infra/repositories/note.ts:93 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/infra/repositories/note.ts:66
- src/app/middlewares/graphql/auth.ts:13 · src/app/middlewares/rest/auth.ts:28 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/app/middlewares/graphql/auth.ts:13
- src/infra/repositories/note.ts:23 · src/infra/repositories/user.ts:21 · src/infra/repositories/user.ts:45 — the 3 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/infra/repositories/note.ts:23
- src/main/factories/app/handlers/find-note.ts:15 · src/main/factories/app/handlers/find-notes-by-user-id.ts:15 · src/main/factories/app/handlers/find-user.ts:15 · src/main/factories/app/handlers/update-note.ts:15 — the 4 copies are spread across 4 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/main/factories/app/handlers/find-note.ts:15
- src/app/controllers/template/http-controller.ts:32 · src/app/middlewares/template/http-middleware.ts:20 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/app/controllers/template/http-controller.ts:32
- src/main/factories/app/controllers/graphql/get-notes-by-user-id.ts:8 · src/main/factories/app/controllers/graphql/update-finished-note.ts:8 · src/main/factories/app/controllers/rest/get-notes-by-user-id.ts:8 · src/main/factories/app/controllers/rest/update-finished-note.ts:8 — the 4 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 4 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — src/main/factories/app/controllers/graphql/get-notes-by-user-id.ts:8
- src/app/controllers/graphql/sign-in.ts:12 · src/app/controllers/graphql/sign-up.ts:10 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/app/controllers/graphql/sign-in.ts:12
- src/main/factories/app/handlers/delete-note.ts:9 · src/main/factories/app/handlers/is-note-finished.ts:9 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — src/main/factories/app/handlers/delete-note.ts:9
- src/main/routes/create-note.route.ts:4 · src/main/routes/delete-note.route.ts:4 — the two spans are one implementation copied and then locally edited — 56 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/main/routes/create-note.route.ts:4
- src/main/routes/delete-note.route.ts:4 · src/main/routes/find-note.route.ts:4 — the two spans are one implementation copied and then locally edited — 56 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/main/routes/delete-note.route.ts:4
- src/main/routes/delete-note.route.ts:4 · src/main/routes/find-notes-by-user-id.route.ts:4 — the two spans are one implementation copied and then locally edited — 56 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/main/routes/delete-note.route.ts:4
- src/main/routes/delete-note.route.ts:4 · src/main/routes/update-finished-note.route.ts:4 — the two spans are one implementation copied and then locally edited — 56 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/main/routes/delete-note.route.ts:4
- src/main/routes/delete-note.route.ts:4 · src/main/routes/update-note.route.ts:4 — the two spans are one implementation copied and then locally edited — 56 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/main/routes/delete-note.route.ts:4
- src/app/controllers/utils/http.ts:3 · src/app/controllers/utils/http.ts:15 · src/app/controllers/utils/http.ts:30 · src/app/middlewares/utils/http.ts:3 · +1 more site(s) not listed — the 5 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/app/controllers/utils/http.ts:3
- src/main/factories/app/controllers/graphql/create-note.ts:8 · src/main/factories/app/controllers/graphql/delete-note.ts:8 · src/main/factories/app/controllers/graphql/get-note.ts:8 · src/main/factories/app/controllers/graphql/update-note.ts:8 · +4 more site(s) not listed — the 8 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 8 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — src/main/factories/app/controllers/graphql/create-note.ts:8
- src/main/factories/app/controllers/graphql/sign-in.ts:8 · src/main/factories/app/controllers/graphql/sign-up.ts:8 · src/main/factories/app/controllers/rest/sign-in.ts:8 · src/main/factories/app/controllers/rest/sign-up.ts:8 · +2 more site(s) not listed — the 6 copies are spread across 4 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 6 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — src/main/factories/app/controllers/graphql/sign-in.ts:8
- src/app/controllers/graphql/delete-note.ts:21 · src/app/controllers/graphql/get-note.ts:20 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — src/app/controllers/graphql/delete-note.ts:21
- src/main/graphql/apollo/index.ts:43 · src/main/graphql/apollo/index.ts:49 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/main/graphql/apollo/index.ts:43
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R11 · Import Boundaries
R2 · Cyclomatic Complexity
- handle has cyclomatic complexity 13 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/app/controllers/strategies/error-handler.ts:58
- validate has cyclomatic complexity 13 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/app/validation/builder/required-param.ts:51
R3 · Large Files
R4 · Test Coverage
- No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×21) — src/main/factories/app/controllers/rest/get-notes-by-user-id.ts:1, src/main/factories/app/controllers/rest/update-finished-note.ts:1, src/main/factories/app/controllers/rest/create-note.ts:1, …
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R6 · Tooling
R7 · Dead Code
- Unreachable from the 5 application, 4 tooling and 126 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
- no import path from any entry point (5 application, 4 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/main/factories/app/controllers/rest/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×8) — src/main/factories/app/controllers/rest/get-notes-by-user-id.ts, src/main/factories/app/controllers/rest/update-finished-note.ts, src/main/factories/app/controllers/rest/create-note.ts, …
- no import path from any entry point (5 application, 4 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/main/factories/app/middlewares/rest/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/main/factories/app/middlewares/rest/auth.ts
- no import path from any entry point (5 application, 4 tooling, 126 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×12) — src/main/routes/create-note.route.ts, src/main/routes/delete-note.route.ts, src/main/routes/find-note.route.ts, …
- no import path from any entry point (5 application, 4 tooling, 126 test roots considered), but 8 in-repo import(s) from 8 other file(s) do name it (src/main/routes/create-note.route.ts, src/main/routes/delete-note.route.ts, src/main/routes/find-note.route.ts and 5 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/main/factories/app/controllers/rest/index.ts
- no import path from any entry point (5 application, 4 tooling, 126 test roots considered), but 6 in-repo import(s) from 6 other file(s) do name it (src/main/routes/create-note.route.ts, src/main/routes/delete-note.route.ts, src/main/routes/find-note.route.ts and 3 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/main/factories/app/middlewares/rest/index.ts
What to do
- Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene
- Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×3)
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
S1 · Web-Security Posture
- `{(…).listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.) — src/main/server/index.ts:10
What to do
- Enforce HTTPS on each listed server: serve TLS itself, or redirect plain requests to `https://` and send `Strict-Transport-Security` (`helmet()` does by default) behind the TLS-terminating proxy — and commit that proxy's configuration beside the service. A server only this machine reaches should bind `127.0.0.1`.
X1 · Async correctness
- `forEach` ignores what its callback returns, so the Promise each `async` call returns is dropped: nothing can await it, the code after this loop runs before any of the awaited work has finished (a function that `await`s around this loop still returns early), and a rejection is never handled — in Node.js an unhandled rejection terminates the process by default, and in a browser it is lost. Iterate with `for (const item of items) { await … }` when the work must run in order, or `await Promise.all(items.map(async (item) => { … }))` when it may run concurrently, so the enclosing function finishes only when the work does and its failures reach the caller. Where firing and forgetting is genuinely intended, make the callback's whole body a `try { … } catch (e) { … }` that handles the failure, so it cannot escape. — src/main/config/routes.ts:6
What to do
- `async` callback passed to `forEach`
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
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
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
- 0/1 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
What to do
- The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 69% | Adequate — gated by X5 | 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 | 57% | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 28% | Weak — gated by D13, P2, P5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 70% | Adequate | Acceptable, with room to improve. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 2 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: this repository stores data through 'pg' (src/infra/database/postgres/postgres-transaction.ts:1) but declares no persisted model this check reads (TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entities, Mongoose schemas, Sequelize or Drizzle tables, Knex migrations, Prisma models). Personal data may be written through raw SQL or a hosted backend, so whether its changes need an audit trail could not be established, and the trail's absence is not scored.
- C4 Data Retention — Not assessed: this repository stores data through 'pg' (src/infra/database/postgres/postgres-transaction.ts:1) but declares no persisted model this check reads (TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entities, Mongoose schemas, Sequelize or Drizzle tables, Knex migrations, Prisma models). Personal data may be written through raw SQL or a hosted backend, so whether a retention limit applies here could not be established, and its absence is not scored.
- C5 Data-Subject Rights — Not assessed: this repository stores data through 'pg' (src/infra/database/postgres/postgres-transaction.ts:1) but declares no persisted model this check reads (TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entities, Mongoose schemas, Sequelize or Drizzle tables, Knex migrations, Prisma models). Personal data may be written through raw SQL or a hosted backend, so whether data-subject rights apply here could not be established, and their absence is not scored.
- P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 57 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — Not applicable: TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — compose up failed (exit 17 — an image could not be built) — unable to prepare context: path "docker/dev/docker/dev/images/postgres" not found; 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: this repository stores data through 'pg' (src/infra/database/postgres/postgres-transaction.ts:1) but declares no persisted model this check reads (TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entities, Mongoose schemas, Sequelize or Drizzle tables, Knex migrations, Prisma models). Personal data may be written through raw SQL or a hosted backend, so the absence of a personal-data field here is not evidence that none is stored, and encryption at rest is not scored over a subject that could not be established.
- D11 Test Reliability — Test reliability not included
- D12 Dependency Hygiene — Dependency currency not established — this repository commits no lockfile to resolve
- D14 License Compliance — npm licences not graded — this npm repository commits no lockfile this pass can resolve
- D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (1392 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — Too few judgeable comments (29 of at least 30); comment value is not applicable here.
- 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.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D4 Code Duplication — This repository's production source (.ts) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D5 Coupling — Not applicable — this npm build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 7 value object(s); a Domain/Aggregates/ValueObjects layer
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks. 5 claim(s) of kinds M4 does not check were not checked (command argument 5); M4 checks only links and versions and artefact counts.
- P12 CI test-gate honesty — Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the JavaScript/TypeScript source (service entry point: src/main/config/server.ts:10 (express()))
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- R5 Dependency Freshness — no package-lock.json — dependency freshness not measured (would require an npm lockfile); JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
- X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 26 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 98 finding(s)
- No test reaches this file src/main/factories/app/controllers/rest/get-notes-by-user-id.ts:1
- No test reaches this file src/main/factories/app/controllers/rest/update-finished-note.ts:1
- No test reaches this file src/main/factories/app/controllers/rest/create-note.ts:1
- No test reaches this file src/main/factories/app/controllers/rest/delete-note.ts:1
- No test reaches this file src/main/factories/app/controllers/rest/get-note.ts:1
- No test reaches this file src/main/factories/app/controllers/rest/update-note.ts:1
- No test reaches this file src/main/factories/app/middlewares/rest/auth.ts:1
- No test reaches this file src/main/factories/app/controllers/rest/sign-in.ts:1
- No test reaches this file src/main/factories/app/controllers/rest/sign-up.ts:1
- No test reaches this file src/main/server/index.ts:1
- No test reaches this file src/main/routes/create-note.route.ts:1
- No test reaches this file src/main/routes/delete-note.route.ts:1
- No test reaches this file src/main/routes/find-note.route.ts:1
- No test reaches this file src/main/routes/find-notes-by-user-id.route.ts:1
- No test reaches this file src/main/routes/update-finished-note.route.ts:1
- No test reaches this file src/main/routes/update-note.route.ts:1
- No test reaches this file src/main/middlewares/no-cache.ts:1
- No test reaches this file src/main/middlewares/cors.ts:1
- No test reaches this file src/main/routes/sign-in.route.ts:1
- No test reaches this file src/main/routes/sign-up.route.ts:1
- No test reaches this file src/main/middlewares/body-parser.ts:1
- Dead file (~15 LoC) src/main/routes/create-note.route.ts
- Dead file (~15 LoC) src/main/routes/delete-note.route.ts
- Dead file (~15 LoC) src/main/routes/find-note.route.ts
- Dead file (~15 LoC) src/main/routes/find-notes-by-user-id.route.ts
- Dead file (~15 LoC) src/main/routes/update-finished-note.route.ts
- Dead file (~15 LoC) src/main/routes/update-note.route.ts
- Duplicated block with local edits (11 matched lines × 2 locations) src/main/routes/create-note.route.ts:4
- Duplicated block with local edits (11 matched lines × 2 locations) src/main/routes/delete-note.route.ts:4
- Duplicated block with local edits (11 matched lines × 2 locations) src/main/routes/delete-note.route.ts:4
- Duplicated block with local edits (11 matched lines × 2 locations) src/main/routes/delete-note.route.ts:4
- Duplicated block with local edits (11 matched lines × 2 locations) src/main/routes/delete-note.route.ts:4
- Dead file (~18 LoC) src/main/factories/app/controllers/rest/create-note.ts
- Dead file (~18 LoC) src/main/factories/app/controllers/rest/delete-note.ts
- Dead file (~18 LoC) src/main/factories/app/controllers/rest/get-note.ts
- Dead file (~18 LoC) src/main/factories/app/controllers/rest/update-note.ts
- Dead file (~18 LoC) src/main/factories/app/middlewares/rest/auth.ts
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (14 lines × 2 locations) src/app/controllers/decorators/database.ts:11
- Duplicated block (14 lines × 2 locations) src/app/controllers/template/graphql-controller.ts:10
- Duplicated block (14 lines × 2 locations) src/infra/repositories/note.ts:66
- Duplicated block (20 lines × 2 locations) src/domain/value-objects/description.ts:4
- Duplicated block (20 lines × 2 locations) src/domain/value-objects/lastname.ts:5
- Duplicated block (17 lines × 2 locations) src/app/controllers/graphql/update-finished-note.ts:9
- Duplicated block (17 lines × 2 locations) src/app/controllers/rest/sign-in.ts:21
- Duplicated block (11 lines × 2 locations) src/app/controllers/graphql/sign-in.ts:12
- Duplicated block (11 lines × 2 locations) src/main/factories/app/handlers/delete-note.ts:9
- Dead file (~21 LoC) src/main/factories/app/controllers/rest/get-notes-by-user-id.ts
- Dead file (~21 LoC) src/main/factories/app/controllers/rest/update-finished-note.ts
- Dead file (~17 LoC) src/main/factories/app/controllers/rest/sign-in.ts
- Dead file (~17 LoC) src/main/factories/app/controllers/rest/sign-up.ts
- Dead file (~9 LoC) src/main/routes/sign-in.route.ts
- Dead file (~9 LoC) src/main/routes/sign-up.route.ts
- Dead file (~8 LoC) src/main/factories/app/controllers/rest/index.ts
- Dead file (~8 LoC) src/main/middlewares/content-type.ts
- No assertions: should open and close database connection tests/integration/infra/database/postgres/connection/pg-connection.test.ts:4
- REDACTED
- REDACTED
- End-of-life runtime: Node.js 18 .nvmrc:1
- Low coverage: src/infra/database/postgres/postgres-transaction.ts src/infra/database/postgres/postgres-transaction.ts:1
- No structured logging
- No DR/backup evidence
- Duplication concentrated across 2 sibling directories (7 clone groups) src/app/controllers/strategies/error-handler.ts:63
- Duplicated block with local edits (66 matched lines × 2 locations) src/infra/repositories/note.ts:97
- Duplicated block with local edits (52 matched lines × 2 locations) src/infra/providers/decryption.ts:5
- Duplicated block (44 lines × 2 locations) src/app/controllers/strategies/error-handler.ts:63
- Duplicated block (41 lines × 2 locations) src/app/controllers/rest/create-note.ts:12
- Duplicated block (39 lines × 2 locations) src/infra/repositories/note.ts:268
- Duplicated block (38 lines × 2 locations) src/app/controllers/rest/delete-note.ts:14
- Duplicated block (27 lines × 2 locations) src/app/controllers/rest/update-finished-note.ts:29
- Duplicated block (23 lines × 2 locations) src/infra/repositories/user.ts:21
- Duplicated block (21 lines × 5 locations) src/main/factories/app/handlers/find-note.ts:4
- Duplicated block (19 lines × 2 locations) src/infra/repositories/user.ts:94
- Duplicated block (17 lines × 6 locations) src/app/controllers/rest/create-note.ts:10
- Duplicated block (14 lines × 5 locations) src/app/controllers/graphql/create-note.ts:9
- Duplicated block (13 lines × 2 locations) src/app/middlewares/graphql/auth.ts:13
- Duplicated block (13 lines × 3 locations) src/infra/repositories/note.ts:23
- Duplicated block (13 lines × 4 locations) src/main/factories/app/handlers/find-note.ts:15
- Duplicated block (12 lines × 2 locations) src/app/controllers/template/http-controller.ts:32
- Duplicated block (12 lines × 4 locations) src/main/factories/app/controllers/graphql/get-notes-by-user-id.ts:8
- Duplicated block (9 lines × 5 locations) src/app/controllers/utils/http.ts:3
- Duplicated block (9 lines × 8 locations) src/main/factories/app/controllers/graphql/create-note.ts:8
- Duplicated block (8 lines × 6 locations) src/main/factories/app/controllers/graphql/sign-in.ts:8
- Duplicated block (6 lines × 2 locations) src/app/controllers/graphql/delete-note.ts:21
- Duplicated block (5 lines × 2 locations) src/main/graphql/apollo/index.ts:43
- Complex function handle (cyclomatic 13, cognitive 12) src/app/controllers/strategies/error-handler.ts:58
- Complex function validate (cyclomatic 13, cognitive 12) src/app/validation/builder/required-param.ts:51
- Dead file (~14 LoC) src/main/middlewares/no-cache.ts
- Dead file (~10 LoC) src/main/middlewares/cors.ts
- Dead file (~5 LoC) src/main/middlewares/body-parser.ts
- Dead file (~1 LoC) src/main/factories/app/middlewares/rest/index.ts
- Unused dependency 'cors'
- Unused dependency 'cpf-cnpj-validator'
- Unused dependency 'helmet'
- JavaScript dependencies are not locked package.json:62
- `async` callback passed to `forEach` src/main/config/routes.ts:6
Minor — 22 finding(s)
- Orphaned file src/infra/repositories/note.ts:1
- Orphaned file jest.config.js:1
- Orphaned file jest-integration.config.js:1
- Orphaned file jest-unit.config.js:1
- Orphaned file jest-e2e.config.js:1
- Orphaned file src/infra/repositories/user.ts:1
- Orphaned file src/infra/database/postgres/proxies/circuit-breaker.ts:1
- Orphaned file src/app/controllers/strategies/error-handler.ts:1
- Orphaned file src/shared/either.ts:1
- No named authorization policies src/app/middlewares/utils/http.ts:14
- Projects may be oversized for their cohesion
- High interface indirection
- Scattered collaborators
- REDACTED
- REDACTED
- Orphaned files with no living knowledge
- REDACTED
- No ADRs
- No dependency-update automation package.json:62
- No rollback/health safety
- No app-layer HTTPS enforcement detected src/main/server/index.ts:10
- Strict null checking is not enabled everywhere the repository type-checks
Minor — 1 finding(s)
- Dependency hygiene PARTLY measured — npm pinning read, dependency currency not (no committed lockfile, so no resolved version to grade)
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-1fcc484f11b94be48fa1f882c7971dbe/history.json --exit-code 0 --source . | 2 | 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-1fcc484f11b94be48fa1f882c7971dbe/tree.json --exit-code 0 --source . | 2 | 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 . | 19 | 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 . | 0 | — |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 5 | 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 | — |
| 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 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |