Executive summary
marshiyar/myUpscaler falls short of our standard for a preview release, in part because we found no logging, tracing or health checks in the code. It scores 56.7 out of 100 and is rated Adequate, and all 29 of its critical findings are security problems in the build pipeline.
Production Readiness, at 38.0, is the weakest lens and counts most in the score. The best first step is adding a diagnostic log, worth about 8.2 points. Recording design decisions comes next, worth about 3.2 points. Raising Production Readiness to 62 would lift the score to about 67.8.
Twenty-nine pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Pinning each tool to an exact version would close this risk.
The product code is 14,055 lines, about €19,000 to rebuild.
If Production Readiness rose from 38.0 to 62, the lowest score rated Strong, the score would rise from 56.7 to about 67.8.
Rebuild cost: about €19,000 · Estimate
| Cost to rebuild | €6,300 to €31,000, for 104 to 331 hours of work, about 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 57. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 14,055 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 desktop.scripts | 2 myupscaler.progress | 3 myupscaler.screenshot | 4 repository | 5 up60p | 6 up60p.engine | 7 up60p.engine.absent | 8 up60p.engine.json | 9 up60p.frame | 10 up60p.options | 11 up60p.par | 12 up60p.png | 13 myupscaler | 14 myupscaler.preview | 15 myupscaler.settings | 16 up60p.bin.up60p | 17 up60p.filters | 18 up60p.header | 19 up60p.filters.atadenoise | 20 up60p.filters.bm3d | 21 up60p.filters.deband | 22 up60p.filters.deblock | 23 up60p.filters.decimate | 24 up60p.filters.eq | 25 up60p.filters.grain | 26 up60p.filters.hqdn3d | 27 up60p.filters.interpolate | 28 up60p.filters.nlmeans | 29 up60p.filters.scale | 30 up60p.filters.sharpen | 31 up60p.pipeline | 32 up60p.job |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 desktop.scripts | ||||||||||||||||||||||||||||||||
| 2 myupscaler.progress | ||||||||||||||||||||||||||||||||
| 3 myupscaler.screenshot | ||||||||||||||||||||||||||||||||
| 4 repository | ||||||||||||||||||||||||||||||||
| 5 up60p | ||||||||||||||||||||||||||||||||
| 6 up60p.engine | ||||||||||||||||||||||||||||||||
| 7 up60p.engine.absent | ||||||||||||||||||||||||||||||||
| 8 up60p.engine.json | ||||||||||||||||||||||||||||||||
| 9 up60p.frame | ||||||||||||||||||||||||||||||||
| 10 up60p.options | ||||||||||||||||||||||||||||||||
| 11 up60p.par | ||||||||||||||||||||||||||||||||
| 12 up60p.png | ||||||||||||||||||||||||||||||||
| 13 myupscaler | 1 | 1 | ||||||||||||||||||||||||||||||
| 14 myupscaler.preview | 1 | 2 | ||||||||||||||||||||||||||||||
| 15 myupscaler.settings | 1 | |||||||||||||||||||||||||||||||
| 16 up60p.bin.up60p | 1 | |||||||||||||||||||||||||||||||
| 17 up60p.filters | 4 | |||||||||||||||||||||||||||||||
| 18 up60p.header | 1 | |||||||||||||||||||||||||||||||
| 19 up60p.filters.atadenoise | 1 | 1 | ||||||||||||||||||||||||||||||
| 20 up60p.filters.bm3d | 3 | 1 | ||||||||||||||||||||||||||||||
| 21 up60p.filters.deband | 2 | 2 | ||||||||||||||||||||||||||||||
| 22 up60p.filters.deblock | 2 | 1 | ||||||||||||||||||||||||||||||
| 23 up60p.filters.decimate | 2 | 1 | ||||||||||||||||||||||||||||||
| 24 up60p.filters.eq | 1 | 1 | ||||||||||||||||||||||||||||||
| 25 up60p.filters.grain | 1 | 1 | ||||||||||||||||||||||||||||||
| 26 up60p.filters.hqdn3d | 2 | 1 | ||||||||||||||||||||||||||||||
| 27 up60p.filters.interpolate | 5 | 1 | ||||||||||||||||||||||||||||||
| 28 up60p.filters.nlmeans | 2 | 1 | ||||||||||||||||||||||||||||||
| 29 up60p.filters.scale | 2 | 1 | ||||||||||||||||||||||||||||||
| 30 up60p.filters.sharpen | 3 | 2 | ||||||||||||||||||||||||||||||
| 31 up60p.pipeline | 1 | 2 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||
| 32 up60p.job | 3 | 2 | 1 |
13→2 myupscaler uses myupscaler.progress✕
- Connections
- 1 pair of types, where a type in myupscaler uses a type in myupscaler.progress.
- The types involved
myupscaler.State→myupscaler.progress.Progress
- Direction
- myupscaler uses myupscaler.progress, so a change to myupscaler.progress can break myupscaler, while a change to myupscaler can't break myupscaler.progress.
- Position
- Below the diagonal: myupscaler uses a module listed above it, which is the healthy direction.
13→10 myupscaler uses up60p.options✕
- Connections
- 1 pair of types, where a type in myupscaler uses a type in up60p.options.
- The types involved
myupscaler.myupscaler$module→up60p.options.Options
- Direction
- myupscaler uses up60p.options, so a change to up60p.options can break myupscaler, while a change to myupscaler can't break up60p.options.
- Position
- Below the diagonal: myupscaler uses a module listed above it, which is the healthy direction.
14→6 myupscaler.preview uses up60p.engine✕
- Connections
- 1 pair of types, where a type in myupscaler.preview uses a type in up60p.engine.
- The types involved
myupscaler.preview.Open→up60p.engine.Video
- Direction
- myupscaler.preview uses up60p.engine, so a change to up60p.engine can break myupscaler.preview, while a change to myupscaler.preview can't break up60p.engine.
- Position
- Below the diagonal: myupscaler.preview uses a module listed above it, which is the healthy direction.
14→10 myupscaler.preview uses up60p.options✕
- Connections
- 2 pairs of types, where a type in myupscaler.preview uses a type in up60p.options.
- The types involved
myupscaler.preview.Request→up60p.options.Optionsmyupscaler.preview.preview$module→up60p.options.Options
- Direction
- myupscaler.preview uses up60p.options, so a change to up60p.options can break myupscaler.preview, while a change to myupscaler.preview can't break up60p.options.
- Position
- Below the diagonal: myupscaler.preview uses a module listed above it, which is the healthy direction.
15→10 myupscaler.settings uses up60p.options✕
- Connections
- 1 pair of types, where a type in myupscaler.settings uses a type in up60p.options.
- The types involved
myupscaler.settings.settings$module→up60p.options.Options
- Direction
- myupscaler.settings uses up60p.options, so a change to up60p.options can break myupscaler.settings, while a change to myupscaler.settings can't break up60p.options.
- Position
- Below the diagonal: myupscaler.settings uses a module listed above it, which is the healthy direction.
16→10 up60p.bin.up60p uses up60p.options✕
- Connections
- 1 pair of types, where a type in up60p.bin.up60p uses a type in up60p.options.
- The types involved
up60p.bin.up60p.up60p$module→up60p.options.Options
- Direction
- up60p.bin.up60p uses up60p.options, so a change to up60p.options can break up60p.bin.up60p, while a change to up60p.bin.up60p can't break up60p.options.
- Position
- Below the diagonal: up60p.bin.up60p uses a module listed above it, which is the healthy direction.
17→9 up60p.filters uses up60p.frame✕
- Connections
- 4 pairs of types, where a type in up60p.filters uses a type in up60p.frame.
- The types involved
up60p.filters.Chain→up60p.frame.Frameup60p.filters.Filter→up60p.frame.Frameup60p.filters.Spatial→up60p.frame.Frameup60p.filters.filters$module→up60p.frame.Plane
- Direction
- up60p.filters uses up60p.frame, so a change to up60p.frame can break up60p.filters, while a change to up60p.filters can't break up60p.frame.
- Position
- Below the diagonal: up60p.filters uses a module listed above it, which is the healthy direction.
18→10 up60p.header uses up60p.options✕
- Connections
- 1 pair of types, where a type in up60p.header uses a type in up60p.options.
- The types involved
up60p.header.header$module→up60p.options.Kind
- Direction
- up60p.header uses up60p.options, so a change to up60p.options can break up60p.header, while a change to up60p.header can't break up60p.options.
- Position
- Below the diagonal: up60p.header uses a module listed above it, which is the healthy direction.
19→9 up60p.filters.atadenoise uses up60p.frame✕
- Connections
- 1 pair of types, where a type in up60p.filters.atadenoise uses a type in up60p.frame.
- The types involved
up60p.filters.atadenoise.AtaDenoise→up60p.frame.Frame
- Direction
- up60p.filters.atadenoise uses up60p.frame, so a change to up60p.frame can break up60p.filters.atadenoise, while a change to up60p.filters.atadenoise can't break up60p.frame.
- Position
- Below the diagonal: up60p.filters.atadenoise uses a module listed above it, which is the healthy direction.
19→17 up60p.filters.atadenoise uses up60p.filters✕
- Connections
- 1 pair of types, where a type in up60p.filters.atadenoise uses a type in up60p.filters.
- The types involved
up60p.filters.atadenoise.AtaDenoise→up60p.filters.Filter
- Direction
- up60p.filters.atadenoise uses up60p.filters, so a change to up60p.filters can break up60p.filters.atadenoise, while a change to up60p.filters.atadenoise can't break up60p.filters.
- Position
- Below the diagonal: up60p.filters.atadenoise uses a module listed above it, which is the healthy direction.
20→9 up60p.filters.bm3d uses up60p.frame✕
- Connections
- 3 pairs of types, where a type in up60p.filters.bm3d uses a type in up60p.frame.
- The types involved
up60p.filters.bm3d.Bm3d→up60p.frame.Frameup60p.filters.bm3d.Bm3d→up60p.frame.Planeup60p.filters.bm3d.bm3d$module→up60p.frame.Plane
- Direction
- up60p.filters.bm3d uses up60p.frame, so a change to up60p.frame can break up60p.filters.bm3d, while a change to up60p.filters.bm3d can't break up60p.frame.
- Position
- Below the diagonal: up60p.filters.bm3d uses a module listed above it, which is the healthy direction.
20→17 up60p.filters.bm3d uses up60p.filters✕
- Connections
- 1 pair of types, where a type in up60p.filters.bm3d uses a type in up60p.filters.
- The types involved
up60p.filters.bm3d.Bm3d→up60p.filters.Spatial
- Direction
- up60p.filters.bm3d uses up60p.filters, so a change to up60p.filters can break up60p.filters.bm3d, while a change to up60p.filters.bm3d can't break up60p.filters.
- Position
- Below the diagonal: up60p.filters.bm3d uses a module listed above it, which is the healthy direction.
21→9 up60p.filters.deband uses up60p.frame✕
- Connections
- 2 pairs of types, where a type in up60p.filters.deband uses a type in up60p.frame.
- The types involved
up60p.filters.deband.Deband→up60p.frame.Frameup60p.filters.deband.GradFun→up60p.frame.Frame
- Direction
- up60p.filters.deband uses up60p.frame, so a change to up60p.frame can break up60p.filters.deband, while a change to up60p.filters.deband can't break up60p.frame.
- Position
- Below the diagonal: up60p.filters.deband uses a module listed above it, which is the healthy direction.
21→17 up60p.filters.deband uses up60p.filters✕
- Connections
- 2 pairs of types, where a type in up60p.filters.deband uses a type in up60p.filters.
- The types involved
up60p.filters.deband.Deband→up60p.filters.Spatialup60p.filters.deband.GradFun→up60p.filters.Spatial
- Direction
- up60p.filters.deband uses up60p.filters, so a change to up60p.filters can break up60p.filters.deband, while a change to up60p.filters.deband can't break up60p.filters.
- Position
- Below the diagonal: up60p.filters.deband uses a module listed above it, which is the healthy direction.
22→9 up60p.filters.deblock uses up60p.frame✕
- Connections
- 2 pairs of types, where a type in up60p.filters.deblock uses a type in up60p.frame.
- The types involved
up60p.filters.deblock.Deblock→up60p.frame.Frameup60p.filters.deblock.Deblock→up60p.frame.Plane
- Direction
- up60p.filters.deblock uses up60p.frame, so a change to up60p.frame can break up60p.filters.deblock, while a change to up60p.filters.deblock can't break up60p.frame.
- Position
- Below the diagonal: up60p.filters.deblock uses a module listed above it, which is the healthy direction.
22→17 up60p.filters.deblock uses up60p.filters✕
- Connections
- 1 pair of types, where a type in up60p.filters.deblock uses a type in up60p.filters.
- The types involved
up60p.filters.deblock.Deblock→up60p.filters.Spatial
- Direction
- up60p.filters.deblock uses up60p.filters, so a change to up60p.filters can break up60p.filters.deblock, while a change to up60p.filters.deblock can't break up60p.filters.
- Position
- Below the diagonal: up60p.filters.deblock uses a module listed above it, which is the healthy direction.
23→9 up60p.filters.decimate uses up60p.frame✕
- Connections
- 2 pairs of types, where a type in up60p.filters.decimate uses a type in up60p.frame.
- The types involved
up60p.filters.decimate.Decimate→up60p.frame.Frameup60p.filters.decimate.Decimate→up60p.frame.Plane
- Direction
- up60p.filters.decimate uses up60p.frame, so a change to up60p.frame can break up60p.filters.decimate, while a change to up60p.filters.decimate can't break up60p.frame.
- Position
- Below the diagonal: up60p.filters.decimate uses a module listed above it, which is the healthy direction.
23→17 up60p.filters.decimate uses up60p.filters✕
- Connections
- 1 pair of types, where a type in up60p.filters.decimate uses a type in up60p.filters.
- The types involved
up60p.filters.decimate.Decimate→up60p.filters.Filter
- Direction
- up60p.filters.decimate uses up60p.filters, so a change to up60p.filters can break up60p.filters.decimate, while a change to up60p.filters.decimate can't break up60p.filters.
- Position
- Below the diagonal: up60p.filters.decimate uses a module listed above it, which is the healthy direction.
24→9 up60p.filters.eq uses up60p.frame✕
- Connections
- 1 pair of types, where a type in up60p.filters.eq uses a type in up60p.frame.
- The types involved
up60p.filters.eq.Eq→up60p.frame.Frame
- Direction
- up60p.filters.eq uses up60p.frame, so a change to up60p.frame can break up60p.filters.eq, while a change to up60p.filters.eq can't break up60p.frame.
- Position
- Below the diagonal: up60p.filters.eq uses a module listed above it, which is the healthy direction.
24→17 up60p.filters.eq uses up60p.filters✕
- Connections
- 1 pair of types, where a type in up60p.filters.eq uses a type in up60p.filters.
- The types involved
up60p.filters.eq.Eq→up60p.filters.Spatial
- Direction
- up60p.filters.eq uses up60p.filters, so a change to up60p.filters can break up60p.filters.eq, while a change to up60p.filters.eq can't break up60p.filters.
- Position
- Below the diagonal: up60p.filters.eq uses a module listed above it, which is the healthy direction.
25→9 up60p.filters.grain uses up60p.frame✕
- Connections
- 1 pair of types, where a type in up60p.filters.grain uses a type in up60p.frame.
- The types involved
up60p.filters.grain.Grain→up60p.frame.Frame
- Direction
- up60p.filters.grain uses up60p.frame, so a change to up60p.frame can break up60p.filters.grain, while a change to up60p.filters.grain can't break up60p.frame.
- Position
- Below the diagonal: up60p.filters.grain uses a module listed above it, which is the healthy direction.
25→17 up60p.filters.grain uses up60p.filters✕
- Connections
- 1 pair of types, where a type in up60p.filters.grain uses a type in up60p.filters.
- The types involved
up60p.filters.grain.Grain→up60p.filters.Spatial
- Direction
- up60p.filters.grain uses up60p.filters, so a change to up60p.filters can break up60p.filters.grain, while a change to up60p.filters.grain can't break up60p.filters.
- Position
- Below the diagonal: up60p.filters.grain uses a module listed above it, which is the healthy direction.
26→9 up60p.filters.hqdn3d uses up60p.frame✕
- Connections
- 2 pairs of types, where a type in up60p.filters.hqdn3d uses a type in up60p.frame.
- The types involved
up60p.filters.hqdn3d.Hqdn3d→up60p.frame.Frameup60p.filters.hqdn3d.Hqdn3d→up60p.frame.Plane
- Direction
- up60p.filters.hqdn3d uses up60p.frame, so a change to up60p.frame can break up60p.filters.hqdn3d, while a change to up60p.filters.hqdn3d can't break up60p.frame.
- Position
- Below the diagonal: up60p.filters.hqdn3d uses a module listed above it, which is the healthy direction.
26→17 up60p.filters.hqdn3d uses up60p.filters✕
- Connections
- 1 pair of types, where a type in up60p.filters.hqdn3d uses a type in up60p.filters.
- The types involved
up60p.filters.hqdn3d.Hqdn3d→up60p.filters.Filter
- Direction
- up60p.filters.hqdn3d uses up60p.filters, so a change to up60p.filters can break up60p.filters.hqdn3d, while a change to up60p.filters.hqdn3d can't break up60p.filters.
- Position
- Below the diagonal: up60p.filters.hqdn3d uses a module listed above it, which is the healthy direction.
27→9 up60p.filters.interpolate uses up60p.frame✕
- Connections
- 5 pairs of types, where a type in up60p.filters.interpolate uses a type in up60p.frame.
- The types involved
up60p.filters.interpolate.MotionField→up60p.frame.Frameup60p.filters.interpolate.MotionField→up60p.frame.Planeup60p.filters.interpolate.Retimer→up60p.frame.Frameup60p.filters.interpolate.interpolate$module→up60p.frame.Frameup60p.filters.interpolate.interpolate$module→up60p.frame.Plane
- Direction
- up60p.filters.interpolate uses up60p.frame, so a change to up60p.frame can break up60p.filters.interpolate, while a change to up60p.filters.interpolate can't break up60p.frame.
- Position
- Below the diagonal: up60p.filters.interpolate uses a module listed above it, which is the healthy direction.
27→17 up60p.filters.interpolate uses up60p.filters✕
- Connections
- 1 pair of types, where a type in up60p.filters.interpolate uses a type in up60p.filters.
- The types involved
up60p.filters.interpolate.Retimer→up60p.filters.Filter
- Direction
- up60p.filters.interpolate uses up60p.filters, so a change to up60p.filters can break up60p.filters.interpolate, while a change to up60p.filters.interpolate can't break up60p.filters.
- Position
- Below the diagonal: up60p.filters.interpolate uses a module listed above it, which is the healthy direction.
28→9 up60p.filters.nlmeans uses up60p.frame✕
- Connections
- 2 pairs of types, where a type in up60p.filters.nlmeans uses a type in up60p.frame.
- The types involved
up60p.filters.nlmeans.NlMeans→up60p.frame.Frameup60p.filters.nlmeans.NlMeans→up60p.frame.Plane
- Direction
- up60p.filters.nlmeans uses up60p.frame, so a change to up60p.frame can break up60p.filters.nlmeans, while a change to up60p.filters.nlmeans can't break up60p.frame.
- Position
- Below the diagonal: up60p.filters.nlmeans uses a module listed above it, which is the healthy direction.
28→17 up60p.filters.nlmeans uses up60p.filters✕
- Connections
- 1 pair of types, where a type in up60p.filters.nlmeans uses a type in up60p.filters.
- The types involved
up60p.filters.nlmeans.NlMeans→up60p.filters.Spatial
- Direction
- up60p.filters.nlmeans uses up60p.filters, so a change to up60p.filters can break up60p.filters.nlmeans, while a change to up60p.filters.nlmeans can't break up60p.filters.
- Position
- Below the diagonal: up60p.filters.nlmeans uses a module listed above it, which is the healthy direction.
29→9 up60p.filters.scale uses up60p.frame✕
- Connections
- 2 pairs of types, where a type in up60p.filters.scale uses a type in up60p.frame.
- The types involved
up60p.filters.scale.Lanczos→up60p.frame.Frameup60p.filters.scale.scale$module→up60p.frame.Plane
- Direction
- up60p.filters.scale uses up60p.frame, so a change to up60p.frame can break up60p.filters.scale, while a change to up60p.filters.scale can't break up60p.frame.
- Position
- Below the diagonal: up60p.filters.scale uses a module listed above it, which is the healthy direction.
29→17 up60p.filters.scale uses up60p.filters✕
- Connections
- 1 pair of types, where a type in up60p.filters.scale uses a type in up60p.filters.
- The types involved
up60p.filters.scale.Lanczos→up60p.filters.Spatial
- Direction
- up60p.filters.scale uses up60p.filters, so a change to up60p.filters can break up60p.filters.scale, while a change to up60p.filters.scale can't break up60p.filters.
- Position
- Below the diagonal: up60p.filters.scale uses a module listed above it, which is the healthy direction.
30→9 up60p.filters.sharpen uses up60p.frame✕
- Connections
- 3 pairs of types, where a type in up60p.filters.sharpen uses a type in up60p.frame.
- The types involved
up60p.filters.sharpen.Cas→up60p.frame.Frameup60p.filters.sharpen.Unsharp→up60p.frame.Frameup60p.filters.sharpen.Unsharp→up60p.frame.Plane
- Direction
- up60p.filters.sharpen uses up60p.frame, so a change to up60p.frame can break up60p.filters.sharpen, while a change to up60p.filters.sharpen can't break up60p.frame.
- Position
- Below the diagonal: up60p.filters.sharpen uses a module listed above it, which is the healthy direction.
30→17 up60p.filters.sharpen uses up60p.filters✕
- Connections
- 2 pairs of types, where a type in up60p.filters.sharpen uses a type in up60p.filters.
- The types involved
up60p.filters.sharpen.Cas→up60p.filters.Spatialup60p.filters.sharpen.Unsharp→up60p.filters.Spatial
- Direction
- up60p.filters.sharpen uses up60p.filters, so a change to up60p.filters can break up60p.filters.sharpen, while a change to up60p.filters.sharpen can't break up60p.filters.
- Position
- Below the diagonal: up60p.filters.sharpen uses a module listed above it, which is the healthy direction.
31→6 up60p.pipeline uses up60p.engine✕
- Connections
- 1 pair of types, where a type in up60p.pipeline uses a type in up60p.engine.
- The types involved
up60p.pipeline.pipeline$module→up60p.engine.Quality
- Direction
- up60p.pipeline uses up60p.engine, so a change to up60p.engine can break up60p.pipeline, while a change to up60p.pipeline can't break up60p.engine.
- Position
- Below the diagonal: up60p.pipeline uses a module listed above it, which is the healthy direction.
31→10 up60p.pipeline uses up60p.options✕
- Connections
- 2 pairs of types, where a type in up60p.pipeline uses a type in up60p.options.
- The types involved
up60p.pipeline.Timing→up60p.options.Optionsup60p.pipeline.pipeline$module→up60p.options.Options
- Direction
- up60p.pipeline uses up60p.options, so a change to up60p.options can break up60p.pipeline, while a change to up60p.pipeline can't break up60p.options.
- Position
- Below the diagonal: up60p.pipeline uses a module listed above it, which is the healthy direction.
31→17 up60p.pipeline uses up60p.filters✕
- Connections
- 1 pair of types, where a type in up60p.pipeline uses a type in up60p.filters.
- The types involved
up60p.pipeline.Plan→up60p.filters.Chain
- Direction
- up60p.pipeline uses up60p.filters, so a change to up60p.filters can break up60p.pipeline, while a change to up60p.pipeline can't break up60p.filters.
- Position
- Below the diagonal: up60p.pipeline uses a module listed above it, which is the healthy direction.
31→19 up60p.pipeline uses up60p.filters.atadenoise✕
- Connections
- 1 pair of types, where a type in up60p.pipeline uses a type in up60p.filters.atadenoise.
- The types involved
up60p.pipeline.pipeline$module→up60p.filters.atadenoise.AtaDenoise
- Direction
- up60p.pipeline uses up60p.filters.atadenoise, so a change to up60p.filters.atadenoise can break up60p.pipeline, while a change to up60p.pipeline can't break up60p.filters.atadenoise.
- Position
- Below the diagonal: up60p.pipeline uses a module listed above it, which is the healthy direction.
31→20 up60p.pipeline uses up60p.filters.bm3d✕
- Connections
- 1 pair of types, where a type in up60p.pipeline uses a type in up60p.filters.bm3d.
- The types involved
up60p.pipeline.pipeline$module→up60p.filters.bm3d.Bm3d
- Direction
- up60p.pipeline uses up60p.filters.bm3d, so a change to up60p.filters.bm3d can break up60p.pipeline, while a change to up60p.pipeline can't break up60p.filters.bm3d.
- Position
- Below the diagonal: up60p.pipeline uses a module listed above it, which is the healthy direction.
31→26 up60p.pipeline uses up60p.filters.hqdn3d✕
- Connections
- 1 pair of types, where a type in up60p.pipeline uses a type in up60p.filters.hqdn3d.
- The types involved
up60p.pipeline.pipeline$module→up60p.filters.hqdn3d.Hqdn3d
- Direction
- up60p.pipeline uses up60p.filters.hqdn3d, so a change to up60p.filters.hqdn3d can break up60p.pipeline, while a change to up60p.pipeline can't break up60p.filters.hqdn3d.
- Position
- Below the diagonal: up60p.pipeline uses a module listed above it, which is the healthy direction.
31→28 up60p.pipeline uses up60p.filters.nlmeans✕
- Connections
- 1 pair of types, where a type in up60p.pipeline uses a type in up60p.filters.nlmeans.
- The types involved
up60p.pipeline.pipeline$module→up60p.filters.nlmeans.NlMeans
- Direction
- up60p.pipeline uses up60p.filters.nlmeans, so a change to up60p.filters.nlmeans can break up60p.pipeline, while a change to up60p.pipeline can't break up60p.filters.nlmeans.
- Position
- Below the diagonal: up60p.pipeline uses a module listed above it, which is the healthy direction.
32→6 up60p.job uses up60p.engine✕
- Connections
- 3 pairs of types, where a type in up60p.job uses a type in up60p.engine.
- The types involved
up60p.job.JobError→up60p.engine.EngineErrorup60p.job.job$module→up60p.engine.Mp4Writerup60p.job.job$module→up60p.engine.Video
- Direction
- up60p.job uses up60p.engine, so a change to up60p.engine can break up60p.job, while a change to up60p.job can't break up60p.engine.
- Position
- Below the diagonal: up60p.job uses a module listed above it, which is the healthy direction.
32→10 up60p.job uses up60p.options✕
- Connections
- 2 pairs of types, where a type in up60p.job uses a type in up60p.options.
- The types involved
up60p.job.Job→up60p.options.Optionsup60p.job.job$module→up60p.options.Options
- Direction
- up60p.job uses up60p.options, so a change to up60p.options can break up60p.job, while a change to up60p.job can't break up60p.options.
- Position
- Below the diagonal: up60p.job uses a module listed above it, which is the healthy direction.
32→31 up60p.job uses up60p.pipeline✕
- Connections
- 1 pair of types, where a type in up60p.job uses a type in up60p.pipeline.
- The types involved
up60p.job.Job→up60p.pipeline.Plan
- Direction
- up60p.job uses up60p.pipeline, so a change to up60p.pipeline can break up60p.job, while a change to up60p.job can't break up60p.pipeline.
- Position
- Below the diagonal: up60p.job uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 29 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 14 | Medium |
Roadmap
Top priorities: Write a diagnostic trail the user can hand back with a bug report: log through `os.Logger` (one per subsystem), which the unified log keeps and a sysdiagnose carries to you. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce; Automate the release in CI — a deploy stage for a service (Helm/Kubernetes manifests or an equivalent rollout), or a tag-triggered publish job for an artifact — so releases are repeatable and reversible; Enable Dependabot/Renovate or a dependency-review gate.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Write a diagnostic trail the user can hand back with a bug report: log through `os.Logger` (one per subsystem), which the unified log keeps and a sysdiagnose carries to you. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce. | +8.2 pts | Medium | Observability |
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with project.pbxproj. | +3.2 pts | Low | ADR Quality |
| Automate the release in CI — a deploy stage for a service (Helm/Kubernetes manifests or an equivalent rollout), or a tag-triggered publish job for an artifact — so releases are repeatable and reversible. | +5.6 pts | Medium | Deployment & Rollback |
| Enable Dependabot/Renovate or a dependency-review gate. | +3.6 pts | Medium | Security & performance tooling |
| Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with rust-toolchain.toml. | +1.7 pts | Low | Platform End-of-Life |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +3.0 pts | Medium | Architecture documentation |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +2.8 pts | Medium | Release Hygiene |
| Resolve the 2 REDACTED finding(s) charged to Static Analysis (SAST) — the other 27 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. | +1.2 pts | Low | Static Analysis (SAST) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.5 | Mixed | Static Analysis (SAST): High: REDACTED |
| myUpscaler/Processing/CoreMLProcessingJob.swift | 5.5 | Mixed | Cyclomatic Complexity: CoreMLProcessingJob.process (cyclomatic 29) |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Dependency Vulnerabilities: Medium advisory (unmaintained): REDACTED |
| myUpscaler/State/PresetStore.swift | 6.0 | Mixed | Explicit Debt: TodoComment |
| myUpscaler/Processing/CoreMLEngine+Shaders.swift | 7.0 | Near-clean | Cyclomatic Complexity: CoreMLProcessingJob.applyPostProcessing (cyclomatic 20) |
| myUpscaler/Processing/CoreAIModelWorker.swift | 7.1 | Near-clean | Cyclomatic Complexity: CoreAIModelWorker.prediction (cyclomatic 41) |
| backend/src/pipeline.rs | 7.2 | Near-clean | Cyclomatic Complexity: up60p::pipeline::build (cyclomatic 36) |
| myUpscaler/Processing/Up60PEngine.swift | 7.2 | Near-clean | Cyclomatic Complexity: Up60PEngine.makeOptions (cyclomatic 27) |
| backend/src/filters/bm3d.rs | 7.2 | Near-clean | Cyclomatic Complexity: Bm3d::denoise (cyclomatic 27) |
| REDACTED | 7.2 | Near-clean | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Near-clean | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Near-clean | Static Analysis (SAST): High: REDACTED |
| myUpscaler/Processing/UpscaleRunner.swift | 7.4 | Near-clean | Cyclomatic Complexity: UpscaleRunner.run (cyclomatic 71) |
| backend/src/job.rs | 7.4 | Near-clean | Cyclomatic Complexity: Job::video (cyclomatic 23) |
| myUpscaler/Support/ProgressParser.swift | 7.4 | Near-clean | Cyclomatic Complexity: ProgressParser.parse (cyclomatic 22) |
| desktop/src/main.rs | 7.4 | Near-clean | Cyclomatic Complexity: myupscaler::wire (cyclomatic 18) |
| backend/src/filters/interpolate.rs | 7.4 | Near-clean | Cyclomatic Complexity: MotionField::interpolate (cyclomatic 17) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 40 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 40 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, 141 of 150 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: this repository's production source spans .rs, .swift, and our analyzer cannot run the .swift test suite(s) — so no coverage was collected for the repository as a whole. The Rust half did build and run, and its own line coverage came back at 30.1% — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — coverage is excluded from the score rather than counted as a near-zero.
- D10 Test Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 16 test(s) behind this row are the ones the code-model census could read, and this repository also carries at least 10 test source file(s) (.rs) that it cannot: it reads the test types the .swift frontend declared, so a suite in any other language 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.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — 3 direct Cargo declaration(s) were read, but the outdated signal needs crates.io, and no committed REDACTED resolves them to versions, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- D14 License Compliance — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — this repository's REDACTED was read and none of the crates it resolves comes from crates.io: they are git, path or private-registry dependencies, which publish no licence anywhere this pass can read. Licences are resolved from the public crates.io registry, because a Cargo checkout does not contain its dependencies' licences. NOT a finding that this repository's licences are compliant: this dimension asserts nothing about its licensing in either direction.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-contributor repository — bus factor is not applicable (1 contributor(s) across 85 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Tracing effort is measured over resolved call sites, and all 354 sampled here came from .swift files. This repository's .rs source is a material share of its production lines and contributed none, so the score above is a verdict about the part that was read. Not a finding that the unread half navigates well — it is unmeasured.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `myUpscaler/Processing/CoreAIModelWorker.swift`, `myUpscaler/Processing/CoreMLModelManager.swift`, `myUpscaler/Processing/CoreMLProcessingJob.swift`, `myUpscaler/Processing/ProcessingControl.swift`, `myUpscaler/Processing/VideoAudioMuxer.swift`, … (+2 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- D34 Knowledge Freshness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. File-level freshness contradicts repo activity: 42 commits in the last 90 days, yet 69 of 72 significant files carry no living knowledge. Those two readings cannot both be true, so the per-file recency signal is treated as unreliable here and freshness is not scored for this run.
- AX6 Interface segregation — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
- AXB1 Runtime evidence locked — no reproducible boot — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: a native UI project (myUpscaler.xcodeproj/project.pbxproj). The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
- C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
- C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java source only, and this repository's Python, Swift, c is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby, Scala and Rust source only, and this repository's Python, Swift, c is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. 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.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X19 Unrestored process-global state — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
- X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X21 Side-effecting pattern guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X22 Contradicted release guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X25 Inert configuration knob — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X29 Per-element action decided by a fixed element — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X3 Exception handling — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
- X30 Support guard that admits what it rejects — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D13 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.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- 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.
- 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.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- 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".
- 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
24 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was UpscaleRunner.run at 71. A further 2 method(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 up60p::bin::up60p::apply at 64 — they are counted neither in the figure above nor in this dimension's score. 2 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: backend/src/bin/up60p.rs (up60p::bin::up60p::apply at 64), myUpscaler/Models/CoreMLModelRegistry.swift (CoreMLModelSpec.displayName at 20). 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 5 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with UpscaleRunner.run (cyclomatic 71), SourceVideoTiming.inspect (cyclomatic 44), CoreAIModelWorker.prediction (cyclomatic 41). — 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 5 together lifts Cyclomatic Complexity from 6.0 to about 7.2/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
D2 · Cognitive Complexity
35 method(s) exceeded the cognitive complexity threshold of 15; the worst was CoreAIModelWorker.prediction at 106.
What to do
- Bring the 4 bodies over 60 down to 60 or less in Cognitive Complexity — start with CoreAIModelWorker.prediction (cognitive 106), UpscaleRunner.run (cognitive 91), Bm3d::denoise (cognitive 74). — 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 4 together lifts Cognitive Complexity from 4.2 to about 5.3/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
D3 · God Classes
9 god class(es) detected.
What to do
- Resolve the 6 MethodTooLong finding(s) in God Classes — start with UpscaleRunner.swift, CoreMLProcessingJob.swift, job.rs. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 1 TooManyFields finding(s) in God Classes — start with options.rs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 TooManyMethods finding(s) in God Classes — start with CoreMLProcessingJob.swift. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
11 duplicated block group(s) detected. 3.0 % of the production lines (428 of 14,055) are in a reported copy. A further 8 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 3 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with CoreMLProcessingJob.swift, ContentViewComponents.swift, bm3d.rs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with CoreAIModelWorker.swift, SettingsParameterRules.swift. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with RestorationPanels.swift, sharpen.rs. — One of this dimension's main actionable groups (2 warning-level).
D5 · Coupling
3 production modules (Cargo+Xcode), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; a workspace's implicit (product-name) dependency is not visible there; 1 module(s) off the main sequence.
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).
D6 · Cohesion (LCOM4)
2 of 20 classes have LCOM4 above 3.
What to do
- Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with UpscaleSettings.swift, CoreMLProcessingJob.swift. — One of this dimension's main actionable groups (2 warning-level).
D10 · Test Quality
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 16 tests. Measured on the .swift suite only — at least 10 test source file(s) (.rs) went unread, so its test quality is unmeasured and is not in these counts.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D15 · Churn × Complexity Hotspots
Top hotspots: myUpscaler/Processing/Up60PEngine.swift (4×27=108)
What to do
- Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with Up60PEngine.swift. — One of this dimension's main actionable groups (1 warning-level).
D17 · Explicit Debt
2 deducted task-comment markers across 14055 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 2 TodoComment finding(s) in Explicit Debt — start with PresetStore.swift (2). — One of this dimension's main actionable groups (2 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 6 document(s) read across 3 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with project.pbxproj. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 3 build units (Cargo, Xcode) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with project.pbxproj. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
0 % of calls cross a namespace and 4 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated. Measured over the .swift source only — this repository's .rs was not sampled for call sites, so this score covers part of the tree, not all of it.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
29 finding(s): 0 critical, 29 high, 0 medium, 0 low. 27 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens.
What to do
- Resolve the 2 REDACTED finding(s) charged to Static Analysis (SAST) — the other 27 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. — One of this dimension's main actionable groups (29 issue-level, 2 of them charged here).
D30 · Dependency Vulnerabilities
10 finding(s): 0 critical, 0 high, 10 medium, 0 low.
What to do
- Resolve the 7 Medium advisory (unmaintained) finding(s) in Dependency Vulnerabilities — start with REDACTED (7). — One of this dimension's main actionable groups (7 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).
- Resolve the 1 Medium advisory (unsound) finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
1 end-of-life runtime(s) and 0 end-of-life framework(s), read from 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.
What to do
- Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with rust-toolchain.toml. — One of this dimension's main actionable groups (1 warning-level).
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
AX8 · Test isolation
AX9 · CQS / query purity
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.
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
P1 · CI/CD gates
P2 · Observability
- No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
What to do
- Write a diagnostic trail the user can hand back with a bug report: log through `os.Logger` (one per subsystem), which the unified log keeps and a sysdiagnose carries to you. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
P3 · Security & performance tooling
- `desktop/Cargo.toml` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — desktop/Cargo.toml:13
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- No release automation was found in CI — neither a deploy stage (Helm/Kubernetes/compose manifests, an orchestrated rollout) nor a publish job that ships the built artifact. Releases appear to be run by hand, which is slower, less repeatable and harder to reverse.
What to do
- Automate the release in CI — a deploy stage for a service (Helm/Kubernetes manifests or an equivalent rollout), or a tag-triggered publish job for an artifact — so releases are repeatable and reversible.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF3 · Async & latency hygiene
X19 · Unrestored process-global state
X3 · Exception handling
X5 · Nullable reference types
- `slint_build::compile_with_config("ui/app.slint",config)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `main` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — desktop/build.rs:27
- `cache.as_mut()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `serve` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — desktop/src/preview.rs:68
What to do
- Each row is a forced `Option`/`Result` no guard on its path proves present. Handle the absent case where it arises rather than forcing it: `?` to hand it to the caller, `if let` / `match` / `let … else` to branch on it, `unwrap_or` / `unwrap_or_default` / `unwrap_or_else` where a default is right. Where the value genuinely cannot be absent, say so in a way a reader can check from the line: test it first (`if x.is_none() { return … }`), look the key up with `contains_key` or the index against `len()`, or construct the value so it cannot be absent.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 87.3 | Exemplary | Solid. |
| Architecture | 94.6 | Exemplary | Solid. |
| Maturity | 70.2 | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 38.0 | Weak — gated by P2, P4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 63.9 | Checked 4 of 10 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100.0 | Exemplary | Strongest area. |
Unscored — 3 check(s) recorded observations but carry no score
- P12 CI test-gate honesty — 1 observation(s) recorded · 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'.
- X10 Duplicated predicate — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 69 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- 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; this repository's Swift imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. No Swift request handler (a Vapor, Hummingbird, Kitura, Swifter or Perfect route handler, as a method or a registered closure) is declared, so no state 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.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- D11 Test Reliability — Test source is present (.swift, .rs) and this repository's suite is reachable only from an Apple platform: it ships myUpscaler.xcodeproj and no SwiftPM manifest, so it is built by Xcode rather than by `swift test`. The analyzer runs on Linux, where no simulator exists, so the suite was not re-run. Not scored: nothing was exercised.
- D12 Dependency Hygiene — Not scored — 3 direct Cargo declaration(s) were read, but the outdated signal needs crates.io, and no committed REDACTED resolves them to versions, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- D14 License Compliance — Crate licences not graded — nothing in this REDACTED resolves from crates.io
- D16 Bus Factor — single-contributor repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 3 candidate(s) found and not reported.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .py, .rs, .swift, 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
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 7 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D34 Knowledge Freshness — knowledge concentrated in recent work — freshness signal contradicted by repo activity
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- 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 — polyglot repository, one half has no runner
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (1 value object(s))
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and this analysis resolves a call's owner only where the receiver's type is written down in the source. Reported as guidance rather than measured
- 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, Scala, Rust and Java, 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
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Python, Rust, Swift source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage data present for 5 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `Benchmark("…")` in a file importing package-benchmark, or package-benchmark in Package.swift, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X12 Unreachable branch — X12 reached only 41% of this repository's production lines — swift (8,233 lines), c (26 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X16 Unfloored truncation loop — X16 reached only 41% of this repository's production lines — swift (8,233 lines), python (42 lines), c (26 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — X18 reached only 41% of this repository's production lines — swift (8,233 lines), python (42 lines), c (26 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X21 Side-effecting pattern guard — X21 reached only 41% of this repository's production lines — swift (8,233 lines), c (26 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X22 Contradicted release guard — X22 reached only 41% of this repository's production lines — swift (8,233 lines), c (26 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X25 Inert configuration knob — X25 reached only 41% of this repository's production lines — swift (8,233 lines), c (26 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — X29 reached only 41% of this repository's production lines — swift (8,233 lines), python (42 lines), c (26 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X30 Support guard that admits what it rejects — X30 reached only 41% of this repository's production lines — swift (8,233 lines), c (26 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Swift was read, and it logs through none: `print` and `NSLog` take one finished line, and os's `Logger` keeps each interpolated value as its own argument, so an assembled message there loses nothing the API could have kept (as with log4net in C#). Calls through swift-log (`import Logging`) and `os_log` calls would be judged.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 29 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
Serious — 110 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- MethodTooLong: UpscaleRunner.run myUpscaler/Processing/UpscaleRunner.swift:128
- MethodTooLong: CoreMLProcessingJob.process myUpscaler/Processing/CoreMLProcessingJob.swift:29
- MethodTooLong: Job.video backend/src/job.rs:184
- MethodTooLong: HardwareEncodingPanel.body myUpscaler/Views/ContentView/EncodingPanels.swift:78
- MethodTooLong: ContentView.body myUpscaler/Views/ContentView/ContentView.swift:26
- MethodTooLong: UpscaleSettingsSnapshot.apply myUpscaler/State/PresetStore.swift:263
- up60p::pipeline::build (cognitive 52) backend/src/pipeline.rs:258
- up60p::png::zlib (cognitive 37) backend/src/png.rs:190
- up60p::png::filter_rows (cognitive 26) backend/src/png.rs:49
- up60p::bin::up60p::main (cognitive 21) backend/src/bin/up60p.rs:41
- up60p::pipeline::debander (cognitive 21) backend/src/pipeline.rs:142
- Duplicated block (9 lines × 2) myUpscaler/Processing/CoreMLProcessingJob.swift:298
- Duplicated block (9 lines × 2) myUpscaler/Views/ContentView/ContentViewComponents.swift:13
- Duplicated block (9 lines × 2) backend/src/filters/bm3d.rs:66
- up60p::pipeline::build (cyclomatic 36) backend/src/pipeline.rs:258
- up60p::up60p_process_path (cyclomatic 16) backend/src/lib.rs:111
- TodoComment myUpscaler/State/PresetStore.swift:547
- TodoComment myUpscaler/State/PresetStore.swift:560
- Bm3d::denoise (cognitive 74) backend/src/filters/bm3d.rs:87
- Bm3d::dct2 (cognitive 22) backend/src/filters/bm3d.rs:63
- myupscaler::wire (cognitive 18) desktop/src/main.rs:272
- myupscaler::drain (cognitive 16) desktop/src/main.rs:190
- Duplicated block (8 lines × 2) myUpscaler/Processing/CoreAIModelWorker.swift:97
- Duplicated block (8 lines × 2) myUpscaler/State/SettingsParameterRules.swift:394
- Duplicated block (6 lines × 2) myUpscaler/Views/ContentView/RestorationPanels.swift:137
- Duplicated block (6 lines × 2) backend/src/filters/sharpen.rs:84
- Low cohesion: UpscaleSettings (LCOM4 7) myUpscaler/State/UpscaleSettings.swift:5
- Low cohesion: CoreMLProcessingJob (LCOM4 4) myUpscaler/Processing/CoreMLProcessingJob.swift:10
- Symbol treated as nullable, then dereferenced unguarded desktop/build.rs:27
- Symbol treated as nullable, then dereferenced unguarded desktop/src/preview.rs:68
- UpscaleRunner.run (cyclomatic 71) myUpscaler/Processing/UpscaleRunner.swift:128
- SourceVideoTiming.inspect (cyclomatic 44) myUpscaler/Processing/SourceVideoTiming.swift:11
- CoreAIModelWorker.prediction (cyclomatic 41) myUpscaler/Processing/CoreAIModelWorker.swift:58
- SettingsNormalization.normalizeStage (cyclomatic 31) myUpscaler/State/SettingsNormalization.swift:11
- CoreMLProcessingJob.process (cyclomatic 29) myUpscaler/Processing/CoreMLProcessingJob.swift:29
- Up60PEngine.makeOptions (cyclomatic 27) myUpscaler/Processing/Up60PEngine.swift:155
- Bm3d::denoise (cyclomatic 27) backend/src/filters/bm3d.rs:87
- Up60PEngine.process (cyclomatic 25) myUpscaler/Processing/Up60PEngine.swift:271
- PreviewRenderer.render (cyclomatic 25) myUpscaler/State/EditorState+PreviewRenderer.swift:6
- EditorState.loadFullResolutionFrame (cyclomatic 25) myUpscaler/State/EditorState+MediaLoading.swift:67
- UpscaleSettings.makePreviewFilterParameters (cyclomatic 24) myUpscaler/State/SettingsPreviewParameters.swift:36
- CoreMLProcessingJob.blendTileIntoCanvas (cyclomatic 23) myUpscaler/Processing/CoreMLProcessingJob.swift:416
- Job::video (cyclomatic 23) backend/src/job.rs:184
- ProgressParser.parse (cyclomatic 22) myUpscaler/Support/ProgressParser.swift:17
- CoreMLProcessingJob.applyPostProcessing (cyclomatic 20) myUpscaler/Processing/CoreMLEngine+Shaders.swift:364
- BatchPlan.make (cyclomatic 18) myUpscaler/Processing/BatchPlan.swift:13
- CoreAIModelWorker.prepare (cyclomatic 18) myUpscaler/Processing/CoreAIModelWorker.swift:25
- DragDropView.body (cyclomatic 18) myUpscaler/Views/DragDropView.swift:28
- myupscaler::wire (cyclomatic 18) desktop/src/main.rs:272
- ProgressUpdateGate.shouldEmit (cyclomatic 17) myUpscaler/Processing/ProgressUpdateGate.swift:8
- MotionField::interpolate (cyclomatic 17) backend/src/filters/interpolate.rs:271
- KeyboardShortcutsManager.init (cyclomatic 16) myUpscaler/State/KeyboardShortcutsManager.swift:30
- Hotspot: myUpscaler/Processing/Up60PEngine.swift myUpscaler/Processing/Up60PEngine.swift:155
- CoreAIModelWorker.prediction (cognitive 106) myUpscaler/Processing/CoreAIModelWorker.swift:58
- UpscaleRunner.run (cognitive 91) myUpscaler/Processing/UpscaleRunner.swift:128
- SourceVideoTiming.inspect (cognitive 69) myUpscaler/Processing/SourceVideoTiming.swift:11
- CoreMLProcessingJob.process (cognitive 47) myUpscaler/Processing/CoreMLProcessingJob.swift:29
- NlMeans::plane (cognitive 44) backend/src/filters/nlmeans.rs:28
- Up60PEngine.process (cognitive 41) myUpscaler/Processing/Up60PEngine.swift:271
- SettingsNormalization.normalizeStage (cognitive 40) myUpscaler/State/SettingsNormalization.swift:11
- ProgressParser.parse (cognitive 39) myUpscaler/Support/ProgressParser.swift:17
- MotionField::interpolate (cognitive 39) backend/src/filters/interpolate.rs:271
- CoreMLProcessingJob.blendTileIntoCanvas (cognitive 35) myUpscaler/Processing/CoreMLProcessingJob.swift:416
- BatchPlan.make (cognitive 34) myUpscaler/Processing/BatchPlan.swift:13
- PreviewRenderer.render (cognitive 32) myUpscaler/State/EditorState+PreviewRenderer.swift:6
- Job::video (cognitive 29) backend/src/job.rs:184
- EditorState.loadFullResolutionFrame (cognitive 28) myUpscaler/State/EditorState+MediaLoading.swift:67
- KeyboardShortcutsManager.init (cognitive 27) myUpscaler/State/KeyboardShortcutsManager.swift:30
- Up60PEngine.makeOptions (cognitive 26) myUpscaler/Processing/Up60PEngine.swift:155
- DragDropView.body (cognitive 26) myUpscaler/Views/DragDropView.swift:28
- AtaDenoise::filter_frame (cognitive 25) backend/src/filters/atadenoise.rs:40
- CoreMLProcessingJob.applyPostProcessing (cognitive 23) myUpscaler/Processing/CoreMLEngine+Shaders.swift:364
- UpscaleSettings.makePreviewFilterParameters (cognitive 23) myUpscaler/State/SettingsPreviewParameters.swift:36
- CoreAIModelWorker.prepare (cognitive 17) myUpscaler/Processing/CoreAIModelWorker.swift:25
- VideoTimelineLoader.sampleTimes (cognitive 17) myUpscaler/State/EditorState+TimelineLoader.swift:76
- ProgressUpdateGate.shouldEmit (cognitive 16) myUpscaler/Processing/ProgressUpdateGate.swift:8
- ProgressParser.parseTimeString (cognitive 16) myUpscaler/Support/ProgressParser.swift:97
- Deband::apply (cognitive 16) backend/src/filters/deband.rs:42
- Retimer::between (cognitive 16) backend/src/filters/interpolate.rs:100
- TooManyFields: Options backend/src/options.rs:29
- TooManyMethods: CoreMLProcessingJob myUpscaler/Processing/CoreMLProcessingJob.swift:10
- FunctionTooLong: up60p::pipeline::build backend/src/pipeline.rs:258
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (10 corresponding lines) myUpscaler/State/SettingsParameterRules.swift:392
- Edited copies of one member (3 members, 22+ corresponding lines) myUpscaler/Processing/CoreMLEngine+Shaders.swift:126
- Edited copy of a member (13 corresponding lines) myUpscaler/Views/DesignSystem.swift:133
- Edited copies of one member (8 members, 7+ corresponding lines) myUpscaler/Processing/CoreMLEngine+Shaders.swift:234
- Edited copy of a member (11 corresponding lines) myUpscaler/Views/ContentView/ContentViewComponents.swift:13
- Edited copies of one member (5 members, 6+ corresponding lines) myUpscaler/Processing/CoreMLEngine+Shaders.swift:204
- Edited copies of one member (3 members, 5+ corresponding lines) myUpscaler/Processing/CoreMLEngine+Shaders.swift:255
- Edited copy of a member (7 corresponding lines) myUpscaler/State/SettingsParameterRules.swift:403
- Duplicated block (21–24 lines × 2) myUpscaler/Processing/CoreMLEngine+Shaders.swift:369
- Duplicated block (14–16 lines × 2) myUpscaler/Views/ContentView/EncodingPanels.swift:188
- Duplicated block (10–11 lines × 3) myUpscaler/Views/ContentView/AIEnginePanel.swift:10
- Duplicated block (11 lines × 3) myUpscaler/Views/ContentView/EncodingPanels.swift:9
- End-of-life runtime: Rust 1.97 rust-toolchain.toml:1
- Off the main sequence: up60p
- Test failure does not fail the CI gate REDACTED:93
- No structured logging
- No deployment automation
Minor — 11 finding(s)
- Duplicated predicate myUpscaler/Processing/ProgressUpdateGate.swift:10
- Duplicated predicate myUpscaler/Views/ContentView/EncodingPanels.swift:210
- No ADRs found myUpscaler.xcodeproj/project.pbxproj:1
- Projects may be oversized for their cohesion myUpscaler.xcodeproj/project.pbxproj:1
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No dependency-update automation desktop/Cargo.toml:13
- No changelog
- Silent fallback default on Err desktop/src/main.rs:100
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-4e54454b817243758d5881bd0dbdf2ee/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-4e54454b817243758d5881bd0dbdf2ee/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 29 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 10 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 7 file(s) — `myUpscaler/Processing/CoreAIModelWorker.swift`, `myUpscaler/Processing/CoreMLModelManager.swift`, `myUpscaler/Processing/CoreMLProcessingJob.swift`, `myUpscaler/Processing/ProcessingControl.swift`, `myUpscaler/Processing/VideoAudioMuxer.swift`, … (+2 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |