Executive summary
loco-rs/loco falls short of our standard for production, in part because it has pages that don't say their language. It scores 51 out of 100 and is rated Adequate, and 83 of its 90 critical findings are security problems in the build pipeline and in its code.
Accessibility, at 41, is the weakest lens and counts most in the score. The best first step is adding text alternatives, worth about 6 points. Fixing the nine places where personal data leaves where it belongs comes next, worth about 2 points. Raising Accessibility to 70 would lift the score to about 58.
Fifty-nine pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Eighteen weaknesses in the code could be used by an attacker, and six pipeline steps install packages that can change without warning. Pinning each tool to an exact version, fixing the weaknesses the scanner points to and pinning what the pipeline installs would close these risks. The two pages or frames without a title need a descriptive title.
The product code is 50,989 lines, about €59,000 to rebuild.
If Accessibility rose from 41 to 70, the lowest score rated Strong, the score would rise from 51 to about 58.
New since the last survey: 18 findings
- Cognitive Complexity · LocalStore::list (cognitive 20) src/storage/drivers/local.rs
- God Classes · FileTooLong: REDACTED REDACTED
- God Classes · FileTooLong: REDACTED REDACTED
- Code Duplication · Near-duplicate member pair (38 shared lines) REDACTED
- Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) src/bgworker/redis.rs
- Code Duplication · Duplicated block (16 lines × 2) src/bgworker/mod.rs
- Code Duplication · Duplicated block (15 lines × 2) REDACTED
- Code Duplication · Duplicated block (14 lines × 2) REDACTED
- Code Duplication · Duplicated block (14 lines × 2) REDACTED
- Code Duplication · Duplicated block (12 lines × 2) REDACTED
- Code Duplication · Duplicated block (11 lines × 2) REDACTED
- Code Duplication · Duplicated block (8 lines × 2) REDACTED
- Code Duplication · Duplicated block (11 lines × 2) REDACTED
- Code Duplication · Duplicated block (5 lines × 2) REDACTED
- Code Duplication · Duplicated block (11 lines × 2) REDACTED
- Knowledge Freshness · Orphaned knowledge src/model/query/dsl/mod.rs
- Visual & motion safety · Animation without a prefers-reduced-motion guard website/src/styles/global.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard website/src/styles/starlight.css
Fixed since the last survey: 6 findings
- Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) src/bgworker/redis.rs
- Code Duplication · Duplicated block (14 lines × 2) src/scheduler.rs
- Code Duplication · Duplicated block (15 lines × 2) REDACTED
- Code Duplication · Duplicated block (12 lines × 2) REDACTED
- Code Duplication · Duplicated block (9 lines × 2) REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
Rebuild cost: about €59,000 · Estimate
| Cost to rebuild | €20,000 to €99,000, for 329 to 1,044 hours of work, about 0.4 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 51. 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: 50,989 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 — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 loco.base_template.src.models._entities.users | 2 loco.settings | 3 loco_gen.rrgen | 4 loco_rs.auth.jwt | 5 loco_rs.config.database | 6 loco_rs.config.logger | 7 loco_rs.config.mailer | 8 loco_rs.config.queue | 9 loco_rs.controller.routes | 10 loco_rs.environment | 11 loco_rs.storage.stream | 12 loco_gen | 13 loco_rs.config.auth | 14 loco_rs.controller.app_routes | 15 loco_rs.task | 16 loco_rs.config | 17 loco_rs.storage.drivers | 18 loco_rs.bgworker | 19 loco_rs.cli | 20 loco_rs.storage | 21 loco_rs.bgworker.redis | 22 loco_rs.boot | 23 loco_rs.storage.strategies | 24 loco_rs.app | 25 loco_rs.bgworker.sql | 26 loco_rs.storage.strategies.replicated | 27 loco_rs.storage.strategies.single | 28 loco_rs.auth.cookies | 29 loco_rs.bgworker.pg | 30 loco_rs.bgworker.sqlt | 31 loco_rs.controller.extractor.auth | 32 loco_rs.controller.middleware | 33 loco_rs.evals.tasks.api-key-endpoint.wiring.src.app | 34 loco_rs.evals.tasks.cached-stats.wiring.src.app | 35 loco_rs.evals.tasks.nightly-digest.wiring.src.app | 36 loco_rs.evals.tasks.purge-unverified.wiring.src.app | 37 loco_rs.evals.tasks.typed-errors.wiring.src.app | 38 loco_rs.evals.tasks.user-search.wiring.src.app | 39 loco_rs.auth.oauth | 40 loco_rs.controller.middleware.logger |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 loco.base_template.src.models._entities.users | ||||||||||||||||||||||||||||||||||||||||
| 2 loco.settings | ||||||||||||||||||||||||||||||||||||||||
| 3 loco_gen.rrgen | ||||||||||||||||||||||||||||||||||||||||
| 4 loco_rs.auth.jwt | ||||||||||||||||||||||||||||||||||||||||
| 5 loco_rs.config.database | ||||||||||||||||||||||||||||||||||||||||
| 6 loco_rs.config.logger | ||||||||||||||||||||||||||||||||||||||||
| 7 loco_rs.config.mailer | ||||||||||||||||||||||||||||||||||||||||
| 8 loco_rs.config.queue | ||||||||||||||||||||||||||||||||||||||||
| 9 loco_rs.controller.routes | ||||||||||||||||||||||||||||||||||||||||
| 10 loco_rs.environment | ||||||||||||||||||||||||||||||||||||||||
| 11 loco_rs.storage.stream | ||||||||||||||||||||||||||||||||||||||||
| 12 loco_gen | 2 | |||||||||||||||||||||||||||||||||||||||
| 13 loco_rs.config.auth | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 loco_rs.controller.app_routes | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 15 loco_rs.task | 2 | |||||||||||||||||||||||||||||||||||||||
| 16 loco_rs.config | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 17 loco_rs.storage.drivers | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 18 loco_rs.bgworker | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 19 loco_rs.cli | 1 | 1 | 3 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 20 loco_rs.storage | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 21 loco_rs.bgworker.redis | 2 | 1 | 4 | |||||||||||||||||||||||||||||||||||||
| 22 loco_rs.boot | 1 | 1 | 1 | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||
| 23 loco_rs.storage.strategies | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 24 loco_rs.app | 3 | 1 | 1 | 3 | 3 | 2 | 3 | |||||||||||||||||||||||||||||||||
| 25 loco_rs.bgworker.sql | 2 | 2 | 3 | 1 | ||||||||||||||||||||||||||||||||||||
| 26 loco_rs.storage.strategies.replicated | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 27 loco_rs.storage.strategies.single | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 28 loco_rs.auth.cookies | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 29 loco_rs.bgworker.pg | 1 | 2 | 4 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 30 loco_rs.bgworker.sqlt | 1 | 2 | 4 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 31 loco_rs.controller.extractor.auth | 2 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 32 loco_rs.controller.middleware | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 33 loco_rs.evals.tasks.api-key-endpoint.wiring.src.app | 1 | 1 | 1 | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||
| 34 loco_rs.evals.tasks.cached-stats.wiring.src.app | 1 | 1 | 1 | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||
| 35 loco_rs.evals.tasks.nightly-digest.wiring.src.app | 1 | 1 | 1 | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||
| 36 loco_rs.evals.tasks.purge-unverified.wiring.src.app | 1 | 1 | 1 | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||
| 37 loco_rs.evals.tasks.typed-errors.wiring.src.app | 1 | 1 | 1 | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||
| 38 loco_rs.evals.tasks.user-search.wiring.src.app | 1 | 1 | 1 | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||
| 39 loco_rs.auth.oauth | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 40 loco_rs.controller.middleware.logger | 2 | 2 | 1 |
12→3 loco_gen uses loco_gen.rrgen✕
- Connections
- 2 pairs of types, where a type in loco_gen uses a type in loco_gen.rrgen.
- The types involved
loco_gen.GenerateResults→loco_gen.rrgen.GenResultloco_gen.loco_gen$module→loco_gen.rrgen.RRgen
- Direction
- loco_gen uses loco_gen.rrgen, so a change to loco_gen.rrgen can break loco_gen, while a change to loco_gen can't break loco_gen.rrgen.
- Position
- Below the diagonal: loco_gen uses a module listed above it, which is the healthy direction.
13→4 loco_rs.config.auth uses loco_rs.auth.jwt✕
- Connections
- 1 pair of types, where a type in loco_rs.config.auth uses a type in loco_rs.auth.jwt.
- The types involved
loco_rs.config.auth.Auth→loco_rs.auth.jwt.JWT
- Direction
- loco_rs.config.auth uses loco_rs.auth.jwt, so a change to loco_rs.auth.jwt can break loco_rs.config.auth, while a change to loco_rs.config.auth can't break loco_rs.auth.jwt.
- Position
- Below the diagonal: loco_rs.config.auth uses a module listed above it, which is the healthy direction.
14→9 loco_rs.controller.app_routes uses loco_rs.controller.routes✕
- Connections
- 1 pair of types, where a type in loco_rs.controller.app_routes uses a type in loco_rs.controller.routes.
- The types involved
loco_rs.controller.app_routes.AppRoutes→loco_rs.controller.routes.Routes
- Direction
- loco_rs.controller.app_routes uses loco_rs.controller.routes, so a change to loco_rs.controller.routes can break loco_rs.controller.app_routes, while a change to loco_rs.controller.app_routes can't break loco_rs.controller.routes.
- Position
- Below the diagonal: loco_rs.controller.app_routes uses a module listed above it, which is the healthy direction.
14→24 loco_rs.controller.app_routes uses loco_rs.app part of a loop✕
- Connections
- 1 pair of types, where a type in loco_rs.controller.app_routes uses a type in loco_rs.app.
- The types involved
loco_rs.controller.app_routes.AppRoutes→loco_rs.app.AppContext
- Direction
- loco_rs.controller.app_routes uses loco_rs.app, so a change to loco_rs.app can break loco_rs.controller.app_routes, while a change to loco_rs.controller.app_routes can't break loco_rs.app.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→24 loco_rs.task uses loco_rs.app part of a loop✕
- Connections
- 2 pairs of types, where a type in loco_rs.task uses a type in loco_rs.app.
- The types involved
loco_rs.task.Task→loco_rs.app.AppContextloco_rs.task.Tasks→loco_rs.app.AppContext
- Direction
- loco_rs.task uses loco_rs.app, so a change to loco_rs.app can break loco_rs.task, while a change to loco_rs.task can't break loco_rs.app.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→2 loco_rs.config uses loco.settings✕
- Connections
- 1 pair of types, where a type in loco_rs.config uses a type in loco.settings.
- The types involved
loco_rs.config.Config→loco.settings.Initializers
- Direction
- loco_rs.config uses loco.settings, so a change to loco.settings can break loco_rs.config, while a change to loco_rs.config can't break loco.settings.
- Position
- Below the diagonal: loco_rs.config uses a module listed above it, which is the healthy direction.
16→5 loco_rs.config uses loco_rs.config.database✕
- Connections
- 1 pair of types, where a type in loco_rs.config uses a type in loco_rs.config.database.
- The types involved
loco_rs.config.Config→loco_rs.config.database.Database
- Direction
- loco_rs.config uses loco_rs.config.database, so a change to loco_rs.config.database can break loco_rs.config, while a change to loco_rs.config can't break loco_rs.config.database.
- Position
- Below the diagonal: loco_rs.config uses a module listed above it, which is the healthy direction.
16→6 loco_rs.config uses loco_rs.config.logger✕
- Connections
- 1 pair of types, where a type in loco_rs.config uses a type in loco_rs.config.logger.
- The types involved
loco_rs.config.Config→loco_rs.config.logger.Logger
- Direction
- loco_rs.config uses loco_rs.config.logger, so a change to loco_rs.config.logger can break loco_rs.config, while a change to loco_rs.config can't break loco_rs.config.logger.
- Position
- Below the diagonal: loco_rs.config uses a module listed above it, which is the healthy direction.
16→7 loco_rs.config uses loco_rs.config.mailer✕
- Connections
- 1 pair of types, where a type in loco_rs.config uses a type in loco_rs.config.mailer.
- The types involved
loco_rs.config.Config→loco_rs.config.mailer.Mailer
- Direction
- loco_rs.config uses loco_rs.config.mailer, so a change to loco_rs.config.mailer can break loco_rs.config, while a change to loco_rs.config can't break loco_rs.config.mailer.
- Position
- Below the diagonal: loco_rs.config uses a module listed above it, which is the healthy direction.
16→8 loco_rs.config uses loco_rs.config.queue✕
- Connections
- 1 pair of types, where a type in loco_rs.config uses a type in loco_rs.config.queue.
- The types involved
loco_rs.config.Config→loco_rs.config.queue.QueueConfig
- Direction
- loco_rs.config uses loco_rs.config.queue, so a change to loco_rs.config.queue can break loco_rs.config, while a change to loco_rs.config can't break loco_rs.config.queue.
- Position
- Below the diagonal: loco_rs.config uses a module listed above it, which is the healthy direction.
16→10 loco_rs.config uses loco_rs.environment✕
- Connections
- 1 pair of types, where a type in loco_rs.config uses a type in loco_rs.environment.
- The types involved
loco_rs.config.Config→loco_rs.environment.Environment
- Direction
- loco_rs.config uses loco_rs.environment, so a change to loco_rs.environment can break loco_rs.config, while a change to loco_rs.config can't break loco_rs.environment.
- Position
- Below the diagonal: loco_rs.config uses a module listed above it, which is the healthy direction.
16→13 loco_rs.config uses loco_rs.config.auth✕
- Connections
- 1 pair of types, where a type in loco_rs.config uses a type in loco_rs.config.auth.
- The types involved
loco_rs.config.Config→loco_rs.config.auth.Auth
- Direction
- loco_rs.config uses loco_rs.config.auth, so a change to loco_rs.config.auth can break loco_rs.config, while a change to loco_rs.config can't break loco_rs.config.auth.
- Position
- Below the diagonal: loco_rs.config uses a module listed above it, which is the healthy direction.
17→11 loco_rs.storage.drivers uses loco_rs.storage.stream✕
- Connections
- 1 pair of types, where a type in loco_rs.storage.drivers uses a type in loco_rs.storage.stream.
- The types involved
loco_rs.storage.drivers.StoreDriver→loco_rs.storage.stream.BytesStream
- Direction
- loco_rs.storage.drivers uses loco_rs.storage.stream, so a change to loco_rs.storage.stream can break loco_rs.storage.drivers, while a change to loco_rs.storage.drivers can't break loco_rs.storage.stream.
- Position
- Below the diagonal: loco_rs.storage.drivers uses a module listed above it, which is the healthy direction.
17→12 loco_rs.storage.drivers uses loco_gen✕
- Connections
- 1 pair of types, where a type in loco_rs.storage.drivers uses a type in loco_gen.
- The types involved
loco_rs.storage.drivers.drivers$module→loco_gen.Error
- Direction
- loco_rs.storage.drivers uses loco_gen, so a change to loco_gen can break loco_rs.storage.drivers, while a change to loco_rs.storage.drivers can't break loco_gen.
- Position
- Below the diagonal: loco_rs.storage.drivers uses a module listed above it, which is the healthy direction.
18→8 loco_rs.bgworker uses loco_rs.config.queue✕
- Connections
- 1 pair of types, where a type in loco_rs.bgworker uses a type in loco_rs.config.queue.
- The types involved
loco_rs.bgworker.bgworker$module→loco_rs.config.queue.QueueConfig
- Direction
- loco_rs.bgworker uses loco_rs.config.queue, so a change to loco_rs.config.queue can break loco_rs.bgworker, while a change to loco_rs.bgworker can't break loco_rs.config.queue.
- Position
- Below the diagonal: loco_rs.bgworker uses a module listed above it, which is the healthy direction.
18→16 loco_rs.bgworker uses loco_rs.config✕
- Connections
- 1 pair of types, where a type in loco_rs.bgworker uses a type in loco_rs.config.
- The types involved
loco_rs.bgworker.bgworker$module→loco_rs.config.Config
- Direction
- loco_rs.bgworker uses loco_rs.config, so a change to loco_rs.config can break loco_rs.bgworker, while a change to loco_rs.bgworker can't break loco_rs.config.
- Position
- Below the diagonal: loco_rs.bgworker uses a module listed above it, which is the healthy direction.
18→24 loco_rs.bgworker uses loco_rs.app part of a loop✕
- Connections
- 1 pair of types, where a type in loco_rs.bgworker uses a type in loco_rs.app.
- The types involved
loco_rs.bgworker.BackgroundWorker→loco_rs.app.AppContext
- Direction
- loco_rs.bgworker uses loco_rs.app, so a change to loco_rs.app can break loco_rs.bgworker, while a change to loco_rs.bgworker can't break loco_rs.app.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→10 loco_rs.cli uses loco_rs.environment✕
- Connections
- 1 pair of types, where a type in loco_rs.cli uses a type in loco_rs.environment.
- The types involved
loco_rs.cli.cli$module→loco_rs.environment.Environment
- Direction
- loco_rs.cli uses loco_rs.environment, so a change to loco_rs.environment can break loco_rs.cli, while a change to loco_rs.cli can't break loco_rs.environment.
- Position
- Below the diagonal: loco_rs.cli uses a module listed above it, which is the healthy direction.
19→12 loco_rs.cli uses loco_gen✕
- Connections
- 1 pair of types, where a type in loco_rs.cli uses a type in loco_gen.
- The types involved
loco_rs.cli.DeploymentKind→loco_gen.Component
- Direction
- loco_rs.cli uses loco_gen, so a change to loco_gen can break loco_rs.cli, while a change to loco_rs.cli can't break loco_gen.
- Position
- Below the diagonal: loco_rs.cli uses a module listed above it, which is the healthy direction.
19→16 loco_rs.cli uses loco_rs.config✕
- Connections
- 3 pairs of types, where a type in loco_rs.cli uses a type in loco_rs.config.
- The types involved
loco_rs.cli.ComponentArg→loco_rs.config.Configloco_rs.cli.DeploymentKind→loco_rs.config.Configloco_rs.cli.cli$module→loco_rs.config.Config
- Direction
- loco_rs.cli uses loco_rs.config, so a change to loco_rs.config can break loco_rs.cli, while a change to loco_rs.cli can't break loco_rs.config.
- Position
- Below the diagonal: loco_rs.cli uses a module listed above it, which is the healthy direction.
19→22 loco_rs.cli uses loco_rs.boot part of a loop✕
- Connections
- 1 pair of types, where a type in loco_rs.cli uses a type in loco_rs.boot.
- The types involved
loco_rs.cli.cli$module→loco_rs.boot.StartMode
- Direction
- loco_rs.cli uses loco_rs.boot, so a change to loco_rs.boot can break loco_rs.cli, while a change to loco_rs.cli can't break loco_rs.boot.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→24 loco_rs.cli uses loco_rs.app part of a loop✕
- Connections
- 1 pair of types, where a type in loco_rs.cli uses a type in loco_rs.app.
- The types involved
loco_rs.cli.cli$module→loco_rs.app.AppContext
- Direction
- loco_rs.cli uses loco_rs.app, so a change to loco_rs.app can break loco_rs.cli, while a change to loco_rs.cli can't break loco_rs.app.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→11 loco_rs.storage uses loco_rs.storage.stream✕
- Connections
- 1 pair of types, where a type in loco_rs.storage uses a type in loco_rs.storage.stream.
- The types involved
loco_rs.storage.Storage→loco_rs.storage.stream.BytesStream
- Direction
- loco_rs.storage uses loco_rs.storage.stream, so a change to loco_rs.storage.stream can break loco_rs.storage, while a change to loco_rs.storage can't break loco_rs.storage.stream.
- Position
- Below the diagonal: loco_rs.storage uses a module listed above it, which is the healthy direction.
20→12 loco_rs.storage uses loco_gen✕
- Connections
- 1 pair of types, where a type in loco_rs.storage uses a type in loco_gen.
- The types involved
loco_rs.storage.StorageError→loco_gen.Error
- Direction
- loco_rs.storage uses loco_gen, so a change to loco_gen can break loco_rs.storage, while a change to loco_rs.storage can't break loco_gen.
- Position
- Below the diagonal: loco_rs.storage uses a module listed above it, which is the healthy direction.
20→17 loco_rs.storage uses loco_rs.storage.drivers✕
- Connections
- 1 pair of types, where a type in loco_rs.storage uses a type in loco_rs.storage.drivers.
- The types involved
loco_rs.storage.Storage→loco_rs.storage.drivers.PresignPutOptions
- Direction
- loco_rs.storage uses loco_rs.storage.drivers, so a change to loco_rs.storage.drivers can break loco_rs.storage, while a change to loco_rs.storage can't break loco_rs.storage.drivers.
- Position
- Below the diagonal: loco_rs.storage uses a module listed above it, which is the healthy direction.
21→8 loco_rs.bgworker.redis uses loco_rs.config.queue✕
- Connections
- 2 pairs of types, where a type in loco_rs.bgworker.redis uses a type in loco_rs.config.queue.
- The types involved
loco_rs.bgworker.redis.RunOpts→loco_rs.config.queue.ReaperConfigloco_rs.bgworker.redis.redis$module→loco_rs.config.queue.RedisQueueConfig
- Direction
- loco_rs.bgworker.redis uses loco_rs.config.queue, so a change to loco_rs.config.queue can break loco_rs.bgworker.redis, while a change to loco_rs.bgworker.redis can't break loco_rs.config.queue.
- Position
- Below the diagonal: loco_rs.bgworker.redis uses a module listed above it, which is the healthy direction.
21→12 loco_rs.bgworker.redis uses loco_gen✕
- Connections
- 1 pair of types, where a type in loco_rs.bgworker.redis uses a type in loco_gen.
- The types involved
loco_rs.bgworker.redis.redis$module→loco_gen.Error
- Direction
- loco_rs.bgworker.redis uses loco_gen, so a change to loco_gen can break loco_rs.bgworker.redis, while a change to loco_rs.bgworker.redis can't break loco_gen.
- Position
- Below the diagonal: loco_rs.bgworker.redis uses a module listed above it, which is the healthy direction.
21→18 loco_rs.bgworker.redis uses loco_rs.bgworker✕
- Connections
- 4 pairs of types, where a type in loco_rs.bgworker.redis uses a type in loco_rs.bgworker.
- The types involved
loco_rs.bgworker.redis.RedisQueue→loco_rs.bgworker.JobStatusloco_rs.bgworker.redis.RedisQueue→loco_rs.bgworker.QueueProviderloco_rs.bgworker.redis.redis$module→loco_rs.bgworker.Jobloco_rs.bgworker.redis.redis$module→loco_rs.bgworker.JobStatus
- Direction
- loco_rs.bgworker.redis uses loco_rs.bgworker, so a change to loco_rs.bgworker can break loco_rs.bgworker.redis, while a change to loco_rs.bgworker.redis can't break loco_rs.bgworker.
- Position
- Below the diagonal: loco_rs.bgworker.redis uses a module listed above it, which is the healthy direction.
22→7 loco_rs.boot uses loco_rs.config.mailer✕
- Connections
- 1 pair of types, where a type in loco_rs.boot uses a type in loco_rs.config.mailer.
- The types involved
loco_rs.boot.boot$module→loco_rs.config.mailer.Mailer
- Direction
- loco_rs.boot uses loco_rs.config.mailer, so a change to loco_rs.config.mailer can break loco_rs.boot, while a change to loco_rs.boot can't break loco_rs.config.mailer.
- Position
- Below the diagonal: loco_rs.boot uses a module listed above it, which is the healthy direction.
22→10 loco_rs.boot uses loco_rs.environment✕
- Connections
- 1 pair of types, where a type in loco_rs.boot uses a type in loco_rs.environment.
- The types involved
loco_rs.boot.boot$module→loco_rs.environment.Environment
- Direction
- loco_rs.boot uses loco_rs.environment, so a change to loco_rs.environment can break loco_rs.boot, while a change to loco_rs.boot can't break loco_rs.environment.
- Position
- Below the diagonal: loco_rs.boot uses a module listed above it, which is the healthy direction.
22→14 loco_rs.boot uses loco_rs.controller.app_routes✕
- Connections
- 1 pair of types, where a type in loco_rs.boot uses a type in loco_rs.controller.app_routes.
- The types involved
loco_rs.boot.boot$module→loco_rs.controller.app_routes.ListRoutes
- Direction
- loco_rs.boot uses loco_rs.controller.app_routes, so a change to loco_rs.controller.app_routes can break loco_rs.boot, while a change to loco_rs.boot can't break loco_rs.controller.app_routes.
- Position
- Below the diagonal: loco_rs.boot uses a module listed above it, which is the healthy direction.
22→15 loco_rs.boot uses loco_rs.task✕
- Connections
- 1 pair of types, where a type in loco_rs.boot uses a type in loco_rs.task.
- The types involved
loco_rs.boot.boot$module→loco_rs.task.Vars
- Direction
- loco_rs.boot uses loco_rs.task, so a change to loco_rs.task can break loco_rs.boot, while a change to loco_rs.boot can't break loco_rs.task.
- Position
- Below the diagonal: loco_rs.boot uses a module listed above it, which is the healthy direction.
22→16 loco_rs.boot uses loco_rs.config✕
- Connections
- 1 pair of types, where a type in loco_rs.boot uses a type in loco_rs.config.
- The types involved
loco_rs.boot.boot$module→loco_rs.config.Config
- Direction
- loco_rs.boot uses loco_rs.config, so a change to loco_rs.config can break loco_rs.boot, while a change to loco_rs.boot can't break loco_rs.config.
- Position
- Below the diagonal: loco_rs.boot uses a module listed above it, which is the healthy direction.
22→19 loco_rs.boot uses loco_rs.cli✕
- Connections
- 1 pair of types, where a type in loco_rs.boot uses a type in loco_rs.cli.
- The types involved
loco_rs.boot.RunDbCommand→loco_rs.cli.DbCommands
- Direction
- loco_rs.boot uses loco_rs.cli, so a change to loco_rs.cli can break loco_rs.boot, while a change to loco_rs.boot can't break loco_rs.cli.
- Position
- Below the diagonal: loco_rs.boot uses a module listed above it, which is the healthy direction.
22→24 loco_rs.boot uses loco_rs.app part of a loop✕
- Connections
- 2 pairs of types, where a type in loco_rs.boot uses a type in loco_rs.app.
- The types involved
loco_rs.boot.BootResult→loco_rs.app.AppContextloco_rs.boot.boot$module→loco_rs.app.AppContext
- Direction
- loco_rs.boot uses loco_rs.app, so a change to loco_rs.app can break loco_rs.boot, while a change to loco_rs.boot can't break loco_rs.app.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→11 loco_rs.storage.strategies uses loco_rs.storage.stream✕
- Connections
- 1 pair of types, where a type in loco_rs.storage.strategies uses a type in loco_rs.storage.stream.
- The types involved
loco_rs.storage.strategies.StorageStrategy→loco_rs.storage.stream.BytesStream
- Direction
- loco_rs.storage.strategies uses loco_rs.storage.stream, so a change to loco_rs.storage.stream can break loco_rs.storage.strategies, while a change to loco_rs.storage.strategies can't break loco_rs.storage.stream.
- Position
- Below the diagonal: loco_rs.storage.strategies uses a module listed above it, which is the healthy direction.
23→17 loco_rs.storage.strategies uses loco_rs.storage.drivers✕
- Connections
- 1 pair of types, where a type in loco_rs.storage.strategies uses a type in loco_rs.storage.drivers.
- The types involved
loco_rs.storage.strategies.StorageStrategy→loco_rs.storage.drivers.PresignPutOptions
- Direction
- loco_rs.storage.strategies uses loco_rs.storage.drivers, so a change to loco_rs.storage.drivers can break loco_rs.storage.strategies, while a change to loco_rs.storage.strategies can't break loco_rs.storage.drivers.
- Position
- Below the diagonal: loco_rs.storage.strategies uses a module listed above it, which is the healthy direction.
23→20 loco_rs.storage.strategies uses loco_rs.storage✕
- Connections
- 1 pair of types, where a type in loco_rs.storage.strategies uses a type in loco_rs.storage.
- The types involved
loco_rs.storage.strategies.StorageStrategy→loco_rs.storage.Storage
- Direction
- loco_rs.storage.strategies uses loco_rs.storage, so a change to loco_rs.storage can break loco_rs.storage.strategies, while a change to loco_rs.storage.strategies can't break loco_rs.storage.
- Position
- Below the diagonal: loco_rs.storage.strategies uses a module listed above it, which is the healthy direction.
24→10 loco_rs.app uses loco_rs.environment✕
- Connections
- 3 pairs of types, where a type in loco_rs.app uses a type in loco_rs.environment.
- The types involved
loco_rs.app.AppContext→loco_rs.environment.Environmentloco_rs.app.AppContextBuilder→loco_rs.environment.Environmentloco_rs.app.Hooks→loco_rs.environment.Environment
- Direction
- loco_rs.app uses loco_rs.environment, so a change to loco_rs.environment can break loco_rs.app, while a change to loco_rs.app can't break loco_rs.environment.
- Position
- Below the diagonal: loco_rs.app uses a module listed above it, which is the healthy direction.
24→14 loco_rs.app uses loco_rs.controller.app_routes✕
- Connections
- 1 pair of types, where a type in loco_rs.app uses a type in loco_rs.controller.app_routes.
- The types involved
loco_rs.app.Hooks→loco_rs.controller.app_routes.AppRoutes
- Direction
- loco_rs.app uses loco_rs.controller.app_routes, so a change to loco_rs.controller.app_routes can break loco_rs.app, while a change to loco_rs.app can't break loco_rs.controller.app_routes.
- Position
- Below the diagonal: loco_rs.app uses a module listed above it, which is the healthy direction.
24→15 loco_rs.app uses loco_rs.task✕
- Connections
- 1 pair of types, where a type in loco_rs.app uses a type in loco_rs.task.
- The types involved
loco_rs.app.Hooks→loco_rs.task.Tasks
- Direction
- loco_rs.app uses loco_rs.task, so a change to loco_rs.task can break loco_rs.app, while a change to loco_rs.app can't break loco_rs.task.
- Position
- Below the diagonal: loco_rs.app uses a module listed above it, which is the healthy direction.
24→16 loco_rs.app uses loco_rs.config✕
- Connections
- 3 pairs of types, where a type in loco_rs.app uses a type in loco_rs.config.
- The types involved
loco_rs.app.AppContext→loco_rs.config.Configloco_rs.app.AppContextBuilder→loco_rs.config.Configloco_rs.app.Hooks→loco_rs.config.Config
- Direction
- loco_rs.app uses loco_rs.config, so a change to loco_rs.config can break loco_rs.app, while a change to loco_rs.app can't break loco_rs.config.
- Position
- Below the diagonal: loco_rs.app uses a module listed above it, which is the healthy direction.
24→18 loco_rs.app uses loco_rs.bgworker✕
- Connections
- 3 pairs of types, where a type in loco_rs.app uses a type in loco_rs.bgworker.
- The types involved
loco_rs.app.AppContext→loco_rs.bgworker.Queueloco_rs.app.AppContextBuilder→loco_rs.bgworker.Queueloco_rs.app.Hooks→loco_rs.bgworker.Queue
- Direction
- loco_rs.app uses loco_rs.bgworker, so a change to loco_rs.bgworker can break loco_rs.app, while a change to loco_rs.app can't break loco_rs.bgworker.
- Position
- Below the diagonal: loco_rs.app uses a module listed above it, which is the healthy direction.
24→20 loco_rs.app uses loco_rs.storage✕
- Connections
- 2 pairs of types, where a type in loco_rs.app uses a type in loco_rs.storage.
- The types involved
loco_rs.app.AppContext→loco_rs.storage.Storageloco_rs.app.AppContextBuilder→loco_rs.storage.Storage
- Direction
- loco_rs.app uses loco_rs.storage, so a change to loco_rs.storage can break loco_rs.app, while a change to loco_rs.app can't break loco_rs.storage.
- Position
- Below the diagonal: loco_rs.app uses a module listed above it, which is the healthy direction.
24→22 loco_rs.app uses loco_rs.boot✕
- Connections
- 3 pairs of types, where a type in loco_rs.app uses a type in loco_rs.boot.
- The types involved
loco_rs.app.Hooks→loco_rs.boot.ServeParamsloco_rs.app.Hooks→loco_rs.boot.StartModeloco_rs.app.app$module→loco_rs.boot.ServeParams
- Direction
- loco_rs.app uses loco_rs.boot, so a change to loco_rs.boot can break loco_rs.app, while a change to loco_rs.app can't break loco_rs.boot.
- Position
- Below the diagonal: loco_rs.app uses a module listed above it, which is the healthy direction.
25→8 loco_rs.bgworker.sql uses loco_rs.config.queue✕
- Connections
- 2 pairs of types, where a type in loco_rs.bgworker.sql uses a type in loco_rs.config.queue.
- The types involved
loco_rs.bgworker.sql.RunOpts→loco_rs.config.queue.ReaperConfigloco_rs.bgworker.sql.sql$module→loco_rs.config.queue.ReaperConfig
- Direction
- loco_rs.bgworker.sql uses loco_rs.config.queue, so a change to loco_rs.config.queue can break loco_rs.bgworker.sql, while a change to loco_rs.bgworker.sql can't break loco_rs.config.queue.
- Position
- Below the diagonal: loco_rs.bgworker.sql uses a module listed above it, which is the healthy direction.
25→12 loco_rs.bgworker.sql uses loco_gen✕
- Connections
- 2 pairs of types, where a type in loco_rs.bgworker.sql uses a type in loco_gen.
- The types involved
loco_rs.bgworker.sql.Driver→loco_gen.Errorloco_rs.bgworker.sql.sql$module→loco_gen.Error
- Direction
- loco_rs.bgworker.sql uses loco_gen, so a change to loco_gen can break loco_rs.bgworker.sql, while a change to loco_rs.bgworker.sql can't break loco_gen.
- Position
- Below the diagonal: loco_rs.bgworker.sql uses a module listed above it, which is the healthy direction.
25→18 loco_rs.bgworker.sql uses loco_rs.bgworker✕
- Connections
- 3 pairs of types, where a type in loco_rs.bgworker.sql uses a type in loco_rs.bgworker.
- The types involved
loco_rs.bgworker.sql.JobRegistry→loco_rs.bgworker.RetryPolicyloco_rs.bgworker.sql.sql$module→loco_rs.bgworker.Jobloco_rs.bgworker.sql.sql$module→loco_rs.bgworker.RetryPolicy
- Direction
- loco_rs.bgworker.sql uses loco_rs.bgworker, so a change to loco_rs.bgworker can break loco_rs.bgworker.sql, while a change to loco_rs.bgworker.sql can't break loco_rs.bgworker.
- Position
- Below the diagonal: loco_rs.bgworker.sql uses a module listed above it, which is the healthy direction.
25→21 loco_rs.bgworker.sql uses loco_rs.bgworker.redis✕
- Connections
- 1 pair of types, where a type in loco_rs.bgworker.sql uses a type in loco_rs.bgworker.redis.
- The types involved
loco_rs.bgworker.sql.JobRegistry→loco_rs.bgworker.redis.RunOpts
- Direction
- loco_rs.bgworker.sql uses loco_rs.bgworker.redis, so a change to loco_rs.bgworker.redis can break loco_rs.bgworker.sql, while a change to loco_rs.bgworker.sql can't break loco_rs.bgworker.redis.
- Position
- Below the diagonal: loco_rs.bgworker.sql uses a module listed above it, which is the healthy direction.
26→11 loco_rs.storage.strategies.replicated uses loco_rs.storage.stream✕
- Connections
- 1 pair of types, where a type in loco_rs.storage.strategies.replicated uses a type in loco_rs.storage.stream.
- The types involved
loco_rs.storage.strategies.replicated.ReplicatedStrategy→loco_rs.storage.stream.BytesStream
- Direction
- loco_rs.storage.strategies.replicated uses loco_rs.storage.stream, so a change to loco_rs.storage.stream can break loco_rs.storage.strategies.replicated, while a change to loco_rs.storage.strategies.replicated can't break loco_rs.storage.stream.
- Position
- Below the diagonal: loco_rs.storage.strategies.replicated uses a module listed above it, which is the healthy direction.
26→17 loco_rs.storage.strategies.replicated uses loco_rs.storage.drivers✕
- Connections
- 1 pair of types, where a type in loco_rs.storage.strategies.replicated uses a type in loco_rs.storage.drivers.
- The types involved
loco_rs.storage.strategies.replicated.ReplicatedStrategy→loco_rs.storage.drivers.PresignPutOptions
- Direction
- loco_rs.storage.strategies.replicated uses loco_rs.storage.drivers, so a change to loco_rs.storage.drivers can break loco_rs.storage.strategies.replicated, while a change to loco_rs.storage.strategies.replicated can't break loco_rs.storage.drivers.
- Position
- Below the diagonal: loco_rs.storage.strategies.replicated uses a module listed above it, which is the healthy direction.
26→20 loco_rs.storage.strategies.replicated uses loco_rs.storage✕
- Connections
- 1 pair of types, where a type in loco_rs.storage.strategies.replicated uses a type in loco_rs.storage.
- The types involved
loco_rs.storage.strategies.replicated.ReplicatedStrategy→loco_rs.storage.Storage
- Direction
- loco_rs.storage.strategies.replicated uses loco_rs.storage, so a change to loco_rs.storage can break loco_rs.storage.strategies.replicated, while a change to loco_rs.storage.strategies.replicated can't break loco_rs.storage.
- Position
- Below the diagonal: loco_rs.storage.strategies.replicated uses a module listed above it, which is the healthy direction.
26→23 loco_rs.storage.strategies.replicated uses loco_rs.storage.strategies✕
- Connections
- 1 pair of types, where a type in loco_rs.storage.strategies.replicated uses a type in loco_rs.storage.strategies.
- The types involved
loco_rs.storage.strategies.replicated.ReplicatedStrategy→loco_rs.storage.strategies.StorageStrategy
- Direction
- loco_rs.storage.strategies.replicated uses loco_rs.storage.strategies, so a change to loco_rs.storage.strategies can break loco_rs.storage.strategies.replicated, while a change to loco_rs.storage.strategies.replicated can't break loco_rs.storage.strategies.
- Position
- Below the diagonal: loco_rs.storage.strategies.replicated uses a module listed above it, which is the healthy direction.
27→11 loco_rs.storage.strategies.single uses loco_rs.storage.stream✕
- Connections
- 1 pair of types, where a type in loco_rs.storage.strategies.single uses a type in loco_rs.storage.stream.
- The types involved
loco_rs.storage.strategies.single.SingleStrategy→loco_rs.storage.stream.BytesStream
- Direction
- loco_rs.storage.strategies.single uses loco_rs.storage.stream, so a change to loco_rs.storage.stream can break loco_rs.storage.strategies.single, while a change to loco_rs.storage.strategies.single can't break loco_rs.storage.stream.
- Position
- Below the diagonal: loco_rs.storage.strategies.single uses a module listed above it, which is the healthy direction.
27→17 loco_rs.storage.strategies.single uses loco_rs.storage.drivers✕
- Connections
- 1 pair of types, where a type in loco_rs.storage.strategies.single uses a type in loco_rs.storage.drivers.
- The types involved
loco_rs.storage.strategies.single.SingleStrategy→loco_rs.storage.drivers.PresignPutOptions
- Direction
- loco_rs.storage.strategies.single uses loco_rs.storage.drivers, so a change to loco_rs.storage.drivers can break loco_rs.storage.strategies.single, while a change to loco_rs.storage.strategies.single can't break loco_rs.storage.drivers.
- Position
- Below the diagonal: loco_rs.storage.strategies.single uses a module listed above it, which is the healthy direction.
27→20 loco_rs.storage.strategies.single uses loco_rs.storage✕
- Connections
- 1 pair of types, where a type in loco_rs.storage.strategies.single uses a type in loco_rs.storage.
- The types involved
loco_rs.storage.strategies.single.SingleStrategy→loco_rs.storage.Storage
- Direction
- loco_rs.storage.strategies.single uses loco_rs.storage, so a change to loco_rs.storage can break loco_rs.storage.strategies.single, while a change to loco_rs.storage.strategies.single can't break loco_rs.storage.
- Position
- Below the diagonal: loco_rs.storage.strategies.single uses a module listed above it, which is the healthy direction.
27→23 loco_rs.storage.strategies.single uses loco_rs.storage.strategies✕
- Connections
- 1 pair of types, where a type in loco_rs.storage.strategies.single uses a type in loco_rs.storage.strategies.
- The types involved
loco_rs.storage.strategies.single.SingleStrategy→loco_rs.storage.strategies.StorageStrategy
- Direction
- loco_rs.storage.strategies.single uses loco_rs.storage.strategies, so a change to loco_rs.storage.strategies can break loco_rs.storage.strategies.single, while a change to loco_rs.storage.strategies.single can't break loco_rs.storage.strategies.
- Position
- Below the diagonal: loco_rs.storage.strategies.single uses a module listed above it, which is the healthy direction.
28→10 loco_rs.auth.cookies uses loco_rs.environment✕
- Connections
- 1 pair of types, where a type in loco_rs.auth.cookies uses a type in loco_rs.environment.
- The types involved
loco_rs.auth.cookies.cookies$module→loco_rs.environment.Environment
- Direction
- loco_rs.auth.cookies uses loco_rs.environment, so a change to loco_rs.environment can break loco_rs.auth.cookies, while a change to loco_rs.auth.cookies can't break loco_rs.environment.
- Position
- Below the diagonal: loco_rs.auth.cookies uses a module listed above it, which is the healthy direction.
28→13 loco_rs.auth.cookies uses loco_rs.config.auth✕
- Connections
- 1 pair of types, where a type in loco_rs.auth.cookies uses a type in loco_rs.config.auth.
- The types involved
loco_rs.auth.cookies.cookies$module→loco_rs.config.auth.SessionConfig
- Direction
- loco_rs.auth.cookies uses loco_rs.config.auth, so a change to loco_rs.config.auth can break loco_rs.auth.cookies, while a change to loco_rs.auth.cookies can't break loco_rs.config.auth.
- Position
- Below the diagonal: loco_rs.auth.cookies uses a module listed above it, which is the healthy direction.
28→16 loco_rs.auth.cookies uses loco_rs.config✕
- Connections
- 2 pairs of types, where a type in loco_rs.auth.cookies uses a type in loco_rs.config.
- The types involved
loco_rs.auth.cookies.CookieOptions→loco_rs.config.Configloco_rs.auth.cookies.cookies$module→loco_rs.config.Config
- Direction
- loco_rs.auth.cookies uses loco_rs.config, so a change to loco_rs.config can break loco_rs.auth.cookies, while a change to loco_rs.auth.cookies can't break loco_rs.config.
- Position
- Below the diagonal: loco_rs.auth.cookies uses a module listed above it, which is the healthy direction.
28→24 loco_rs.auth.cookies uses loco_rs.app✕
- Connections
- 1 pair of types, where a type in loco_rs.auth.cookies uses a type in loco_rs.app.
- The types involved
loco_rs.auth.cookies.cookies$module→loco_rs.app.AppContext
- Direction
- loco_rs.auth.cookies uses loco_rs.app, so a change to loco_rs.app can break loco_rs.auth.cookies, while a change to loco_rs.auth.cookies can't break loco_rs.app.
- Position
- Below the diagonal: loco_rs.auth.cookies uses a module listed above it, which is the healthy direction.
29→8 loco_rs.bgworker.pg uses loco_rs.config.queue✕
- Connections
- 1 pair of types, where a type in loco_rs.bgworker.pg uses a type in loco_rs.config.queue.
- The types involved
loco_rs.bgworker.pg.pg$module→loco_rs.config.queue.PostgresQueueConfig
- Direction
- loco_rs.bgworker.pg uses loco_rs.config.queue, so a change to loco_rs.config.queue can break loco_rs.bgworker.pg, while a change to loco_rs.bgworker.pg can't break loco_rs.config.queue.
- Position
- Below the diagonal: loco_rs.bgworker.pg uses a module listed above it, which is the healthy direction.
29→12 loco_rs.bgworker.pg uses loco_gen✕
- Connections
- 2 pairs of types, where a type in loco_rs.bgworker.pg uses a type in loco_gen.
- The types involved
loco_rs.bgworker.pg.PgDriver→loco_gen.Errorloco_rs.bgworker.pg.pg$module→loco_gen.Error
- Direction
- loco_rs.bgworker.pg uses loco_gen, so a change to loco_gen can break loco_rs.bgworker.pg, while a change to loco_rs.bgworker.pg can't break loco_gen.
- Position
- Below the diagonal: loco_rs.bgworker.pg uses a module listed above it, which is the healthy direction.
29→18 loco_rs.bgworker.pg uses loco_rs.bgworker✕
- Connections
- 4 pairs of types, where a type in loco_rs.bgworker.pg uses a type in loco_rs.bgworker.
- The types involved
loco_rs.bgworker.pg.PgQueue→loco_rs.bgworker.JobStatusloco_rs.bgworker.pg.PgQueue→loco_rs.bgworker.QueueProviderloco_rs.bgworker.pg.PgQueue→loco_rs.bgworker.RetryPolicyloco_rs.bgworker.pg.pg$module→loco_rs.bgworker.JobStatus
- Direction
- loco_rs.bgworker.pg uses loco_rs.bgworker, so a change to loco_rs.bgworker can break loco_rs.bgworker.pg, while a change to loco_rs.bgworker.pg can't break loco_rs.bgworker.
- Position
- Below the diagonal: loco_rs.bgworker.pg uses a module listed above it, which is the healthy direction.
29→21 loco_rs.bgworker.pg uses loco_rs.bgworker.redis✕
- Connections
- 2 pairs of types, where a type in loco_rs.bgworker.pg uses a type in loco_rs.bgworker.redis.
- The types involved
loco_rs.bgworker.pg.PgQueue→loco_rs.bgworker.redis.JobRegistryloco_rs.bgworker.pg.PgQueue→loco_rs.bgworker.redis.RunOpts
- Direction
- loco_rs.bgworker.pg uses loco_rs.bgworker.redis, so a change to loco_rs.bgworker.redis can break loco_rs.bgworker.pg, while a change to loco_rs.bgworker.pg can't break loco_rs.bgworker.redis.
- Position
- Below the diagonal: loco_rs.bgworker.pg uses a module listed above it, which is the healthy direction.
29→25 loco_rs.bgworker.pg uses loco_rs.bgworker.sql✕
- Connections
- 1 pair of types, where a type in loco_rs.bgworker.pg uses a type in loco_rs.bgworker.sql.
- The types involved
loco_rs.bgworker.pg.PgDriver→loco_rs.bgworker.sql.Driver
- Direction
- loco_rs.bgworker.pg uses loco_rs.bgworker.sql, so a change to loco_rs.bgworker.sql can break loco_rs.bgworker.pg, while a change to loco_rs.bgworker.pg can't break loco_rs.bgworker.sql.
- Position
- Below the diagonal: loco_rs.bgworker.pg uses a module listed above it, which is the healthy direction.
30→8 loco_rs.bgworker.sqlt uses loco_rs.config.queue✕
- Connections
- 1 pair of types, where a type in loco_rs.bgworker.sqlt uses a type in loco_rs.config.queue.
- The types involved
loco_rs.bgworker.sqlt.sqlt$module→loco_rs.config.queue.SqliteQueueConfig
- Direction
- loco_rs.bgworker.sqlt uses loco_rs.config.queue, so a change to loco_rs.config.queue can break loco_rs.bgworker.sqlt, while a change to loco_rs.bgworker.sqlt can't break loco_rs.config.queue.
- Position
- Below the diagonal: loco_rs.bgworker.sqlt uses a module listed above it, which is the healthy direction.
30→12 loco_rs.bgworker.sqlt uses loco_gen✕
- Connections
- 2 pairs of types, where a type in loco_rs.bgworker.sqlt uses a type in loco_gen.
- The types involved
loco_rs.bgworker.sqlt.SqliteDriver→loco_gen.Errorloco_rs.bgworker.sqlt.sqlt$module→loco_gen.Error
- Direction
- loco_rs.bgworker.sqlt uses loco_gen, so a change to loco_gen can break loco_rs.bgworker.sqlt, while a change to loco_rs.bgworker.sqlt can't break loco_gen.
- Position
- Below the diagonal: loco_rs.bgworker.sqlt uses a module listed above it, which is the healthy direction.
30→18 loco_rs.bgworker.sqlt uses loco_rs.bgworker✕
- Connections
- 4 pairs of types, where a type in loco_rs.bgworker.sqlt uses a type in loco_rs.bgworker.
- The types involved
loco_rs.bgworker.sqlt.SqliteQueue→loco_rs.bgworker.JobStatusloco_rs.bgworker.sqlt.SqliteQueue→loco_rs.bgworker.QueueProviderloco_rs.bgworker.sqlt.SqliteQueue→loco_rs.bgworker.RetryPolicyloco_rs.bgworker.sqlt.sqlt$module→loco_rs.bgworker.JobStatus
- Direction
- loco_rs.bgworker.sqlt uses loco_rs.bgworker, so a change to loco_rs.bgworker can break loco_rs.bgworker.sqlt, while a change to loco_rs.bgworker.sqlt can't break loco_rs.bgworker.
- Position
- Below the diagonal: loco_rs.bgworker.sqlt uses a module listed above it, which is the healthy direction.
30→21 loco_rs.bgworker.sqlt uses loco_rs.bgworker.redis✕
- Connections
- 2 pairs of types, where a type in loco_rs.bgworker.sqlt uses a type in loco_rs.bgworker.redis.
- The types involved
loco_rs.bgworker.sqlt.SqliteQueue→loco_rs.bgworker.redis.JobRegistryloco_rs.bgworker.sqlt.SqliteQueue→loco_rs.bgworker.redis.RunOpts
- Direction
- loco_rs.bgworker.sqlt uses loco_rs.bgworker.redis, so a change to loco_rs.bgworker.redis can break loco_rs.bgworker.sqlt, while a change to loco_rs.bgworker.sqlt can't break loco_rs.bgworker.redis.
- Position
- Below the diagonal: loco_rs.bgworker.sqlt uses a module listed above it, which is the healthy direction.
30→25 loco_rs.bgworker.sqlt uses loco_rs.bgworker.sql✕
- Connections
- 1 pair of types, where a type in loco_rs.bgworker.sqlt uses a type in loco_rs.bgworker.sql.
- The types involved
loco_rs.bgworker.sqlt.SqliteDriver→loco_rs.bgworker.sql.Driver
- Direction
- loco_rs.bgworker.sqlt uses loco_rs.bgworker.sql, so a change to loco_rs.bgworker.sql can break loco_rs.bgworker.sqlt, while a change to loco_rs.bgworker.sqlt can't break loco_rs.bgworker.sql.
- Position
- Below the diagonal: loco_rs.bgworker.sqlt uses a module listed above it, which is the healthy direction.
31→4 loco_rs.controller.extractor.auth uses loco_rs.auth.jwt✕
- Connections
- 2 pairs of types, where a type in loco_rs.controller.extractor.auth uses a type in loco_rs.auth.jwt.
- The types involved
loco_rs.controller.extractor.auth.JWT→loco_rs.auth.jwt.UserClaimsloco_rs.controller.extractor.auth.JWTWithUser→loco_rs.auth.jwt.UserClaims
- Direction
- loco_rs.controller.extractor.auth uses loco_rs.auth.jwt, so a change to loco_rs.auth.jwt can break loco_rs.controller.extractor.auth, while a change to loco_rs.controller.extractor.auth can't break loco_rs.auth.jwt.
- Position
- Below the diagonal: loco_rs.controller.extractor.auth uses a module listed above it, which is the healthy direction.
31→12 loco_rs.controller.extractor.auth uses loco_gen✕
- Connections
- 1 pair of types, where a type in loco_rs.controller.extractor.auth uses a type in loco_gen.
- The types involved
loco_rs.controller.extractor.auth.auth$module→loco_gen.Error
- Direction
- loco_rs.controller.extractor.auth uses loco_gen, so a change to loco_gen can break loco_rs.controller.extractor.auth, while a change to loco_rs.controller.extractor.auth can't break loco_gen.
- Position
- Below the diagonal: loco_rs.controller.extractor.auth uses a module listed above it, which is the healthy direction.
31→13 loco_rs.controller.extractor.auth uses loco_rs.config.auth✕
- Connections
- 2 pairs of types, where a type in loco_rs.controller.extractor.auth uses a type in loco_rs.config.auth.
- The types involved
loco_rs.controller.extractor.auth.auth$module→loco_rs.config.auth.JWTLocationloco_rs.controller.extractor.auth.auth$module→loco_rs.config.auth.JWTLocationConfig
- Direction
- loco_rs.controller.extractor.auth uses loco_rs.config.auth, so a change to loco_rs.config.auth can break loco_rs.controller.extractor.auth, while a change to loco_rs.controller.extractor.auth can't break loco_rs.config.auth.
- Position
- Below the diagonal: loco_rs.controller.extractor.auth uses a module listed above it, which is the healthy direction.
31→24 loco_rs.controller.extractor.auth uses loco_rs.app✕
- Connections
- 1 pair of types, where a type in loco_rs.controller.extractor.auth uses a type in loco_rs.app.
- The types involved
loco_rs.controller.extractor.auth.auth$module→loco_rs.app.AppContext
- Direction
- loco_rs.controller.extractor.auth uses loco_rs.app, so a change to loco_rs.app can break loco_rs.controller.extractor.auth, while a change to loco_rs.controller.extractor.auth can't break loco_rs.app.
- Position
- Below the diagonal: loco_rs.controller.extractor.auth uses a module listed above it, which is the healthy direction.
32→16 loco_rs.controller.middleware uses loco_rs.config✕
- Connections
- 1 pair of types, where a type in loco_rs.controller.middleware uses a type in loco_rs.config.
- The types involved
loco_rs.controller.middleware.Config→loco_rs.config.Config
- Direction
- loco_rs.controller.middleware uses loco_rs.config, so a change to loco_rs.config can break loco_rs.controller.middleware, while a change to loco_rs.controller.middleware can't break loco_rs.config.
- Position
- Below the diagonal: loco_rs.controller.middleware uses a module listed above it, which is the healthy direction.
32→24 loco_rs.controller.middleware uses loco_rs.app✕
- Connections
- 1 pair of types, where a type in loco_rs.controller.middleware uses a type in loco_rs.app.
- The types involved
loco_rs.controller.middleware.middleware$module→loco_rs.app.AppContext
- Direction
- loco_rs.controller.middleware uses loco_rs.app, so a change to loco_rs.app can break loco_rs.controller.middleware, while a change to loco_rs.controller.middleware can't break loco_rs.app.
- Position
- Below the diagonal: loco_rs.controller.middleware uses a module listed above it, which is the healthy direction.
33→10 loco_rs.evals.tasks.api-key-endpoint.wiring.src.app uses loco_rs.environment✕
- Connections
- 1 pair of types, where a type in loco_rs.evals.tasks.api-key-endpoint.wiring.src.app uses a type in loco_rs.environment.
- The types involved
loco_rs.evals.tasks.api-key-endpoint.wiring.src.app.App→loco_rs.environment.Environment
- Direction
- loco_rs.evals.tasks.api-key-endpoint.wiring.src.app uses loco_rs.environment, so a change to loco_rs.environment can break loco_rs.evals.tasks.api-key-endpoint.wiring.src.app, while a change to loco_rs.evals.tasks.api-key-endpoint.wiring.src.app can't break loco_rs.environment.
- Position
- Below the diagonal: loco_rs.evals.tasks.api-key-endpoint.wiring.src.app uses a module listed above it, which is the healthy direction.
33→14 loco_rs.evals.tasks.api-key-endpoint.wiring.src.app uses loco_rs.controller.app_routes✕
- Connections
- 1 pair of types, where a type in loco_rs.evals.tasks.api-key-endpoint.wiring.src.app uses a type in loco_rs.controller.app_routes.
- The types involved
loco_rs.evals.tasks.api-key-endpoint.wiring.src.app.App→loco_rs.controller.app_routes.AppRoutes
- Direction
- loco_rs.evals.tasks.api-key-endpoint.wiring.src.app uses loco_rs.controller.app_routes, so a change to loco_rs.controller.app_routes can break loco_rs.evals.tasks.api-key-endpoint.wiring.src.app, while a change to loco_rs.evals.tasks.api-key-endpoint.wiring.src.app can't break loco_rs.controller.app_routes.
- Position
- Below the diagonal: loco_rs.evals.tasks.api-key-endpoint.wiring.src.app uses a module listed above it, which is the healthy direction.
33→15 loco_rs.evals.tasks.api-key-endpoint.wiring.src.app uses loco_rs.task✕
- Connections
- 1 pair of types, where a type in loco_rs.evals.tasks.api-key-endpoint.wiring.src.app uses a type in loco_rs.task.
- The types involved
loco_rs.evals.tasks.api-key-endpoint.wiring.src.app.App→loco_rs.task.Tasks
- Direction
- loco_rs.evals.tasks.api-key-endpoint.wiring.src.app uses loco_rs.task, so a change to loco_rs.task can break loco_rs.evals.tasks.api-key-endpoint.wiring.src.app, while a change to loco_rs.evals.tasks.api-key-endpoint.wiring.src.app can't break loco_rs.task.
- Position
- Below the diagonal: loco_rs.evals.tasks.api-key-endpoint.wiring.src.app uses a module listed above it, which is the healthy direction.
33→16 loco_rs.evals.tasks.api-key-endpoint.wiring.src.app uses loco_rs.config✕
- Connections
- 1 pair of types, where a type in loco_rs.evals.tasks.api-key-endpoint.wiring.src.app uses a type in loco_rs.config.
- The types involved
loco_rs.evals.tasks.api-key-endpoint.wiring.src.app.App→loco_rs.config.Config
- Direction
- loco_rs.evals.tasks.api-key-endpoint.wiring.src.app uses loco_rs.config, so a change to loco_rs.config can break loco_rs.evals.tasks.api-key-endpoint.wiring.src.app, while a change to loco_rs.evals.tasks.api-key-endpoint.wiring.src.app can't break loco_rs.config.
- Position
- Below the diagonal: loco_rs.evals.tasks.api-key-endpoint.wiring.src.app uses a module listed above it, which is the healthy direction.
33→18 loco_rs.evals.tasks.api-key-endpoint.wiring.src.app uses loco_rs.bgworker✕
- Connections
- 1 pair of types, where a type in loco_rs.evals.tasks.api-key-endpoint.wiring.src.app uses a type in loco_rs.bgworker.
- The types involved
loco_rs.evals.tasks.api-key-endpoint.wiring.src.app.App→loco_rs.bgworker.Queue
- Direction
- loco_rs.evals.tasks.api-key-endpoint.wiring.src.app uses loco_rs.bgworker, so a change to loco_rs.bgworker can break loco_rs.evals.tasks.api-key-endpoint.wiring.src.app, while a change to loco_rs.evals.tasks.api-key-endpoint.wiring.src.app can't break loco_rs.bgworker.
- Position
- Below the diagonal: loco_rs.evals.tasks.api-key-endpoint.wiring.src.app uses a module listed above it, which is the healthy direction.
33→22 loco_rs.evals.tasks.api-key-endpoint.wiring.src.app uses loco_rs.boot✕
- Connections
- 1 pair of types, where a type in loco_rs.evals.tasks.api-key-endpoint.wiring.src.app uses a type in loco_rs.boot.
- The types involved
loco_rs.evals.tasks.api-key-endpoint.wiring.src.app.App→loco_rs.boot.StartMode
- Direction
- loco_rs.evals.tasks.api-key-endpoint.wiring.src.app uses loco_rs.boot, so a change to loco_rs.boot can break loco_rs.evals.tasks.api-key-endpoint.wiring.src.app, while a change to loco_rs.evals.tasks.api-key-endpoint.wiring.src.app can't break loco_rs.boot.
- Position
- Below the diagonal: loco_rs.evals.tasks.api-key-endpoint.wiring.src.app uses a module listed above it, which is the healthy direction.
33→24 loco_rs.evals.tasks.api-key-endpoint.wiring.src.app uses loco_rs.app✕
- Connections
- 2 pairs of types, where a type in loco_rs.evals.tasks.api-key-endpoint.wiring.src.app uses a type in loco_rs.app.
- The types involved
loco_rs.evals.tasks.api-key-endpoint.wiring.src.app.App→loco_rs.app.AppContextloco_rs.evals.tasks.api-key-endpoint.wiring.src.app.App→loco_rs.app.Hooks
- Direction
- loco_rs.evals.tasks.api-key-endpoint.wiring.src.app uses loco_rs.app, so a change to loco_rs.app can break loco_rs.evals.tasks.api-key-endpoint.wiring.src.app, while a change to loco_rs.evals.tasks.api-key-endpoint.wiring.src.app can't break loco_rs.app.
- Position
- Below the diagonal: loco_rs.evals.tasks.api-key-endpoint.wiring.src.app uses a module listed above it, which is the healthy direction.
34→10 loco_rs.evals.tasks.cached-stats.wiring.src.app uses loco_rs.environment✕
- Connections
- 1 pair of types, where a type in loco_rs.evals.tasks.cached-stats.wiring.src.app uses a type in loco_rs.environment.
- The types involved
loco_rs.evals.tasks.cached-stats.wiring.src.app.App→loco_rs.environment.Environment
- Direction
- loco_rs.evals.tasks.cached-stats.wiring.src.app uses loco_rs.environment, so a change to loco_rs.environment can break loco_rs.evals.tasks.cached-stats.wiring.src.app, while a change to loco_rs.evals.tasks.cached-stats.wiring.src.app can't break loco_rs.environment.
- Position
- Below the diagonal: loco_rs.evals.tasks.cached-stats.wiring.src.app uses a module listed above it, which is the healthy direction.
34→14 loco_rs.evals.tasks.cached-stats.wiring.src.app uses loco_rs.controller.app_routes✕
- Connections
- 1 pair of types, where a type in loco_rs.evals.tasks.cached-stats.wiring.src.app uses a type in loco_rs.controller.app_routes.
- The types involved
loco_rs.evals.tasks.cached-stats.wiring.src.app.App→loco_rs.controller.app_routes.AppRoutes
- Direction
- loco_rs.evals.tasks.cached-stats.wiring.src.app uses loco_rs.controller.app_routes, so a change to loco_rs.controller.app_routes can break loco_rs.evals.tasks.cached-stats.wiring.src.app, while a change to loco_rs.evals.tasks.cached-stats.wiring.src.app can't break loco_rs.controller.app_routes.
- Position
- Below the diagonal: loco_rs.evals.tasks.cached-stats.wiring.src.app uses a module listed above it, which is the healthy direction.
34→15 loco_rs.evals.tasks.cached-stats.wiring.src.app uses loco_rs.task✕
- Connections
- 1 pair of types, where a type in loco_rs.evals.tasks.cached-stats.wiring.src.app uses a type in loco_rs.task.
- The types involved
loco_rs.evals.tasks.cached-stats.wiring.src.app.App→loco_rs.task.Tasks
- Direction
- loco_rs.evals.tasks.cached-stats.wiring.src.app uses loco_rs.task, so a change to loco_rs.task can break loco_rs.evals.tasks.cached-stats.wiring.src.app, while a change to loco_rs.evals.tasks.cached-stats.wiring.src.app can't break loco_rs.task.
- Position
- Below the diagonal: loco_rs.evals.tasks.cached-stats.wiring.src.app uses a module listed above it, which is the healthy direction.
34→16 loco_rs.evals.tasks.cached-stats.wiring.src.app uses loco_rs.config✕
- Connections
- 1 pair of types, where a type in loco_rs.evals.tasks.cached-stats.wiring.src.app uses a type in loco_rs.config.
- The types involved
loco_rs.evals.tasks.cached-stats.wiring.src.app.App→loco_rs.config.Config
- Direction
- loco_rs.evals.tasks.cached-stats.wiring.src.app uses loco_rs.config, so a change to loco_rs.config can break loco_rs.evals.tasks.cached-stats.wiring.src.app, while a change to loco_rs.evals.tasks.cached-stats.wiring.src.app can't break loco_rs.config.
- Position
- Below the diagonal: loco_rs.evals.tasks.cached-stats.wiring.src.app uses a module listed above it, which is the healthy direction.
34→18 loco_rs.evals.tasks.cached-stats.wiring.src.app uses loco_rs.bgworker✕
- Connections
- 1 pair of types, where a type in loco_rs.evals.tasks.cached-stats.wiring.src.app uses a type in loco_rs.bgworker.
- The types involved
loco_rs.evals.tasks.cached-stats.wiring.src.app.App→loco_rs.bgworker.Queue
- Direction
- loco_rs.evals.tasks.cached-stats.wiring.src.app uses loco_rs.bgworker, so a change to loco_rs.bgworker can break loco_rs.evals.tasks.cached-stats.wiring.src.app, while a change to loco_rs.evals.tasks.cached-stats.wiring.src.app can't break loco_rs.bgworker.
- Position
- Below the diagonal: loco_rs.evals.tasks.cached-stats.wiring.src.app uses a module listed above it, which is the healthy direction.
34→22 loco_rs.evals.tasks.cached-stats.wiring.src.app uses loco_rs.boot✕
- Connections
- 1 pair of types, where a type in loco_rs.evals.tasks.cached-stats.wiring.src.app uses a type in loco_rs.boot.
- The types involved
loco_rs.evals.tasks.cached-stats.wiring.src.app.App→loco_rs.boot.StartMode
- Direction
- loco_rs.evals.tasks.cached-stats.wiring.src.app uses loco_rs.boot, so a change to loco_rs.boot can break loco_rs.evals.tasks.cached-stats.wiring.src.app, while a change to loco_rs.evals.tasks.cached-stats.wiring.src.app can't break loco_rs.boot.
- Position
- Below the diagonal: loco_rs.evals.tasks.cached-stats.wiring.src.app uses a module listed above it, which is the healthy direction.
34→24 loco_rs.evals.tasks.cached-stats.wiring.src.app uses loco_rs.app✕
- Connections
- 2 pairs of types, where a type in loco_rs.evals.tasks.cached-stats.wiring.src.app uses a type in loco_rs.app.
- The types involved
loco_rs.evals.tasks.cached-stats.wiring.src.app.App→loco_rs.app.AppContextloco_rs.evals.tasks.cached-stats.wiring.src.app.App→loco_rs.app.Hooks
- Direction
- loco_rs.evals.tasks.cached-stats.wiring.src.app uses loco_rs.app, so a change to loco_rs.app can break loco_rs.evals.tasks.cached-stats.wiring.src.app, while a change to loco_rs.evals.tasks.cached-stats.wiring.src.app can't break loco_rs.app.
- Position
- Below the diagonal: loco_rs.evals.tasks.cached-stats.wiring.src.app uses a module listed above it, which is the healthy direction.
35→10 loco_rs.evals.tasks.nightly-digest.wiring.src.app uses loco_rs.environment✕
- Connections
- 1 pair of types, where a type in loco_rs.evals.tasks.nightly-digest.wiring.src.app uses a type in loco_rs.environment.
- The types involved
loco_rs.evals.tasks.nightly-digest.wiring.src.app.App→loco_rs.environment.Environment
- Direction
- loco_rs.evals.tasks.nightly-digest.wiring.src.app uses loco_rs.environment, so a change to loco_rs.environment can break loco_rs.evals.tasks.nightly-digest.wiring.src.app, while a change to loco_rs.evals.tasks.nightly-digest.wiring.src.app can't break loco_rs.environment.
- Position
- Below the diagonal: loco_rs.evals.tasks.nightly-digest.wiring.src.app uses a module listed above it, which is the healthy direction.
35→14 loco_rs.evals.tasks.nightly-digest.wiring.src.app uses loco_rs.controller.app_routes✕
- Connections
- 1 pair of types, where a type in loco_rs.evals.tasks.nightly-digest.wiring.src.app uses a type in loco_rs.controller.app_routes.
- The types involved
loco_rs.evals.tasks.nightly-digest.wiring.src.app.App→loco_rs.controller.app_routes.AppRoutes
- Direction
- loco_rs.evals.tasks.nightly-digest.wiring.src.app uses loco_rs.controller.app_routes, so a change to loco_rs.controller.app_routes can break loco_rs.evals.tasks.nightly-digest.wiring.src.app, while a change to loco_rs.evals.tasks.nightly-digest.wiring.src.app can't break loco_rs.controller.app_routes.
- Position
- Below the diagonal: loco_rs.evals.tasks.nightly-digest.wiring.src.app uses a module listed above it, which is the healthy direction.
35→15 loco_rs.evals.tasks.nightly-digest.wiring.src.app uses loco_rs.task✕
- Connections
- 1 pair of types, where a type in loco_rs.evals.tasks.nightly-digest.wiring.src.app uses a type in loco_rs.task.
- The types involved
loco_rs.evals.tasks.nightly-digest.wiring.src.app.App→loco_rs.task.Tasks
- Direction
- loco_rs.evals.tasks.nightly-digest.wiring.src.app uses loco_rs.task, so a change to loco_rs.task can break loco_rs.evals.tasks.nightly-digest.wiring.src.app, while a change to loco_rs.evals.tasks.nightly-digest.wiring.src.app can't break loco_rs.task.
- Position
- Below the diagonal: loco_rs.evals.tasks.nightly-digest.wiring.src.app uses a module listed above it, which is the healthy direction.
35→16 loco_rs.evals.tasks.nightly-digest.wiring.src.app uses loco_rs.config✕
- Connections
- 1 pair of types, where a type in loco_rs.evals.tasks.nightly-digest.wiring.src.app uses a type in loco_rs.config.
- The types involved
loco_rs.evals.tasks.nightly-digest.wiring.src.app.App→loco_rs.config.Config
- Direction
- loco_rs.evals.tasks.nightly-digest.wiring.src.app uses loco_rs.config, so a change to loco_rs.config can break loco_rs.evals.tasks.nightly-digest.wiring.src.app, while a change to loco_rs.evals.tasks.nightly-digest.wiring.src.app can't break loco_rs.config.
- Position
- Below the diagonal: loco_rs.evals.tasks.nightly-digest.wiring.src.app uses a module listed above it, which is the healthy direction.
35→18 loco_rs.evals.tasks.nightly-digest.wiring.src.app uses loco_rs.bgworker✕
- Connections
- 1 pair of types, where a type in loco_rs.evals.tasks.nightly-digest.wiring.src.app uses a type in loco_rs.bgworker.
- The types involved
loco_rs.evals.tasks.nightly-digest.wiring.src.app.App→loco_rs.bgworker.Queue
- Direction
- loco_rs.evals.tasks.nightly-digest.wiring.src.app uses loco_rs.bgworker, so a change to loco_rs.bgworker can break loco_rs.evals.tasks.nightly-digest.wiring.src.app, while a change to loco_rs.evals.tasks.nightly-digest.wiring.src.app can't break loco_rs.bgworker.
- Position
- Below the diagonal: loco_rs.evals.tasks.nightly-digest.wiring.src.app uses a module listed above it, which is the healthy direction.
35→22 loco_rs.evals.tasks.nightly-digest.wiring.src.app uses loco_rs.boot✕
- Connections
- 1 pair of types, where a type in loco_rs.evals.tasks.nightly-digest.wiring.src.app uses a type in loco_rs.boot.
- The types involved
loco_rs.evals.tasks.nightly-digest.wiring.src.app.App→loco_rs.boot.StartMode
- Direction
- loco_rs.evals.tasks.nightly-digest.wiring.src.app uses loco_rs.boot, so a change to loco_rs.boot can break loco_rs.evals.tasks.nightly-digest.wiring.src.app, while a change to loco_rs.evals.tasks.nightly-digest.wiring.src.app can't break loco_rs.boot.
- Position
- Below the diagonal: loco_rs.evals.tasks.nightly-digest.wiring.src.app uses a module listed above it, which is the healthy direction.
35→24 loco_rs.evals.tasks.nightly-digest.wiring.src.app uses loco_rs.app✕
- Connections
- 2 pairs of types, where a type in loco_rs.evals.tasks.nightly-digest.wiring.src.app uses a type in loco_rs.app.
- The types involved
loco_rs.evals.tasks.nightly-digest.wiring.src.app.App→loco_rs.app.AppContextloco_rs.evals.tasks.nightly-digest.wiring.src.app.App→loco_rs.app.Hooks
- Direction
- loco_rs.evals.tasks.nightly-digest.wiring.src.app uses loco_rs.app, so a change to loco_rs.app can break loco_rs.evals.tasks.nightly-digest.wiring.src.app, while a change to loco_rs.evals.tasks.nightly-digest.wiring.src.app can't break loco_rs.app.
- Position
- Below the diagonal: loco_rs.evals.tasks.nightly-digest.wiring.src.app uses a module listed above it, which is the healthy direction.
36→10 loco_rs.evals.tasks.purge-unverified.wiring.src.app uses loco_rs.environment✕
- Connections
- 1 pair of types, where a type in loco_rs.evals.tasks.purge-unverified.wiring.src.app uses a type in loco_rs.environment.
- The types involved
loco_rs.evals.tasks.purge-unverified.wiring.src.app.App→loco_rs.environment.Environment
- Direction
- loco_rs.evals.tasks.purge-unverified.wiring.src.app uses loco_rs.environment, so a change to loco_rs.environment can break loco_rs.evals.tasks.purge-unverified.wiring.src.app, while a change to loco_rs.evals.tasks.purge-unverified.wiring.src.app can't break loco_rs.environment.
- Position
- Below the diagonal: loco_rs.evals.tasks.purge-unverified.wiring.src.app uses a module listed above it, which is the healthy direction.
36→14 loco_rs.evals.tasks.purge-unverified.wiring.src.app uses loco_rs.controller.app_routes✕
- Connections
- 1 pair of types, where a type in loco_rs.evals.tasks.purge-unverified.wiring.src.app uses a type in loco_rs.controller.app_routes.
- The types involved
loco_rs.evals.tasks.purge-unverified.wiring.src.app.App→loco_rs.controller.app_routes.AppRoutes
- Direction
- loco_rs.evals.tasks.purge-unverified.wiring.src.app uses loco_rs.controller.app_routes, so a change to loco_rs.controller.app_routes can break loco_rs.evals.tasks.purge-unverified.wiring.src.app, while a change to loco_rs.evals.tasks.purge-unverified.wiring.src.app can't break loco_rs.controller.app_routes.
- Position
- Below the diagonal: loco_rs.evals.tasks.purge-unverified.wiring.src.app uses a module listed above it, which is the healthy direction.
36→15 loco_rs.evals.tasks.purge-unverified.wiring.src.app uses loco_rs.task✕
- Connections
- 1 pair of types, where a type in loco_rs.evals.tasks.purge-unverified.wiring.src.app uses a type in loco_rs.task.
- The types involved
loco_rs.evals.tasks.purge-unverified.wiring.src.app.App→loco_rs.task.Tasks
- Direction
- loco_rs.evals.tasks.purge-unverified.wiring.src.app uses loco_rs.task, so a change to loco_rs.task can break loco_rs.evals.tasks.purge-unverified.wiring.src.app, while a change to loco_rs.evals.tasks.purge-unverified.wiring.src.app can't break loco_rs.task.
- Position
- Below the diagonal: loco_rs.evals.tasks.purge-unverified.wiring.src.app uses a module listed above it, which is the healthy direction.
36→16 loco_rs.evals.tasks.purge-unverified.wiring.src.app uses loco_rs.config✕
- Connections
- 1 pair of types, where a type in loco_rs.evals.tasks.purge-unverified.wiring.src.app uses a type in loco_rs.config.
- The types involved
loco_rs.evals.tasks.purge-unverified.wiring.src.app.App→loco_rs.config.Config
- Direction
- loco_rs.evals.tasks.purge-unverified.wiring.src.app uses loco_rs.config, so a change to loco_rs.config can break loco_rs.evals.tasks.purge-unverified.wiring.src.app, while a change to loco_rs.evals.tasks.purge-unverified.wiring.src.app can't break loco_rs.config.
- Position
- Below the diagonal: loco_rs.evals.tasks.purge-unverified.wiring.src.app uses a module listed above it, which is the healthy direction.
36→18 loco_rs.evals.tasks.purge-unverified.wiring.src.app uses loco_rs.bgworker✕
- Connections
- 1 pair of types, where a type in loco_rs.evals.tasks.purge-unverified.wiring.src.app uses a type in loco_rs.bgworker.
- The types involved
loco_rs.evals.tasks.purge-unverified.wiring.src.app.App→loco_rs.bgworker.Queue
- Direction
- loco_rs.evals.tasks.purge-unverified.wiring.src.app uses loco_rs.bgworker, so a change to loco_rs.bgworker can break loco_rs.evals.tasks.purge-unverified.wiring.src.app, while a change to loco_rs.evals.tasks.purge-unverified.wiring.src.app can't break loco_rs.bgworker.
- Position
- Below the diagonal: loco_rs.evals.tasks.purge-unverified.wiring.src.app uses a module listed above it, which is the healthy direction.
36→22 loco_rs.evals.tasks.purge-unverified.wiring.src.app uses loco_rs.boot✕
- Connections
- 1 pair of types, where a type in loco_rs.evals.tasks.purge-unverified.wiring.src.app uses a type in loco_rs.boot.
- The types involved
loco_rs.evals.tasks.purge-unverified.wiring.src.app.App→loco_rs.boot.StartMode
- Direction
- loco_rs.evals.tasks.purge-unverified.wiring.src.app uses loco_rs.boot, so a change to loco_rs.boot can break loco_rs.evals.tasks.purge-unverified.wiring.src.app, while a change to loco_rs.evals.tasks.purge-unverified.wiring.src.app can't break loco_rs.boot.
- Position
- Below the diagonal: loco_rs.evals.tasks.purge-unverified.wiring.src.app uses a module listed above it, which is the healthy direction.
36→24 loco_rs.evals.tasks.purge-unverified.wiring.src.app uses loco_rs.app✕
- Connections
- 2 pairs of types, where a type in loco_rs.evals.tasks.purge-unverified.wiring.src.app uses a type in loco_rs.app.
- The types involved
loco_rs.evals.tasks.purge-unverified.wiring.src.app.App→loco_rs.app.AppContextloco_rs.evals.tasks.purge-unverified.wiring.src.app.App→loco_rs.app.Hooks
- Direction
- loco_rs.evals.tasks.purge-unverified.wiring.src.app uses loco_rs.app, so a change to loco_rs.app can break loco_rs.evals.tasks.purge-unverified.wiring.src.app, while a change to loco_rs.evals.tasks.purge-unverified.wiring.src.app can't break loco_rs.app.
- Position
- Below the diagonal: loco_rs.evals.tasks.purge-unverified.wiring.src.app uses a module listed above it, which is the healthy direction.
37→10 loco_rs.evals.tasks.typed-errors.wiring.src.app uses loco_rs.environment✕
- Connections
- 1 pair of types, where a type in loco_rs.evals.tasks.typed-errors.wiring.src.app uses a type in loco_rs.environment.
- The types involved
loco_rs.evals.tasks.typed-errors.wiring.src.app.App→loco_rs.environment.Environment
- Direction
- loco_rs.evals.tasks.typed-errors.wiring.src.app uses loco_rs.environment, so a change to loco_rs.environment can break loco_rs.evals.tasks.typed-errors.wiring.src.app, while a change to loco_rs.evals.tasks.typed-errors.wiring.src.app can't break loco_rs.environment.
- Position
- Below the diagonal: loco_rs.evals.tasks.typed-errors.wiring.src.app uses a module listed above it, which is the healthy direction.
37→14 loco_rs.evals.tasks.typed-errors.wiring.src.app uses loco_rs.controller.app_routes✕
- Connections
- 1 pair of types, where a type in loco_rs.evals.tasks.typed-errors.wiring.src.app uses a type in loco_rs.controller.app_routes.
- The types involved
loco_rs.evals.tasks.typed-errors.wiring.src.app.App→loco_rs.controller.app_routes.AppRoutes
- Direction
- loco_rs.evals.tasks.typed-errors.wiring.src.app uses loco_rs.controller.app_routes, so a change to loco_rs.controller.app_routes can break loco_rs.evals.tasks.typed-errors.wiring.src.app, while a change to loco_rs.evals.tasks.typed-errors.wiring.src.app can't break loco_rs.controller.app_routes.
- Position
- Below the diagonal: loco_rs.evals.tasks.typed-errors.wiring.src.app uses a module listed above it, which is the healthy direction.
37→15 loco_rs.evals.tasks.typed-errors.wiring.src.app uses loco_rs.task✕
- Connections
- 1 pair of types, where a type in loco_rs.evals.tasks.typed-errors.wiring.src.app uses a type in loco_rs.task.
- The types involved
loco_rs.evals.tasks.typed-errors.wiring.src.app.App→loco_rs.task.Tasks
- Direction
- loco_rs.evals.tasks.typed-errors.wiring.src.app uses loco_rs.task, so a change to loco_rs.task can break loco_rs.evals.tasks.typed-errors.wiring.src.app, while a change to loco_rs.evals.tasks.typed-errors.wiring.src.app can't break loco_rs.task.
- Position
- Below the diagonal: loco_rs.evals.tasks.typed-errors.wiring.src.app uses a module listed above it, which is the healthy direction.
37→16 loco_rs.evals.tasks.typed-errors.wiring.src.app uses loco_rs.config✕
- Connections
- 1 pair of types, where a type in loco_rs.evals.tasks.typed-errors.wiring.src.app uses a type in loco_rs.config.
- The types involved
loco_rs.evals.tasks.typed-errors.wiring.src.app.App→loco_rs.config.Config
- Direction
- loco_rs.evals.tasks.typed-errors.wiring.src.app uses loco_rs.config, so a change to loco_rs.config can break loco_rs.evals.tasks.typed-errors.wiring.src.app, while a change to loco_rs.evals.tasks.typed-errors.wiring.src.app can't break loco_rs.config.
- Position
- Below the diagonal: loco_rs.evals.tasks.typed-errors.wiring.src.app uses a module listed above it, which is the healthy direction.
37→18 loco_rs.evals.tasks.typed-errors.wiring.src.app uses loco_rs.bgworker✕
- Connections
- 1 pair of types, where a type in loco_rs.evals.tasks.typed-errors.wiring.src.app uses a type in loco_rs.bgworker.
- The types involved
loco_rs.evals.tasks.typed-errors.wiring.src.app.App→loco_rs.bgworker.Queue
- Direction
- loco_rs.evals.tasks.typed-errors.wiring.src.app uses loco_rs.bgworker, so a change to loco_rs.bgworker can break loco_rs.evals.tasks.typed-errors.wiring.src.app, while a change to loco_rs.evals.tasks.typed-errors.wiring.src.app can't break loco_rs.bgworker.
- Position
- Below the diagonal: loco_rs.evals.tasks.typed-errors.wiring.src.app uses a module listed above it, which is the healthy direction.
37→22 loco_rs.evals.tasks.typed-errors.wiring.src.app uses loco_rs.boot✕
- Connections
- 1 pair of types, where a type in loco_rs.evals.tasks.typed-errors.wiring.src.app uses a type in loco_rs.boot.
- The types involved
loco_rs.evals.tasks.typed-errors.wiring.src.app.App→loco_rs.boot.StartMode
- Direction
- loco_rs.evals.tasks.typed-errors.wiring.src.app uses loco_rs.boot, so a change to loco_rs.boot can break loco_rs.evals.tasks.typed-errors.wiring.src.app, while a change to loco_rs.evals.tasks.typed-errors.wiring.src.app can't break loco_rs.boot.
- Position
- Below the diagonal: loco_rs.evals.tasks.typed-errors.wiring.src.app uses a module listed above it, which is the healthy direction.
37→24 loco_rs.evals.tasks.typed-errors.wiring.src.app uses loco_rs.app✕
- Connections
- 2 pairs of types, where a type in loco_rs.evals.tasks.typed-errors.wiring.src.app uses a type in loco_rs.app.
- The types involved
loco_rs.evals.tasks.typed-errors.wiring.src.app.App→loco_rs.app.AppContextloco_rs.evals.tasks.typed-errors.wiring.src.app.App→loco_rs.app.Hooks
- Direction
- loco_rs.evals.tasks.typed-errors.wiring.src.app uses loco_rs.app, so a change to loco_rs.app can break loco_rs.evals.tasks.typed-errors.wiring.src.app, while a change to loco_rs.evals.tasks.typed-errors.wiring.src.app can't break loco_rs.app.
- Position
- Below the diagonal: loco_rs.evals.tasks.typed-errors.wiring.src.app uses a module listed above it, which is the healthy direction.
38→10 loco_rs.evals.tasks.user-search.wiring.src.app uses loco_rs.environment✕
- Connections
- 1 pair of types, where a type in loco_rs.evals.tasks.user-search.wiring.src.app uses a type in loco_rs.environment.
- The types involved
loco_rs.evals.tasks.user-search.wiring.src.app.App→loco_rs.environment.Environment
- Direction
- loco_rs.evals.tasks.user-search.wiring.src.app uses loco_rs.environment, so a change to loco_rs.environment can break loco_rs.evals.tasks.user-search.wiring.src.app, while a change to loco_rs.evals.tasks.user-search.wiring.src.app can't break loco_rs.environment.
- Position
- Below the diagonal: loco_rs.evals.tasks.user-search.wiring.src.app uses a module listed above it, which is the healthy direction.
38→14 loco_rs.evals.tasks.user-search.wiring.src.app uses loco_rs.controller.app_routes✕
- Connections
- 1 pair of types, where a type in loco_rs.evals.tasks.user-search.wiring.src.app uses a type in loco_rs.controller.app_routes.
- The types involved
loco_rs.evals.tasks.user-search.wiring.src.app.App→loco_rs.controller.app_routes.AppRoutes
- Direction
- loco_rs.evals.tasks.user-search.wiring.src.app uses loco_rs.controller.app_routes, so a change to loco_rs.controller.app_routes can break loco_rs.evals.tasks.user-search.wiring.src.app, while a change to loco_rs.evals.tasks.user-search.wiring.src.app can't break loco_rs.controller.app_routes.
- Position
- Below the diagonal: loco_rs.evals.tasks.user-search.wiring.src.app uses a module listed above it, which is the healthy direction.
38→15 loco_rs.evals.tasks.user-search.wiring.src.app uses loco_rs.task✕
- Connections
- 1 pair of types, where a type in loco_rs.evals.tasks.user-search.wiring.src.app uses a type in loco_rs.task.
- The types involved
loco_rs.evals.tasks.user-search.wiring.src.app.App→loco_rs.task.Tasks
- Direction
- loco_rs.evals.tasks.user-search.wiring.src.app uses loco_rs.task, so a change to loco_rs.task can break loco_rs.evals.tasks.user-search.wiring.src.app, while a change to loco_rs.evals.tasks.user-search.wiring.src.app can't break loco_rs.task.
- Position
- Below the diagonal: loco_rs.evals.tasks.user-search.wiring.src.app uses a module listed above it, which is the healthy direction.
38→16 loco_rs.evals.tasks.user-search.wiring.src.app uses loco_rs.config✕
- Connections
- 1 pair of types, where a type in loco_rs.evals.tasks.user-search.wiring.src.app uses a type in loco_rs.config.
- The types involved
loco_rs.evals.tasks.user-search.wiring.src.app.App→loco_rs.config.Config
- Direction
- loco_rs.evals.tasks.user-search.wiring.src.app uses loco_rs.config, so a change to loco_rs.config can break loco_rs.evals.tasks.user-search.wiring.src.app, while a change to loco_rs.evals.tasks.user-search.wiring.src.app can't break loco_rs.config.
- Position
- Below the diagonal: loco_rs.evals.tasks.user-search.wiring.src.app uses a module listed above it, which is the healthy direction.
38→18 loco_rs.evals.tasks.user-search.wiring.src.app uses loco_rs.bgworker✕
- Connections
- 1 pair of types, where a type in loco_rs.evals.tasks.user-search.wiring.src.app uses a type in loco_rs.bgworker.
- The types involved
loco_rs.evals.tasks.user-search.wiring.src.app.App→loco_rs.bgworker.Queue
- Direction
- loco_rs.evals.tasks.user-search.wiring.src.app uses loco_rs.bgworker, so a change to loco_rs.bgworker can break loco_rs.evals.tasks.user-search.wiring.src.app, while a change to loco_rs.evals.tasks.user-search.wiring.src.app can't break loco_rs.bgworker.
- Position
- Below the diagonal: loco_rs.evals.tasks.user-search.wiring.src.app uses a module listed above it, which is the healthy direction.
38→22 loco_rs.evals.tasks.user-search.wiring.src.app uses loco_rs.boot✕
- Connections
- 1 pair of types, where a type in loco_rs.evals.tasks.user-search.wiring.src.app uses a type in loco_rs.boot.
- The types involved
loco_rs.evals.tasks.user-search.wiring.src.app.App→loco_rs.boot.StartMode
- Direction
- loco_rs.evals.tasks.user-search.wiring.src.app uses loco_rs.boot, so a change to loco_rs.boot can break loco_rs.evals.tasks.user-search.wiring.src.app, while a change to loco_rs.evals.tasks.user-search.wiring.src.app can't break loco_rs.boot.
- Position
- Below the diagonal: loco_rs.evals.tasks.user-search.wiring.src.app uses a module listed above it, which is the healthy direction.
38→24 loco_rs.evals.tasks.user-search.wiring.src.app uses loco_rs.app✕
- Connections
- 2 pairs of types, where a type in loco_rs.evals.tasks.user-search.wiring.src.app uses a type in loco_rs.app.
- The types involved
loco_rs.evals.tasks.user-search.wiring.src.app.App→loco_rs.app.AppContextloco_rs.evals.tasks.user-search.wiring.src.app.App→loco_rs.app.Hooks
- Direction
- loco_rs.evals.tasks.user-search.wiring.src.app uses loco_rs.app, so a change to loco_rs.app can break loco_rs.evals.tasks.user-search.wiring.src.app, while a change to loco_rs.evals.tasks.user-search.wiring.src.app can't break loco_rs.app.
- Position
- Below the diagonal: loco_rs.evals.tasks.user-search.wiring.src.app uses a module listed above it, which is the healthy direction.
39→9 loco_rs.auth.oauth uses loco_rs.controller.routes✕
- Connections
- 1 pair of types, where a type in loco_rs.auth.oauth uses a type in loco_rs.controller.routes.
- The types involved
loco_rs.auth.oauth.oauth$module→loco_rs.controller.routes.Routes
- Direction
- loco_rs.auth.oauth uses loco_rs.controller.routes, so a change to loco_rs.controller.routes can break loco_rs.auth.oauth, while a change to loco_rs.auth.oauth can't break loco_rs.controller.routes.
- Position
- Below the diagonal: loco_rs.auth.oauth uses a module listed above it, which is the healthy direction.
39→13 loco_rs.auth.oauth uses loco_rs.config.auth✕
- Connections
- 1 pair of types, where a type in loco_rs.auth.oauth uses a type in loco_rs.config.auth.
- The types involved
loco_rs.auth.oauth.oauth$module→loco_rs.config.auth.OAuthConfig
- Direction
- loco_rs.auth.oauth uses loco_rs.config.auth, so a change to loco_rs.config.auth can break loco_rs.auth.oauth, while a change to loco_rs.auth.oauth can't break loco_rs.config.auth.
- Position
- Below the diagonal: loco_rs.auth.oauth uses a module listed above it, which is the healthy direction.
39→24 loco_rs.auth.oauth uses loco_rs.app✕
- Connections
- 2 pairs of types, where a type in loco_rs.auth.oauth uses a type in loco_rs.app.
- The types involved
loco_rs.auth.oauth.OAuthHandler→loco_rs.app.AppContextloco_rs.auth.oauth.oauth$module→loco_rs.app.AppContext
- Direction
- loco_rs.auth.oauth uses loco_rs.app, so a change to loco_rs.app can break loco_rs.auth.oauth, while a change to loco_rs.auth.oauth can't break loco_rs.app.
- Position
- Below the diagonal: loco_rs.auth.oauth uses a module listed above it, which is the healthy direction.
39→28 loco_rs.auth.oauth uses loco_rs.auth.cookies✕
- Connections
- 1 pair of types, where a type in loco_rs.auth.oauth uses a type in loco_rs.auth.cookies.
- The types involved
loco_rs.auth.oauth.oauth$module→loco_rs.auth.cookies.SignedCookies
- Direction
- loco_rs.auth.oauth uses loco_rs.auth.cookies, so a change to loco_rs.auth.cookies can break loco_rs.auth.oauth, while a change to loco_rs.auth.oauth can't break loco_rs.auth.cookies.
- Position
- Below the diagonal: loco_rs.auth.oauth uses a module listed above it, which is the healthy direction.
40→10 loco_rs.controller.middleware.logger uses loco_rs.environment✕
- Connections
- 2 pairs of types, where a type in loco_rs.controller.middleware.logger uses a type in loco_rs.environment.
- The types involved
loco_rs.controller.middleware.logger.Middleware→loco_rs.environment.Environmentloco_rs.controller.middleware.logger.logger$module→loco_rs.environment.Environment
- Direction
- loco_rs.controller.middleware.logger uses loco_rs.environment, so a change to loco_rs.environment can break loco_rs.controller.middleware.logger, while a change to loco_rs.controller.middleware.logger can't break loco_rs.environment.
- Position
- Below the diagonal: loco_rs.controller.middleware.logger uses a module listed above it, which is the healthy direction.
40→16 loco_rs.controller.middleware.logger uses loco_rs.config✕
- Connections
- 2 pairs of types, where a type in loco_rs.controller.middleware.logger uses a type in loco_rs.config.
- The types involved
loco_rs.controller.middleware.logger.Middleware→loco_rs.config.Configloco_rs.controller.middleware.logger.logger$module→loco_rs.config.Config
- Direction
- loco_rs.controller.middleware.logger uses loco_rs.config, so a change to loco_rs.config can break loco_rs.controller.middleware.logger, while a change to loco_rs.controller.middleware.logger can't break loco_rs.config.
- Position
- Below the diagonal: loco_rs.controller.middleware.logger uses a module listed above it, which is the healthy direction.
40→32 loco_rs.controller.middleware.logger uses loco_rs.controller.middleware✕
- Connections
- 1 pair of types, where a type in loco_rs.controller.middleware.logger uses a type in loco_rs.controller.middleware.
- The types involved
loco_rs.controller.middleware.logger.Middleware→loco_rs.controller.middleware.MiddlewareLayer
- Direction
- loco_rs.controller.middleware.logger uses loco_rs.controller.middleware, so a change to loco_rs.controller.middleware can break loco_rs.controller.middleware.logger, while a change to loco_rs.controller.middleware.logger can't break loco_rs.controller.middleware.
- Position
- Below the diagonal: loco_rs.controller.middleware.logger uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 84 | High / Critical |
| A01:2025 — Broken Access Control | 9 | Medium |
| A03:2025 — Software Supply Chain Failures | 2 | Medium |
Roadmap
First, ensure all media elements have appropriate text alternatives and captions to support screen readers and audio users. Next, strengthen data security by vaulting encryption keys and encrypting sensitive database columns to eliminate gaps in data-at-rest protection. Additionally, fix structural issues by declaring language, titles, and main landmarks, while ensuring headings are ordered correctly and meta-refreshes are removed. Finally, improve visual accessibility by maintaining visible focus styles, respecting reduced motion preferences, and correcting low-contrast colors, then enforce these standards using linting tools and CI gates.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video. | +5.9 pts | Medium | Text alternatives |
| Resolve the 9 REDACTED finding(s) in Data Compliance (PII/GDPR) — start with REDACTED (9). | +2.2 pts | Low | Data Compliance (PII/GDPR) |
| Strengthen data-at-rest protection: vault your keys (AWS KMS / Secrets Manager, GCP KMS / Secret Manager, Azure Key Vault, HashiCorp Vault — not a key read from an environment variable beside the data) and encrypt the most sensitive columns (an AEAD over the field before Diesel/sqlx write it, SQLCipher, pgcrypto) — partial coverage still leaves gaps. | +3.8 pts | Medium | Data Protection |
| Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh. | +3.5 pts | Medium | Page structure |
| 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. | +3.5 pts | Medium | Visual & motion safety |
| Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y, then assert with vitest-axe in tests, then gate axe/pa11y/Lighthouse in CI. | +3.5 pts | Medium | A11y enforcement |
| Resolve the 18 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (5), REDACTED (5), REDACTED (5). | +2.5 pts | Medium | Static Analysis (SAST) |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +1.0 pts | Low | ADR Quality |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.6 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.1 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.1 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.6 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Data Compliance (PII/GDPR): Medium: REDACTED |
| REDACTED | 6.9 | Mixed | Dependency Vulnerabilities: Medium advisory (unmaintained): REDACTED |
| src/bgworker/redis.rs | 7.0 | Mixed | Cyclomatic Complexity: loco_rs::bgworker::redis::clear_jobs_older_than (cyclomatic 19) |
| src/cli.rs | 7.1 | Mixed | Cyclomatic Complexity: loco_rs::cli::dispatch_common (cyclomatic 22) |
| xtask/src/agent_skill.rs | 7.1 | Mixed | Cyclomatic Complexity: xtask::agent_skill::render_type (cyclomatic 16) |
| xtask/src/eval.rs | 7.1 | Mixed | Cognitive Complexity: xtask::eval::judge_arm (cognitive 27) |
| loco-gen/src/column.rs | 7.2 | Mixed | Cyclomatic Complexity: loco_gen::column::parse_column (cyclomatic 25) |
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
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 63 of 63 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.8 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
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, 277 of 293 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, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — 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 |
| Watchdog duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D10 Test Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 44 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 129 test source file(s) (.rs) 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 — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — this repository declares Cargo manifests but commits no REDACTED, so its dependency graph was closed from the manifests over the crates.io index, and part of it could not be read: no published release of serde_yaml satisfies `0.10`. A licence verdict over part of a dependency graph is not a licence verdict. NOT a finding that this repository's licences are compliant: this dimension asserts nothing about its licensing in either direction.
- D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape 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. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (dev). the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence.
- GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Rust 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Rust 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.
- M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9). Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P8 Schema migrations — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. The schema may be created by a runner, a deploy script or a config file outside what this check reads, so an absence here is our blind spot rather than a missing migration strategy. The card abstains instead of scoring. You can widen what we reach: if the schema is created and evolved by a tool this check does not name, naming it lets us teach the detector to read it.
- X12 Unreachable branch — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X16 Unfloored truncation loop — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X19 Unrestored process-global state — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X22 Contradicted release guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, TypeScript/JavaScript, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded, and this repository's Rust 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.
- X23 Unguarded diagnostic materialisation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X25 Inert configuration knob — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart and Ruby source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart or Ruby was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X3 Exception handling — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go and JavaScript/TypeScript source only, and no C# was loaded and no PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go, JavaScript or TypeScript was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X5 Nullable reference types — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- 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.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs 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").
- 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.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- 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.
- D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D32 Data Compliance (PII/GDPR): PII/GDPR signals are heuristic pattern matches in code — they flag likely handling concerns, not legal compliance, and cannot trace where data actually flows at runtime.
- 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 Dockerfile (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.
- AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- C4 Data Retention: This control is scored from in-repo evidence only — its real-world effectiveness, exercised only at runtime, is outside a static scan.
- DM4 Rich vs anemic domain model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- 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
8 function(s) exceeded the cyclomatic complexity threshold of 15; the worst was loco_rs::build::embedded_assets::generate_asset_code at 26. A further 5 function(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being ColType::to_def at 120 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: src/controller/mod.rs (Error::into_response at 21). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 8 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with loco_rs::build::embedded_assets::generate_asset_code (cyclomatic 26), loco_gen::column::parse_column (cyclomatic 25), loco_rs::cli::dispatch_common (cyclomatic 22). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 8 together lifts Cyclomatic Complexity from 8.8 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
26 function(s) exceeded the cognitive complexity threshold of 15; the worst was loco_rs::build::embedded_assets::generate_asset_code at 48.
What to do
- Bring the 26 bodies over 15 down to 15 or less in Cognitive Complexity — start with loco_rs::build::embedded_assets::generate_asset_code (cognitive 48), JobRegistry::run (cognitive 45), JobRegistry::run (cognitive 44). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 26 together lifts Cognitive Complexity from 6.8 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
11 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 8 FileTooLong finding(s) in God Classes — start with eval.rs, redis.rs, cli.rs. — One of this dimension's main actionable groups (8 warning-level).
- Resolve the 2 MethodTooLong finding(s) in God Classes — start with REDACTED, mod.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 FunctionTooLong finding(s) in God Classes — start with column.rs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
57 duplicated block group(s) detected. A further 3 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
What to do
- Resolve the 6 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with redis.rs (3), REDACTED, REDACTED. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 5 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with REDACTED (5). — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 5 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with REDACTED (4), redis.rs. — One of this dimension's main actionable groups (5 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
5 production modules (Cargo+npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence, with abstractness counted on 4 of the 5 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
0 of 65 classes have LCOM4 above 3.
D9 · Test Distribution
985 test methods: 726 unit, 259 integration, 0 BDD, 0 e2e. The JavaScript/TypeScript suite contributes 44 `it`/`test` case(s) across 4 test file(s) declaring at least one; its tier split is read from package names and paths only. The Rust suite contributes 941 `#[test]` function(s) across 135 file(s) declaring at least one; its unit/integration split is Cargo's own — 45 of those file(s) are integration-test targets under a crate's tests/ directory, and the rest are #[test] functions compiled into the crate they test.
D10 · Test Quality
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 44 tests. Measured on the JavaScript/TypeScript suite only — at least 129 test source file(s) (.rs) went unread, so its test quality is unmeasured and is not in these counts.
D11 · Test Reliability
0 flaky across 2 measured tier(s). JavaScript/TypeScript (vitest via `pnpm install --frozen-lockfile --ignore-scripts` in website/ (44 tests)): measured (0 flaky); Rust (repository root, 135 test files): measured (0 flaky).
D12 · Dependency Hygiene
0 outdated, 0 yanked direct Cargo dependencies. 65 of 72 direct crates were graded against crates.io (0 not published there, 7 not resolved by a committed REDACTED). Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from REDACTED there.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D15 · Churn × Complexity Hotspots
Top hotspots: src/cli.rs (5×22=110); src/controller/mod.rs (4×21=84)
What to do
- Resolve the 2 Hotspot finding(s) in Churn × Complexity Hotspots — start with cli.rs, mod.rs. — One of this dimension's main actionable groups (2 warning-level).
D16 · Bus Factor
6 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/bgworker/sql.rs. Counted over 124 of the 203 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
11 deducted task-comment markers across 50989 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.
What to do
- Resolve the 11 TodoComment finding(s) in Explicit Debt — start with downloader.rs (3), mod.rs (2), opendal_adapter.rs (2). — One of this dimension's main actionable groups (11 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 6 build units (Cargo, 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).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
84 finding(s): 0 critical, 83 high, 1 medium, 0 low. 59 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. semgrep hit a parse error in 1 file(s) — `src/controller/middleware/static_assets_embedded.rs` (lines 85–213) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. 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 18 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (5), REDACTED (5), REDACTED (5). — One of this dimension's main actionable groups (18 issue-level).
- Resolve the 6 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (6 issue-level).
- No action in Static Analysis (SAST) — all 59 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 (59 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
2 finding(s): 0 critical, 0 high, 2 medium, 0 low.
What to do
- Resolve the 1 Medium advisory (unmaintained) finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D32 · Data Compliance (PII/GDPR)
9 finding(s): 0 critical, 0 high, 9 medium, 0 low.
What to do
- Resolve the 9 REDACTED finding(s) in Data Compliance (PII/GDPR) — start with REDACTED (9). — One of this dimension's main actionable groups (9 warning-level).
D34 · Knowledge Freshness
25 of 124 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/model/query/dsl/mod.rs. Counted over 124 of the 203 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with mod.rs. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 24 Orphaned file finding(s) in Knowledge Freshness — start with mod.rs (2), auth.rs (2), template.rs (2). — One of this dimension's main actionable groups (24 recommendation-level).
- Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
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
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AC1 · Text alternatives
- An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. — loco-new/base_template/assets/views/home/hello.html:2
What to do
- Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
AC2 · Forms & labels
AC3 · Page structure
- The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). (×2) — loco-new/base_template/assets/static/404.html:1, loco-new/base_template/assets/views/home/hello.html:1
- A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>. (×2) — loco-new/base_template/assets/static/404.html:1, loco-new/base_template/assets/views/home/hello.html:1
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×3) — loco-new/base_template/assets/static/404.html:1, loco-new/base_template/assets/views/home/hello.html:1, src/controller/middleware/fallback.html:2
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="root">, so there is no content here to wrap — render the <main> from the component mounted into it. — loco-new/base_template/frontend/index.html:2
- Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. — src/controller/middleware/fallback.html:39
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.
AC5 · ARIA correctness
AC6 · Visual & motion safety
- `html.js [data-reveal]` moves (`transition: opacity .6s ease, transform .6s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — website/src/styles/global.css:58
- `.docs-hub .hub-card` moves (`transition: transform 0.15s ease, border-color 0.15s ease, box-shadow 0.15s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — website/src/styles/starlight.css:130
What to do
- Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AC7 · A11y enforcement
- No accessibility enforcement found — no a11y linter (eslint-plugin-jsx-a11y) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 11 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
What to do
- Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y, then assert with vitest-axe in tests, then gate axe/pa11y/Lighthouse in CI.
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX9 · CQS / query purity
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 key read from an environment variable beside the data) and encrypt the most sensitive columns (an AEAD over the field before Diesel/sqlx write it, SQLCipher, pgcrypto) — partial coverage still leaves gaps.
- Enforce HTTPS on the server that receives this data: terminate TLS in it (axum-server/actix bind_rustls, tonic ServerTlsConfig, a tokio-rustls acceptor) and send Strict-Transport-Security, or run it behind a TLS-terminating proxy, so data in transit is always encrypted.
C2 · Access Controls
- Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect.
What to do
- Name the access rules — roles and permissions declared once (an enum Role/Permission, actix-web-grants #[protect(…)], axum-login's permission_required!, a casbin or oso policy) and consulted where access is checked, so the rule set is reviewable and testable on its own.
C4 · Data Retention
- A retention mechanism is present, but the data-lifecycle is not yet complete — missing: an expiry limit — a declared maximum age / TTL after which the data is no longer kept.
What to do
- Complete the data-lifecycle story: an expiry limit (a declared maximum age for the stored data — a retention-age setting, or a store-level TTL where your storage offers one), a scheduled purge/cleanup job that enforces it, and a documented retention period covering the personal data.
DM4 · Rich vs anemic domain model
DM6 · Domain ↔ infrastructure boundary
- `Model` is a domain AGGREGATE fused to persistence ON ITS OWN DECLARATION (the sea-orm `#[derive(DeriveEntityModel)]` + `#[sea_orm(table_name)]` mapping) with a singular-entity write-persistence method (create/update/delete taking a DB connection) on the domain type and no separate pure-domain layer — the domain entity IS the ORM row (active-record). A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository). — loco-new/base_template/src/models/_entities/users.rs:8
What to do
- Keep the ORM/table mapping on a boundary data-model + mapper; leave the domain entity framework-free (map row↔domain through a repository).
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 4 of 10 project(s) that lack one — worth up to 0.8 pts.
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
M4 · Documentation accuracy
- CONTRIBUTING.md links to `./starters/README.md`, but `starters/README.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — CONTRIBUTING.md:111
- loco-new/base_template/README.md links to `config/development.yaml`, but `loco-new/base_template/config/development.yaml` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — loco-new/base_template/README.md:53
What to do
- Reconcile the README with reality: CONTRIBUTING.md links to `./starters/README.md`, but `starters/README.md` does not exist; loco-new/base_template/README.md links to `config/development.yaml`, but `loco-new/base_template/config/development.yaml` does not exist.
P1 · CI/CD gates
P10 · Library API & versioning
- 241/321 types (75%) declared in the published library are public. For a library, every public type is a stability contract — keep implementation types off the surface and expose only the intended API.
What to do
- Keep implementation types off the public surface (Rust: `pub(crate)`, or keep the module private) so internals can change without breaking consumers.
P2 · Observability
- Only 3/4 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `xtask`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
- Add OpenTelemetry tracing/metrics (opentelemetry with tracing-opentelemetry) so requests are traceable across the system, not just health-probable.
P3 · Security & performance tooling
What to do
- Dependabot is configured but does not watch `npm` — add that `package-ecosystem` entry to .github/dependabot.yml so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P5 · DR & Backup
What to do
- Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
P6 · Release Hygiene
P7 · Outbound HTTP resilience
PF3 · Async & latency hygiene
S1 · Web-Security Posture
- This repository starts an HTTP server and nothing in its Rust source or committed `Rocket.toml` secures the transport: no TLS served (actix-web `bind_rustls`/`bind_openssl`, axum-server `bind_rustls` with a `RustlsConfig`, tonic `ServerTlsConfig`, a `TlsAcceptor`, Rocket's `[default.tls]`), no `Strict-Transport-Security` header, no `X-Forwarded-Proto` read from a TLS-terminating proxy — so its traffic may cross the network in clear text. (−2.0 on this card.) The server: `axum::serve(` (src/app.rs:654).
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is set on a response this repository's Rust server sends — defense in depth, even when a proxy could set them. (−2.0 on this card.) The server: `axum::serve(` (src/app.rs:654).
What to do
- Secure the server's transport: serve TLS itself (`HttpServer::bind_rustls_0_23(addr, config)` in actix-web, `axum_server::bind_rustls(addr, RustlsConfig::from_pem_file(…))`, tonic's `Server::builder().tls_config(ServerTlsConfig::new().identity(…))`, Rocket's `[default.tls]`), or run it behind a TLS-terminating proxy and check `X-Forwarded-Proto`; send `Strict-Transport-Security` once it is HTTPS-only.
- Set security response headers on what the server sends — actix-web's `DefaultHeaders::new().add((header::X_CONTENT_TYPE_OPTIONS, "nosniff"))`, tower-http's `SetResponseHeaderLayer::overriding(…)` on an axum router, or keep Rocket's default `Shield` — with `Content-Security-Policy`, `X-Content-Type-Options` and a frame policy on every response.
X1 · Async correctness
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X21 · Side-effecting pattern guard
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X30 · Support guard that admits what it rejects
X4 · Structured logging
- `warn!` at line 348 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/boot.rs:348
- `info!` at line 973 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — REDACTED:973
- `info!` at line 996 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — REDACTED:996
- `warn!` at line 44 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/db/entities.rs:44
- `info!` at line 301 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/controller/app_routes.rs:301
- `info!` at line 36 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/controller/describe.rs:36
- `info!` at line 112 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/controller/views/engine_embedded.rs:112
- `debug!` at line 129 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/controller/views/engine_embedded.rs:129
- `error!` at line 132 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/controller/views/engine_embedded.rs:132
- `warn!` at line 175 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/controller/views/engine_embedded.rs:175
- `debug!` at line 178 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/controller/views/engine_embedded.rs:178
- `warn!` at line 93 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/controller/middleware/request_id.rs:93
- `info!` at line 87 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/controller/middleware/static_assets_embedded.rs:87
- `info!` at line 93 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/controller/middleware/static_assets_embedded.rs:93
- `info!` at line 97 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/controller/middleware/static_assets_embedded.rs:97
- `warn!` at line 101 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/controller/middleware/static_assets_embedded.rs:101
- `warn!` at line 126 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/controller/middleware/static_assets_embedded.rs:126
- `debug!` at line 152 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/controller/middleware/static_assets_embedded.rs:152
- `error!` at line 179 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/controller/extractor/auth.rs:179
- `error!` at line 23 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/controller/extractor/shared_store.rs:23
What to do
- Interpolated log message defeats structured logging
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 |
| AC5 · ARIA correctness | 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
| AC7 · A11y enforcement | enforcement — no page criterion | Enforcement posture (process) |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 82% | Strong | Solid. |
| Architecture | 94% | Exemplary | Solid. |
| Maturity | 66% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 62% | Adequate | Acceptable, with room to improve. |
| Security | 49% | Weak — gated by D29, D32, C1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 63% | Adequate — gated by DM6 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 41% | Weak — gated by AC1, AC3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for
- C3 Audit Trail — Repo shows no audit-logging mechanism (an audit-log table or model — a struct, Diesel table, SeaORM entity or SQL migration table named for it — a SeaORM ActiveModelBehavior hook or database trigger that records each change, or an event-sourced store beside one) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
- 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 — 61 check(s) not relevant to this codebase
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
- AX1 Captive dependencies — Not applicable: Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written. 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 — no exported interface declares behaviour
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- D14 License Compliance — Crate licences not graded — the lock-less Cargo graph could not be read in full
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D19 Documentation Quality — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
- D21 Naming Consistency — Naming consistency is measured on C# only; JavaScript, Python, Rust, TypeScript not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .rs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D36 Supply-chain Provenance & Signing — The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — website/ runs vitest but declares no coverage provider, so the suite can run and still produce no lcov — add `@vitest/coverage-v8` (or `@vitest/coverage-istanbul`) as a devDependency. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan. Alternatively, commit the lcov/Cobertura report your CI produces and it is read without a re-run.
- DM1 Aggregate boundaries — this Rust crate declares no domain aggregate (a struct with private state and its own command methods), so DM1's aggregate-boundary read has no population to be taken over
- DM2 Strongly-typed ids — the crate defines newtype typed-ids but declares no domain aggregate that could carry an id — so DM2's adoption ratio has no population to be taken over
- DM3 Integration-event coupling — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM5 Encapsulated state — this Rust crate declares no type implementing a hand-rolled Hash/PartialEq, so DM5's value-identity encapsulation read has no population to be taken over
- DM7 Repository granularity — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P8 Schema migrations — SeaORM, sqlx is declared, but the schema-migration mechanism could not be identified. Our limit, not a verdict on this repository.
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `#[bench]`, criterion's `bench_function`/`bench_with_input`, `#[divan::bench]` or `#[library_benchmark]` in any `.rs` file, or criterion, divan, iai or a `[[bench]]` target in a Cargo.toml, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not applicable: Rust spells out every heap allocation and makes borrowed slices (&[T], &str) its ordinary parameter types, so the allocation-aware style this card rewards elsewhere is the language's baseline rather than a rung to climb.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — 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
- X13 Undrained process stream — 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
- X16 Unfloored truncation loop — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X17 Uncapped recursion over a caller-supplied document — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X18 Disposal-pattern correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X19 Unrestored process-global state — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X2 Cancellation propagation — no C# was loaded; this repository's Rust was read, and no request in it can be cancelled by a caller — a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — not 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
- X23 Unguarded diagnostic materialisation — 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
- X24 Document value interpolated into markup unescaped — 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
- X25 Inert configuration knob — 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
- 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. Rust's compiler refuses the unsynchronised version: a collection shared between a callback's thread and the waiting body must be `Sync`, which a `Vec`, `VecDeque` or `HashMap` is only behind a `Mutex`/`RwLock`, so the race this check looks for cannot be written in safe Rust. Not a gap in the analyzer and not a finding about your code.
- X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 90 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
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <html> without a lang loco-new/base_template/assets/static/404.html:1
- <html> without a lang loco-new/base_template/assets/views/home/hello.html:1
- Document without a <title> loco-new/base_template/assets/static/404.html:1
- Document without a <title> loco-new/base_template/assets/views/home/hello.html:1
- <img> without a text alternative loco-new/base_template/assets/views/home/hello.html:2
- Orphaned knowledge src/model/query/dsl/mod.rs:1
- Domain fused to persistence infrastructure: Model loco-new/base_template/src/models/_entities/users.rs:8
Serious — 140 finding(s)
- TodoComment src/storage/drivers/mod.rs:151
- TodoComment src/storage/drivers/opendal_adapter.rs:40
- TodoComment src/storage/drivers/opendal_adapter.rs:140
- TodoComment loco-new/src/generator/mod.rs:88
- TodoComment loco-new/src/generator/executer/filesystem.rs:132
- TodoComment loco-new/base_template/src/workers/downloader.rs:19
- TodoComment examples/reference_spa/src/workers/downloader.rs:19
- TodoComment examples/demo/src/workers/downloader.rs:19
- TodoComment loco-gen/src/lib.rs:2
- TodoComment examples/reference_spa/tests/requests/auth.rs:9
- TodoComment examples/demo/tests/requests/auth.rs:9
- loco_rs::build::embedded_assets::generate_asset_code (cognitive 48) build/embedded_assets.rs:200
- loco_rs::bgworker::redis::dequeue_with_conn (cognitive 44) src/bgworker/redis.rs:419
- loco_rs::bgworker::redis::requeue (cognitive 37) src/bgworker/redis.rs:938
- loco_rs::bgworker::redis::clear_jobs_older_than (cognitive 36) src/bgworker/redis.rs:794
- loco_rs::schema::create_table_impl (cognitive 33) REDACTED:568
- loco_rs::db::introspect::dump_tables (cognitive 32) src/db/introspect.rs:174
- loco_rs::cli::dispatch_common (cognitive 28) src/cli.rs:833
- loco_rs::bgworker::redis::clear_by_status (cognitive 26) src/bgworker/redis.rs:710
- loco_rs::banner::print_banner (cognitive 16) src/banner.rs:23
- loco_rs::db::entities::fix_entities (cognitive 16) src/db/entities.rs:134
- xtask::docs_syntax::collect (cognitive 30) xtask/src/docs_syntax.rs:184
- xtask::agent_skill::inherent_methods (cognitive 27) xtask/src/agent_skill.rs:481
- xtask::eval::judge_arm (cognitive 27) xtask/src/eval.rs:893
- xtask::eval::salvage_objects (cognitive 26) xtask/src/eval.rs:998
- xtask::eval::parse_cases (cognitive 25) xtask/src/eval.rs:718
- xtask::eval::run (cognitive 23) xtask/src/eval.rs:451
- xtask::eval::report (cognitive 22) xtask/src/eval.rs:1122
- xtask::agent_skill::trait_methods (cognitive 20) xtask/src/agent_skill.rs:435
- xtask::agent_skill::render_type (cognitive 20) xtask/src/agent_skill.rs:849
- xtask::agent_skill::emit (cognitive 16) xtask/src/agent_skill.rs:590
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- FileTooLong: src/eval.rs xtask/src/eval.rs
- FileTooLong: bgworker/redis.rs src/bgworker/redis.rs
- FileTooLong: src/cli.rs src/cli.rs
- FileTooLong: REDACTED REDACTED
- FileTooLong: bgworker/mod.rs src/bgworker/mod.rs
- FileTooLong: src/agent_skill.rs xtask/src/agent_skill.rs
- FileTooLong: REDACTED REDACTED
- FileTooLong: REDACTED REDACTED
- Duplicated block (8 lines × 2) REDACTED:493
- Duplicated block (8 lines × 2) src/bgworker/redis.rs:765
- Duplicated block (8 lines × 2) src/bgworker/redis.rs:831
- Duplicated block (8 lines × 2) src/bgworker/redis.rs:972
- Duplicated block (8 lines × 2) REDACTED:179
- Duplicated block (8 lines × 2) src/cli/tree.rs:47
- loco_rs::build::embedded_assets::generate_asset_code (cyclomatic 26) build/embedded_assets.rs:200
- loco_rs::cli::dispatch_common (cyclomatic 22) src/cli.rs:833
- loco_rs::bgworker::redis::clear_jobs_older_than (cyclomatic 19) src/bgworker/redis.rs:794
- loco_rs::bgworker::redis::requeue (cyclomatic 17) src/bgworker/redis.rs:938
- loco_rs::schema::create_table_impl (cyclomatic 17) REDACTED:568
- Duplicated block (12 lines × 2) REDACTED:448
- Duplicated block (12 lines × 2) REDACTED:512
- Duplicated block (12 lines × 2) REDACTED:774
- Duplicated block (12 lines × 2) REDACTED:586
- Duplicated block (12 lines × 2) REDACTED:611
- Duplicated block (11 lines × 2) REDACTED:796
- Duplicated block (11 lines × 2) src/bgworker/redis.rs:753
- Duplicated block (11 lines × 2) REDACTED:60
- Duplicated block (11 lines × 2) REDACTED:634
- Duplicated block (11 lines × 2) REDACTED:738
- Duplicated block (7 lines × 2) src/bgworker/redis.rs:544
- Duplicated block (7 lines × 2) src/cli.rs:807
- Duplicated block (7 lines × 2) src/controller/monitoring.rs:73
- Duplicated block (7 lines × 2) src/storage/strategies/replicated.rs:247
- Duplicated block (7 lines × 2) evals/tasks/user-search/reference/src/views/user_search.rs:23
- Duplicated block (5 lines × 2) src/bgworker/mod.rs:974
- Duplicated block (5 lines × 2) src/bgworker/redis.rs:742
- Duplicated block (5 lines × 2) REDACTED:133
- Duplicated block (5 lines × 2) REDACTED:844
- Duplicated block (5 lines × 2) src/bgworker/redis.rs:564
- Page without a main landmark loco-new/base_template/assets/static/404.html:1
- Page without a main landmark loco-new/base_template/assets/views/home/hello.html:1
- Page without a main landmark loco-new/base_template/frontend/index.html:2
- Page without a main landmark src/controller/middleware/fallback.html:2
- Duplicated block (9 lines × 2) REDACTED:377
- Duplicated block (9 lines × 2) REDACTED:543
- Duplicated block (9 lines × 2) loco-gen/src/column.rs:265
- Duplicated block (9 lines × 2) REDACTED:835
- Duplicated block (6 lines × 2) REDACTED:504
- Duplicated block (6 lines × 2) src/bgworker/redis.rs:982
- Duplicated block (6 lines × 2) src/boot.rs:455
- Duplicated block (6 lines × 2) src/bgworker/redis.rs:79
- Animation without a prefers-reduced-motion guard website/src/styles/global.css:58
- Animation without a prefers-reduced-motion guard website/src/styles/starlight.css:130
- Hotspot: src/cli.rs src/cli.rs:833
- Hotspot: src/controller/mod.rs src/controller/mod.rs:201
- JobRegistry::run (cognitive 45) src/bgworker/redis.rs:94
- JobRegistry::run (cognitive 44) src/bgworker/sql.rs:252
- MethodTooLong: ColType.to_def REDACTED:328
- MethodTooLong: Error.into_response src/controller/mod.rs:201
- Duplicated block (15 lines × 2) REDACTED:404
- Duplicated block (15 lines × 2) REDACTED:99
- Duplicated block (14 lines × 2) REDACTED:347
- Duplicated block (14 lines × 2) REDACTED:389
- Duplicated block (10 lines × 2) REDACTED:434
- Duplicated block (10 lines × 2) src/mailer/mod.rs:273
- Heading level jumps from h1 to h3 src/controller/middleware/fallback.html:39
- Accessibility enforcement below the top rung
- loco_gen::column::parse_column (cyclomatic 25) loco-gen/src/column.rs:180
- Cors::cors (cyclomatic 19) src/controller/middleware/cors.rs:89
- xtask::agent_skill::render_type (cyclomatic 16) xtask/src/agent_skill.rs:849
- Cors::cors (cognitive 30) src/controller/middleware/cors.rs:89
- loco_gen::column::parse_column (cognitive 27) loco-gen/src/column.rs:180
- LocalStore::list (cognitive 20) src/storage/drivers/local.rs:148
- loco::bin::main::main (cognitive 20) loco-new/src/bin/main.rs:74
- REDACTED
- FunctionTooLong: loco_gen::column::parse_column loco-gen/src/column.rs:180
- REDACTED
- REDACTED
- Near-duplicate member pair (38 shared lines) REDACTED:376
- Near-duplicate member pair (26 shared lines) REDACTED:488
- Members sharing a duplicated core (4 members, 50+ identical tokens) src/bgworker/redis.rs:710
- Duplicated block (29 lines × 2) src/mailer/email_sender.rs:135
- Duplicated block (22 lines × 2) src/bgworker/redis.rs:714
- Duplicated block (20–22 lines × 2) src/cli.rs:784
- Duplicated block (18–21 lines × 2) REDACTED:697
- Duplicated block (16 lines × 2) src/bgworker/mod.rs:1113
- Duplicated block (15 lines × 3) REDACTED:151
- Duplicated block (10–15 lines × 2) src/bgworker/redis.rs:955
- Duplicated block (11–13 lines × 3) src/bgworker/redis.rs:729
- Duplicated block (10 lines × 3) src/mailer/mod.rs:192
- Duplicated block (7–9 lines × 4) src/bgworker/redis.rs:754
- Duplicated block (7–9 lines × 2) src/mailer/email_sender.rs:119
- Duplicated block (8–9 lines × 2) src/storage/drivers/aws.rs:64
- Duplicated block (6–7 lines × 2) REDACTED:559
- Duplicated block (6 lines × 3) src/cli.rs:725
- Duplicated block (5 lines × 5) src/bgworker/redis.rs:755
- Duplicated block (9 lines × 6) evals/tasks/api-key-endpoint/wiring/src/app.rs:28
- Duplicated block (5 lines × 6) evals/tasks/api-key-endpoint/wiring/src/app.rs:73
- Off the main sequence: loco-gen
- Coverage not measured — JavaScript/TypeScript suite
Minor — 63 finding(s)
- Orphaned file src/testing/selector.rs:1
- Orphaned file src/cache/mod.rs:1
- Orphaned file src/controller/monitoring.rs:1
- Orphaned file loco-new/src/wizard.rs:1
- Orphaned file loco-new/base_template/src/models/users.rs:1
- Orphaned file loco-new/src/generator/mod.rs:1
- Orphaned file src/testing/request.rs:1
- Orphaned file loco-new/src/generator/executer/filesystem.rs:1
- Orphaned file loco-new/base_template/src/controllers/auth.rs:1
- Orphaned file src/task.rs:1
- Orphaned file src/cache/drivers/redis.rs:1
- Orphaned file loco-gen/src/template.rs:1
- Orphaned file loco-new/src/generator/template.rs:1
- Orphaned file src/data.rs:1
- Orphaned file loco-new/src/generator/executer/inmem.rs:1
- Orphaned file src/model/query/dsl/date_range.rs:1
- Orphaned file src/tests_cfg/db.rs:1
- Orphaned file src/controller/middleware/logger.rs:1
- Orphaned file loco-new/base_template/src/tasks/user_create.rs:1
- Orphaned file src/controller/middleware/catch_panic.rs:1
- Orphaned file src/tests_cfg/config.rs:1
- Orphaned file src/controller/middleware/powered_by.rs:1
- Orphaned file src/cache/drivers/null.rs:1
- Orphaned file loco-new/base_template/src/mailers/auth.rs:1
- Interpolated log message defeats structured logging src/boot.rs:348
- Interpolated log message defeats structured logging REDACTED:973
- Interpolated log message defeats structured logging REDACTED:996
- Interpolated log message defeats structured logging src/db/entities.rs:44
- Interpolated log message defeats structured logging src/controller/app_routes.rs:301
- Interpolated log message defeats structured logging src/controller/describe.rs:36
- Interpolated log message defeats structured logging src/controller/views/engine_embedded.rs:112
- Interpolated log message defeats structured logging src/controller/views/engine_embedded.rs:129
- Interpolated log message defeats structured logging src/controller/views/engine_embedded.rs:132
- Interpolated log message defeats structured logging src/controller/views/engine_embedded.rs:175
- Interpolated log message defeats structured logging src/controller/views/engine_embedded.rs:178
- Interpolated log message defeats structured logging src/controller/middleware/request_id.rs:93
- Interpolated log message defeats structured logging src/controller/middleware/static_assets_embedded.rs:87
- Interpolated log message defeats structured logging src/controller/middleware/static_assets_embedded.rs:93
- Interpolated log message defeats structured logging src/controller/middleware/static_assets_embedded.rs:97
- Interpolated log message defeats structured logging src/controller/middleware/static_assets_embedded.rs:101
- Interpolated log message defeats structured logging src/controller/middleware/static_assets_embedded.rs:126
- Interpolated log message defeats structured logging src/controller/middleware/static_assets_embedded.rs:152
- Interpolated log message defeats structured logging src/controller/extractor/auth.rs:179
- Interpolated log message defeats structured logging src/controller/extractor/shared_store.rs:23
- Duplicated predicate website/scripts/convert-frontmatter.mjs:17
- Duplicated predicate src/storage/drivers/local.rs:150
- Duplicated predicate REDACTED:1792
- Duplicated predicate src/config/auth.rs:321
- README/code drift CONTRIBUTING.md:111
- README/code drift loco-new/base_template/README.md:53
- No named authorization policies
- Partial data-retention evidence
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- No ADRs found
- Projects may be oversized for their cohesion
- Further orphaned files (smaller)
- REDACTED
- No ADRs
- Large public API surface
- Logging is not universal
- No app-layer HTTPS enforcement detected
- No security response headers detected
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-de00c2db1ffe49478f51b2c78fe64392/history.json --exit-code 0 --source . | 14 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-de00c2db1ffe49478f51b2c78fe64392/tree.json --exit-code 0 --source . | 3 | 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/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude .cargo --exclude .vscode --exclude evals/judge --exclude evals/tasks/deactivation-mailer/reference/src/mailers/deactivation --exclude evals/tasks/nightly-digest/reference/append/config --exclude evals/tasks/user-search/reference/append/config --exclude evals/tasks/user-search/wiring/config --exclude examples/demo/.cargo --exclude examples/demo/assets --exclude examples/demo/config --exclude examples/demo/src/fixtures --exclude examples/demo/src/mailers/auth --exclude examples/demo/src/models/_entities --exclude examples/demo/tests/models/snapshots --exclude examples/demo/tests/requests/snapshots --exclude examples/reference_spa/.cargo --exclude examples/reference_spa/config --exclude examples/reference_spa/frontend --exclude examples/reference_spa/src/fixtures --exclude examples/reference_spa/src/mailers/auth --exclude examples/reference_spa/src/models/_entities --exclude examples/reference_spa/tests/models/snapshots --exclude examples/reference_spa/tests/requests/snapshots --exclude loco-gen/src/templates --exclude loco-gen/tests/snapshots --exclude loco-gen/tests/templates/snapshots --exclude loco-new/base_template/.cargo --exclude loco-new/base_template/.claude --exclude loco-new/base_template/assets --exclude loco-new/base_template/config --exclude loco-new/base_template/examples --exclude loco-new/base_template/frontend --exclude loco-new/base_template/src/bin --exclude loco-new/base_template/src/data --exclude loco-new/base_template/src/fixtures --exclude loco-new/base_template/src/mailers/auth --exclude loco-new/base_template/src/models/_entities --exclude loco-new/base_template/tests/models --exclude loco-new/base_template/tests/requests --exclude loco-new/base_template/tests/tasks --exclude loco-new/tests/templates/snapshots --exclude media --exclude skills --exclude src/auth/oauth/snapshots --exclude src/auth/snapshots --exclude src/bgworker/snapshots --exclude src/controller/extractor/snapshots --exclude src/controller/middleware/snapshots --exclude src/controller/snapshots --exclude src/db/snapshots --exclude src/mailer/snapshots --exclude src/snapshots --exclude tests/build_scripts/snapshots --exclude tests/controller/snapshots --exclude tests/fixtures --exclude website . | 84 | 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/** . --skip-db-update | 2 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep --config /opt/semgrep-rules/gdpr.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude .cargo --exclude .vscode --exclude evals/judge --exclude evals/tasks/deactivation-mailer/reference/src/mailers/deactivation --exclude evals/tasks/nightly-digest/reference/append/config --exclude evals/tasks/user-search/reference/append/config --exclude evals/tasks/user-search/wiring/config --exclude examples/demo/.cargo --exclude examples/demo/assets --exclude examples/demo/config --exclude examples/demo/src/fixtures --exclude examples/demo/src/mailers/auth --exclude examples/demo/src/models/_entities --exclude examples/demo/tests/models/snapshots --exclude examples/demo/tests/requests/snapshots --exclude examples/reference_spa/.cargo --exclude examples/reference_spa/config --exclude examples/reference_spa/frontend --exclude examples/reference_spa/src/fixtures --exclude examples/reference_spa/src/mailers/auth --exclude examples/reference_spa/src/models/_entities --exclude examples/reference_spa/tests/models/snapshots --exclude examples/reference_spa/tests/requests/snapshots --exclude loco-gen/src/templates --exclude loco-gen/tests/snapshots --exclude loco-gen/tests/templates/snapshots --exclude loco-new/base_template/.cargo --exclude loco-new/base_template/.claude --exclude loco-new/base_template/assets --exclude loco-new/base_template/config --exclude loco-new/base_template/examples --exclude loco-new/base_template/frontend --exclude loco-new/base_template/src/bin --exclude loco-new/base_template/src/data --exclude loco-new/base_template/src/fixtures --exclude loco-new/base_template/src/mailers/auth --exclude loco-new/base_template/src/models/_entities --exclude loco-new/base_template/tests/models --exclude loco-new/base_template/tests/requests --exclude loco-new/base_template/tests/tasks --exclude loco-new/tests/templates/snapshots --exclude media --exclude skills --exclude src/auth/oauth/snapshots --exclude src/auth/snapshots --exclude src/bgworker/snapshots --exclude src/controller/extractor/snapshots --exclude src/controller/middleware/snapshots --exclude src/controller/snapshots --exclude src/db/snapshots --exclude src/mailer/snapshots --exclude src/snapshots --exclude tests/build_scripts/snapshots --exclude tests/controller/snapshots --exclude tests/fixtures --exclude website . | 9 | artifacts/raw/semgrep-gdpr.json |
| 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/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |