Executive summary
mirego/accent is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back in part because we found no automated security scanning of the code, its secrets or its dependencies. It scores 44 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 23, is the weakest lens and counts most in the score. The best first step is pinning the dependencies taken from a moving source, worth about 4 points. Adding automated security scanning would lift Production Readiness itself, also worth about 4. Raising Production Readiness to 70 would lift the score to about 61.
Twenty-four known security holes in the packages the code depends on can be used by attackers. Nine pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and four secrets can leak from the build pipeline. Updating the vulnerable packages, pinning each tool to an exact version and limiting each secret to its own step would close these risks. Passing outside input through environment variables would fix the pipeline step that puts outside input straight into a shell command, and the place where the code runs text as code or as a command needs a direct call instead. The three pages that don't say their language need their language set.
The product code is 28,444 lines, about €37,000 to rebuild.
If Production Readiness rose from 23 to 70, the lowest score rated Strong, the score would rise from 44 to about 61.
New since the last survey: 83 findings
- Cyclomatic Complexity · fileSaver (cyclomatic 29) webapp/app/utils/file-saver.js
- Code Duplication · Edited copy of a member (25 corresponding lines) lib/movement/persisters/operations_update_all_dynamic.ex
- Code Duplication · Edited copy of a member (23 corresponding lines) lib/graphql/resolvers/revision.ex
- Code Duplication · Edited copy of a member (13 corresponding lines) lib/machine_translations/provider/deepl.ex
- Code Duplication · Edited copy of a member (14 corresponding lines) lib/web/controllers/merge_controller.ex
- Code Duplication · Edited copy of a member (19 corresponding lines) lib/accent/scopes/language.ex
- Code Duplication · Edited copy of a member (11 corresponding lines) lib/graphql/resolvers/revision.ex
- Code Duplication · Edited copy of a member (14 corresponding lines) lib/graphql/resolvers/project.ex
- Code Duplication · Edited copy of a member (11 corresponding lines) lib/graphql/resolvers/document.ex
- Code Duplication · Edited copy of a member (17 corresponding lines) lib/movement/mappers/operation.ex
- Code Duplication · Edited copy of a member (9 corresponding lines) lib/web/controllers/peek_controller.ex
- Code Duplication · Edited copy of a member (16 corresponding lines) lib/movement/persisters/new_slave.ex
- Code Duplication · Edited copy of a member (11 corresponding lines) lib/movement/builders/revision_correct_all.ex
- Code Duplication · Edited copy of a member (15 corresponding lines) lib/langue/formatter/android/parser.ex
- Code Duplication · Edited copy of a member (15 corresponding lines) lib/accent/machine_translations_config/machine_translations_config_manager.ex
- Code Duplication · Edited copy of a member (8 corresponding lines) lib/movement/builders/revision_merge.ex
- Code Duplication · Edited copy of a member (14 corresponding lines) lib/accent/schemas/operation.ex
- Code Duplication · Edited copy of a member (6 corresponding lines) lib/langue/formatter/android/serializer.ex
- Code Duplication · Edited copies of one member (4 members, 9+ corresponding lines) lib/graphql/helpers/authorization.ex
- Code Duplication · Edited copies of one member (3 members, 10+ corresponding lines) lib/graphql/resolvers/comment.ex
- Code Duplication · Edited copy of a member (10 corresponding lines) lib/movement/migration/conflict.ex
- Code Duplication · Edited copies of one member (8 members, 7+ corresponding lines) lib/graphql/resolvers/api_token.ex
- Code Duplication · Edited copy of a member (12 corresponding lines) lib/movement/builders/rollback.ex
- Code Duplication · Edited copy of a member (8 corresponding lines) lib/web/controllers/lint_controller.ex
- Code Duplication · Edited copy of a member (4 corresponding lines) lib/langue/utils/line_by_line_helper/parser.ex
- Code Duplication · Edited copy of a member (5 corresponding lines) lib/langue/formatter/json/serializer.ex
- Code Duplication · Edited copy of a member (9 corresponding lines) lib/web/controllers/export_controller.ex
- Code Duplication · Edited copy of a member (7 corresponding lines) lib/web/controllers/export_jipt_controller.ex
- Code Duplication · Edited copy of a member (6 corresponding lines) lib/graphql/resolvers/document.ex
- Code Duplication · Edited copy of a member (7 corresponding lines) lib/graphql/resolvers/collaborator.ex
- Code Duplication · Edited copy of a member (8 corresponding lines) lib/movement/builders/new_slave.ex
- Code Duplication · Edited copy of a member (12 corresponding lines) lib/accent/scopes/project.ex
- Code Duplication · Edited copies of one member (4 members, 9+ corresponding lines) lib/lint/checks/double_spaces.ex
- Code Duplication · Edited copy of a member (6 corresponding lines) lib/hook/outbounds/discord.ex
- Code Duplication · Edited copy of a member (8 corresponding lines) lib/web/controllers/lint_controller.ex
- Code Duplication · Edited copies of one member (3 members, 4+ corresponding lines) lib/web/controllers/merge_controller.ex
- Code Duplication · Edited copy of a member (5 corresponding lines) lib/graphql/resolvers/comment.ex
- Code Duplication · Edited copy of a member (6 corresponding lines) lib/langue/formatter/java_properties/parser.ex
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Hygiene · Unused dependency '@oclif/plugin-warn-if-update-available'
- Dependency Hygiene · Unused dependency 'tslib'
- Dependency Hygiene · Unused dependency '@ember/optional-features'
- Dependency Hygiene · Unused dependency '@ember/render-modifiers'
- Dependency Hygiene · Unused dependency '@ember/string'
- Dependency Hygiene · Unused dependency '@embroider/legacy-inspector-support'
- Dependency Hygiene · Unused dependency 'color'
- Dependency Hygiene · Unused dependency 'cryptiles'
- Dependency Hygiene · Unused dependency 'ember-auto-import'
- Dependency Hygiene · Unused dependency 'ember-autoresize-modifier'
- Dependency Hygiene · Unused dependency 'ember-cli-babel'
- Dependency Hygiene · Unused dependency 'ember-cli-htmlbars'
- Dependency Hygiene · Unused dependency 'ember-keyboard'
- Dependency Hygiene · Unused dependency 'ember-page-title'
- Dependency Hygiene · Unused dependency 'ember-power-select'
- Dependency Hygiene · Unused dependency 'ember-qunit'
- Dependency Hygiene · Unused dependency 'ember-route-template'
- Dependency Hygiene · Unused dependency 'emoji-picker-element'
- Dependency Hygiene · Unused dependency 'highlight.js'
- Dependency Hygiene · Unused dependency 'markdown-it'
- Dependency Hygiene · Unused dependency 'pell'
- Dependency Hygiene · Unused dependency 'pretender'
- Dependency Hygiene · Unused dependency 'simple-fmt'
Fixed since the last survey: 235 findings
- Cyclomatic Complexity · file-saver.fileSaver (cyclomatic 29) webapp/app/utils/file-saver.js
- Secret Scanning · Leaked secret: hardcoded-credential REDACTED
- Secret Scanning · Leaked secret: high-entropy-secret cli/examples/phoenix/accent.json
- Secrets (history) · Secret: generic-api-key cli/examples/phoenix/accent.json
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Code Duplication · Duplicated block with local edits (13 matched lines × 2 locations) webapp/app/controllers/logged-in/jipt/index.ts
- Code Duplication · Duplicated block (13 lines × 2 locations) webapp/app/controllers/logged-in/project/conflicts.ts
- Code Duplication · Duplicated block (13 lines × 2 locations) webapp/app/controllers/logged-in/project/files/export.ts
- Code Duplication · Duplicated block (13 lines × 2 locations) webapp/app/controllers/logged-in/project/revision/translations.ts
- Code Duplication · Duplicated block (12 lines × 2 locations) cli/src/base.ts
- Code Duplication · Duplicated block with local edits (12 matched lines × 2 locations) cli/src/commands/stats.ts
- Code Duplication · Duplicated block (12 lines × 2 locations) webapp/app/controllers/logged-in/project/comments.ts
- Code Duplication · Duplicated block (12 lines × 2 locations) webapp/app/controllers/logged-in/project/edit/index.ts
- Code Duplication · Duplicated block (12 lines × 2 locations) webapp/app/controllers/logged-in/project/edit/jipt.ts
- Code Duplication · Duplicated block (12 lines × 2 locations) webapp/app/controllers/logged-in/project/edit/lint-entries.ts
- Code Duplication · Duplicated block (12 lines × 5 locations) webapp/app/controllers/logged-in/project/files/add-translations.ts
- Code Duplication · Duplicated block (12 lines × 3 locations) webapp/app/routes/logged-in/project/files/add-translations.ts
- Code Duplication · Duplicated block (10 lines × 2 locations) cli/src/commands/export.ts
- Code Duplication · Duplicated block (10 lines × 2 locations) cli/src/services/document.ts
- Code Duplication · Duplicated block (10 lines × 2 locations) jipt/src/frame-listener.ts
- Code Duplication · Duplicated block (10 lines × 4 locations) webapp/app/controllers/logged-in/jipt/translation/index.ts
- Code Duplication · Duplicated block (10 lines × 5 locations) webapp/app/controllers/logged-in/project/edit/index.ts
- Code Duplication · Duplicated block (10 lines × 6 locations) webapp/app/controllers/logged-in/project/revision/translations.ts
- Code Duplication · Duplicated block (10 lines × 2 locations) webapp/app/services/exporter.ts
- Code Duplication · Duplicated block (9 lines × 6 locations) webapp/app/controllers/logged-in/project/activity.ts
- Code Duplication · Duplicated block (9 lines × 2 locations) webapp/app/controllers/logged-in/project/files.ts
- Code Duplication · Duplicated block (9 lines × 2 locations) webapp/app/controllers/logged-in/project/files/export.ts
- Code Duplication · Duplicated block (8 lines × 17 locations) webapp/app/routes/logged-in/jipt.ts
- Code Duplication · Duplicated block (7 lines × 2 locations) webapp/app/routes/logged-in/project/revision/lint-translations.ts
- Code Duplication · Duplicated block (6 lines × 3 locations) cli/src/services/document.ts
- Test Coverage · No test reaches this file webapp/app/queries/project-activity.ts
- Test Coverage · No test reaches this file webapp/app/queries/translations.ts
- Test Coverage · No test reaches this file webapp/app/routes/logged-in/project/revision/lint-translations.ts
- Test Coverage · No test reaches this file webapp/app/services/authenticated-request.ts
- Test Coverage · No test reaches this file webapp/app/controllers/logged-in/project/edit/prompts/edit.ts
- Test Coverage · No test reaches this file webapp/app/helpers/string-diff.ts
- Test Coverage · No test reaches this file webapp/app/routes/logged-in/project/activities.ts
- Test Coverage · No test reaches this file webapp/app/controllers/logged-in/project/files/jipt.ts
- Test Coverage · No test reaches this file cli/src/commands/stats.ts
- Test Coverage · No test reaches this file webapp/app/controllers/logged-in/project/files.ts
- Test Coverage · No test reaches this file webapp/app/router.js
- Test Coverage · No test reaches this file webapp/app/controllers/logged-in/project/activities.ts
- Test Coverage · No test reaches this file webapp/app/routes/logged-in/project.ts
- Test Coverage · No test reaches this file webapp/app/controllers/logged-in/project/versions/edit.ts
- Test Coverage · No test reaches this file webapp/app/routes/logged-in/jipt/index.ts
- Test Coverage · No test reaches this file webapp/app/controllers/logged-in/project/edit/machine-translations.ts
- Test Coverage · No test reaches this file jipt/src/ui/pin.ts
- Test Coverage · No test reaches this file cli/src/services/config.ts
- Test Coverage · No test reaches this file webapp/app/queries/translation-activities.ts
- Test Coverage · No test reaches this file webapp/app/queries/lint-translations.ts
- Test Coverage · No test reaches this file webapp/app/routes/logged-in/jipt.ts
- Test Coverage · No test reaches this file webapp/app/controllers/logged-in/project/versions/new.ts
- Test Coverage · No test reaches this file webapp/app/controllers/logged-in/project/files/machine-translations.ts
- Test Coverage · No test reaches this file webapp/app/routes/logged-in/project/integration-executions.ts
- Test Coverage · No test reaches this file REDACTED
- Test Coverage · No test reaches this file cli/src/services/formatters/base.ts
- Test Coverage · No test reaches this file webapp/app/queries/activity-activities.ts
- Test Coverage · No test reaches this file webapp/app/controllers/logged-in/project/comments.ts
- Test Coverage · No test reaches this file webapp/app/routes/logged-in/project/files.ts
- Test Coverage · No test reaches this file webapp/app/controllers/logged-in/jipt/index.ts
- Test Coverage · No test reaches this file webapp/app/routes/logged-in/project/translation/comments.ts
- Test Coverage · No test reaches this file webapp/app/controllers/logged-in/project/manage-languages/edit.ts
- Test Coverage · No test reaches this file webapp/app/routes/logged-in/project/translation/activities.ts
- Test Coverage · No test reaches this file webapp/app/queries/project-service-integrations.ts
- Test Coverage · No test reaches this file webapp/app/services/machine-translations.ts
- Test Coverage · No test reaches this file webapp/app/routes/logged-in/project/translation/editions.ts
- Test Coverage · No test reaches this file webapp/app/controllers/logged-in/jipt.ts
- Test Coverage · No test reaches this file webapp/app/controllers/logged-in/project/versions.ts
- Test Coverage · No test reaches this file cli/src/commands/format.ts
- Test Coverage · No test reaches this file webapp/app/controllers/logged-in/project/translation/editions.ts
- Test Coverage · No test reaches this file webapp/app/routes/logged-in/project/comments.ts
- Test Coverage · No test reaches this file webapp/app/routes/logged-in/project/versions.ts
- Test Coverage · No test reaches this file webapp/app/controllers/logged-in/project/translation/settings.ts
- Test Coverage · No test reaches this file webapp/app/controllers/logged-in/project/files/new-machine-translations.ts
- Test Coverage · No test reaches this file webapp/app/queries/translation-editions.ts
- Test Coverage · No test reaches this file webapp/app/routes/logged-in/project/edit/lint-entries.ts
- Test Coverage · No test reaches this file cli/src/commands/export.ts
- Test Coverage · No test reaches this file webapp/app/queries/jipt-translations.ts
- Test Coverage · No test reaches this file webapp/app/queries/translation-comments.ts
- Test Coverage · No test reaches this file webapp/app/routes/logged-in/project/manage-languages.ts
- Test Coverage · No test reaches this file webapp/app/controllers/logged-in/project/activity.ts
- Test Coverage · No test reaches this file webapp/app/controllers/logged-in/project/revision/lint-translations.ts
- Test Coverage · No test reaches this file webapp/app/routes/logged-in/project/index.ts
- Test Coverage · No test reaches this file cli/src/commands/lint.ts
- Test Coverage · No test reaches this file cli/src/commands/jipt.ts
- Test Coverage · No test reaches this file webapp/app/controllers/logged-in/projects.ts
- Test Coverage · No test reaches this file webapp/app/controllers/logged-in/projects/new.ts
- Test Coverage · No test reaches this file webapp/app/queries/project-documents.ts
- Test Coverage · No test reaches this file webapp/app/routes/logged-in/project/activity.ts
- Test Coverage · No test reaches this file webapp/app/queries/project-versions.ts
- Test Coverage · No test reaches this file webapp/app/routes/logged-in/project/collaborators.ts
- Test Coverage · No test reaches this file webapp/app/routes/logged-in/project/edit/badges.ts
- Test Coverage · No test reaches this file webapp/app/routes/logged-in/project/edit/index.ts
- Test Coverage · No test reaches this file webapp/app/routes/logged-in/project/service-integrations.ts
- Test Coverage · No test reaches this file webapp/app/routes/logged-in/project/translation.ts
- Test Coverage · No test reaches this file webapp/app/services/merger.ts
Rebuild cost: about €37,000 · Estimate
| Cost to rebuild | €12,000 to €61,000, for 202 to 642 hours of work, about 0.3 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 44. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 28,444 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 Langue.Formatter | 2 Movement | 3 cli.src.types.config | 4 cli.src.types.document-config | 5 cli.src.types.project | 6 jipt.src.state | 7 webapp.app.services.apollo | 8 webapp.app.services.authenticated-request | 9 webapp.app.services.file-saver | 10 webapp.app.services.global-state | 11 webapp.app.services.jipt | 12 webapp.app.services.route-params | 13 cli.src.base | 14 cli.src.services.document | 15 cli.src.services.formatters.commit-operation | 16 jipt.src.mutation.live-node | 17 jipt.src.ui.ui | 18 webapp.app.controllers.logged-in.jipt | 19 webapp.app.controllers.logged-in.project.files.export | 20 webapp.app.services.apollo-mutate | 21 webapp.app.services.apollo-subscription | 22 webapp.app.services.exporter | 23 webapp.app.services.peeker | 24 webapp.app.services.session | 25 cli.src.commands.sync | 26 jipt.src.frame-listener | 27 jipt.src.ui.pin | 28 webapp.app.controllers.logged-in.jipt.translation | 29 webapp.app.controllers.logged-in.project | 30 webapp.app.controllers.logged-in.project.activities | 31 webapp.app.controllers.logged-in.project.conflicts | 32 webapp.app.controllers.logged-in.project.files.add-translations | 33 webapp.app.controllers.logged-in.project.revision.translations | 34 webapp.app.controllers.logged-in.projects | 35 webapp.app.routes.logged-in.jipt | 36 webapp.app.routes.logged-in.project | 37 webapp.app.services.syncer | 38 webapp.app.controllers.logged-in.project.files.new-sync | 39 webapp.app.controllers.logged-in.project.files.sync | 40 webapp.app.routes.logged-in.projects |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Langue.Formatter | ||||||||||||||||||||||||||||||||||||||||
| 2 Movement | ||||||||||||||||||||||||||||||||||||||||
| 3 cli.src.types.config | ||||||||||||||||||||||||||||||||||||||||
| 4 cli.src.types.document-config | ||||||||||||||||||||||||||||||||||||||||
| 5 cli.src.types.project | ||||||||||||||||||||||||||||||||||||||||
| 6 jipt.src.state | ||||||||||||||||||||||||||||||||||||||||
| 7 webapp.app.services.apollo | ||||||||||||||||||||||||||||||||||||||||
| 8 webapp.app.services.authenticated-request | ||||||||||||||||||||||||||||||||||||||||
| 9 webapp.app.services.file-saver | ||||||||||||||||||||||||||||||||||||||||
| 10 webapp.app.services.global-state | ||||||||||||||||||||||||||||||||||||||||
| 11 webapp.app.services.jipt | ||||||||||||||||||||||||||||||||||||||||
| 12 webapp.app.services.route-params | ||||||||||||||||||||||||||||||||||||||||
| 13 cli.src.base | 2 | |||||||||||||||||||||||||||||||||||||||
| 14 cli.src.services.document | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 15 cli.src.services.formatters.commit-operation | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 jipt.src.mutation.live-node | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 jipt.src.ui.ui | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 18 webapp.app.controllers.logged-in.jipt | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 webapp.app.controllers.logged-in.project.files.export | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 20 webapp.app.services.apollo-mutate | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 webapp.app.services.apollo-subscription | 2 | |||||||||||||||||||||||||||||||||||||||
| 22 webapp.app.services.exporter | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 webapp.app.services.peeker | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 webapp.app.services.session | 1 | |||||||||||||||||||||||||||||||||||||||
| 25 cli.src.commands.sync | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 26 jipt.src.frame-listener | 1 | 2 | 2 | 3 | ||||||||||||||||||||||||||||||||||||
| 27 jipt.src.ui.pin | 2 | 2 | 3 | |||||||||||||||||||||||||||||||||||||
| 28 webapp.app.controllers.logged-in.jipt.translation | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 29 webapp.app.controllers.logged-in.project | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 30 webapp.app.controllers.logged-in.project.activities | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 31 webapp.app.controllers.logged-in.project.conflicts | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 32 webapp.app.controllers.logged-in.project.files.add-translations | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 33 webapp.app.controllers.logged-in.project.revision.translations | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 34 webapp.app.controllers.logged-in.projects | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 35 webapp.app.routes.logged-in.jipt | 1 | 1 | 1 | 1 | 4 | |||||||||||||||||||||||||||||||||||
| 36 webapp.app.routes.logged-in.project | 1 | 1 | 4 | |||||||||||||||||||||||||||||||||||||
| 37 webapp.app.services.syncer | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 38 webapp.app.controllers.logged-in.project.files.new-sync | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 39 webapp.app.controllers.logged-in.project.files.sync | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 40 webapp.app.routes.logged-in.projects | 2 | 1 | 1 |
13→5 cli.src.base uses cli.src.types.project✕
- Connections
- 2 pairs of types, where a type in cli.src.base uses a type in cli.src.types.project.
- The types involved
cli.src.base.BaseCommand→cli.src.types.project.Projectcli.src.base.BaseCommand→cli.src.types.project.ProjectViewer
- Direction
- cli.src.base uses cli.src.types.project, so a change to cli.src.types.project can break cli.src.base, while a change to cli.src.base can't break cli.src.types.project.
- Position
- Below the diagonal: cli.src.base uses a module listed above it, which is the healthy direction.
14→3 cli.src.services.document uses cli.src.types.config✕
- Connections
- 1 pair of types, where a type in cli.src.services.document uses a type in cli.src.types.config.
- The types involved
cli.src.services.document.Document→cli.src.types.config.Config
- Direction
- cli.src.services.document uses cli.src.types.config, so a change to cli.src.types.config can break cli.src.services.document, while a change to cli.src.services.document can't break cli.src.types.config.
- Position
- Below the diagonal: cli.src.services.document uses a module listed above it, which is the healthy direction.
14→4 cli.src.services.document uses cli.src.types.document-config✕
- Connections
- 1 pair of types, where a type in cli.src.services.document uses a type in cli.src.types.document-config.
- The types involved
cli.src.services.document.Document→cli.src.types.document-config.DocumentConfig
- Direction
- cli.src.services.document uses cli.src.types.document-config, so a change to cli.src.types.document-config can break cli.src.services.document, while a change to cli.src.services.document can't break cli.src.types.document-config.
- Position
- Below the diagonal: cli.src.services.document uses a module listed above it, which is the healthy direction.
14→5 cli.src.services.document uses cli.src.types.project✕
- Connections
- 1 pair of types, where a type in cli.src.services.document uses a type in cli.src.types.project.
- The types involved
cli.src.services.document.Document→cli.src.types.project.Project
- Direction
- cli.src.services.document uses cli.src.types.project, so a change to cli.src.types.project can break cli.src.services.document, while a change to cli.src.services.document can't break cli.src.types.project.
- Position
- Below the diagonal: cli.src.services.document uses a module listed above it, which is the healthy direction.
15→5 cli.src.services.formatters.commit-operation uses cli.src.types.project✕
- Connections
- 1 pair of types, where a type in cli.src.services.formatters.commit-operation uses a type in cli.src.types.project.
- The types involved
cli.src.services.formatters.commit-operation.CommitOperationFormatter→cli.src.types.project.Project
- Direction
- cli.src.services.formatters.commit-operation uses cli.src.types.project, so a change to cli.src.types.project can break cli.src.services.formatters.commit-operation, while a change to cli.src.services.formatters.commit-operation can't break cli.src.types.project.
- Position
- Below the diagonal: cli.src.services.formatters.commit-operation uses a module listed above it, which is the healthy direction.
16→6 jipt.src.mutation.live-node uses jipt.src.state✕
- Connections
- 1 pair of types, where a type in jipt.src.mutation.live-node uses a type in jipt.src.state.
- The types involved
jipt.src.mutation.live-node.LiveNode→jipt.src.state.State
- Direction
- jipt.src.mutation.live-node uses jipt.src.state, so a change to jipt.src.state can break jipt.src.mutation.live-node, while a change to jipt.src.mutation.live-node can't break jipt.src.state.
- Position
- Below the diagonal: jipt.src.mutation.live-node uses a module listed above it, which is the healthy direction.
17→3 jipt.src.ui.ui uses cli.src.types.config✕
- Connections
- 2 pairs of types, where a type in jipt.src.ui.ui uses a type in cli.src.types.config.
- The types involved
jipt.src.ui.ui.Props→cli.src.types.config.Configjipt.src.ui.ui.UI→cli.src.types.config.Config
- Direction
- jipt.src.ui.ui uses cli.src.types.config, so a change to cli.src.types.config can break jipt.src.ui.ui, while a change to jipt.src.ui.ui can't break cli.src.types.config.
- Position
- Below the diagonal: jipt.src.ui.ui uses a module listed above it, which is the healthy direction.
17→6 jipt.src.ui.ui uses jipt.src.state✕
- Connections
- 2 pairs of types, where a type in jipt.src.ui.ui uses a type in jipt.src.state.
- The types involved
jipt.src.ui.ui.Props→jipt.src.state.Statejipt.src.ui.ui.UI→jipt.src.state.State
- Direction
- jipt.src.ui.ui uses jipt.src.state, so a change to jipt.src.state can break jipt.src.ui.ui, while a change to jipt.src.ui.ui can't break jipt.src.state.
- Position
- Below the diagonal: jipt.src.ui.ui uses a module listed above it, which is the healthy direction.
18→10 webapp.app.controllers.logged-in.jipt uses webapp.app.services.global-state✕
- Connections
- 1 pair of types, where a type in webapp.app.controllers.logged-in.jipt uses a type in webapp.app.services.global-state.
- The types involved
webapp.app.controllers.logged-in.jipt.JIPTController→webapp.app.services.global-state.GlobalState
- Direction
- webapp.app.controllers.logged-in.jipt uses webapp.app.services.global-state, so a change to webapp.app.services.global-state can break webapp.app.controllers.logged-in.jipt, while a change to webapp.app.controllers.logged-in.jipt can't break webapp.app.services.global-state.
- Position
- Below the diagonal: webapp.app.controllers.logged-in.jipt uses a module listed above it, which is the healthy direction.
19→9 webapp.app.controllers.logged-in.project.files.export uses webapp.app.services.file-saver✕
- Connections
- 1 pair of types, where a type in webapp.app.controllers.logged-in.project.files.export uses a type in webapp.app.services.file-saver.
- The types involved
webapp.app.controllers.logged-in.project.files.export.ExportController→webapp.app.services.file-saver.FileSaver
- Direction
- webapp.app.controllers.logged-in.project.files.export uses webapp.app.services.file-saver, so a change to webapp.app.services.file-saver can break webapp.app.controllers.logged-in.project.files.export, while a change to webapp.app.controllers.logged-in.project.files.export can't break webapp.app.services.file-saver.
- Position
- Below the diagonal: webapp.app.controllers.logged-in.project.files.export uses a module listed above it, which is the healthy direction.
19→10 webapp.app.controllers.logged-in.project.files.export uses webapp.app.services.global-state✕
- Connections
- 1 pair of types, where a type in webapp.app.controllers.logged-in.project.files.export uses a type in webapp.app.services.global-state.
- The types involved
webapp.app.controllers.logged-in.project.files.export.ExportController→webapp.app.services.global-state.GlobalState
- Direction
- webapp.app.controllers.logged-in.project.files.export uses webapp.app.services.global-state, so a change to webapp.app.services.global-state can break webapp.app.controllers.logged-in.project.files.export, while a change to webapp.app.controllers.logged-in.project.files.export can't break webapp.app.services.global-state.
- Position
- Below the diagonal: webapp.app.controllers.logged-in.project.files.export uses a module listed above it, which is the healthy direction.
20→7 webapp.app.services.apollo-mutate uses webapp.app.services.apollo✕
- Connections
- 1 pair of types, where a type in webapp.app.services.apollo-mutate uses a type in webapp.app.services.apollo.
- The types involved
webapp.app.services.apollo-mutate.ApolloMutate→webapp.app.services.apollo.Apollo
- Direction
- webapp.app.services.apollo-mutate uses webapp.app.services.apollo, so a change to webapp.app.services.apollo can break webapp.app.services.apollo-mutate, while a change to webapp.app.services.apollo-mutate can't break webapp.app.services.apollo.
- Position
- Below the diagonal: webapp.app.services.apollo-mutate uses a module listed above it, which is the healthy direction.
21→7 webapp.app.services.apollo-subscription uses webapp.app.services.apollo✕
- Connections
- 2 pairs of types, where a type in webapp.app.services.apollo-subscription uses a type in webapp.app.services.apollo.
- The types involved
webapp.app.services.apollo-subscription.ApolloSubscription→webapp.app.services.apollo.Apollowebapp.app.services.apollo-subscription.Subscription→webapp.app.services.apollo.Apollo
- Direction
- webapp.app.services.apollo-subscription uses webapp.app.services.apollo, so a change to webapp.app.services.apollo can break webapp.app.services.apollo-subscription, while a change to webapp.app.services.apollo-subscription can't break webapp.app.services.apollo.
- Position
- Below the diagonal: webapp.app.services.apollo-subscription uses a module listed above it, which is the healthy direction.
22→8 webapp.app.services.exporter uses webapp.app.services.authenticated-request✕
- Connections
- 1 pair of types, where a type in webapp.app.services.exporter uses a type in webapp.app.services.authenticated-request.
- The types involved
webapp.app.services.exporter.Exporter→webapp.app.services.authenticated-request.AuthenticatedRequest
- Direction
- webapp.app.services.exporter uses webapp.app.services.authenticated-request, so a change to webapp.app.services.authenticated-request can break webapp.app.services.exporter, while a change to webapp.app.services.exporter can't break webapp.app.services.authenticated-request.
- Position
- Below the diagonal: webapp.app.services.exporter uses a module listed above it, which is the healthy direction.
23→8 webapp.app.services.peeker uses webapp.app.services.authenticated-request✕
- Connections
- 1 pair of types, where a type in webapp.app.services.peeker uses a type in webapp.app.services.authenticated-request.
- The types involved
webapp.app.services.peeker.Peeker→webapp.app.services.authenticated-request.AuthenticatedRequest
- Direction
- webapp.app.services.peeker uses webapp.app.services.authenticated-request, so a change to webapp.app.services.authenticated-request can break webapp.app.services.peeker, while a change to webapp.app.services.peeker can't break webapp.app.services.authenticated-request.
- Position
- Below the diagonal: webapp.app.services.peeker uses a module listed above it, which is the healthy direction.
24→11 webapp.app.services.session uses webapp.app.services.jipt✕
- Connections
- 1 pair of types, where a type in webapp.app.services.session uses a type in webapp.app.services.jipt.
- The types involved
webapp.app.services.session.Session→webapp.app.services.jipt.JIPT
- Direction
- webapp.app.services.session uses webapp.app.services.jipt, so a change to webapp.app.services.jipt can break webapp.app.services.session, while a change to webapp.app.services.session can't break webapp.app.services.jipt.
- Position
- Below the diagonal: webapp.app.services.session uses a module listed above it, which is the healthy direction.
25→5 cli.src.commands.sync uses cli.src.types.project✕
- Connections
- 1 pair of types, where a type in cli.src.commands.sync uses a type in cli.src.types.project.
- The types involved
cli.src.commands.sync.Sync→cli.src.types.project.Document
- Direction
- cli.src.commands.sync uses cli.src.types.project, so a change to cli.src.types.project can break cli.src.commands.sync, while a change to cli.src.commands.sync can't break cli.src.types.project.
- Position
- Below the diagonal: cli.src.commands.sync uses a module listed above it, which is the healthy direction.
25→13 cli.src.commands.sync uses cli.src.base✕
- Connections
- 1 pair of types, where a type in cli.src.commands.sync uses a type in cli.src.base.
- The types involved
cli.src.commands.sync.Sync→cli.src.base.BaseCommand
- Direction
- cli.src.commands.sync uses cli.src.base, so a change to cli.src.base can break cli.src.commands.sync, while a change to cli.src.commands.sync can't break cli.src.base.
- Position
- Below the diagonal: cli.src.commands.sync uses a module listed above it, which is the healthy direction.
25→15 cli.src.commands.sync uses cli.src.services.formatters.commit-operation✕
- Connections
- 1 pair of types, where a type in cli.src.commands.sync uses a type in cli.src.services.formatters.commit-operation.
- The types involved
cli.src.commands.sync.Sync→cli.src.services.formatters.commit-operation.CommitOperationFormatter
- Direction
- cli.src.commands.sync uses cli.src.services.formatters.commit-operation, so a change to cli.src.services.formatters.commit-operation can break cli.src.commands.sync, while a change to cli.src.commands.sync can't break cli.src.services.formatters.commit-operation.
- Position
- Below the diagonal: cli.src.commands.sync uses a module listed above it, which is the healthy direction.
26→3 jipt.src.frame-listener uses cli.src.types.config✕
- Connections
- 1 pair of types, where a type in jipt.src.frame-listener uses a type in cli.src.types.config.
- The types involved
jipt.src.frame-listener.Props→cli.src.types.config.Config
- Direction
- jipt.src.frame-listener uses cli.src.types.config, so a change to cli.src.types.config can break jipt.src.frame-listener, while a change to jipt.src.frame-listener can't break cli.src.types.config.
- Position
- Below the diagonal: jipt.src.frame-listener uses a module listed above it, which is the healthy direction.
26→6 jipt.src.frame-listener uses jipt.src.state✕
- Connections
- 2 pairs of types, where a type in jipt.src.frame-listener uses a type in jipt.src.state.
- The types involved
jipt.src.frame-listener.FrameListener→jipt.src.state.Statejipt.src.frame-listener.Props→jipt.src.state.State
- Direction
- jipt.src.frame-listener uses jipt.src.state, so a change to jipt.src.state can break jipt.src.frame-listener, while a change to jipt.src.frame-listener can't break jipt.src.state.
- Position
- Below the diagonal: jipt.src.frame-listener uses a module listed above it, which is the healthy direction.
26→16 jipt.src.frame-listener uses jipt.src.mutation.live-node✕
- Connections
- 2 pairs of types, where a type in jipt.src.frame-listener uses a type in jipt.src.mutation.live-node.
- The types involved
jipt.src.frame-listener.FrameListener→jipt.src.mutation.live-node.LiveNodejipt.src.frame-listener.Props→jipt.src.mutation.live-node.LiveNode
- Direction
- jipt.src.frame-listener uses jipt.src.mutation.live-node, so a change to jipt.src.mutation.live-node can break jipt.src.frame-listener, while a change to jipt.src.frame-listener can't break jipt.src.mutation.live-node.
- Position
- Below the diagonal: jipt.src.frame-listener uses a module listed above it, which is the healthy direction.
26→17 jipt.src.frame-listener uses jipt.src.ui.ui✕
- Connections
- 3 pairs of types, where a type in jipt.src.frame-listener uses a type in jipt.src.ui.ui.
- The types involved
jipt.src.frame-listener.FrameListener→jipt.src.ui.ui.Propsjipt.src.frame-listener.FrameListener→jipt.src.ui.ui.UIjipt.src.frame-listener.Props→jipt.src.ui.ui.UI
- Direction
- jipt.src.frame-listener uses jipt.src.ui.ui, so a change to jipt.src.ui.ui can break jipt.src.frame-listener, while a change to jipt.src.frame-listener can't break jipt.src.ui.ui.
- Position
- Below the diagonal: jipt.src.frame-listener uses a module listed above it, which is the healthy direction.
27→6 jipt.src.ui.pin uses jipt.src.state✕
- Connections
- 2 pairs of types, where a type in jipt.src.ui.pin uses a type in jipt.src.state.
- The types involved
jipt.src.ui.pin.Pin→jipt.src.state.Statejipt.src.ui.pin.Props→jipt.src.state.State
- Direction
- jipt.src.ui.pin uses jipt.src.state, so a change to jipt.src.state can break jipt.src.ui.pin, while a change to jipt.src.ui.pin can't break jipt.src.state.
- Position
- Below the diagonal: jipt.src.ui.pin uses a module listed above it, which is the healthy direction.
27→16 jipt.src.ui.pin uses jipt.src.mutation.live-node✕
- Connections
- 2 pairs of types, where a type in jipt.src.ui.pin uses a type in jipt.src.mutation.live-node.
- The types involved
jipt.src.ui.pin.Pin→jipt.src.mutation.live-node.LiveNodejipt.src.ui.pin.Props→jipt.src.mutation.live-node.LiveNode
- Direction
- jipt.src.ui.pin uses jipt.src.mutation.live-node, so a change to jipt.src.mutation.live-node can break jipt.src.ui.pin, while a change to jipt.src.ui.pin can't break jipt.src.mutation.live-node.
- Position
- Below the diagonal: jipt.src.ui.pin uses a module listed above it, which is the healthy direction.
27→17 jipt.src.ui.pin uses jipt.src.ui.ui✕
- Connections
- 3 pairs of types, where a type in jipt.src.ui.pin uses a type in jipt.src.ui.ui.
- The types involved
jipt.src.ui.pin.Pin→jipt.src.ui.ui.Propsjipt.src.ui.pin.Pin→jipt.src.ui.ui.UIjipt.src.ui.pin.Props→jipt.src.ui.ui.UI
- Direction
- jipt.src.ui.pin uses jipt.src.ui.ui, so a change to jipt.src.ui.ui can break jipt.src.ui.pin, while a change to jipt.src.ui.pin can't break jipt.src.ui.ui.
- Position
- Below the diagonal: jipt.src.ui.pin uses a module listed above it, which is the healthy direction.
28→10 webapp.app.controllers.logged-in.jipt.translation uses webapp.app.services.global-state✕
- Connections
- 2 pairs of types, where a type in webapp.app.controllers.logged-in.jipt.translation uses a type in webapp.app.services.global-state.
- The types involved
webapp.app.controllers.logged-in.jipt.translation.IndexController→webapp.app.services.global-state.GlobalStatewebapp.app.controllers.logged-in.jipt.translation.TranslationController→webapp.app.services.global-state.GlobalState
- Direction
- webapp.app.controllers.logged-in.jipt.translation uses webapp.app.services.global-state, so a change to webapp.app.services.global-state can break webapp.app.controllers.logged-in.jipt.translation, while a change to webapp.app.controllers.logged-in.jipt.translation can't break webapp.app.services.global-state.
- Position
- Below the diagonal: webapp.app.controllers.logged-in.jipt.translation uses a module listed above it, which is the healthy direction.
28→11 webapp.app.controllers.logged-in.jipt.translation uses webapp.app.services.jipt✕
- Connections
- 1 pair of types, where a type in webapp.app.controllers.logged-in.jipt.translation uses a type in webapp.app.services.jipt.
- The types involved
webapp.app.controllers.logged-in.jipt.translation.IndexController→webapp.app.services.jipt.JIPT
- Direction
- webapp.app.controllers.logged-in.jipt.translation uses webapp.app.services.jipt, so a change to webapp.app.services.jipt can break webapp.app.controllers.logged-in.jipt.translation, while a change to webapp.app.controllers.logged-in.jipt.translation can't break webapp.app.services.jipt.
- Position
- Below the diagonal: webapp.app.controllers.logged-in.jipt.translation uses a module listed above it, which is the healthy direction.
28→20 webapp.app.controllers.logged-in.jipt.translation uses webapp.app.services.apollo-mutate✕
- Connections
- 1 pair of types, where a type in webapp.app.controllers.logged-in.jipt.translation uses a type in webapp.app.services.apollo-mutate.
- The types involved
webapp.app.controllers.logged-in.jipt.translation.IndexController→webapp.app.services.apollo-mutate.ApolloMutate
- Direction
- webapp.app.controllers.logged-in.jipt.translation uses webapp.app.services.apollo-mutate, so a change to webapp.app.services.apollo-mutate can break webapp.app.controllers.logged-in.jipt.translation, while a change to webapp.app.controllers.logged-in.jipt.translation can't break webapp.app.services.apollo-mutate.
- Position
- Below the diagonal: webapp.app.controllers.logged-in.jipt.translation uses a module listed above it, which is the healthy direction.
29→10 webapp.app.controllers.logged-in.project uses webapp.app.services.global-state✕
- Connections
- 2 pairs of types, where a type in webapp.app.controllers.logged-in.project uses a type in webapp.app.services.global-state.
- The types involved
webapp.app.controllers.logged-in.project.ProjectController→webapp.app.services.global-state.GlobalStatewebapp.app.controllers.logged-in.project.ProjectIndexController→webapp.app.services.global-state.GlobalState
- Direction
- webapp.app.controllers.logged-in.project uses webapp.app.services.global-state, so a change to webapp.app.services.global-state can break webapp.app.controllers.logged-in.project, while a change to webapp.app.controllers.logged-in.project can't break webapp.app.services.global-state.
- Position
- Below the diagonal: webapp.app.controllers.logged-in.project uses a module listed above it, which is the healthy direction.
29→20 webapp.app.controllers.logged-in.project uses webapp.app.services.apollo-mutate✕
- Connections
- 1 pair of types, where a type in webapp.app.controllers.logged-in.project uses a type in webapp.app.services.apollo-mutate.
- The types involved
webapp.app.controllers.logged-in.project.ProjectIndexController→webapp.app.services.apollo-mutate.ApolloMutate
- Direction
- webapp.app.controllers.logged-in.project uses webapp.app.services.apollo-mutate, so a change to webapp.app.services.apollo-mutate can break webapp.app.controllers.logged-in.project, while a change to webapp.app.controllers.logged-in.project can't break webapp.app.services.apollo-mutate.
- Position
- Below the diagonal: webapp.app.controllers.logged-in.project uses a module listed above it, which is the healthy direction.
29→24 webapp.app.controllers.logged-in.project uses webapp.app.services.session✕
- Connections
- 1 pair of types, where a type in webapp.app.controllers.logged-in.project uses a type in webapp.app.services.session.
- The types involved
webapp.app.controllers.logged-in.project.ProjectController→webapp.app.services.session.Session
- Direction
- webapp.app.controllers.logged-in.project uses webapp.app.services.session, so a change to webapp.app.services.session can break webapp.app.controllers.logged-in.project, while a change to webapp.app.controllers.logged-in.project can't break webapp.app.services.session.
- Position
- Below the diagonal: webapp.app.controllers.logged-in.project uses a module listed above it, which is the healthy direction.
30→10 webapp.app.controllers.logged-in.project.activities uses webapp.app.services.global-state✕
- Connections
- 1 pair of types, where a type in webapp.app.controllers.logged-in.project.activities uses a type in webapp.app.services.global-state.
- The types involved
webapp.app.controllers.logged-in.project.activities.ActivitiesController→webapp.app.services.global-state.GlobalState
- Direction
- webapp.app.controllers.logged-in.project.activities uses webapp.app.services.global-state, so a change to webapp.app.services.global-state can break webapp.app.controllers.logged-in.project.activities, while a change to webapp.app.controllers.logged-in.project.activities can't break webapp.app.services.global-state.
- Position
- Below the diagonal: webapp.app.controllers.logged-in.project.activities uses a module listed above it, which is the healthy direction.
30→20 webapp.app.controllers.logged-in.project.activities uses webapp.app.services.apollo-mutate✕
- Connections
- 1 pair of types, where a type in webapp.app.controllers.logged-in.project.activities uses a type in webapp.app.services.apollo-mutate.
- The types involved
webapp.app.controllers.logged-in.project.activities.ActivitiesController→webapp.app.services.apollo-mutate.ApolloMutate
- Direction
- webapp.app.controllers.logged-in.project.activities uses webapp.app.services.apollo-mutate, so a change to webapp.app.services.apollo-mutate can break webapp.app.controllers.logged-in.project.activities, while a change to webapp.app.controllers.logged-in.project.activities can't break webapp.app.services.apollo-mutate.
- Position
- Below the diagonal: webapp.app.controllers.logged-in.project.activities uses a module listed above it, which is the healthy direction.
31→7 webapp.app.controllers.logged-in.project.conflicts uses webapp.app.services.apollo✕
- Connections
- 1 pair of types, where a type in webapp.app.controllers.logged-in.project.conflicts uses a type in webapp.app.services.apollo.
- The types involved
webapp.app.controllers.logged-in.project.conflicts.ConflictsController→webapp.app.services.apollo.Apollo
- Direction
- webapp.app.controllers.logged-in.project.conflicts uses webapp.app.services.apollo, so a change to webapp.app.services.apollo can break webapp.app.controllers.logged-in.project.conflicts, while a change to webapp.app.controllers.logged-in.project.conflicts can't break webapp.app.services.apollo.
- Position
- Below the diagonal: webapp.app.controllers.logged-in.project.conflicts uses a module listed above it, which is the healthy direction.
31→10 webapp.app.controllers.logged-in.project.conflicts uses webapp.app.services.global-state✕
- Connections
- 1 pair of types, where a type in webapp.app.controllers.logged-in.project.conflicts uses a type in webapp.app.services.global-state.
- The types involved
webapp.app.controllers.logged-in.project.conflicts.ConflictsController→webapp.app.services.global-state.GlobalState
- Direction
- webapp.app.controllers.logged-in.project.conflicts uses webapp.app.services.global-state, so a change to webapp.app.services.global-state can break webapp.app.controllers.logged-in.project.conflicts, while a change to webapp.app.controllers.logged-in.project.conflicts can't break webapp.app.services.global-state.
- Position
- Below the diagonal: webapp.app.controllers.logged-in.project.conflicts uses a module listed above it, which is the healthy direction.
31→20 webapp.app.controllers.logged-in.project.conflicts uses webapp.app.services.apollo-mutate✕
- Connections
- 1 pair of types, where a type in webapp.app.controllers.logged-in.project.conflicts uses a type in webapp.app.services.apollo-mutate.
- The types involved
webapp.app.controllers.logged-in.project.conflicts.ConflictsController→webapp.app.services.apollo-mutate.ApolloMutate
- Direction
- webapp.app.controllers.logged-in.project.conflicts uses webapp.app.services.apollo-mutate, so a change to webapp.app.services.apollo-mutate can break webapp.app.controllers.logged-in.project.conflicts, while a change to webapp.app.controllers.logged-in.project.conflicts can't break webapp.app.services.apollo-mutate.
- Position
- Below the diagonal: webapp.app.controllers.logged-in.project.conflicts uses a module listed above it, which is the healthy direction.
32→10 webapp.app.controllers.logged-in.project.files.add-translations uses webapp.app.services.global-state✕
- Connections
- 1 pair of types, where a type in webapp.app.controllers.logged-in.project.files.add-translations uses a type in webapp.app.services.global-state.
- The types involved
webapp.app.controllers.logged-in.project.files.add-translations.AddTranslationsController→webapp.app.services.global-state.GlobalState
- Direction
- webapp.app.controllers.logged-in.project.files.add-translations uses webapp.app.services.global-state, so a change to webapp.app.services.global-state can break webapp.app.controllers.logged-in.project.files.add-translations, while a change to webapp.app.controllers.logged-in.project.files.add-translations can't break webapp.app.services.global-state.
- Position
- Below the diagonal: webapp.app.controllers.logged-in.project.files.add-translations uses a module listed above it, which is the healthy direction.
32→23 webapp.app.controllers.logged-in.project.files.add-translations uses webapp.app.services.peeker✕
- Connections
- 1 pair of types, where a type in webapp.app.controllers.logged-in.project.files.add-translations uses a type in webapp.app.services.peeker.
- The types involved
webapp.app.controllers.logged-in.project.files.add-translations.AddTranslationsController→webapp.app.services.peeker.Peeker
- Direction
- webapp.app.controllers.logged-in.project.files.add-translations uses webapp.app.services.peeker, so a change to webapp.app.services.peeker can break webapp.app.controllers.logged-in.project.files.add-translations, while a change to webapp.app.controllers.logged-in.project.files.add-translations can't break webapp.app.services.peeker.
- Position
- Below the diagonal: webapp.app.controllers.logged-in.project.files.add-translations uses a module listed above it, which is the healthy direction.
33→10 webapp.app.controllers.logged-in.project.revision.translations uses webapp.app.services.global-state✕
- Connections
- 1 pair of types, where a type in webapp.app.controllers.logged-in.project.revision.translations uses a type in webapp.app.services.global-state.
- The types involved
webapp.app.controllers.logged-in.project.revision.translations.TranslationsController→webapp.app.services.global-state.GlobalState
- Direction
- webapp.app.controllers.logged-in.project.revision.translations uses webapp.app.services.global-state, so a change to webapp.app.services.global-state can break webapp.app.controllers.logged-in.project.revision.translations, while a change to webapp.app.controllers.logged-in.project.revision.translations can't break webapp.app.services.global-state.
- Position
- Below the diagonal: webapp.app.controllers.logged-in.project.revision.translations uses a module listed above it, which is the healthy direction.
33→20 webapp.app.controllers.logged-in.project.revision.translations uses webapp.app.services.apollo-mutate✕
- Connections
- 1 pair of types, where a type in webapp.app.controllers.logged-in.project.revision.translations uses a type in webapp.app.services.apollo-mutate.
- The types involved
webapp.app.controllers.logged-in.project.revision.translations.TranslationsController→webapp.app.services.apollo-mutate.ApolloMutate
- Direction
- webapp.app.controllers.logged-in.project.revision.translations uses webapp.app.services.apollo-mutate, so a change to webapp.app.services.apollo-mutate can break webapp.app.controllers.logged-in.project.revision.translations, while a change to webapp.app.controllers.logged-in.project.revision.translations can't break webapp.app.services.apollo-mutate.
- Position
- Below the diagonal: webapp.app.controllers.logged-in.project.revision.translations uses a module listed above it, which is the healthy direction.
34→10 webapp.app.controllers.logged-in.projects uses webapp.app.services.global-state✕
- Connections
- 1 pair of types, where a type in webapp.app.controllers.logged-in.projects uses a type in webapp.app.services.global-state.
- The types involved
webapp.app.controllers.logged-in.projects.ProjectsController→webapp.app.services.global-state.GlobalState
- Direction
- webapp.app.controllers.logged-in.projects uses webapp.app.services.global-state, so a change to webapp.app.services.global-state can break webapp.app.controllers.logged-in.projects, while a change to webapp.app.controllers.logged-in.projects can't break webapp.app.services.global-state.
- Position
- Below the diagonal: webapp.app.controllers.logged-in.projects uses a module listed above it, which is the healthy direction.
34→11 webapp.app.controllers.logged-in.projects uses webapp.app.services.jipt✕
- Connections
- 1 pair of types, where a type in webapp.app.controllers.logged-in.projects uses a type in webapp.app.services.jipt.
- The types involved
webapp.app.controllers.logged-in.projects.ProjectsController→webapp.app.services.jipt.JIPT
- Direction
- webapp.app.controllers.logged-in.projects uses webapp.app.services.jipt, so a change to webapp.app.services.jipt can break webapp.app.controllers.logged-in.projects, while a change to webapp.app.controllers.logged-in.projects can't break webapp.app.services.jipt.
- Position
- Below the diagonal: webapp.app.controllers.logged-in.projects uses a module listed above it, which is the healthy direction.
34→24 webapp.app.controllers.logged-in.projects uses webapp.app.services.session✕
- Connections
- 1 pair of types, where a type in webapp.app.controllers.logged-in.projects uses a type in webapp.app.services.session.
- The types involved
webapp.app.controllers.logged-in.projects.ProjectsController→webapp.app.services.session.Session
- Direction
- webapp.app.controllers.logged-in.projects uses webapp.app.services.session, so a change to webapp.app.services.session can break webapp.app.controllers.logged-in.projects, while a change to webapp.app.controllers.logged-in.projects can't break webapp.app.services.session.
- Position
- Below the diagonal: webapp.app.controllers.logged-in.projects uses a module listed above it, which is the healthy direction.
35→10 webapp.app.routes.logged-in.jipt uses webapp.app.services.global-state✕
- Connections
- 1 pair of types, where a type in webapp.app.routes.logged-in.jipt uses a type in webapp.app.services.global-state.
- The types involved
webapp.app.routes.logged-in.jipt.JIPTRoute→webapp.app.services.global-state.GlobalState
- Direction
- webapp.app.routes.logged-in.jipt uses webapp.app.services.global-state, so a change to webapp.app.services.global-state can break webapp.app.routes.logged-in.jipt, while a change to webapp.app.routes.logged-in.jipt can't break webapp.app.services.global-state.
- Position
- Below the diagonal: webapp.app.routes.logged-in.jipt uses a module listed above it, which is the healthy direction.
35→11 webapp.app.routes.logged-in.jipt uses webapp.app.services.jipt✕
- Connections
- 1 pair of types, where a type in webapp.app.routes.logged-in.jipt uses a type in webapp.app.services.jipt.
- The types involved
webapp.app.routes.logged-in.jipt.JIPTRoute→webapp.app.services.jipt.JIPT
- Direction
- webapp.app.routes.logged-in.jipt uses webapp.app.services.jipt, so a change to webapp.app.services.jipt can break webapp.app.routes.logged-in.jipt, while a change to webapp.app.routes.logged-in.jipt can't break webapp.app.services.jipt.
- Position
- Below the diagonal: webapp.app.routes.logged-in.jipt uses a module listed above it, which is the healthy direction.
35→12 webapp.app.routes.logged-in.jipt uses webapp.app.services.route-params✕
- Connections
- 1 pair of types, where a type in webapp.app.routes.logged-in.jipt uses a type in webapp.app.services.route-params.
- The types involved
webapp.app.routes.logged-in.jipt.IndexRoute→webapp.app.services.route-params.RouteParams
- Direction
- webapp.app.routes.logged-in.jipt uses webapp.app.services.route-params, so a change to webapp.app.services.route-params can break webapp.app.routes.logged-in.jipt, while a change to webapp.app.routes.logged-in.jipt can't break webapp.app.services.route-params.
- Position
- Below the diagonal: webapp.app.routes.logged-in.jipt uses a module listed above it, which is the healthy direction.
35→18 webapp.app.routes.logged-in.jipt uses webapp.app.controllers.logged-in.jipt✕
- Connections
- 1 pair of types, where a type in webapp.app.routes.logged-in.jipt uses a type in webapp.app.controllers.logged-in.jipt.
- The types involved
webapp.app.routes.logged-in.jipt.IndexRoute→webapp.app.controllers.logged-in.jipt.IndexController
- Direction
- webapp.app.routes.logged-in.jipt uses webapp.app.controllers.logged-in.jipt, so a change to webapp.app.controllers.logged-in.jipt can break webapp.app.routes.logged-in.jipt, while a change to webapp.app.routes.logged-in.jipt can't break webapp.app.controllers.logged-in.jipt.
- Position
- Below the diagonal: webapp.app.routes.logged-in.jipt uses a module listed above it, which is the healthy direction.
35→21 webapp.app.routes.logged-in.jipt uses webapp.app.services.apollo-subscription✕
- Connections
- 4 pairs of types, where a type in webapp.app.routes.logged-in.jipt uses a type in webapp.app.services.apollo-subscription.
- The types involved
webapp.app.routes.logged-in.jipt.IndexRoute→webapp.app.services.apollo-subscription.ApolloSubscriptionwebapp.app.routes.logged-in.jipt.IndexRoute→webapp.app.services.apollo-subscription.Subscriptionwebapp.app.routes.logged-in.jipt.JIPTRoute→webapp.app.services.apollo-subscription.ApolloSubscriptionwebapp.app.routes.logged-in.jipt.JIPTRoute→webapp.app.services.apollo-subscription.Subscription
- Direction
- webapp.app.routes.logged-in.jipt uses webapp.app.services.apollo-subscription, so a change to webapp.app.services.apollo-subscription can break webapp.app.routes.logged-in.jipt, while a change to webapp.app.routes.logged-in.jipt can't break webapp.app.services.apollo-subscription.
- Position
- Below the diagonal: webapp.app.routes.logged-in.jipt uses a module listed above it, which is the healthy direction.
36→10 webapp.app.routes.logged-in.project uses webapp.app.services.global-state✕
- Connections
- 1 pair of types, where a type in webapp.app.routes.logged-in.project uses a type in webapp.app.services.global-state.
- The types involved
webapp.app.routes.logged-in.project.ProjectRoute→webapp.app.services.global-state.GlobalState
- Direction
- webapp.app.routes.logged-in.project uses webapp.app.services.global-state, so a change to webapp.app.services.global-state can break webapp.app.routes.logged-in.project, while a change to webapp.app.routes.logged-in.project can't break webapp.app.services.global-state.
- Position
- Below the diagonal: webapp.app.routes.logged-in.project uses a module listed above it, which is the healthy direction.
36→12 webapp.app.routes.logged-in.project uses webapp.app.services.route-params✕
- Connections
- 1 pair of types, where a type in webapp.app.routes.logged-in.project uses a type in webapp.app.services.route-params.
- The types involved
webapp.app.routes.logged-in.project.ProjectIndexRoute→webapp.app.services.route-params.RouteParams
- Direction
- webapp.app.routes.logged-in.project uses webapp.app.services.route-params, so a change to webapp.app.services.route-params can break webapp.app.routes.logged-in.project, while a change to webapp.app.routes.logged-in.project can't break webapp.app.services.route-params.
- Position
- Below the diagonal: webapp.app.routes.logged-in.project uses a module listed above it, which is the healthy direction.
36→21 webapp.app.routes.logged-in.project uses webapp.app.services.apollo-subscription✕
- Connections
- 4 pairs of types, where a type in webapp.app.routes.logged-in.project uses a type in webapp.app.services.apollo-subscription.
- The types involved
webapp.app.routes.logged-in.project.ProjectIndexRoute→webapp.app.services.apollo-subscription.ApolloSubscriptionwebapp.app.routes.logged-in.project.ProjectIndexRoute→webapp.app.services.apollo-subscription.Subscriptionwebapp.app.routes.logged-in.project.ProjectRoute→webapp.app.services.apollo-subscription.ApolloSubscriptionwebapp.app.routes.logged-in.project.ProjectRoute→webapp.app.services.apollo-subscription.Subscription
- Direction
- webapp.app.routes.logged-in.project uses webapp.app.services.apollo-subscription, so a change to webapp.app.services.apollo-subscription can break webapp.app.routes.logged-in.project, while a change to webapp.app.routes.logged-in.project can't break webapp.app.services.apollo-subscription.
- Position
- Below the diagonal: webapp.app.routes.logged-in.project uses a module listed above it, which is the healthy direction.
37→8 webapp.app.services.syncer uses webapp.app.services.authenticated-request✕
- Connections
- 1 pair of types, where a type in webapp.app.services.syncer uses a type in webapp.app.services.authenticated-request.
- The types involved
webapp.app.services.syncer.Syncer→webapp.app.services.authenticated-request.AuthenticatedRequest
- Direction
- webapp.app.services.syncer uses webapp.app.services.authenticated-request, so a change to webapp.app.services.authenticated-request can break webapp.app.services.syncer, while a change to webapp.app.services.syncer can't break webapp.app.services.authenticated-request.
- Position
- Below the diagonal: webapp.app.services.syncer uses a module listed above it, which is the healthy direction.
37→23 webapp.app.services.syncer uses webapp.app.services.peeker✕
- Connections
- 1 pair of types, where a type in webapp.app.services.syncer uses a type in webapp.app.services.peeker.
- The types involved
webapp.app.services.syncer.Syncer→webapp.app.services.peeker.SyncOptions
- Direction
- webapp.app.services.syncer uses webapp.app.services.peeker, so a change to webapp.app.services.peeker can break webapp.app.services.syncer, while a change to webapp.app.services.syncer can't break webapp.app.services.peeker.
- Position
- Below the diagonal: webapp.app.services.syncer uses a module listed above it, which is the healthy direction.
38→10 webapp.app.controllers.logged-in.project.files.new-sync uses webapp.app.services.global-state✕
- Connections
- 1 pair of types, where a type in webapp.app.controllers.logged-in.project.files.new-sync uses a type in webapp.app.services.global-state.
- The types involved
webapp.app.controllers.logged-in.project.files.new-sync.NewSyncController→webapp.app.services.global-state.GlobalState
- Direction
- webapp.app.controllers.logged-in.project.files.new-sync uses webapp.app.services.global-state, so a change to webapp.app.services.global-state can break webapp.app.controllers.logged-in.project.files.new-sync, while a change to webapp.app.controllers.logged-in.project.files.new-sync can't break webapp.app.services.global-state.
- Position
- Below the diagonal: webapp.app.controllers.logged-in.project.files.new-sync uses a module listed above it, which is the healthy direction.
38→23 webapp.app.controllers.logged-in.project.files.new-sync uses webapp.app.services.peeker✕
- Connections
- 1 pair of types, where a type in webapp.app.controllers.logged-in.project.files.new-sync uses a type in webapp.app.services.peeker.
- The types involved
webapp.app.controllers.logged-in.project.files.new-sync.NewSyncController→webapp.app.services.peeker.Peeker
- Direction
- webapp.app.controllers.logged-in.project.files.new-sync uses webapp.app.services.peeker, so a change to webapp.app.services.peeker can break webapp.app.controllers.logged-in.project.files.new-sync, while a change to webapp.app.controllers.logged-in.project.files.new-sync can't break webapp.app.services.peeker.
- Position
- Below the diagonal: webapp.app.controllers.logged-in.project.files.new-sync uses a module listed above it, which is the healthy direction.
38→37 webapp.app.controllers.logged-in.project.files.new-sync uses webapp.app.services.syncer✕
- Connections
- 1 pair of types, where a type in webapp.app.controllers.logged-in.project.files.new-sync uses a type in webapp.app.services.syncer.
- The types involved
webapp.app.controllers.logged-in.project.files.new-sync.NewSyncController→webapp.app.services.syncer.Syncer
- Direction
- webapp.app.controllers.logged-in.project.files.new-sync uses webapp.app.services.syncer, so a change to webapp.app.services.syncer can break webapp.app.controllers.logged-in.project.files.new-sync, while a change to webapp.app.controllers.logged-in.project.files.new-sync can't break webapp.app.services.syncer.
- Position
- Below the diagonal: webapp.app.controllers.logged-in.project.files.new-sync uses a module listed above it, which is the healthy direction.
39→10 webapp.app.controllers.logged-in.project.files.sync uses webapp.app.services.global-state✕
- Connections
- 1 pair of types, where a type in webapp.app.controllers.logged-in.project.files.sync uses a type in webapp.app.services.global-state.
- The types involved
webapp.app.controllers.logged-in.project.files.sync.SyncController→webapp.app.services.global-state.GlobalState
- Direction
- webapp.app.controllers.logged-in.project.files.sync uses webapp.app.services.global-state, so a change to webapp.app.services.global-state can break webapp.app.controllers.logged-in.project.files.sync, while a change to webapp.app.controllers.logged-in.project.files.sync can't break webapp.app.services.global-state.
- Position
- Below the diagonal: webapp.app.controllers.logged-in.project.files.sync uses a module listed above it, which is the healthy direction.
39→23 webapp.app.controllers.logged-in.project.files.sync uses webapp.app.services.peeker✕
- Connections
- 1 pair of types, where a type in webapp.app.controllers.logged-in.project.files.sync uses a type in webapp.app.services.peeker.
- The types involved
webapp.app.controllers.logged-in.project.files.sync.SyncController→webapp.app.services.peeker.Peeker
- Direction
- webapp.app.controllers.logged-in.project.files.sync uses webapp.app.services.peeker, so a change to webapp.app.services.peeker can break webapp.app.controllers.logged-in.project.files.sync, while a change to webapp.app.controllers.logged-in.project.files.sync can't break webapp.app.services.peeker.
- Position
- Below the diagonal: webapp.app.controllers.logged-in.project.files.sync uses a module listed above it, which is the healthy direction.
39→37 webapp.app.controllers.logged-in.project.files.sync uses webapp.app.services.syncer✕
- Connections
- 1 pair of types, where a type in webapp.app.controllers.logged-in.project.files.sync uses a type in webapp.app.services.syncer.
- The types involved
webapp.app.controllers.logged-in.project.files.sync.SyncController→webapp.app.services.syncer.Syncer
- Direction
- webapp.app.controllers.logged-in.project.files.sync uses webapp.app.services.syncer, so a change to webapp.app.services.syncer can break webapp.app.controllers.logged-in.project.files.sync, while a change to webapp.app.controllers.logged-in.project.files.sync can't break webapp.app.services.syncer.
- Position
- Below the diagonal: webapp.app.controllers.logged-in.project.files.sync uses a module listed above it, which is the healthy direction.
40→21 webapp.app.routes.logged-in.projects uses webapp.app.services.apollo-subscription✕
- Connections
- 2 pairs of types, where a type in webapp.app.routes.logged-in.projects uses a type in webapp.app.services.apollo-subscription.
- The types involved
webapp.app.routes.logged-in.projects.ProjectsRoute→webapp.app.services.apollo-subscription.ApolloSubscriptionwebapp.app.routes.logged-in.projects.ProjectsRoute→webapp.app.services.apollo-subscription.Subscription
- Direction
- webapp.app.routes.logged-in.projects uses webapp.app.services.apollo-subscription, so a change to webapp.app.services.apollo-subscription can break webapp.app.routes.logged-in.projects, while a change to webapp.app.routes.logged-in.projects can't break webapp.app.services.apollo-subscription.
- Position
- Below the diagonal: webapp.app.routes.logged-in.projects uses a module listed above it, which is the healthy direction.
40→24 webapp.app.routes.logged-in.projects uses webapp.app.services.session✕
- Connections
- 1 pair of types, where a type in webapp.app.routes.logged-in.projects uses a type in webapp.app.services.session.
- The types involved
webapp.app.routes.logged-in.projects.ProjectsRoute→webapp.app.services.session.Session
- Direction
- webapp.app.routes.logged-in.projects uses webapp.app.services.session, so a change to webapp.app.services.session can break webapp.app.routes.logged-in.projects, while a change to webapp.app.routes.logged-in.projects can't break webapp.app.services.session.
- Position
- Below the diagonal: webapp.app.routes.logged-in.projects uses a module listed above it, which is the healthy direction.
40→34 webapp.app.routes.logged-in.projects uses webapp.app.controllers.logged-in.projects✕
- Connections
- 1 pair of types, where a type in webapp.app.routes.logged-in.projects uses a type in webapp.app.controllers.logged-in.projects.
- The types involved
webapp.app.routes.logged-in.projects.ProjectsRoute→webapp.app.controllers.logged-in.projects.ProjectsController
- Direction
- webapp.app.routes.logged-in.projects uses webapp.app.controllers.logged-in.projects, so a change to webapp.app.controllers.logged-in.projects can break webapp.app.routes.logged-in.projects, while a change to webapp.app.routes.logged-in.projects can't break webapp.app.controllers.logged-in.projects.
- Position
- Below the diagonal: webapp.app.routes.logged-in.projects uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 54 | High / Critical |
| A05:2025 — Injection | 25 | High / Critical |
| A02:2025 — Security Misconfiguration | 9 | High / Critical |
Roadmap
Top priorities: Add a SAST step to CI running what this repository's stack ships: sobelow (Elixir/Phoenix) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing; Resolve the 1 finding(s) in DR & Backup; Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 Floating source dependency finding(s) in Dependency Hygiene. | +3.7 pts | Low | Dependency Hygiene |
| Add a SAST step to CI running what this repository's stack ships: sobelow (Elixir/Phoenix) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +3.7 pts | Medium | Security & performance tooling |
| Resolve the 1 finding(s) in DR & Backup. | +3.7 pts | Medium | DR & Backup |
| Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies. | +3.7 pts | Medium | Dependency Hygiene |
| Add tests that import the unreached modules (directly or through their public entry). | +3.6 pts | Medium | Test Coverage |
| Set an explicit timeout on every client — `recv_timeout:` for HTTPoison, `receive_timeout:` for Req and Finch, `Tesla.Middleware.Timeout` (or the adapter's `recv_timeout`) for Tesla, `timeout:` for `:httpc` — and add retries with back-off (`Tesla.Middleware.Retry`, Req's `retry:`) and a breaker (`:fuse`, `ExternalService`) around dependencies that fail. | +2.2 pts | Medium | Outbound HTTP resilience |
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with mix.exs. | +0.8 pts | Low | ADR Quality |
| TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants. | +1.3 pts | Medium | Async & latency hygiene |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.2 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 0.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 5.2 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 5.8 | Mixed | Dependency Vulnerabilities: Medium CVE: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.9 | Mixed | Dependency Vulnerabilities: Medium CVE: REDACTED |
| webapp/app/utils/file-saver.js | 6.9 | Mixed | Cyclomatic Complexity: fileSaver (cyclomatic 29) |
| lib/accent/telemetry_ui/telemetry_ui.ex | 7.1 | Mixed | God Classes: FileTooLong: telemetry_ui/telemetry_ui.ex |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| lib/graphql/resolvers/document.ex | 7.4 | Mixed | Code Duplication: Edited copy of a member (11 corresponding lines) |
| lib/movement/persisters/operations_update_all_dynamic.ex | 7.8 | Mixed | Code Duplication: Edited copy of a member (25 corresponding lines) |
| lib/graphql/resolvers/revision.ex | 7.8 | Mixed | Code Duplication: Edited copy of a member (23 corresponding lines) |
| lib/web/controllers/merge_controller.ex | 7.8 | Mixed | Code Duplication: Edited copy of a member (14 corresponding lines) |
| lib/accent/scopes/language.ex | 7.8 | Mixed | Code Duplication: Edited copy of a member (19 corresponding lines) |
| lib/graphql/resolvers/project.ex | 7.8 | Mixed | Code Duplication: Edited copy of a member (14 corresponding lines) |
| lib/movement/persisters/new_slave.ex | 7.8 | Mixed | Code Duplication: Edited copy of a member (16 corresponding lines) |
| lib/accent/machine_translations_config/machine_translations_config_manager.ex | 7.8 | Mixed | Code Duplication: Edited copy of a member (15 corresponding lines) |
| lib/movement/builders/revision_merge.ex | 7.8 | Mixed | Code Duplication: Edited copy of a member (8 corresponding lines) |
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 63 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 63 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, 304 of 357 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
- D10 Test Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 91 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 149 test source file(s) (.exs) that it cannot: it reads JavaScript/TypeScript test declarations off disk, so a JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares an Elixir mix.exs/REDACTED (Hex), but the licence verdict published here was taken over its gem dependencies. Nothing was read about its Mix dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its gem dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (52 contributor(s) across 948 commit(s) sampled, automation and bot accounts excluded). One of them holds 87% of the history; the other 51 hold 0.3% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- 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 a COLLECTOR gap, not an environment fault: it declares a published package (cli/package.json), but no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
- D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D27 Navigability — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Tracing effort is measured over resolved call sites, and all 272 sampled here came from .ex files. This repository's .ts source is a material share of its production lines and contributed none, so the score above is a verdict about the part that was read. Not a finding that the unread half navigates well — it is unmeasured.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 17 — an image could not be built) — failed to solve: process "/bin/sh -c cd ./vendor/language_tool/priv/native/languagetool && ./gradlew shadowJar" did not complete successfully: exit code: 1; runtime evidence skipped.
- C1 Data Protection — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
- C2 Access Controls — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Elixir is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Elixir is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- R10 Code Duplication — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 25 further occurrence(s) are not listed individually; the score already reflects all 65.
- R4 Test Coverage — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 200 further occurrence(s) are not listed individually; the score already reflects all 240.
- X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X19 Unrestored process-global state — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- 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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X21 Side-effecting pattern guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X27 Collection changed while being enumerated — 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 Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded, no Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala or Kotlin was found, and this repository's Elixir is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X29 Per-element action decided by a fixed element — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- 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.
- X7 Silent fallback defaults — 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. X7 measured the part of this repository it reads (C#, Python, TypeScript/JavaScript, Rust, Go, Java, Kotlin, Scala, PHP, Ruby, Swift and Dart), and its Elixir source is outside the check's reach, so the card covers only part of the product. That is a gap in this analyzer's language reach — not a finding that the unread source is free of silent defaults.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- 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.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
2 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was fileSaver at 29.
What to do
- Bring the 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with fileSaver (cyclomatic 29). — Refactoring it lifts Cyclomatic Complexity from 9.2 to about 10.0/10.
D2 · Cognitive Complexity
2 method(s) exceeded the cognitive complexity threshold of 15; the worst was fileSaver at 33.
What to do
- Bring the 1 body over 15 down to 15 or less in Cognitive Complexity — start with fileSaver (cognitive 33). — Refactoring it lifts Cognitive Complexity from 9.0 to about 10.0/10.
D3 · God Classes
3 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 1 TooManyFunctions finding(s) in God Classes — start with translation.ex. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 FunctionTooLong finding(s) in God Classes — start with file-saver.js. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 FileTooLong finding(s) in God Classes — start with telemetry_ui.ex. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
14 duplicated block group(s) detected. A further 38 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. Measured on part of this repository only: .ts (41% of production source) was not exposed to THIS dimension's token comparison and is not in this count; duplication there is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream.
What to do
- Resolve the 4 Edited copy of a member (8 corresponding lines) finding(s) in Code Duplication — start with lint_controller.ex (2), revision_merge.ex, new_slave.ex. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 4 Edited copy of a member (6 corresponding lines) finding(s) in Code Duplication — start with serializer.ex, document.ex, discord.ex. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 3 Edited copy of a member (14 corresponding lines) finding(s) in Code Duplication — start with merge_controller.ex, project.ex, operation.ex. — One of this dimension's main actionable groups (3 warning-level).
D5 · Coupling
3 production modules (npm+OTP), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence.
D6 · Cohesion (LCOM4)
0 of 1 classes have LCOM4 above 3.
D8 · Code Coverage
Line coverage 95.3%. Measured from the JavaScript/TypeScript suite (node:test via `npm ci --ignore-scripts` in cli/; node:test via `npm ci --ignore-scripts` in jipt/).
D10 · Test Quality
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 91 tests. Measured on the JavaScript/TypeScript suite only — at least 149 test source file(s) (.exs) went unread, so its test quality is unmeasured and is not in these counts.
D11 · Test Reliability
0 flaky across 1 measured tier(s). JavaScript/TypeScript (node:test via `npm ci --ignore-scripts` in cli/ (77 tests); node:test via `npm ci --ignore-scripts` in jipt/ (14 tests)): measured (0 flaky).
D12 · Dependency Hygiene
11 outdated, 0 retired direct Hex dependencies, 1 pinning defect(s). Whether any of these packages is UNMAINTAINED is not graded — hex.pm publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: a Hex app name does not determine the modules it provides (`ecto_sql` provides Ecto.Adapters.SQL), and a large idiomatic class of BEAM dependencies — runtime adapters, codec plugins, protocol implementations and OTP applications the release starts — is correctly declared and never referenced in source, so absence of a reference is not evidence of an unused dependency. Known CVEs in this dependency graph are D30's question, read from REDACTED there.
What to do
- Resolve the 1 Floating source dependency finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 3 shipped gem(s) use a banned license. Licences were resolved from rubygems.org over the 3 gem(s) a consumer installs — this repository's runtime declarations closed transitively over its committed Gemfile.lock. Development-group and `add_development_dependency` gems are excluded: they are not distributed with this repository. ★ COVERAGE OF THIS VERDICT: it grades this repository's gem dependencies and nothing else. The repository also declares an Elixir mix.exs/REDACTED (Hex) and package.json, and the licences of those dependency graphs were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
0 deducted task-comment markers across 28444 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
2 of 2 documentation facets pass in full. 3 document(s) read across 4 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with mix.exs. — One of this dimension's main actionable groups (1 recommendation-level).
D24 · Comment Value
1 of 32 judged comments only repeat the code they sit on (3.1 %). 2 comment(s) in another language or script were not judged.
What to do
- Resolve the 1 redundant comment finding(s) in Comment Value — start with file-saver.js. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
2 of 4 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
29 % of calls cross a namespace and 0 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated. Measured over the .ex source only — this repository's .ts was not sampled for call sites, so this score covers part of the tree, not all of it.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
25 finding(s): 0 critical, 15 high, 10 medium, 0 low. 9 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. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
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 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 9 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 (9 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
47 finding(s): 2 critical, 22 high, 23 medium, 0 low.
What to do
- Resolve the 23 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (13), REDACTED (10). — One of this dimension's main actionable groups (23 warning-level).
- Resolve the 22 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (22). — One of this dimension's main actionable groups (22 issue-level).
- Resolve the 2 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
D31 · IaC & Container Security
9 finding(s): 0 critical, 1 high, 7 medium, 1 low.
What to do
- 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 7 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (6), REDACTED. — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 1 Low IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 123 of the 674 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: accent.ex↔mix.exs 80%; endpoint.ex↔mix.exs 50%; router.ex↔mix.exs 50%
What to do
- Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with mix.exs. — One of this dimension's main actionable groups (1 warning-level).
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
1 end-of-life runtime(s) and 0 end-of-life framework(s), read from 8 platform declaration(s) and 7 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 package.json. — One of this dimension's main actionable groups (1 warning-level).
Frontend & cross-cutting dimensions
AC1 · Text alternatives
AC2 · Forms & labels
AC3 · Page structure
- The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). (×3) — jipt/index.html:1, lib/web/templates/email_layout/index.html.eex:1, webapp/index.html:2
- A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>. (×2) — jipt/index.html:1, lib/web/templates/email_layout/index.html.eex:1
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×3) — jipt/index.html:1, lib/web/templates/email_layout/index.html.eex:1, lib/web/templates/graphiql/index.html.eex:9
- A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope). — lib/web/templates/email_layout/index.html.eex:3
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="modals">, so there is no content here to wrap — render the <main> from the component mounted into it. — webapp/index.html:2
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC6 · Visual & motion safety
- `.ember-power-select-trigger-multiple-input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — webapp/app/styles/app.css:888
- `.pell-content` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — webapp/app/styles/app.css:1024
- `.pell-button` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — webapp/app/styles/app.css:1060
What to do
- Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
C1 · Data Protection
What to do
- Strengthen data-at-rest protection: vault your keys (AWS KMS / Secrets Manager, GCP KMS / Secret Manager, Azure Key Vault, HashiCorp Vault — not a Cloak key read from an environment variable beside the data) and encrypt the most sensitive columns (Cloak.Ecto field types) — partial coverage still leaves gaps.
C2 · Access Controls
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
- Only 1/2 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `cli`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add sobelow (Elixir/Phoenix) (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 1 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
- `package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — package.json:11
What to do
- Add a SAST step to CI running what this repository's stack ships: sobelow (Elixir/Phoenix) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- Deployment is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever reaches the release trigger goes to production unreviewed, so a mistaken merge or tag is live before anyone can stop it.
What to do
- Add 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.
P6 · Release Hygiene
P7 · Outbound HTTP resilience
- `Req.put(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×2) — lib/accent/integrations/execute/aws_s3.ex:51, lib/accent/integrations/execute/azure_storage_container.ex:18
- `Req.post(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×4) — lib/hook/outbounds/helpers/post_url.ex:41, lib/machine_translations/provider/deepl.ex:50, lib/machine_translations/provider/google_translate.ex:144, …
- `Req.new(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — lib/utils/http_client.ex:9
What to do
- Set an explicit timeout on every client — `recv_timeout:` for HTTPoison, `receive_timeout:` for Req and Finch, `Tesla.Middleware.Timeout` (or the adapter's `recv_timeout`) for Tesla, `timeout:` for `:httpc` — and add retries with back-off (`Tesla.Middleware.Retry`, Req's `retry:`) and a breaker (`:fuse`, `ExternalService`) around dependencies that fail.
PF3 · Async & latency hygiene
- `fs.existsSync` in `init` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — cli/src/base.ts:35
- `fs.statSync` in `init` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — cli/src/base.ts:36
- `fs.existsSync` in `run` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — cli/src/commands/format.ts:47, cli/src/commands/lint.ts:34
- `fs.readFileSync` in `run` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — cli/src/commands/format.ts:48, cli/src/commands/format.ts:50
- `existsSync` in `callback to targets.filter` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — cli/src/commands/sync.ts:176
- `execSync` in `callback to hooks.forEach` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:26
What to do
- TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.
R1 · Type Safety
R10 · Code Duplication
- 7 duplicated blocks under webapp/app/controllers/logged-in/project/ have copies in at least two of the sibling directories edit, files, revision, translation, versions — 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. — webapp/app/controllers/logged-in/project/files/jipt.ts:10
- 5 duplicated blocks under webapp/app/routes/logged-in/ have copies in at least two of the sibling directories jipt, project, projects — 3 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 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 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 5 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. — webapp/app/routes/logged-in/jipt/index.ts:12
- webapp/app/controllers/logged-in/project/files/export-all.ts:1 · webapp/app/controllers/logged-in/project/files/export.ts:1 — these 2 files are line-for-line copies of one another — 67 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — webapp/app/controllers/logged-in/project/files/export-all.ts:1
- webapp/app/controllers/logged-in/project/edit/prompts/edit.ts:18 · webapp/app/controllers/logged-in/project/edit/prompts/new.ts:30 — the two spans are one implementation copied and then locally edited — 280 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. — webapp/app/controllers/logged-in/project/edit/prompts/edit.ts:18
- webapp/app/controllers/logged-in/project/files/jipt.ts:10 · webapp/app/controllers/logged-in/project/versions/export.ts:10 — the two spans are one implementation copied and then locally edited — 346 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. — webapp/app/controllers/logged-in/project/files/jipt.ts:10
- webapp/app/controllers/logged-in/jipt/translation/index.ts:1 · webapp/app/controllers/logged-in/project/translation/index.ts:1 — these 2 files are line-for-line copies of one another — 63 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — webapp/app/controllers/logged-in/jipt/translation/index.ts:1
- webapp/app/routes/logged-in/project/conflicts.ts:14 · webapp/app/routes/logged-in/project/revision/translations.ts:14 — 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. — webapp/app/routes/logged-in/project/conflicts.ts:14
- webapp/app/controllers/logged-in/project/edit/machine-translations.ts:21 · webapp/app/controllers/logged-in/project/edit/prompts.ts:34 — 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. — webapp/app/controllers/logged-in/project/edit/machine-translations.ts:21
- webapp/app/routes/logged-in/project/files.ts:34 · webapp/app/routes/logged-in/project/versions.ts:27 — 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. — webapp/app/routes/logged-in/project/files.ts:34
- webapp/app/routes/logged-in/project/edit/api-token.ts:11 · webapp/app/routes/logged-in/project/edit/prompts.ts:11 — 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. — webapp/app/routes/logged-in/project/edit/api-token.ts:11
- webapp/app/controllers/logged-in/project/versions/edit.ts:59 · webapp/app/controllers/logged-in/project/versions/new.ts:45 — 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. — webapp/app/controllers/logged-in/project/versions/edit.ts:59
- webapp/app/controllers/logged-in/project/files.ts:20 · webapp/app/controllers/logged-in/project/versions.ts:15 — 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. — webapp/app/controllers/logged-in/project/files.ts:20
- webapp/app/routes/logged-in/project/files/export-all.ts:7 · webapp/app/routes/logged-in/project/files/export.ts:7 — 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. — webapp/app/routes/logged-in/project/files/export-all.ts:7
- webapp/app/controllers/logged-in/project/collaborators.ts:91 · webapp/app/controllers/logged-in/project/edit/api-token.ts:87 — 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. — webapp/app/controllers/logged-in/project/collaborators.ts:91
- webapp/app/controllers/logged-in/project/comments.ts:48 · webapp/app/controllers/logged-in/project/translation/comments.ts:69 — 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. — webapp/app/controllers/logged-in/project/comments.ts:48
- webapp/app/routes/logged-in/project/activity.ts:21 · webapp/app/routes/logged-in/project/edit/lint-entries.ts:27 — 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. — webapp/app/routes/logged-in/project/activity.ts:21
- webapp/app/routes/logged-in/project/collaborators.ts:21 · webapp/app/routes/logged-in/project/edit/badges.ts:21 · webapp/app/routes/logged-in/project/edit/index.ts:21 · webapp/app/routes/logged-in/project/service-integrations.ts:21 — 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. — webapp/app/routes/logged-in/project/collaborators.ts:21
- webapp/app/routes/logged-in/project/comments.ts:40 · webapp/app/routes/logged-in/project/integration-executions.ts:51 — 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. — webapp/app/routes/logged-in/project/comments.ts:40
- webapp/app/routes/logged-in/project/conflicts.ts:89 · webapp/app/routes/logged-in/project/revision/translations.ts:87 — 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. — webapp/app/routes/logged-in/project/conflicts.ts:89
- webapp/app/controllers/logged-in/project/files/add-translations.ts:78 · webapp/app/controllers/logged-in/project/files/new-sync.ts:61 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — webapp/app/controllers/logged-in/project/files/add-translations.ts:78
- webapp/app/routes/logged-in/project/activities.ts:53 · webapp/app/routes/logged-in/project/translation.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. — webapp/app/routes/logged-in/project/activities.ts:53
- webapp/app/routes/logged-in/project/comments.ts:12 · webapp/app/routes/logged-in/project/translation/comments.ts:13 — 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. — webapp/app/routes/logged-in/project/comments.ts:12
- webapp/app/routes/logged-in/project/edit/lint-entries.ts:12 · webapp/app/routes/logged-in/project/translation/activities.ts:13 — 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. — webapp/app/routes/logged-in/project/edit/lint-entries.ts:12
- webapp/app/controllers/logged-in/project/files/new-sync.ts:66 · webapp/app/controllers/logged-in/project/files/new-sync.ts:100 — 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. — webapp/app/controllers/logged-in/project/files/new-sync.ts:66
- webapp/app/controllers/logged-in/project/index.ts:108 · webapp/app/controllers/logged-in/project/index.ts:131 — 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. — webapp/app/controllers/logged-in/project/index.ts:108
- cli/src/services/document.ts:97 · cli/src/services/document.ts:132 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — cli/src/services/document.ts:97
- webapp/app/controllers/logged-in/project/files/add-translations.ts:136 · webapp/app/controllers/logged-in/project/files/new-sync.ts:120 · webapp/app/controllers/logged-in/project/files/sync.ts:133 — the 3 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — webapp/app/controllers/logged-in/project/files/add-translations.ts:136
- webapp/app/controllers/logged-in/project/files/sync.ts:82 · webapp/app/controllers/logged-in/project/files/sync.ts:114 — 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. — webapp/app/controllers/logged-in/project/files/sync.ts:82
- webapp/app/routes/logged-in/jipt/index.ts:12 · webapp/app/routes/logged-in/project/activities.ts:13 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — webapp/app/routes/logged-in/jipt/index.ts:12
- webapp/app/routes/logged-in/jipt/translation.ts:11 · webapp/app/routes/logged-in/project/translation.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. — webapp/app/routes/logged-in/jipt/translation.ts:11
- webapp/app/routes/logged-in/project/revision/translations.ts:68 · webapp/app/routes/logged-in/project/translation/editions.ts:27 — 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. — webapp/app/routes/logged-in/project/revision/translations.ts:68
- cli/src/commands/export.ts:36 · cli/src/commands/sync.ts:121 — 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. — cli/src/commands/export.ts:36
- webapp/app/controllers/logged-in/project/translation/editions.ts:47 · webapp/app/controllers/logged-in/project/translation/index.ts:108 — 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. — webapp/app/controllers/logged-in/project/translation/editions.ts:47
- webapp/app/controllers/logged-in/project/conflicts.ts:125 · webapp/app/controllers/logged-in/project/conflicts.ts:144 · webapp/app/controllers/logged-in/project/conflicts.ts:163 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. — webapp/app/controllers/logged-in/project/conflicts.ts:125
- webapp/app/controllers/logged-in/project/translation/index.ts:27 · webapp/app/controllers/logged-in/project/translation/settings.ts:15 — 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. — webapp/app/controllers/logged-in/project/translation/index.ts:27
- webapp/app/routes/logged-in/project/activities.ts:77 · webapp/app/routes/logged-in/project/edit/lint-entries.ts:43 — 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. — webapp/app/routes/logged-in/project/activities.ts:77
- webapp/app/controllers/logged-in/project/conflicts.ts:185 · webapp/app/controllers/logged-in/project/revision/translations.ts:119 — 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. — webapp/app/controllers/logged-in/project/conflicts.ts:185
- webapp/app/controllers/logged-in/project/edit/prompts.ts:133 · webapp/app/controllers/logged-in/project/edit/prompts/new.ts:95 — 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. — webapp/app/controllers/logged-in/project/edit/prompts.ts:133
- webapp/app/routes/logged-in/project/files/add-translations.ts:4 · webapp/app/routes/logged-in/project/files/sync.ts:4 — 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. — webapp/app/routes/logged-in/project/files/add-translations.ts:4
- cli/src/commands/format.ts:33 · cli/src/commands/lint.ts:21 — 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. — cli/src/commands/format.ts:33
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
- webapp/ember-cli-build.js:5 imports ember-cli/lib/broccoli/ember-app, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — webapp/ember-cli-build.js:5
What to do
- Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
R2 · Cyclomatic Complexity
- run has cyclomatic complexity 12 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — cli/src/commands/sync.ts:76
- matchText has cyclomatic complexity 11 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — jipt/src/mutation/live-node.ts:48
R3 · Large Files
R4 · Test Coverage
- No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×40) — cli/src/services/document.ts:1, cli/src/services/formatters/project-stats.ts:1, cli/src/commands/sync.ts:1, …
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness
R6 · Tooling
R7 · Dead Code
- 1 file(s) (~159 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package.
- Unreachable from the 222 application, 21 tooling and 14 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 (222 application, 21 tooling, 14 test roots considered), but 5 in-repo import(s) from 5 other file(s) do name it (cli/src/commands/sync.ts, cli/src/services/config.ts, cli/src/services/document-jipt-paths-fetcher.ts and 2 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 — cli/src/services/document.ts
- no import path from any entry point (222 application, 21 tooling, 14 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (cli/src/commands/stats.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 — cli/src/services/formatters/project-stats.ts
- no import path from any entry point (222 application, 21 tooling, 14 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 (×9) — cli/src/commands/sync.ts, cli/src/commands/stats.ts, cli/src/commands/export.ts, …
- no import path from any entry point (222 application, 21 tooling, 14 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (cli/src/commands/sync.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 (×3) — cli/src/services/formatters/commit-operation.ts, cli/src/services/formatters/project-sync.ts, cli/src/services/formatters/project-add-translations.ts
- no import path from any entry point (222 application, 21 tooling, 14 test roots considered), but 9 in-repo import(s) from 6 other file(s) do name it (cli/src/commands/export.ts, cli/src/commands/format.ts, cli/src/commands/jipt.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 — cli/src/base.ts
- no import path from any entry point (222 application, 21 tooling, 14 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (cli/src/base.ts, cli/src/commands/stats.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 — cli/src/services/project-fetcher.ts
- no import path from any entry point (222 application, 21 tooling, 14 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (cli/src/commands/lint.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 — cli/src/services/formatters/project-lint.ts
- no import path from any entry point (222 application, 21 tooling, 14 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (cli/src/base.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 — cli/src/services/config.ts
- no import path from any entry point (222 application, 21 tooling, 14 test roots considered), but 9 in-repo import(s) from 9 other file(s) do name it (cli/src/services/formatters/commit-operation.ts, cli/src/services/formatters/document-export.ts, cli/src/services/formatters/document-format.ts and 6 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 — cli/src/services/formatters/base.ts
- no import path from any entry point (222 application, 21 tooling, 14 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (cli/src/services/formatters/document-format.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 — cli/src/commands/format.ts
- no import path from any entry point (222 application, 21 tooling, 14 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (cli/src/commands/export.ts, cli/src/commands/jipt.ts, cli/src/commands/sync.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 (×3) — REDACTED, cli/src/services/formatters/document-export.ts, cli/src/services/formatters/project-export.ts
- no import path from any entry point (222 application, 21 tooling, 14 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (cli/src/commands/format.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 — cli/src/services/formatters/document-format.ts
- no import path from any entry point (222 application, 21 tooling, 14 test roots considered), but 7 in-repo import(s) from 7 other file(s) do name it (cli/src/commands/export.ts, cli/src/commands/jipt.ts, cli/src/commands/sync.ts and 4 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 — cli/src/types/document-config.ts
- no import path from any entry point (222 application, 21 tooling, 14 test roots considered), but 5 in-repo import(s) from 5 other file(s) do name it (cli/src/commands/export.ts, cli/src/commands/format.ts, cli/src/commands/lint.ts and 2 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 — cli/src/services/document-paths-fetcher.ts
- no import path from any entry point (222 application, 21 tooling, 14 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (REDACTED) — 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 — cli/src/services/formatters/hook-runner.ts
- no import path from any entry point (222 application, 21 tooling, 14 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (cli/src/commands/jipt.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 — cli/src/services/document-jipt-paths-fetcher.ts
- no import path from any entry point (222 application, 21 tooling, 14 test roots considered), but 7 in-repo import(s) from 7 other file(s) do name it (cli/src/commands/sync.ts, cli/src/services/document-paths-fetcher.ts, cli/src/services/document.ts and 4 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 — cli/src/services/revision-slug-fetcher.ts
- no import path from any entry point (222 application, 21 tooling, 14 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (cli/src/services/document.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 (×2) — cli/src/services/tree.ts, cli/src/types/operation-response.ts
- no import path from any entry point (222 application, 21 tooling, 14 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (cli/src/services/config.ts, cli/src/services/document.ts, cli/src/services/formatters/project-stats.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 — cli/src/services/git-branch-fetcher.ts
- no import path from any entry point (222 application, 21 tooling, 14 test roots considered), but 4 in-repo import(s) from 4 other file(s) do name it (cli/src/services/config.ts, cli/src/services/document.ts, cli/src/services/formatters/project-stats.ts and 1 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 — cli/src/types/config.ts
- no import path from any entry point (222 application, 21 tooling, 14 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (cli/src/commands/lint.ts, cli/src/services/formatters/project-lint.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 — cli/src/types/lint-translation.ts
- no import path from any entry point (222 application, 21 tooling, 14 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (cli/src/commands/sync.ts, cli/src/services/formatters/commit-operation.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 — cli/src/types/operation.ts
- no import path from any entry point (222 application, 21 tooling, 14 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (cli/src/services/document-jipt-paths-fetcher.ts, cli/src/services/document-paths-fetcher.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 — cli/src/types/document-path.ts
- no import path from any entry point (222 application, 21 tooling, 14 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (cli/src/types/config.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 — cli/src/types/version-config.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
- Imported but not declared in any reachable package.json — installs work only by hoisting accident. — webapp/app/services/raven.js:1
- Declared in cli/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. (×5)
- Declared in webapp/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. (×21)
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
- `verify: :verify_none` is set on a TLS client, so every peer certificate is accepted — including one an attacker presents. Chain, expiry, revocation and hostname are all skipped, so an attacker on the network path can present any certificate and read or rewrite the traffic — the connection is encrypted to the attacker, not to the intended host. Remove the override so the peer is verified — `verify: :verify_peer` is what `:ssl`, Mint, Finch, Req and hackney use when nothing is set (OTP 26 and later default to it). Give it the trust roots to check against: `cacerts: :public_key.cacerts_get()` (OTP 25+) or the `CAStore` package's `cacertfile: CAStore.file_path()`, with `customize_hostname_check: [match_fun: :public_key.pkix_verify_hostname_match_fun(:https)]` so the hostname is checked too. If the server presents a self-signed or privately-issued certificate, trust THAT issuer rather than every certificate: pass its CA as `cacertfile:`/`cacerts:`, which keeps the chain and hostname checks on. — config/runtime.exs:54
- MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`:crypto.hash(:sha256, data)`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call. (×2) — lib/hook/events.ex:5, lib/hook/events.ex:22
What to do
- Stop accepting every TLS certificate: delete `verify: :verify_none` (hackney's `insecure: true`, a `verify_fun` that answers `{:valid, _}`, a `match_fun` that returns `true`) so the chain, hostname and expiry are verified, and trust a self-signed or private server by giving the client its CA (`cacertfile:`, `cacerts:`) — never by switching verification off.
- Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key. This repository constructs a collision-broken hash (MD5/SHA1) at 2 sites, not one: `lib/hook/events.ex:5` (:erlang.md5), `lib/hook/events.ex:22` (:erlang.md5). Each is a separate decision — fixing only the line this row cites leaves the others in place.
X5 · Nullable reference types
- 3/4 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.
- ~1.4 `!` null assertions per 1k TypeScript source lines — 21 assertion(s) across the 14714 source line(s) of the 257 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: cli/src/commands/sync.ts (9), cli/src/commands/stats.ts (5), cli/src/base.ts (1). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
What to do
- The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC1 · Text alternatives | 1.1.1, 1.2.2, 1.2.5 | Partial signal |
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 77% | Strong | Strongest area. |
| Architecture | 85% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 65% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 23% | Critical — gated by R4, R8, P3, P5, P7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 60% | Adequate — gated by D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 59% | Adequate — gated by AC3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 60% | Adequate | Acceptable, with room to improve. |
Unscored — 3 check(s) recorded observations but carry no score
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- X10 Duplicated predicate — 7 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X6 Hand-rolled structured-format parsing — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 control(s) we could not find positive evidence for
- C3 Audit Trail — Repo shows no audit-logging mechanism (an audit-log table or schema — a module, Ecto schema or migration table named for it — ExAudit, PaperTrail, AshPaperTrail or Carbonite recording each change, or a Commanded / EventStore event-sourced store beside one) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
- C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
- C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
Not included — 60 check(s) not relevant to this codebase
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
- AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
- AX1 Captive dependencies — Not applicable: the BEAM has no dependency-injection container — state lives in processes, and no process is handed an instance whose lifetime another one scopes; this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Ruby imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Kotlin code is a Spring, JSR-330 or CDI singleton bean. Elixir processes share no mutable memory — state lives in a process's own mailbox — so there is no shared object to race on. 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
- AX6 Interface segregation — AX6 reached only 44% of this repository's production lines — elixir (16,250 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- 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) — failed to solve: process "/bin/sh -c cd ./vendor/language_tool/priv/native/languagetool && ./gradlew shadowJar" did not complete successfully: exit code: 1; 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.
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Elixir, JavaScript, Kotlin, html not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D25 ADR Conformance — no ADRs to check
- 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.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (20 value object(s))
- 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 only 1 of the 3 signals this lens looks for (2 Elixir aggregate(s) emitting domain events (%Event{} from execute/2))
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- M4 Documentation accuracy — Not applicable: the 3 current-state document(s) make no claim of a kind M4 checks. 60 claim(s) of kinds M4 does not check were not checked (path 23, command argument 1, environment variable 36); M4 checks only links and versions and artefact counts.
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage data present for 44 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for Benchee jobs (the entries of a `Benchee.run` job map) or Benchfella `bench "…"` blocks under `use Benchfella` in any `.ex`/`.exs` file, or benchee or benchfella in a mix.exs, 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.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X1 Async correctness — X1 reached only 44% of this repository's production lines — elixir (16,250 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X12 Unreachable branch — X12 reached only 44% of this repository's production lines — elixir (16,250 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X16 Unfloored truncation loop — X16 reached only 44% of this repository's production lines — elixir (16,250 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — X19 reached only 44% of this repository's production lines — elixir (16,250 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X2 Cancellation propagation — X2 reached only 44% of this repository's production lines — elixir (16,250 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- 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.
- X21 Side-effecting pattern guard — X21 reached only 44% of this repository's production lines — elixir (16,250 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — X24 reached only 44% of this repository's production lines — elixir (16,250 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. Elixir processes share no heap: a value sent to another process arrives as a copy, so no collection is reachable from two processes 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 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
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — X29 reached only 44% of this repository's production lines — elixir (16,250 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X3 Exception handling — X3 reached only 44% of this repository's production lines — elixir (16,250 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score.
- 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 — 47 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
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <html> without a lang jipt/index.html:1
- <html> without a lang lib/web/templates/email_layout/index.html.eex:1
- <html> without a lang webapp/index.html:2
- REDACTED
- REDACTED
- REDACTED
- Document without a <title> jipt/index.html:1
- Document without a <title> lib/web/templates/email_layout/index.html.eex:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Unlisted import 'rsvp' webapp/app/services/raven.js:1
- TLS certificate validation disabled config/runtime.exs:54
Serious — 276 finding(s)
- No test reaches this file cli/src/services/document.ts:1
- No test reaches this file cli/src/services/formatters/project-stats.ts:1
- No test reaches this file cli/src/commands/sync.ts:1
- No test reaches this file webapp/app/controllers/logged-in/project/conflicts.ts:1
- No test reaches this file webapp/app/services/raven.js:1
- No test reaches this file webapp/app/queries/integration-executions.ts:1
- No test reaches this file webapp/app/controllers/logged-in/project/index.ts:1
- No test reaches this file webapp/app/controllers/logged-in/project/edit/prompts.ts:1
- No test reaches this file webapp/app/utils/file-saver.js:1
- No test reaches this file REDACTED:1
- No test reaches this file webapp/app/controllers/logged-in/project/revision/translations.ts:1
- No test reaches this file webapp/app/controllers/logged-in/project/files/add-translations.ts:1
- No test reaches this file webapp/app/controllers/logged-in/project/files/export.ts:1
- No test reaches this file webapp/app/controllers/logged-in/project/files/sync.ts:1
- No test reaches this file cli/src/services/formatters/commit-operation.ts:1
- No test reaches this file webapp/app/services/peeker.ts:1
- No test reaches this file webapp/app/controllers/logged-in/project/files/export-all.ts:1
- No test reaches this file webapp/app/queries/project-activities.ts:1
- No test reaches this file webapp/app/controllers/logged-in/project/manage-languages.ts:1
- No test reaches this file webapp/app/controllers/logged-in/project/service-integrations.ts:1
- No test reaches this file webapp/app/controllers/logged-in/project/files/new-sync.ts:1
- No test reaches this file webapp/app/routes/logged-in/project/revision/translations.ts:1
- No test reaches this file webapp/app/controllers/logged-in/project/edit/prompts/new.ts:1
- No test reaches this file webapp/app/queries/conflicts.ts:1
- No test reaches this file webapp/app/queries/translation.ts:1
- 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
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Sync-over-async blocking cli/src/base.ts:35
- Sync-over-async blocking cli/src/base.ts:36
- Sync-over-async blocking cli/src/commands/format.ts:47
- Sync-over-async blocking cli/src/commands/format.ts:48
- Sync-over-async blocking cli/src/commands/format.ts:50
- Sync-over-async blocking cli/src/commands/lint.ts:34
- Sync-over-async blocking cli/src/commands/sync.ts:176
- Sync-over-async blocking REDACTED:26
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Outbound HTTP without resilience lib/accent/integrations/execute/aws_s3.ex:51
- Outbound HTTP without resilience lib/accent/integrations/execute/azure_storage_container.ex:18
- Outbound HTTP without resilience lib/hook/outbounds/helpers/post_url.ex:41
- Outbound HTTP without resilience lib/machine_translations/provider/deepl.ex:50
- Outbound HTTP without resilience lib/machine_translations/provider/google_translate.ex:144
- Outbound HTTP without resilience lib/prompts/provider/open_ai.ex:61
- Outbound HTTP without resilience lib/utils/http_client.ex:9
- Page without a main landmark jipt/index.html:1
- Page without a main landmark lib/web/templates/email_layout/index.html.eex:1
- Page without a main landmark lib/web/templates/graphiql/index.html.eex:9
- Page without a main landmark webapp/index.html:2
- Edited copy of a member (8 corresponding lines) lib/movement/builders/revision_merge.ex:36
- Edited copy of a member (8 corresponding lines) lib/web/controllers/lint_controller.ex:112
- Edited copy of a member (8 corresponding lines) lib/movement/builders/new_slave.ex:71
- Edited copy of a member (8 corresponding lines) lib/web/controllers/lint_controller.ex:135
- Edited copy of a member (6 corresponding lines) lib/langue/formatter/android/serializer.ex:104
- Edited copy of a member (6 corresponding lines) lib/graphql/resolvers/document.ex:50
- Edited copy of a member (6 corresponding lines) lib/hook/outbounds/discord.ex:52
- Edited copy of a member (6 corresponding lines) lib/langue/formatter/java_properties/parser.ex:11
- Duplicated block (21 lines × 2 locations) webapp/app/controllers/logged-in/project/files/add-translations.ts:78
- Duplicated block (21 lines × 2 locations) webapp/app/routes/logged-in/project/activities.ts:53
- Duplicated block (21 lines × 2 locations) webapp/app/routes/logged-in/project/comments.ts:12
- Duplicated block (21 lines × 2 locations) webapp/app/routes/logged-in/project/edit/lint-entries.ts:12
- Duplicated block (18 lines × 2 locations) webapp/app/controllers/logged-in/project/files/sync.ts:82
- Duplicated block (18 lines × 2 locations) webapp/app/routes/logged-in/jipt/index.ts:12
- Duplicated block (18 lines × 2 locations) webapp/app/routes/logged-in/jipt/translation.ts:11
- Duplicated block (18 lines × 2 locations) webapp/app/routes/logged-in/project/revision/translations.ts:68
- Focus outline removed in CSS without a :focus replacement webapp/app/styles/app.css:888
- Focus outline removed in CSS without a :focus replacement webapp/app/styles/app.css:1024
- Focus outline removed in CSS without a :focus replacement webapp/app/styles/app.css:1060
- Edited copy of a member (14 corresponding lines) lib/web/controllers/merge_controller.ex:46
- Edited copy of a member (14 corresponding lines) lib/graphql/resolvers/project.ex:32
- Edited copy of a member (14 corresponding lines) lib/accent/schemas/operation.ex:47
- Edited copy of a member (11 corresponding lines) lib/graphql/resolvers/revision.ex:87
- Edited copy of a member (11 corresponding lines) lib/graphql/resolvers/document.ex:22
- Edited copy of a member (11 corresponding lines) lib/movement/builders/revision_correct_all.ex:13
- Duplicated block (25 lines × 2 locations) webapp/app/controllers/logged-in/project/collaborators.ts:91
- Duplicated block (25 lines × 2 locations) webapp/app/controllers/logged-in/project/comments.ts:48
- Duplicated block (25 lines × 2 locations) webapp/app/routes/logged-in/project/activity.ts:21
- Duplicated block (14 lines × 2 locations) webapp/app/controllers/logged-in/project/conflicts.ts:185
- Duplicated block (14 lines × 2 locations) webapp/app/controllers/logged-in/project/edit/prompts.ts:133
- Duplicated block (14 lines × 2 locations) webapp/app/routes/logged-in/project/files/add-translations.ts:4
- Dead file (~11 LoC) cli/src/types/config.ts
- Dead file (~11 LoC) cli/src/types/lint-translation.ts
- Dead file (~11 LoC) cli/src/types/operation.ts
- Edited copy of a member (9 corresponding lines) lib/web/controllers/peek_controller.ex:46
- Edited copy of a member (9 corresponding lines) lib/web/controllers/export_controller.ex:117
- Edited copy of a member (15 corresponding lines) lib/langue/formatter/android/parser.ex:72
- Edited copy of a member (15 corresponding lines) lib/accent/machine_translations_config/machine_translations_config_manager.ex:11
- Edited copies of one member (4 members, 9+ corresponding lines) lib/graphql/helpers/authorization.ex:31
- Edited copies of one member (4 members, 9+ corresponding lines) lib/lint/checks/double_spaces.ex:16
- Edited copy of a member (12 corresponding lines) lib/movement/builders/rollback.ex:12
- Edited copy of a member (12 corresponding lines) lib/accent/scopes/project.ex:49
- Edited copy of a member (5 corresponding lines) lib/langue/formatter/json/serializer.ex:17
- Edited copy of a member (5 corresponding lines) lib/graphql/resolvers/comment.ex:72
- Edited copy of a member (7 corresponding lines) lib/web/controllers/export_jipt_controller.ex:50
- Edited copy of a member (7 corresponding lines) lib/graphql/resolvers/collaborator.ex:44
- Duplicated block (12 lines × 2) lib/accent/telemetry_ui/telemetry_ui.ex:83
- Duplicated block (12 lines × 2) lib/movement/persisters/operations_update_all_dynamic.ex:20
- Duplicated block (6 lines × 3) lib/graphql/resolvers/machine_translations_config.ex:10
- Duplicated block (6 lines × 3) lib/graphql/resolvers/machine_translations_config.ex:22
- Duplicated block (6 lines × 2) lib/graphql/resolvers/project.ex:40
- Duplicated block (6 lines × 2) lib/movement/persisters/new_slave.ex:12
- Duplicated block (5 lines × 2) lib/movement/builders/revision_merge.ex:40
- Duplicated block (5 lines × 2) lib/accent/machine_translations_config/machine_translations_config_manager.ex:30
- Duplicated block with local edits (64 matched lines × 2 locations) webapp/app/controllers/logged-in/project/edit/prompts/edit.ts:18
- Duplicated block with local edits (64 matched lines × 2 locations) webapp/app/controllers/logged-in/project/files/jipt.ts:10
- Duplicated block (22 lines × 2 locations) webapp/app/routes/logged-in/project/comments.ts:40
- Duplicated block (22 lines × 2 locations) webapp/app/routes/logged-in/project/conflicts.ts:89
- Duplicated block (20 lines × 2 locations) webapp/app/controllers/logged-in/project/files/new-sync.ts:66
- Duplicated block (20 lines × 2 locations) webapp/app/controllers/logged-in/project/index.ts:108
- Duplicated block (17 lines × 2 locations) cli/src/commands/export.ts:36
- Duplicated block (17 lines × 2 locations) webapp/app/controllers/logged-in/project/translation/editions.ts:47
- Duplicated block (16 lines × 2 locations) webapp/app/controllers/logged-in/project/translation/index.ts:27
- Duplicated block (16 lines × 2 locations) webapp/app/routes/logged-in/project/activities.ts:77
- Dead file (~119 LoC) cli/src/base.ts
- Dead file (~119 LoC) cli/src/services/project-fetcher.ts
- Dead file (~13 LoC) cli/src/services/formatters/document-export.ts
- Dead file (~13 LoC) cli/src/services/git-branch-fetcher.ts
- Dead file (~4 LoC) cli/src/types/operation-response.ts
- Dead file (~4 LoC) cli/src/types/version-config.ts
- Weak hash algorithm lib/hook/events.ex:5
- Weak hash algorithm lib/hook/events.ex:22
- Data table has no header cells lib/web/templates/email_layout/index.html.eex:3
- fileSaver (cyclomatic 29) webapp/app/utils/file-saver.js:5
- Floating source dependency: canary
- fileSaver (cognitive 33) webapp/app/utils/file-saver.js:5
- REDACTED
- REDACTED
- TooManyFunctions: Translation lib/accent/scopes/translation.ex:1
- FunctionTooLong: file-saver.fileSaver webapp/app/utils/file-saver.js:5
- FileTooLong: telemetry_ui/telemetry_ui.ex lib/accent/telemetry_ui/telemetry_ui.ex
- Change-coupling hub: mix.exs → accent.ex, endpoint.ex, langue.ex, router.ex mix.exs
- REDACTED
- REDACTED
- REDACTED
- Members sharing a duplicated core (5 members, 50+ identical tokens) lib/accent/telemetry_ui/telemetry_ui.ex:27
- Edited copy of a member (25 corresponding lines) lib/movement/persisters/operations_update_all_dynamic.ex:12
- Edited copy of a member (23 corresponding lines) lib/graphql/resolvers/revision.ex:60
- Edited copy of a member (13 corresponding lines) lib/machine_translations/provider/deepl.ex:46
- Edited copy of a member (19 corresponding lines) lib/accent/scopes/language.ex:30
- Edited copy of a member (17 corresponding lines) lib/movement/mappers/operation.ex:30
- Edited copy of a member (16 corresponding lines) lib/movement/persisters/new_slave.ex:21
- Edited copies of one member (3 members, 10+ corresponding lines) lib/graphql/resolvers/comment.ex:58
- Edited copy of a member (10 corresponding lines) lib/movement/migration/conflict.ex:43
- Edited copies of one member (8 members, 7+ corresponding lines) lib/graphql/resolvers/api_token.ex:11
- Edited copy of a member (4 corresponding lines) lib/langue/utils/line_by_line_helper/parser.ex:27
- Edited copies of one member (3 members, 4+ corresponding lines) lib/web/controllers/merge_controller.ex:64
- Duplicated block (22–25 lines × 2) lib/accent/integrations/execute/aws_s3.ex:53
- Duplicated block (18 lines × 4) lib/accent/telemetry_ui/telemetry_ui.ex:28
- Duplicated block (16 lines × 2) lib/accent/scopes/language.ex:33
- Duplicated block (11 lines × 2) lib/accent/telemetry_ui/telemetry_ui.ex:196
- Duplicated block (9–10 lines × 6) lib/accent/telemetry_ui/telemetry_ui.ex:38
- Duplicated block (7 lines × 2) lib/graphql/resolvers/document.ex:38
- End-of-life runtime: Node.js 16 package.json:9
- Coverage collected but not gated
- No DR/backup evidence
- Duplication concentrated across 5 sibling directories (7 clone groups) webapp/app/controllers/logged-in/project/files/jipt.ts:10
- Duplication concentrated across 3 sibling directories (5 clone groups) webapp/app/routes/logged-in/jipt/index.ts:12
- Wholesale file copy (67 identical lines × 2 files) webapp/app/controllers/logged-in/project/files/export-all.ts:1
- Wholesale file copy (63 identical lines × 2 files) webapp/app/controllers/logged-in/jipt/translation/index.ts:1
- Duplicated block (56 lines × 2 locations) webapp/app/routes/logged-in/project/conflicts.ts:14
- Duplicated block (37 lines × 2 locations) webapp/app/controllers/logged-in/project/edit/machine-translations.ts:21
- Duplicated block (33 lines × 2 locations) webapp/app/routes/logged-in/project/files.ts:34
- Duplicated block (32 lines × 2 locations) webapp/app/routes/logged-in/project/edit/api-token.ts:11
- Duplicated block (30 lines × 2 locations) webapp/app/controllers/logged-in/project/versions/edit.ts:59
- Duplicated block (28 lines × 2 locations) webapp/app/controllers/logged-in/project/files.ts:20
- Duplicated block (27 lines × 2 locations) webapp/app/routes/logged-in/project/files/export-all.ts:7
- Duplicated block (23 lines × 4 locations) webapp/app/routes/logged-in/project/collaborators.ts:21
- Duplicated block (19 lines × 2 locations) cli/src/services/document.ts:97
- Duplicated block (18 lines × 3 locations) webapp/app/controllers/logged-in/project/files/add-translations.ts:136
- Duplicated block (16 lines × 3 locations) webapp/app/controllers/logged-in/project/conflicts.ts:125
- Duplicated block (13 lines × 2 locations) cli/src/commands/format.ts:33
- Boundary violation [package:third-party-deep-import] webapp/ember-cli-build.js:5
- Complex function run (cyclomatic 12, cognitive 13) cli/src/commands/sync.ts:76
- Complex function matchText (cyclomatic 11, cognitive 12) jipt/src/mutation/live-node.ts:48
- Dead file (~298 LoC) cli/src/services/document.ts
- Dead file (~251 LoC) cli/src/services/formatters/project-stats.ts
- Dead file (~223 LoC) cli/src/commands/sync.ts
- Dead file (~148 LoC) cli/src/services/formatters/commit-operation.ts
- Dead file (~116 LoC) cli/src/services/formatters/project-lint.ts
- Dead file (~99 LoC) cli/src/commands/stats.ts
- Dead file (~90 LoC) cli/src/services/config.ts
- Dead file (~77 LoC) cli/src/services/formatters/base.ts
- Dead file (~64 LoC) cli/src/commands/format.ts
- Dead file (~61 LoC) cli/src/commands/export.ts
- Dead file (~58 LoC) cli/src/commands/lint.ts
- Dead file (~56 LoC) cli/src/commands/jipt.ts
- Dead file (~44 LoC) REDACTED
- Dead file (~38 LoC) cli/src/services/formatters/document-format.ts
- Dead file (~32 LoC) cli/src/types/document-config.ts
- Dead file (~31 LoC) cli/src/services/document-paths-fetcher.ts
- Dead file (~30 LoC) cli/src/services/formatters/project-sync.ts
- Dead file (~28 LoC) cli/src/services/formatters/hook-runner.ts
- Dead file (~27 LoC) webapp/testem.js
- Dead file (~26 LoC) cli/src/services/document-jipt-paths-fetcher.ts
- Dead file (~22 LoC) webapp/ember-cli-build.js
- Dead file (~19 LoC) cli/src/services/revision-slug-fetcher.ts
- Dead file (~17 LoC) cli/src/services/formatters/project-add-translations.ts
- Dead file (~14 LoC) cli/src/services/tree.ts
- Dead file (~12 LoC) webapp/config/targets.js
- Dead file (~10 LoC) webapp/config/ember-intl.js
- Dead file (~8 LoC) cli/src/services/formatters/project-export.ts
- Dead file (~5 LoC) cli/src/types/document-path.ts
- Unused dependency '@oclif/plugin-help'
- Unused dependency '@oclif/plugin-not-found'
- Unused dependency '@oclif/plugin-version'
- Unused dependency '@oclif/plugin-warn-if-update-available'
- Unused dependency 'tslib'
- Unused dependency '@ember/optional-features'
- Unused dependency '@ember/render-modifiers'
- Unused dependency '@ember/string'
- Unused dependency '@embroider/legacy-inspector-support'
- Unused dependency 'color'
- Unused dependency 'cryptiles'
- Unused dependency 'ember-auto-import'
- Unused dependency 'ember-autoresize-modifier'
- Unused dependency 'ember-cli-babel'
- Unused dependency 'ember-cli-htmlbars'
- Unused dependency 'ember-keyboard'
- Unused dependency 'ember-page-title'
- Unused dependency 'ember-power-select'
- Unused dependency 'ember-qunit'
- Unused dependency 'ember-route-template'
- Unused dependency 'emoji-picker-element'
- Unused dependency 'highlight.js'
- Unused dependency 'markdown-it'
- Unused dependency 'pell'
- Unused dependency 'pretender'
- Unused dependency 'simple-fmt'
Minor — 23 finding(s)
- Duplicated predicate lib/movement/builders/revision_merge.ex:41
- Duplicated predicate lib/lint/checks/placeholder_count.ex:14
- Duplicated predicate lib/web/controllers/merge_controller.ex:80
- Duplicated predicate lib/movement/migration/conflict.ex:49
- Duplicated predicate lib/graphql/resolvers/lint.ex:61
- Duplicated predicate lib/accent/scopes/translation.ex:62
- Duplicated predicate webapp/app/controllers/logged-in/project/files/export.ts:109
- No ADRs found mix.exs:18
- redundant comment webapp/app/utils/file-saver.js:25
- Projects may be oversized for their cohesion
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- Logging is not universal
- No SAST
- No dependency-update automation package.json:11
- No release approval gate
- Strict null checking is not enabled everywhere the repository type-checks
- Null assertions (`!`) override strict null checking
- Hand-rolled JSON/XML parsing via regex lib/langue/formatter/java_properties_xml/parser.ex:14
Minor — 11 finding(s)
- Outdated: bamboo
- Outdated: bandit
- Outdated: dialyxir
- Outdated: ecto
- Outdated: new_relic_agent
- Outdated: phoenix
- Outdated: phoenix_html
- Outdated: phoenix_live_view
- Outdated: sentry
- Outdated: tidewave
- Outdated: tls_certificate_check
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-cca2cb56ee624ab2b953034426632c8e/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-cca2cb56ee624ab2b953034426632c8e/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 25 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 47 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 9 | 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 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |