Executive summary
sayhisam1/bevy-aqua meets our standard for a preview release. It scores 69.0 out of 100 and is rated Strong, and all 15 of its critical findings are security problems in the build pipeline.
Every lens scores high enough to be rated Strong, so no single lens holds the score back. The best first step is recording design decisions, worth about 6.3 points.
Fifteen 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 11,552 lines, about €25,000 to rebuild.
Every lens already scores high enough to be rated Strong, so no single lens holds the score back.
Rebuild cost: about €25,000 · Estimate
| Cost to rebuild | €8,200 to €41,000, for 136 to 432 hours of work, about 0.2 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 | ×1.0 at a score of 69. 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: 11,552 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 bevy_aqua_core | 2 bevy_aqua_core.amortized_bake | 3 bevy_aqua_core.bed | 4 bevy_aqua_core.pass | 5 bevy_aqua_core.view | 6 bevy_aqua_fft | 7 bevy_aqua_foam.gpu_fixture | 8 bevy_aqua_geom.rings | 9 bevy_aqua_light | 10 bevy_aqua_medium | 11 bevy_aqua_motion | 12 bevy_aqua_motion.prepass | 13 bevy_aqua_optics | 14 bevy_aqua_reflect | 15 bevy_aqua_reflect.camera | 16 bevy_aqua_reflect.prepass_culling | 17 bevy_aqua_sdf.river | 18 bevy_aqua_shore | 19 bevy_aqua_shore.bake | 20 bevy_aqua_spray | 21 bevy_aqua_core.fields | 22 bevy_aqua_query | 23 bevy_aqua_reflect.resolve | 24 bevy_aqua_sdf.shapes | 25 bevy_aqua_core.body | 26 bevy_aqua_core.cascade | 27 bevy_aqua_sdf | 28 bevy_aqua_volume | 29 bevy_aqua | 30 bevy_aqua_core.waves_abi | 31 bevy_aqua_foam | 32 bevy_aqua_foam.render | 33 bevy_aqua_spray.runtime | 34 bevy_aqua_volume.render | 35 bevy_aqua_waves.fft | 36 bevy_aqua_motion.history | 37 bevy_aqua_waves | 38 bevy_aqua_waves.variance | 39 bevy_aqua.ocean | 40 bevy_aqua_waves.render |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 bevy_aqua_core | ||||||||||||||||||||||||||||||||||||||||
| 2 bevy_aqua_core.amortized_bake | ||||||||||||||||||||||||||||||||||||||||
| 3 bevy_aqua_core.bed | ||||||||||||||||||||||||||||||||||||||||
| 4 bevy_aqua_core.pass | ||||||||||||||||||||||||||||||||||||||||
| 5 bevy_aqua_core.view | ||||||||||||||||||||||||||||||||||||||||
| 6 bevy_aqua_fft | ||||||||||||||||||||||||||||||||||||||||
| 7 bevy_aqua_foam.gpu_fixture | ||||||||||||||||||||||||||||||||||||||||
| 8 bevy_aqua_geom.rings | ||||||||||||||||||||||||||||||||||||||||
| 9 bevy_aqua_light | ||||||||||||||||||||||||||||||||||||||||
| 10 bevy_aqua_medium | ||||||||||||||||||||||||||||||||||||||||
| 11 bevy_aqua_motion | ||||||||||||||||||||||||||||||||||||||||
| 12 bevy_aqua_motion.prepass | ||||||||||||||||||||||||||||||||||||||||
| 13 bevy_aqua_optics | ||||||||||||||||||||||||||||||||||||||||
| 14 bevy_aqua_reflect | ||||||||||||||||||||||||||||||||||||||||
| 15 bevy_aqua_reflect.camera | ||||||||||||||||||||||||||||||||||||||||
| 16 bevy_aqua_reflect.prepass_culling | ||||||||||||||||||||||||||||||||||||||||
| 17 bevy_aqua_sdf.river | ||||||||||||||||||||||||||||||||||||||||
| 18 bevy_aqua_shore | ||||||||||||||||||||||||||||||||||||||||
| 19 bevy_aqua_shore.bake | ||||||||||||||||||||||||||||||||||||||||
| 20 bevy_aqua_spray | ||||||||||||||||||||||||||||||||||||||||
| 21 bevy_aqua_core.fields | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 bevy_aqua_query | 3 | |||||||||||||||||||||||||||||||||||||||
| 23 bevy_aqua_reflect.resolve | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 bevy_aqua_sdf.shapes | 2 | |||||||||||||||||||||||||||||||||||||||
| 25 bevy_aqua_core.body | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 26 bevy_aqua_core.cascade | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 27 bevy_aqua_sdf | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 bevy_aqua_volume | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 29 bevy_aqua | 1 | |||||||||||||||||||||||||||||||||||||||
| 30 bevy_aqua_core.waves_abi | 1 | |||||||||||||||||||||||||||||||||||||||
| 31 bevy_aqua_foam | 2 | |||||||||||||||||||||||||||||||||||||||
| 32 bevy_aqua_foam.render | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 33 bevy_aqua_spray.runtime | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 34 bevy_aqua_volume.render | 1 | |||||||||||||||||||||||||||||||||||||||
| 35 bevy_aqua_waves.fft | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 36 bevy_aqua_motion.history | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 37 bevy_aqua_waves | 2 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 38 bevy_aqua_waves.variance | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 39 bevy_aqua.ocean | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 40 bevy_aqua_waves.render | 4 | 1 |
21→2 bevy_aqua_core.fields uses bevy_aqua_core.amortized_bake✕
- Connections
- 1 pair of types, where a type in bevy_aqua_core.fields uses a type in bevy_aqua_core.amortized_bake.
- The types involved
bevy_aqua_core.fields.WaterFields→bevy_aqua_core.amortized_bake.AmortizedBake
- Direction
- bevy_aqua_core.fields uses bevy_aqua_core.amortized_bake, so a change to bevy_aqua_core.amortized_bake can break bevy_aqua_core.fields, while a change to bevy_aqua_core.fields can't break bevy_aqua_core.amortized_bake.
- Position
- Below the diagonal: bevy_aqua_core.fields uses a module listed above it, which is the healthy direction.
22→4 bevy_aqua_query uses bevy_aqua_core.pass✕
- Connections
- 3 pairs of types, where a type in bevy_aqua_query uses a type in bevy_aqua_core.pass.
- The types involved
bevy_aqua_query.Prepared→bevy_aqua_core.pass.Groupsbevy_aqua_query.Prepared→bevy_aqua_core.pass.Passesbevy_aqua_query.bevy_aqua_query$module→bevy_aqua_core.pass.PassSpec
- Direction
- bevy_aqua_query uses bevy_aqua_core.pass, so a change to bevy_aqua_core.pass can break bevy_aqua_query, while a change to bevy_aqua_query can't break bevy_aqua_core.pass.
- Position
- Below the diagonal: bevy_aqua_query uses a module listed above it, which is the healthy direction.
23→4 bevy_aqua_reflect.resolve uses bevy_aqua_core.pass✕
- Connections
- 1 pair of types, where a type in bevy_aqua_reflect.resolve uses a type in bevy_aqua_core.pass.
- The types involved
bevy_aqua_reflect.resolve.ResolvePipeline→bevy_aqua_core.pass.Passes
- Direction
- bevy_aqua_reflect.resolve uses bevy_aqua_core.pass, so a change to bevy_aqua_core.pass can break bevy_aqua_reflect.resolve, while a change to bevy_aqua_reflect.resolve can't break bevy_aqua_core.pass.
- Position
- Below the diagonal: bevy_aqua_reflect.resolve uses a module listed above it, which is the healthy direction.
24→17 bevy_aqua_sdf.shapes uses bevy_aqua_sdf.river✕
- Connections
- 2 pairs of types, where a type in bevy_aqua_sdf.shapes uses a type in bevy_aqua_sdf.river.
- The types involved
bevy_aqua_sdf.shapes.WaterShape→bevy_aqua_sdf.river.RiverPathbevy_aqua_sdf.shapes.shapes$module→bevy_aqua_sdf.river.RiverPath
- Direction
- bevy_aqua_sdf.shapes uses bevy_aqua_sdf.river, so a change to bevy_aqua_sdf.river can break bevy_aqua_sdf.shapes, while a change to bevy_aqua_sdf.shapes can't break bevy_aqua_sdf.river.
- Position
- Below the diagonal: bevy_aqua_sdf.shapes uses a module listed above it, which is the healthy direction.
25→1 bevy_aqua_core.body uses bevy_aqua_core✕
- Connections
- 1 pair of types, where a type in bevy_aqua_core.body uses a type in bevy_aqua_core.
- The types involved
bevy_aqua_core.body.ResolvedWaterBody→bevy_aqua_core.WaterOptics
- Direction
- bevy_aqua_core.body uses bevy_aqua_core, so a change to bevy_aqua_core can break bevy_aqua_core.body, while a change to bevy_aqua_core.body can't break bevy_aqua_core.
- Position
- Below the diagonal: bevy_aqua_core.body uses a module listed above it, which is the healthy direction.
25→24 bevy_aqua_core.body uses bevy_aqua_sdf.shapes✕
- Connections
- 2 pairs of types, where a type in bevy_aqua_core.body uses a type in bevy_aqua_sdf.shapes.
- The types involved
bevy_aqua_core.body.ResolvedWaterBody→bevy_aqua_sdf.shapes.FlowSamplebevy_aqua_core.body.ResolvedWaterBody→bevy_aqua_sdf.shapes.WaterShape
- Direction
- bevy_aqua_core.body uses bevy_aqua_sdf.shapes, so a change to bevy_aqua_sdf.shapes can break bevy_aqua_core.body, while a change to bevy_aqua_core.body can't break bevy_aqua_sdf.shapes.
- Position
- Below the diagonal: bevy_aqua_core.body uses a module listed above it, which is the healthy direction.
26→1 bevy_aqua_core.cascade uses bevy_aqua_core✕
- Connections
- 2 pairs of types, where a type in bevy_aqua_core.cascade uses a type in bevy_aqua_core.
- The types involved
bevy_aqua_core.cascade.SurfaceParams→bevy_aqua_core.WaterOpticsbevy_aqua_core.cascade.cascade$module→bevy_aqua_core.AquaSettings
- Direction
- bevy_aqua_core.cascade uses bevy_aqua_core, so a change to bevy_aqua_core can break bevy_aqua_core.cascade, while a change to bevy_aqua_core.cascade can't break bevy_aqua_core.
- Position
- Below the diagonal: bevy_aqua_core.cascade uses a module listed above it, which is the healthy direction.
26→3 bevy_aqua_core.cascade uses bevy_aqua_core.bed✕
- Connections
- 1 pair of types, where a type in bevy_aqua_core.cascade uses a type in bevy_aqua_core.bed.
- The types involved
bevy_aqua_core.cascade.GpuLayout→bevy_aqua_core.bed.BedHeightMap
- Direction
- bevy_aqua_core.cascade uses bevy_aqua_core.bed, so a change to bevy_aqua_core.bed can break bevy_aqua_core.cascade, while a change to bevy_aqua_core.cascade can't break bevy_aqua_core.bed.
- Position
- Below the diagonal: bevy_aqua_core.cascade uses a module listed above it, which is the healthy direction.
26→21 bevy_aqua_core.cascade uses bevy_aqua_core.fields✕
- Connections
- 1 pair of types, where a type in bevy_aqua_core.cascade uses a type in bevy_aqua_core.fields.
- The types involved
bevy_aqua_core.cascade.CascadeMaterial→bevy_aqua_core.fields.FieldParams
- Direction
- bevy_aqua_core.cascade uses bevy_aqua_core.fields, so a change to bevy_aqua_core.fields can break bevy_aqua_core.cascade, while a change to bevy_aqua_core.cascade can't break bevy_aqua_core.fields.
- Position
- Below the diagonal: bevy_aqua_core.cascade uses a module listed above it, which is the healthy direction.
27→24 bevy_aqua_sdf uses bevy_aqua_sdf.shapes✕
- Connections
- 1 pair of types, where a type in bevy_aqua_sdf uses a type in bevy_aqua_sdf.shapes.
- The types involved
bevy_aqua_sdf.bevy_aqua_sdf$module→bevy_aqua_sdf.shapes.WaterShape
- Direction
- bevy_aqua_sdf uses bevy_aqua_sdf.shapes, so a change to bevy_aqua_sdf.shapes can break bevy_aqua_sdf, while a change to bevy_aqua_sdf can't break bevy_aqua_sdf.shapes.
- Position
- Below the diagonal: bevy_aqua_sdf uses a module listed above it, which is the healthy direction.
28→1 bevy_aqua_volume uses bevy_aqua_core✕
- Connections
- 3 pairs of types, where a type in bevy_aqua_volume uses a type in bevy_aqua_core.
- The types involved
bevy_aqua_volume.ExtractedVolume→bevy_aqua_core.WaterOpticsbevy_aqua_volume.bevy_aqua_volume$module→bevy_aqua_core.AquaSettingsbevy_aqua_volume.bevy_aqua_volume$module→bevy_aqua_core.Ocean
- Direction
- bevy_aqua_volume uses bevy_aqua_core, so a change to bevy_aqua_core can break bevy_aqua_volume, while a change to bevy_aqua_volume can't break bevy_aqua_core.
- Position
- Below the diagonal: bevy_aqua_volume uses a module listed above it, which is the healthy direction.
28→22 bevy_aqua_volume uses bevy_aqua_query✕
- Connections
- 1 pair of types, where a type in bevy_aqua_volume uses a type in bevy_aqua_query.
- The types involved
bevy_aqua_volume.bevy_aqua_volume$module→bevy_aqua_query.WaveSurface
- Direction
- bevy_aqua_volume uses bevy_aqua_query, so a change to bevy_aqua_query can break bevy_aqua_volume, while a change to bevy_aqua_volume can't break bevy_aqua_query.
- Position
- Below the diagonal: bevy_aqua_volume uses a module listed above it, which is the healthy direction.
29→26 bevy_aqua uses bevy_aqua_core.cascade✕
- Connections
- 1 pair of types, where a type in bevy_aqua uses a type in bevy_aqua_core.cascade.
- The types involved
bevy_aqua.bevy_aqua$module→bevy_aqua_core.cascade.UpdateInputs
- Direction
- bevy_aqua uses bevy_aqua_core.cascade, so a change to bevy_aqua_core.cascade can break bevy_aqua, while a change to bevy_aqua can't break bevy_aqua_core.cascade.
- Position
- Below the diagonal: bevy_aqua uses a module listed above it, which is the healthy direction.
30→26 bevy_aqua_core.waves_abi uses bevy_aqua_core.cascade✕
- Connections
- 1 pair of types, where a type in bevy_aqua_core.waves_abi uses a type in bevy_aqua_core.cascade.
- The types involved
bevy_aqua_core.waves_abi.AnimWavesUniform→bevy_aqua_core.cascade.GpuLayout
- Direction
- bevy_aqua_core.waves_abi uses bevy_aqua_core.cascade, so a change to bevy_aqua_core.cascade can break bevy_aqua_core.waves_abi, while a change to bevy_aqua_core.waves_abi can't break bevy_aqua_core.cascade.
- Position
- Below the diagonal: bevy_aqua_core.waves_abi uses a module listed above it, which is the healthy direction.
31→26 bevy_aqua_foam uses bevy_aqua_core.cascade✕
- Connections
- 2 pairs of types, where a type in bevy_aqua_foam uses a type in bevy_aqua_core.cascade.
- The types involved
bevy_aqua_foam.Frame→bevy_aqua_core.cascade.GpuLayoutbevy_aqua_foam.Uniform→bevy_aqua_core.cascade.GpuLayout
- Direction
- bevy_aqua_foam uses bevy_aqua_core.cascade, so a change to bevy_aqua_core.cascade can break bevy_aqua_foam, while a change to bevy_aqua_foam can't break bevy_aqua_core.cascade.
- Position
- Below the diagonal: bevy_aqua_foam uses a module listed above it, which is the healthy direction.
32→4 bevy_aqua_foam.render uses bevy_aqua_core.pass✕
- Connections
- 3 pairs of types, where a type in bevy_aqua_foam.render uses a type in bevy_aqua_core.pass.
- The types involved
bevy_aqua_foam.render.Prepared→bevy_aqua_core.pass.Groupsbevy_aqua_foam.render.Prepared→bevy_aqua_core.pass.Passesbevy_aqua_foam.render.render$module→bevy_aqua_core.pass.PassSpec
- Direction
- bevy_aqua_foam.render uses bevy_aqua_core.pass, so a change to bevy_aqua_core.pass can break bevy_aqua_foam.render, while a change to bevy_aqua_foam.render can't break bevy_aqua_core.pass.
- Position
- Below the diagonal: bevy_aqua_foam.render uses a module listed above it, which is the healthy direction.
32→26 bevy_aqua_foam.render uses bevy_aqua_core.cascade✕
- Connections
- 1 pair of types, where a type in bevy_aqua_foam.render uses a type in bevy_aqua_core.cascade.
- The types involved
bevy_aqua_foam.render.Prepared→bevy_aqua_core.cascade.GpuLayout
- Direction
- bevy_aqua_foam.render uses bevy_aqua_core.cascade, so a change to bevy_aqua_core.cascade can break bevy_aqua_foam.render, while a change to bevy_aqua_foam.render can't break bevy_aqua_core.cascade.
- Position
- Below the diagonal: bevy_aqua_foam.render uses a module listed above it, which is the healthy direction.
33→3 bevy_aqua_spray.runtime uses bevy_aqua_core.bed✕
- Connections
- 1 pair of types, where a type in bevy_aqua_spray.runtime uses a type in bevy_aqua_core.bed.
- The types involved
bevy_aqua_spray.runtime.runtime$module→bevy_aqua_core.bed.BedHeightMap
- Direction
- bevy_aqua_spray.runtime uses bevy_aqua_core.bed, so a change to bevy_aqua_core.bed can break bevy_aqua_spray.runtime, while a change to bevy_aqua_spray.runtime can't break bevy_aqua_core.bed.
- Position
- Below the diagonal: bevy_aqua_spray.runtime uses a module listed above it, which is the healthy direction.
33→20 bevy_aqua_spray.runtime uses bevy_aqua_spray✕
- Connections
- 2 pairs of types, where a type in bevy_aqua_spray.runtime uses a type in bevy_aqua_spray.
- The types involved
bevy_aqua_spray.runtime.runtime$module→bevy_aqua_spray.Budgetbevy_aqua_spray.runtime.runtime$module→bevy_aqua_spray.Limits
- Direction
- bevy_aqua_spray.runtime uses bevy_aqua_spray, so a change to bevy_aqua_spray can break bevy_aqua_spray.runtime, while a change to bevy_aqua_spray.runtime can't break bevy_aqua_spray.
- Position
- Below the diagonal: bevy_aqua_spray.runtime uses a module listed above it, which is the healthy direction.
33→25 bevy_aqua_spray.runtime uses bevy_aqua_core.body✕
- Connections
- 1 pair of types, where a type in bevy_aqua_spray.runtime uses a type in bevy_aqua_core.body.
- The types involved
bevy_aqua_spray.runtime.runtime$module→bevy_aqua_core.body.ResolvedWaterBodies
- Direction
- bevy_aqua_spray.runtime uses bevy_aqua_core.body, so a change to bevy_aqua_core.body can break bevy_aqua_spray.runtime, while a change to bevy_aqua_spray.runtime can't break bevy_aqua_core.body.
- Position
- Below the diagonal: bevy_aqua_spray.runtime uses a module listed above it, which is the healthy direction.
34→28 bevy_aqua_volume.render uses bevy_aqua_volume✕
- Connections
- 1 pair of types, where a type in bevy_aqua_volume.render uses a type in bevy_aqua_volume.
- The types involved
bevy_aqua_volume.render.render$module→bevy_aqua_volume.ExtractedVolume
- Direction
- bevy_aqua_volume.render uses bevy_aqua_volume, so a change to bevy_aqua_volume can break bevy_aqua_volume.render, while a change to bevy_aqua_volume.render can't break bevy_aqua_volume.
- Position
- Below the diagonal: bevy_aqua_volume.render uses a module listed above it, which is the healthy direction.
35→6 bevy_aqua_waves.fft uses bevy_aqua_fft✕
- Connections
- 2 pairs of types, where a type in bevy_aqua_waves.fft uses a type in bevy_aqua_fft.
- The types involved
bevy_aqua_waves.fft.fft$module→bevy_aqua_fft.BinSpecbevy_aqua_waves.fft.fft$module→bevy_aqua_fft.SpectrumAuthoring
- Direction
- bevy_aqua_waves.fft uses bevy_aqua_fft, so a change to bevy_aqua_fft can break bevy_aqua_waves.fft, while a change to bevy_aqua_waves.fft can't break bevy_aqua_fft.
- Position
- Below the diagonal: bevy_aqua_waves.fft uses a module listed above it, which is the healthy direction.
35→26 bevy_aqua_waves.fft uses bevy_aqua_core.cascade✕
- Connections
- 2 pairs of types, where a type in bevy_aqua_waves.fft uses a type in bevy_aqua_core.cascade.
- The types involved
bevy_aqua_waves.fft.Uniform→bevy_aqua_core.cascade.GpuLayoutbevy_aqua_waves.fft.fft$module→bevy_aqua_core.cascade.GpuLayout
- Direction
- bevy_aqua_waves.fft uses bevy_aqua_core.cascade, so a change to bevy_aqua_core.cascade can break bevy_aqua_waves.fft, while a change to bevy_aqua_waves.fft can't break bevy_aqua_core.cascade.
- Position
- Below the diagonal: bevy_aqua_waves.fft uses a module listed above it, which is the healthy direction.
36→26 bevy_aqua_motion.history uses bevy_aqua_core.cascade✕
- Connections
- 1 pair of types, where a type in bevy_aqua_motion.history uses a type in bevy_aqua_core.cascade.
- The types involved
bevy_aqua_motion.history.PreviousFrame→bevy_aqua_core.cascade.GpuLayout
- Direction
- bevy_aqua_motion.history uses bevy_aqua_core.cascade, so a change to bevy_aqua_core.cascade can break bevy_aqua_motion.history, while a change to bevy_aqua_motion.history can't break bevy_aqua_core.cascade.
- Position
- Below the diagonal: bevy_aqua_motion.history uses a module listed above it, which is the healthy direction.
36→30 bevy_aqua_motion.history uses bevy_aqua_core.waves_abi✕
- Connections
- 2 pairs of types, where a type in bevy_aqua_motion.history uses a type in bevy_aqua_core.waves_abi.
- The types involved
bevy_aqua_motion.history.History→bevy_aqua_core.waves_abi.AnimWavesUniformbevy_aqua_motion.history.history$module→bevy_aqua_core.waves_abi.AnimWavesUniform
- Direction
- bevy_aqua_motion.history uses bevy_aqua_core.waves_abi, so a change to bevy_aqua_core.waves_abi can break bevy_aqua_motion.history, while a change to bevy_aqua_motion.history can't break bevy_aqua_core.waves_abi.
- Position
- Below the diagonal: bevy_aqua_motion.history uses a module listed above it, which is the healthy direction.
37→1 bevy_aqua_waves uses bevy_aqua_core✕
- Connections
- 2 pairs of types, where a type in bevy_aqua_waves uses a type in bevy_aqua_core.
- The types involved
bevy_aqua_waves.Frame→bevy_aqua_core.WaveModelbevy_aqua_waves.bevy_aqua_waves$module→bevy_aqua_core.OceanWaves
- Direction
- bevy_aqua_waves uses bevy_aqua_core, so a change to bevy_aqua_core can break bevy_aqua_waves, while a change to bevy_aqua_waves can't break bevy_aqua_core.
- Position
- Below the diagonal: bevy_aqua_waves uses a module listed above it, which is the healthy direction.
37→26 bevy_aqua_waves uses bevy_aqua_core.cascade✕
- Connections
- 1 pair of types, where a type in bevy_aqua_waves uses a type in bevy_aqua_core.cascade.
- The types involved
bevy_aqua_waves.bevy_aqua_waves$module→bevy_aqua_core.cascade.GpuLayout
- Direction
- bevy_aqua_waves uses bevy_aqua_core.cascade, so a change to bevy_aqua_core.cascade can break bevy_aqua_waves, while a change to bevy_aqua_waves can't break bevy_aqua_core.cascade.
- Position
- Below the diagonal: bevy_aqua_waves uses a module listed above it, which is the healthy direction.
37→30 bevy_aqua_waves uses bevy_aqua_core.waves_abi✕
- Connections
- 1 pair of types, where a type in bevy_aqua_waves uses a type in bevy_aqua_core.waves_abi.
- The types involved
bevy_aqua_waves.Frame→bevy_aqua_core.waves_abi.AnimWavesUniform
- Direction
- bevy_aqua_waves uses bevy_aqua_core.waves_abi, so a change to bevy_aqua_core.waves_abi can break bevy_aqua_waves, while a change to bevy_aqua_waves can't break bevy_aqua_core.waves_abi.
- Position
- Below the diagonal: bevy_aqua_waves uses a module listed above it, which is the healthy direction.
37→35 bevy_aqua_waves uses bevy_aqua_waves.fft✕
- Connections
- 2 pairs of types, where a type in bevy_aqua_waves uses a type in bevy_aqua_waves.fft.
- The types involved
bevy_aqua_waves.Frame→bevy_aqua_waves.fft.Uniformbevy_aqua_waves.bevy_aqua_waves$module→bevy_aqua_waves.fft.Uniform
- Direction
- bevy_aqua_waves uses bevy_aqua_waves.fft, so a change to bevy_aqua_waves.fft can break bevy_aqua_waves, while a change to bevy_aqua_waves can't break bevy_aqua_waves.fft.
- Position
- Below the diagonal: bevy_aqua_waves uses a module listed above it, which is the healthy direction.
38→1 bevy_aqua_waves.variance uses bevy_aqua_core✕
- Connections
- 1 pair of types, where a type in bevy_aqua_waves.variance uses a type in bevy_aqua_core.
- The types involved
bevy_aqua_waves.variance.variance$module→bevy_aqua_core.WaveModel
- Direction
- bevy_aqua_waves.variance uses bevy_aqua_core, so a change to bevy_aqua_core can break bevy_aqua_waves.variance, while a change to bevy_aqua_waves.variance can't break bevy_aqua_core.
- Position
- Below the diagonal: bevy_aqua_waves.variance uses a module listed above it, which is the healthy direction.
38→26 bevy_aqua_waves.variance uses bevy_aqua_core.cascade✕
- Connections
- 1 pair of types, where a type in bevy_aqua_waves.variance uses a type in bevy_aqua_core.cascade.
- The types involved
bevy_aqua_waves.variance.variance$module→bevy_aqua_core.cascade.GpuLayout
- Direction
- bevy_aqua_waves.variance uses bevy_aqua_core.cascade, so a change to bevy_aqua_core.cascade can break bevy_aqua_waves.variance, while a change to bevy_aqua_waves.variance can't break bevy_aqua_core.cascade.
- Position
- Below the diagonal: bevy_aqua_waves.variance uses a module listed above it, which is the healthy direction.
38→30 bevy_aqua_waves.variance uses bevy_aqua_core.waves_abi✕
- Connections
- 1 pair of types, where a type in bevy_aqua_waves.variance uses a type in bevy_aqua_core.waves_abi.
- The types involved
bevy_aqua_waves.variance.variance$module→bevy_aqua_core.waves_abi.AnimWavesUniform
- Direction
- bevy_aqua_waves.variance uses bevy_aqua_core.waves_abi, so a change to bevy_aqua_core.waves_abi can break bevy_aqua_waves.variance, while a change to bevy_aqua_waves.variance can't break bevy_aqua_core.waves_abi.
- Position
- Below the diagonal: bevy_aqua_waves.variance uses a module listed above it, which is the healthy direction.
39→1 bevy_aqua.ocean uses bevy_aqua_core✕
- Connections
- 1 pair of types, where a type in bevy_aqua.ocean uses a type in bevy_aqua_core.
- The types involved
bevy_aqua.ocean.BoundsKey→bevy_aqua_core.WaveModel
- Direction
- bevy_aqua.ocean uses bevy_aqua_core, so a change to bevy_aqua_core can break bevy_aqua.ocean, while a change to bevy_aqua.ocean can't break bevy_aqua_core.
- Position
- Below the diagonal: bevy_aqua.ocean uses a module listed above it, which is the healthy direction.
39→8 bevy_aqua.ocean uses bevy_aqua_geom.rings✕
- Connections
- 1 pair of types, where a type in bevy_aqua.ocean uses a type in bevy_aqua_geom.rings.
- The types involved
bevy_aqua.ocean.OceanGeometry→bevy_aqua_geom.rings.Patch
- Direction
- bevy_aqua.ocean uses bevy_aqua_geom.rings, so a change to bevy_aqua_geom.rings can break bevy_aqua.ocean, while a change to bevy_aqua.ocean can't break bevy_aqua_geom.rings.
- Position
- Below the diagonal: bevy_aqua.ocean uses a module listed above it, which is the healthy direction.
39→37 bevy_aqua.ocean uses bevy_aqua_waves✕
- Connections
- 1 pair of types, where a type in bevy_aqua.ocean uses a type in bevy_aqua_waves.
- The types involved
bevy_aqua.ocean.ocean$module→bevy_aqua_waves.DisplacementBounds
- Direction
- bevy_aqua.ocean uses bevy_aqua_waves, so a change to bevy_aqua_waves can break bevy_aqua.ocean, while a change to bevy_aqua.ocean can't break bevy_aqua_waves.
- Position
- Below the diagonal: bevy_aqua.ocean uses a module listed above it, which is the healthy direction.
40→4 bevy_aqua_waves.render uses bevy_aqua_core.pass✕
- Connections
- 4 pairs of types, where a type in bevy_aqua_waves.render uses a type in bevy_aqua_core.pass.
- The types involved
bevy_aqua_waves.render.Prepared→bevy_aqua_core.pass.Groupsbevy_aqua_waves.render.Prepared→bevy_aqua_core.pass.Passesbevy_aqua_waves.render.render$module→bevy_aqua_core.pass.PassSpecbevy_aqua_waves.render.render$module→bevy_aqua_core.pass.Span
- Direction
- bevy_aqua_waves.render uses bevy_aqua_core.pass, so a change to bevy_aqua_core.pass can break bevy_aqua_waves.render, while a change to bevy_aqua_waves.render can't break bevy_aqua_core.pass.
- Position
- Below the diagonal: bevy_aqua_waves.render uses a module listed above it, which is the healthy direction.
40→37 bevy_aqua_waves.render uses bevy_aqua_waves✕
- Connections
- 1 pair of types, where a type in bevy_aqua_waves.render uses a type in bevy_aqua_waves.
- The types involved
bevy_aqua_waves.render.render$module→bevy_aqua_waves.Frame
- Direction
- bevy_aqua_waves.render uses bevy_aqua_waves, so a change to bevy_aqua_waves can break bevy_aqua_waves.render, while a change to bevy_aqua_waves.render can't break bevy_aqua_waves.
- Position
- Below the diagonal: bevy_aqua_waves.render 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
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 15 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 5 | Medium |
Roadmap
Top priorities: 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; Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it; Resolve the 1 Small-team knowledge concentration finding(s) in Bus Factor.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| 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. | +6.3 pts | Medium | Architecture documentation |
| Resolve the 1 Small-team knowledge concentration finding(s) in Bus Factor. | +1.1 pts | Low | Bus Factor |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +0.7 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +0.7 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +0.7 pts | Low | Supply-chain Provenance & Signing |
| Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it. | +1.2 pts | Medium | Deployment & Rollback |
| Resolve the 6 Off the main sequence finding(s) in Coupling. | +0.1 pts | Low | Coupling |
| Bring the 4 bodies over 15 down to 15 or less in Cognitive Complexity — start with bevy_aqua_motion::prepass::queue_motion_prepass (cognitive 39), bevy_aqua_spray::runtime::emit_spray (cognitive 22), bevy_aqua_foam::render::write_foam (cognitive 16). | +0.3 pts | High | Cognitive Complexity |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 4.5 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.5 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| crates/bevy-aqua-foam/src/gpu_fixture.rs | 7.0 | Near-clean | Code Duplication: Duplicated block (77 lines × 2) |
| crates/bevy-aqua-waves/src/render.rs | 7.2 | Near-clean | God Classes: FunctionTooLong: bevy_aqua_waves::render::prepare_bind_groups |
| crates/bevy-aqua-motion/src/prepass.rs | 7.4 | Near-clean | Cyclomatic Complexity: bevy_aqua_motion::prepass::queue_motion_prepass (cyclomatic 17) |
| crates/bevy-aqua-foam/src/render.rs | 7.4 | Near-clean | Cognitive Complexity: bevy_aqua_foam::render::write_foam (cognitive 16) |
| crates/bevy-aqua-core/src/cascade.rs | 7.4 | Near-clean | God Classes: FileTooLong: src/cascade.rs |
| crates/bevy-aqua-spray/src/runtime.rs | 8.5 | Near-clean | Cognitive Complexity: bevy_aqua_spray::runtime::emit_spray (cognitive 22) |
| crates/bevy-aqua-query/src/lib.rs | 8.5 | Near-clean | Cognitive Complexity: bevy_aqua_query::extract_wave_queries (cognitive 16) |
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.9, 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, 71 of 85 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: the Rust half could not be measured — the Cargo suite in repository root was stopped before it finished (scratch ceiling). Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.rs) and this repository declares a Cargo test suite (repository root, 44 test files), but it was not re-run: its build outgrew the 12 GB scratch ceiling (14.255 GB measured) and was stopped; its suite was not run. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- 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 — 4 direct Cargo declaration(s) were read, but the outdated signal needs crates.io, and no committed Cargo.lock resolves them to versions, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- 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's deterministic call-shape rules are gated per language (docs/plans/deterministic-engine.md, P5; C# and each NeutralApiArms arm pass): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — 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 — 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. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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.
- X19 Unrestored process-global state — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala, PHP, Go, Swift, Erlang, F# and Visual Basic source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala, PHP, Go, Swift, Erlang, F# or Visual Basic was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go and JavaScript/TypeScript source only, and no C# was loaded and no PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go, JavaScript or TypeScript was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
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.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- 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").
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- 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
1 function(s) exceeded the cyclomatic complexity threshold of 15; the worst was bevy_aqua_motion::prepass::queue_motion_prepass at 17. A further 1 function(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being bevy_aqua_core::cascade::update at 18 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: crates/bevy-aqua-core/src/cascade.rs (bevy_aqua_core::cascade::update at 18). 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 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with bevy_aqua_motion::prepass::queue_motion_prepass (cyclomatic 17). — Refactoring it lifts Cyclomatic Complexity from 9.8 to about 10.0/10.
D2 · Cognitive Complexity
4 function(s) exceeded the cognitive complexity threshold of 15; the worst was bevy_aqua_motion::prepass::queue_motion_prepass at 39.
What to do
- Bring the 4 bodies over 15 down to 15 or less in Cognitive Complexity — start with bevy_aqua_motion::prepass::queue_motion_prepass (cognitive 39), bevy_aqua_spray::runtime::emit_spray (cognitive 22), bevy_aqua_foam::render::write_foam (cognitive 16). — 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 8.7 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
6 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 4 FunctionTooLong finding(s) in God Classes — start with render.rs (3), prepass.rs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 2 FileTooLong finding(s) in God Classes — start with render.rs, cascade.rs. — One of this dimension's main actionable groups (2 warning-level).
D4 · Code Duplication
10 duplicated block group(s) detected. 4.5 % of the production lines (524 of 11,552) are in a reported copy. A further 2 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 8 of the 12 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
What to do
- Resolve the 2 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with gpu_fixture.rs (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Edited copy of a member (35 corresponding lines) finding(s) in Code Duplication — start with cascade.rs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copy of a member (12 corresponding lines) finding(s) in Code Duplication — start with render.rs. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
16 production modules (Cargo), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 6 module(s) off the main sequence.
What to do
- Resolve the 6 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (6 warning-level).
D6 · Cohesion (LCOM4)
0 of 9 classes have LCOM4 above 3.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 526 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository commits no Cargo.lock, so its graph was resolved here: its manifests' `[dependencies]` and `[build-dependencies]` closed over the crates.io index, each crate at the newest release its requirement admits (what a fresh `cargo generate-lockfile` picks, not a graph the repository has pinned). Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. This repository publishes itself under MIT OR Apache-2.0, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window. Repeated repair below the complexity floor: crates/bevy-aqua-reflect/src/camera.rs (8 of 9 changes were fixes); crates/bevy-aqua-foam/src/render.rs (4 of 6 changes were fixes); crates/bevy-aqua-spray/src/runtime.rs (3 of 5 changes were fixes)
What to do
- Resolve the 4 Repeated repair finding(s) in Churn × Complexity Hotspots — start with camera.rs, render.rs, runtime.rs. — One of this dimension's main actionable groups (4 warning-level).
D16 · Bus Factor
11 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is crates/bevy-aqua-reflect/src/camera.rs. Counted over 36 of the 46 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
0 deducted task-comment markers across 11552 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
D19 · Documentation Quality
2 of 2 documentation facets pass in full. 10 document(s) read across 16 unit(s).
D26 · Project Cohesion
0 of 16 build units (Cargo) flagged as possibly oversized/incoherent.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
15 finding(s): 0 critical, 15 high, 0 medium, 0 low. 15 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- No action in Static Analysis (SAST) — all 15 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (15 issue-level, 0 of them charged here).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 36 of the 46 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — 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).
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX9 · CQS / query purity
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
M1 · Documentation (README)
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
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.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add cargo-audit / cargo-deny (or clippy) (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 3 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:4
- `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`. — Cargo.toml:12
What to do
- Add a SAST step to CI running what this repository's stack ships: cargo-audit / cargo-deny (or clippy) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
P6 · Release Hygiene
X12 · Unreachable branch
X16 · Unfloored truncation loop
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X5 · Nullable reference types
- `mesh.compute_aabb()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `init` 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`). — src/ocean.rs:62
- `components.into_iter().filter(|wave|{wave.wavelength>=layout.cascades[0].max_wavelength*0.5&&wave.wavelength<layout.cascades[LOD_COUNT-1].max_wavelength}).collect::<Vec<_>>().try_into()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `make_uniform` 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`). — crates/bevy-aqua-waves/src/lib.rs:196
- `uniform.as_ref()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `prepare_bind_groups` 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`). (×2) — crates/bevy-aqua-waves/src/render.rs:381, crates/bevy-aqua-foam/src/render.rs:156
- `fft_uniform.as_ref()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `prepare_bind_groups` 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`). — crates/bevy-aqua-waves/src/render.rs:382
- `image.data.as_ref()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `spectral` 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`). — crates/bevy-aqua-waves/src/variance.rs:33
- `bytes[offset..offset+4].try_into()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `spectral_layer_range` 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`). — crates/bevy-aqua-waves/src/variance.rs:76
- `bytes[offset+4..offset+8].try_into()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `spectral_layer_range` 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`). — crates/bevy-aqua-waves/src/variance.rs:77
- `materials.get_mut(id)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `publish` 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`). — crates/bevy-aqua-waves/src/variance.rs:138
- `FIELD_TEXTURE_FORMAT.block_copy_size(None)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `bake` 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`). — crates/bevy-aqua-shore/src/bake.rs:99
- `images.get_mut(&slot.raw)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `ensure_slots` 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`). — crates/bevy-aqua-reflect/src/camera.rs:322
- `images.get_mut(&slot.image)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `ensure_slots` 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`). — crates/bevy-aqua-reflect/src/camera.rs:327
- `wrapper.write(&requests)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `pack_requests` 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`). — crates/bevy-aqua-query/src/lib.rs:333
- `wrapper.create()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `decode_results` 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`). — crates/bevy-aqua-query/src/lib.rs:341
- `descriptor.fragment.as_mut()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `specialize` 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`). — crates/bevy-aqua-motion/src/prepass.rs:86
- `descriptor.depth_stencil.as_mut()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `specialize` 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`). — crates/bevy-aqua-motion/src/prepass.rs:92
- `phases.get_mut(&retained)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `queue_motion_prepass` 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`). — crates/bevy-aqua-motion/src/prepass.rs:315
- `TextureFormat::Rgba16Float.block_copy_size(None)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `make_state_texture` 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`). — crates/bevy-aqua-foam/src/lib.rs:229
- `Image::from_buffer(PATTERN_BYTES,ImageType::Extension("png"),CompressedImageFormats::NONE,true,sampler,RenderAssetUsages::MAIN_WORLD|RenderAssetUsages::RENDER_WORLD,)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `make_pattern_texture` 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`). — crates/bevy-aqua-foam/src/lib.rs:338
- `decoded.data.take()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `make_pattern_texture` 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`). — crates/bevy-aqua-foam/src/lib.rs:349
- `materials.get(&data.material)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `update` 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`). — crates/bevy-aqua-core/src/cascade.rs:562
- `materials.get_mut(&data.material)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `update` 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`). — crates/bevy-aqua-core/src/cascade.rs:633
- `TextureFormat::Rgba16Float.block_copy_size(None)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `make_array_texture` 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`). — crates/bevy-aqua-core/src/cascade.rs:681
- `Image::from_buffer(DETAIL_NORMAL_BYTES,ImageType::Extension("png"),CompressedImageFormats::NONE,false,sampler,RenderAssetUsages::MAIN_WORLD|RenderAssetUsages::RENDER_WORLD,)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `make_detail_normal_texture` 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`). — crates/bevy-aqua-core/src/cascade.rs:735
- `image.data.take()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `make_detail_normal_texture` 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`). — crates/bevy-aqua-core/src/cascade.rs:745
- `FIELD_TEXTURE_FORMAT.block_copy_size(None)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `from_world` 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`). — crates/bevy-aqua-core/src/fields.rs:66
- `self.keys.iter().position(|&(k,e)|k==key&&e==entry)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `get` 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`). — crates/bevy-aqua-core/src/pass.rs:192
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 | 93.3 | Exemplary | Solid. |
| Architecture | 97.3 | Exemplary | Strongest area. |
| Maturity | 62.8 | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 65.0 | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 75.0 | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 75 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.
- AX2 Stateful singletons — Not applicable: 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
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository starts no server another machine can reach (no actix-web HttpServer, axum::serve, Rocket launch, warp::serve, poem or salvo Server, tonic Server::builder, hyper or tiny_http server outside examples and tests, none bound beyond loopback). Access control is therefore N/A here — a crate is authorized by the application that serves it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~7641 lines of test source are present (.rs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .rs suite was found but not re-run
- D12 Dependency Hygiene — Not scored — 4 direct Cargo declaration(s) were read, but the outdated signal needs crates.io, and no committed Cargo.lock resolves them to versions, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (1441 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — API consistency is measured on C#, TypeScript, Go only; the exposed Rust surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ 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 .rs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Cargo manifest — not scanned yet).
- 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) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- 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.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Cargo manifest — not scanned yet).
- 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 — Rust suite
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (24 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 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
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P2 Observability — This repository's Rust source (16 module(s), 46 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Rust 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 not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `#[bench]`, criterion's `bench_function`/`bench_with_input`, `#[divan::bench]` or `#[library_benchmark]` in any `.rs` file, or criterion, divan, iai or a `[[bench]]` target in a Cargo.toml, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not 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.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — No web surface: 41 Rust file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. This repository serves no HTTP of its own — no HTTP-server crate (actix-web, axum, Rocket, warp, poem, tide, salvo, tonic, a hyper server, …) among its Cargo manifests' run-time dependencies, and no server started in its production source — so HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library or worker. If this codebase starts serving HTTP, the dimension reactivates automatically.
- 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
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X2 Cancellation propagation — no C# was loaded; this repository's Rust was read, and no request in it can be cancelled by a caller — a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. Rust's compiler refuses the unsynchronised version: a collection shared between a callback's thread and the waiting body must be `Sync`, which a `Vec`, `VecDeque` or `HashMap` is only behind a `Mutex`/`RwLock`, so the race this check looks for cannot be written in safe Rust. Not a gap in the analyzer and not a finding about your code.
- 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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — 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 Rust was read, and it logs through none: the `log` crate's macros take one finished message (as log4net does in C#; its `kv` values are an opt-in its backends mostly drop), `println!`/`eprintln!` are not loggers, or it makes no log call outside its tests and examples at all. Calls through `tracing` (`tracing::info!`, or `info!` imported from it) 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.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 15 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 61 finding(s)
- Symbol treated as nullable, then dereferenced unguarded src/ocean.rs:62
- Symbol treated as nullable, then dereferenced unguarded crates/bevy-aqua-waves/src/lib.rs:196
- Symbol treated as nullable, then dereferenced unguarded crates/bevy-aqua-waves/src/render.rs:381
- Symbol treated as nullable, then dereferenced unguarded crates/bevy-aqua-waves/src/render.rs:382
- Symbol treated as nullable, then dereferenced unguarded crates/bevy-aqua-waves/src/variance.rs:33
- Symbol treated as nullable, then dereferenced unguarded crates/bevy-aqua-waves/src/variance.rs:76
- Symbol treated as nullable, then dereferenced unguarded crates/bevy-aqua-waves/src/variance.rs:77
- Symbol treated as nullable, then dereferenced unguarded crates/bevy-aqua-waves/src/variance.rs:138
- Symbol treated as nullable, then dereferenced unguarded crates/bevy-aqua-shore/src/bake.rs:99
- Symbol treated as nullable, then dereferenced unguarded crates/bevy-aqua-reflect/src/camera.rs:322
- Symbol treated as nullable, then dereferenced unguarded crates/bevy-aqua-reflect/src/camera.rs:327
- Symbol treated as nullable, then dereferenced unguarded crates/bevy-aqua-query/src/lib.rs:333
- Symbol treated as nullable, then dereferenced unguarded crates/bevy-aqua-query/src/lib.rs:341
- Symbol treated as nullable, then dereferenced unguarded crates/bevy-aqua-motion/src/prepass.rs:86
- Symbol treated as nullable, then dereferenced unguarded crates/bevy-aqua-motion/src/prepass.rs:92
- Symbol treated as nullable, then dereferenced unguarded crates/bevy-aqua-motion/src/prepass.rs:315
- Symbol treated as nullable, then dereferenced unguarded crates/bevy-aqua-foam/src/lib.rs:229
- Symbol treated as nullable, then dereferenced unguarded crates/bevy-aqua-foam/src/lib.rs:338
- Symbol treated as nullable, then dereferenced unguarded crates/bevy-aqua-foam/src/lib.rs:349
- Symbol treated as nullable, then dereferenced unguarded crates/bevy-aqua-foam/src/render.rs:156
- Symbol treated as nullable, then dereferenced unguarded crates/bevy-aqua-core/src/cascade.rs:562
- Symbol treated as nullable, then dereferenced unguarded crates/bevy-aqua-core/src/cascade.rs:633
- Symbol treated as nullable, then dereferenced unguarded crates/bevy-aqua-core/src/cascade.rs:681
- Symbol treated as nullable, then dereferenced unguarded crates/bevy-aqua-core/src/cascade.rs:735
- Symbol treated as nullable, then dereferenced unguarded crates/bevy-aqua-core/src/cascade.rs:745
- Off the main sequence: bevy-aqua-fft
- Off the main sequence: bevy-aqua-geom
- Off the main sequence: bevy-aqua-light
- Off the main sequence: bevy-aqua-medium
- Off the main sequence: bevy-aqua-sdf
- Off the main sequence: bevy-aqua-core
- Repeated repair: crates/bevy-aqua-reflect/src/camera.rs crates/bevy-aqua-reflect/src/camera.rs:200
- Repeated repair: crates/bevy-aqua-foam/src/render.rs crates/bevy-aqua-foam/src/render.rs:187
- Repeated repair: crates/bevy-aqua-spray/src/runtime.rs crates/bevy-aqua-spray/src/runtime.rs:153
- Repeated repair: crates/bevy-aqua-shore/src/lib.rs crates/bevy-aqua-shore/src/lib.rs:83
- FunctionTooLong: bevy_aqua_waves::render::prepare_bind_groups crates/bevy-aqua-waves/src/render.rs:309
- FunctionTooLong: bevy_aqua_waves::render::pass_table crates/bevy-aqua-waves/src/render.rs:60
- FunctionTooLong: bevy_aqua_waves::render::fft_spans crates/bevy-aqua-waves/src/render.rs:591
- FunctionTooLong: bevy_aqua_motion::prepass::queue_motion_prepass crates/bevy-aqua-motion/src/prepass.rs:263
- FileTooLong: src/render.rs crates/bevy-aqua-waves/src/render.rs
- FileTooLong: src/cascade.rs crates/bevy-aqua-core/src/cascade.rs
- Duplicated block (10 lines × 2) crates/bevy-aqua-foam/src/gpu_fixture.rs:116
- Duplicated block (10 lines × 2) crates/bevy-aqua-foam/src/gpu_fixture.rs:234
- bevy_aqua_motion::prepass::queue_motion_prepass (cyclomatic 17) crates/bevy-aqua-motion/src/prepass.rs:263
- bevy_aqua_motion::prepass::queue_motion_prepass (cognitive 39) crates/bevy-aqua-motion/src/prepass.rs:263
- bevy_aqua_spray::runtime::emit_spray (cognitive 22) crates/bevy-aqua-spray/src/runtime.rs:153
- bevy_aqua_foam::render::write_foam (cognitive 16) crates/bevy-aqua-foam/src/render.rs:187
- bevy_aqua_query::extract_wave_queries (cognitive 16) crates/bevy-aqua-query/src/lib.rs:401
- REDACTED
- Edited copy of a member (35 corresponding lines) crates/bevy-aqua-core/src/cascade.rs:678
- Edited copy of a member (12 corresponding lines) crates/bevy-aqua-foam/src/render.rs:94
- Duplicated block (25 lines × 2) crates/bevy-aqua-core/src/cascade.rs:688
- Duplicated block (16 lines × 2) crates/bevy-aqua-foam/src/render.rs:115
- Duplicated block (77 lines × 2) crates/bevy-aqua-foam/src/gpu_fixture.rs:147
- Duplicated block (43 lines × 2) crates/bevy-aqua-foam/src/gpu_fixture.rs:32
- Duplicated block (27 lines × 2) crates/bevy-aqua-foam/src/gpu_fixture.rs:87
- Duplicated block (17 lines × 2) crates/bevy-aqua-foam/src/gpu_fixture.rs:128
- Duplicated block (7 lines × 2) crates/bevy-aqua-foam/src/gpu_fixture.rs:76
- Duplicated block (8 lines × 2) crates/bevy-aqua-foam/src/gpu_fixture.rs:225
Minor — 9 finding(s)
- Small-team knowledge concentration
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- No SAST REDACTED:4
- No dependency-update automation Cargo.toml:12
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-d34d7b5460054023b5b66fa09f85edb5/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-d34d7b5460054023b5b66fa09f85edb5/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 . | 15 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Cargo manifest — not scanned yet). | 0 | — |
| 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. | 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 | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Cargo manifest — not scanned yet). | 0 | — |