Executive summary
image-rs/image meets our standard for a preview release, though we found no recorded design decisions and no architecture document or diagram. It scores 65 out of 100 and is rated Strong, and all 33 of its critical findings are security problems in the build pipeline.
Maturity, at 53, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 11 points. Adding a diagnostic log is another step, worth about 6 points. Raising Maturity to 62 would lift the score to about 69.
Thirty-two pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One pipeline step installs packages that can change without warning. Pinning each tool to an exact version and pinning what the pipeline installs would close both risks.
The product code is 36,561 lines, about €46,000 to rebuild.
If Maturity rose from 53 to 62, the lowest score rated Strong, the score would rise from 65 to about 69.
New since the last survey: 1 finding
- Supply-chain Provenance & Signing · REDACTED
Fixed since the last survey: 1 finding
- Supply-chain Provenance & Signing REDACTED
Rebuild cost: about €46,000 · Estimate
| Cost to rebuild | €15,000 to €77,000, for 254 to 807 hours of work, about 0.3 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.9 at a score of 65. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 36,561 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 animation | 2 math.rect | 3 io | 4 io.encoder | 5 metadata | 6 traits.private | 7 codecs.jpeg.encoder | 8 io.limits | 9 metadata.moxcms | 10 traits | 11 images.sub_image | 12 io.decoder | 13 codecs.ico.decoder | 14 images.generic_image | 15 io.format | 16 images.buffer | 17 io.image_reader_type | 18 codecs.bmp.decoder | 19 codecs.jpeg.decoder | 20 error | 21 codecs.png | 22 imageops.sample | 23 images.dynimage | 24 metadata.cicp | 25 color | 26 codecs.bmp.encoder | 27 codecs.farbfeld | 28 codecs.gif | 29 codecs.pnm.encoder | 30 codecs.tga.decoder | 31 codecs.tiff | 32 images.flat | 33 codecs.avif.yuv | 34 codecs.hdr.decoder | 35 codecs.openexr | 36 codecs.pnm.decoder | 37 codecs.qoi | 38 codecs.tga.encoder | 39 codecs.avif.decoder | 40 codecs.hdr.encoder |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 animation | ||||||||||||||||||||||||||||||||||||||||
| 2 math.rect | ||||||||||||||||||||||||||||||||||||||||
| 3 io | 2 | |||||||||||||||||||||||||||||||||||||||
| 4 io.encoder | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 5 metadata | 2 | |||||||||||||||||||||||||||||||||||||||
| 6 traits.private | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 7 codecs.jpeg.encoder | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 8 io.limits | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 9 metadata.moxcms | 1 | 1 | 3 | |||||||||||||||||||||||||||||||||||||
| 10 traits | 1 | 1 | 4 | |||||||||||||||||||||||||||||||||||||
| 11 images.sub_image | 1 | 1 | 2 | 2 | ||||||||||||||||||||||||||||||||||||
| 12 io.decoder | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 13 codecs.ico.decoder | 1 | 4 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 14 images.generic_image | 2 | 2 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 15 io.format | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 images.buffer | 1 | 2 | 1 | 6 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 17 io.image_reader_type | 1 | 2 | 4 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 18 codecs.bmp.decoder | 1 | 1 | 5 | 1 | ||||||||||||||||||||||||||||||||||||
| 19 codecs.jpeg.decoder | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 20 error | 1 | 1 | 1 | 1 | 7 | |||||||||||||||||||||||||||||||||||
| 21 codecs.png | 2 | 1 | 2 | 1 | 8 | 1 | 2 | 5 | ||||||||||||||||||||||||||||||||
| 22 imageops.sample | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 23 images.dynimage | 1 | 2 | 1 | 2 | 2 | 2 | 1 | 1 | 3 | 2 | 1 | |||||||||||||||||||||||||||||
| 24 metadata.cicp | 3 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 25 color | 12 | 8 | 1 | |||||||||||||||||||||||||||||||||||||
| 26 codecs.bmp.encoder | 2 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 27 codecs.farbfeld | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 28 codecs.gif | 3 | 1 | 1 | 1 | 3 | 1 | 2 | |||||||||||||||||||||||||||||||||
| 29 codecs.pnm.encoder | 1 | 4 | ||||||||||||||||||||||||||||||||||||||
| 30 codecs.tga.decoder | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 31 codecs.tiff | 1 | 1 | 3 | 3 | ||||||||||||||||||||||||||||||||||||
| 32 images.flat | 2 | 3 | 1 | 3 | ||||||||||||||||||||||||||||||||||||
| 33 codecs.avif.yuv | 1 | |||||||||||||||||||||||||||||||||||||||
| 34 codecs.hdr.decoder | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 35 codecs.openexr | 1 | 1 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 36 codecs.pnm.decoder | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 37 codecs.qoi | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 38 codecs.tga.encoder | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 39 codecs.avif.decoder | 2 | 2 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 40 codecs.hdr.encoder | 1 | 2 | 1 |
3→25 io uses color part of a loop✕
- Connections
- 2 pairs of types, where a type in io uses a type in color.
- The types involved
image.io.DecoderPreparedImage→image.color.ColorTypeimage.io.ImageLayout→image.color.ColorType
- Direction
- io uses color, so a change to color can break io, while a change to io can't break color.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
4→23 io.encoder uses images.dynimage part of a loop✕
- Connections
- 2 pairs of types, where a type in io.encoder uses a type in images.dynimage.
- The types involved
image.io.encoder.ImageEncoder→image.images.dynimage.DynamicImageimage.io.encoder.encoder$module→image.images.dynimage.DynamicImage
- Direction
- io.encoder uses images.dynimage, so a change to images.dynimage can break io.encoder, while a change to io.encoder can't break images.dynimage.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
4→25 io.encoder uses color part of a loop✕
- Connections
- 2 pairs of types, where a type in io.encoder uses a type in color.
- The types involved
image.io.encoder.ImageEncoder→image.color.ExtendedColorTypeimage.io.encoder.ImageEncoderBoxed→image.color.ExtendedColorType
- Direction
- io.encoder uses color, so a change to color can break io.encoder, while a change to io.encoder can't break color.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→24 metadata uses metadata.cicp part of a loop✕
- Connections
- 2 pairs of types, where a type in metadata uses a type in metadata.cicp.
- The types involved
image.metadata.CmsProvider→image.metadata.cicp.Cicpimage.metadata.CmsProvider→image.metadata.cicp.CicpTransform
- Direction
- metadata uses metadata.cicp, so a change to metadata.cicp can break metadata, while a change to metadata can't break metadata.cicp.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→24 traits.private uses metadata.cicp part of a loop✕
- Connections
- 2 pairs of types, where a type in traits.private uses a type in metadata.cicp.
- The types involved
image.traits.private.HelpDispatchTransform→image.metadata.cicp.CicpTransformimage.traits.private.private$module→image.metadata.cicp.CicpTransform
- Direction
- traits.private uses metadata.cicp, so a change to metadata.cicp can break traits.private, while a change to traits.private can't break metadata.cicp.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→25 traits.private uses color part of a loop✕
- Connections
- 1 pair of types, where a type in traits.private uses a type in color.
- The types involved
image.traits.private.LayoutWithColor→image.color.ColorType
- Direction
- traits.private uses color, so a change to color can break traits.private, while a change to traits.private can't break color.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→4 codecs.jpeg.encoder uses io.encoder✕
- Connections
- 2 pairs of types, where a type in codecs.jpeg.encoder uses a type in io.encoder.
- The types involved
image.codecs.jpeg.encoder.JpegEncoder→image.io.encoder.ImageEncoderimage.codecs.jpeg.encoder.JpegEncoder→image.io.encoder.MethodSealedToImage
- Direction
- codecs.jpeg.encoder uses io.encoder, so a change to io.encoder can break codecs.jpeg.encoder, while a change to codecs.jpeg.encoder can't break io.encoder.
- Position
- Below the diagonal: codecs.jpeg.encoder uses a module listed above it, which is the healthy direction.
7→23 codecs.jpeg.encoder uses images.dynimage part of a loop✕
- Connections
- 1 pair of types, where a type in codecs.jpeg.encoder uses a type in images.dynimage.
- The types involved
image.codecs.jpeg.encoder.JpegEncoder→image.images.dynimage.DynamicImage
- Direction
- codecs.jpeg.encoder uses images.dynimage, so a change to images.dynimage can break codecs.jpeg.encoder, while a change to codecs.jpeg.encoder can't break images.dynimage.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→25 codecs.jpeg.encoder uses color part of a loop✕
- Connections
- 1 pair of types, where a type in codecs.jpeg.encoder uses a type in color.
- The types involved
image.codecs.jpeg.encoder.JpegEncoder→image.color.ExtendedColorType
- Direction
- codecs.jpeg.encoder uses color, so a change to color can break codecs.jpeg.encoder, while a change to codecs.jpeg.encoder can't break color.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→32 codecs.jpeg.encoder uses images.flat part of a loop✕
- Connections
- 1 pair of types, where a type in codecs.jpeg.encoder uses a type in images.flat.
- The types involved
image.codecs.jpeg.encoder.EncoderError→image.images.flat.Error
- Direction
- codecs.jpeg.encoder uses images.flat, so a change to images.flat can break codecs.jpeg.encoder, while a change to codecs.jpeg.encoder can't break images.flat.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→3 io.limits uses io✕
- Connections
- 1 pair of types, where a type in io.limits uses a type in io.
- The types involved
image.io.limits.Limits→image.io.DecoderPreparedImage
- Direction
- io.limits uses io, so a change to io can break io.limits, while a change to io.limits can't break io.
- Position
- Below the diagonal: io.limits uses a module listed above it, which is the healthy direction.
8→25 io.limits uses color part of a loop✕
- Connections
- 1 pair of types, where a type in io.limits uses a type in color.
- The types involved
image.io.limits.Limits→image.color.ColorType
- Direction
- io.limits uses color, so a change to color can break io.limits, while a change to io.limits can't break color.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→5 metadata.moxcms uses metadata✕
- Connections
- 1 pair of types, where a type in metadata.moxcms uses a type in metadata.
- The types involved
image.metadata.moxcms.Moxcms→image.metadata.CmsProvider
- Direction
- metadata.moxcms uses metadata, so a change to metadata can break metadata.moxcms, while a change to metadata.moxcms can't break metadata.
- Position
- Below the diagonal: metadata.moxcms uses a module listed above it, which is the healthy direction.
9→6 metadata.moxcms uses traits.private✕
- Connections
- 1 pair of types, where a type in metadata.moxcms uses a type in traits.private.
- The types involved
image.metadata.moxcms.ColorProfile→image.traits.private.LayoutWithColor
- Direction
- metadata.moxcms uses traits.private, so a change to traits.private can break metadata.moxcms, while a change to metadata.moxcms can't break traits.private.
- Position
- Below the diagonal: metadata.moxcms uses a module listed above it, which is the healthy direction.
9→24 metadata.moxcms uses metadata.cicp part of a loop✕
- Connections
- 3 pairs of types, where a type in metadata.moxcms uses a type in metadata.cicp.
- The types involved
image.metadata.moxcms.Moxcms→image.metadata.cicp.Cicpimage.metadata.moxcms.Moxcms→image.metadata.cicp.CicpTransformimage.metadata.moxcms.Moxcms→image.metadata.cicp.RgbTransforms
- Direction
- metadata.moxcms uses metadata.cicp, so a change to metadata.cicp can break metadata.moxcms, while a change to metadata.moxcms can't break metadata.cicp.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→1 traits uses animation✕
- Connections
- 1 pair of types, where a type in traits uses a type in animation.
- The types involved
image.traits.Lerp→image.animation.Ratio
- Direction
- traits uses animation, so a change to animation can break traits, while a change to traits can't break animation.
- Position
- Below the diagonal: traits uses a module listed above it, which is the healthy direction.
10→6 traits uses traits.private✕
- Connections
- 1 pair of types, where a type in traits uses a type in traits.private.
- The types involved
image.traits.PixelWithColorType→image.traits.private.SealedPixelWithColorType
- Direction
- traits uses traits.private, so a change to traits.private can break traits, while a change to traits can't break traits.private.
- Position
- Below the diagonal: traits uses a module listed above it, which is the healthy direction.
10→25 traits uses color part of a loop✕
- Connections
- 4 pairs of types, where a type in traits uses a type in color.
- The types involved
image.traits.Pixel→image.color.Lumaimage.traits.Pixel→image.color.LumaAimage.traits.Pixel→image.color.Rgbimage.traits.Pixel→image.color.Rgba
- Direction
- traits uses color, so a change to color can break traits, while a change to traits can't break color.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→2 images.sub_image uses math.rect✕
- Connections
- 1 pair of types, where a type in images.sub_image uses a type in math.rect.
- The types involved
image.images.sub_image.SubImage→image.math.rect.Rect
- Direction
- images.sub_image uses math.rect, so a change to math.rect can break images.sub_image, while a change to images.sub_image can't break math.rect.
- Position
- Below the diagonal: images.sub_image uses a module listed above it, which is the healthy direction.
11→10 images.sub_image uses traits✕
- Connections
- 1 pair of types, where a type in images.sub_image uses a type in traits.
- The types involved
image.images.sub_image.SubImageInner→image.traits.Pixel
- Direction
- images.sub_image uses traits, so a change to traits can break images.sub_image, while a change to images.sub_image can't break traits.
- Position
- Below the diagonal: images.sub_image uses a module listed above it, which is the healthy direction.
11→14 images.sub_image uses images.generic_image part of a loop✕
- Connections
- 2 pairs of types, where a type in images.sub_image uses a type in images.generic_image.
- The types involved
image.images.sub_image.SubImageInner→image.images.generic_image.GenericImageimage.images.sub_image.SubImageInner→image.images.generic_image.GenericImageView
- Direction
- images.sub_image uses images.generic_image, so a change to images.generic_image can break images.sub_image, while a change to images.sub_image can't break images.generic_image.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→16 images.sub_image uses images.buffer part of a loop✕
- Connections
- 2 pairs of types, where a type in images.sub_image uses a type in images.buffer.
- The types involved
image.images.sub_image.SubImage→image.images.buffer.ImageBufferimage.images.sub_image.SubImageInner→image.images.buffer.ImageBuffer
- Direction
- images.sub_image uses images.buffer, so a change to images.buffer can break images.sub_image, while a change to images.sub_image can't break images.buffer.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→1 io.decoder uses animation✕
- Connections
- 1 pair of types, where a type in io.decoder uses a type in animation.
- The types involved
image.io.decoder.DecodedImageAttributes→image.animation.Delay
- Direction
- io.decoder uses animation, so a change to animation can break io.decoder, while a change to io.decoder can't break animation.
- Position
- Below the diagonal: io.decoder uses a module listed above it, which is the healthy direction.
12→5 io.decoder uses metadata✕
- Connections
- 2 pairs of types, where a type in io.decoder uses a type in metadata.
- The types involved
image.io.decoder.DecodedAnimationAttributes→image.metadata.LoopCountimage.io.decoder.DecodedImageAttributes→image.metadata.Orientation
- Direction
- io.decoder uses metadata, so a change to metadata can break io.decoder, while a change to io.decoder can't break metadata.
- Position
- Below the diagonal: io.decoder uses a module listed above it, which is the healthy direction.
12→8 io.decoder uses io.limits✕
- Connections
- 1 pair of types, where a type in io.decoder uses a type in io.limits.
- The types involved
image.io.decoder.ImageDecoder→image.io.limits.Limits
- Direction
- io.decoder uses io.limits, so a change to io.limits can break io.decoder, while a change to io.decoder can't break io.limits.
- Position
- Below the diagonal: io.decoder uses a module listed above it, which is the healthy direction.
12→25 io.decoder uses color part of a loop✕
- Connections
- 1 pair of types, where a type in io.decoder uses a type in color.
- The types involved
image.io.decoder.DecodedImageAttributes→image.color.ExtendedColorType
- Direction
- io.decoder uses color, so a change to color can break io.decoder, while a change to io.decoder can't break color.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→8 codecs.ico.decoder uses io.limits✕
- Connections
- 1 pair of types, where a type in codecs.ico.decoder uses a type in io.limits.
- The types involved
image.codecs.ico.decoder.IcoDecoder→image.io.limits.Limits
- Direction
- codecs.ico.decoder uses io.limits, so a change to io.limits can break codecs.ico.decoder, while a change to codecs.ico.decoder can't break io.limits.
- Position
- Below the diagonal: codecs.ico.decoder uses a module listed above it, which is the healthy direction.
13→12 codecs.ico.decoder uses io.decoder✕
- Connections
- 4 pairs of types, where a type in codecs.ico.decoder uses a type in io.decoder.
- The types involved
image.codecs.ico.decoder.IcoDecoder→image.io.decoder.DecodedAnimationAttributesimage.codecs.ico.decoder.IcoDecoder→image.io.decoder.FormatAttributesimage.codecs.ico.decoder.IcoDecoder→image.io.decoder.ImageDecoderimage.codecs.ico.decoder.IcoDecoder→image.io.decoder.SequenceControl
- Direction
- codecs.ico.decoder uses io.decoder, so a change to io.decoder can break codecs.ico.decoder, while a change to codecs.ico.decoder can't break io.decoder.
- Position
- Below the diagonal: codecs.ico.decoder uses a module listed above it, which is the healthy direction.
13→17 codecs.ico.decoder uses io.image_reader_type part of a loop✕
- Connections
- 2 pairs of types, where a type in codecs.ico.decoder uses a type in io.image_reader_type.
- The types involved
image.codecs.ico.decoder.IcoDecoder→image.io.image_reader_type.SpecComplianceimage.codecs.ico.decoder.decoder$module→image.io.image_reader_type.SpecCompliance
- Direction
- codecs.ico.decoder uses io.image_reader_type, so a change to io.image_reader_type can break codecs.ico.decoder, while a change to codecs.ico.decoder can't break io.image_reader_type.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→32 codecs.ico.decoder uses images.flat part of a loop✕
- Connections
- 1 pair of types, where a type in codecs.ico.decoder uses a type in images.flat.
- The types involved
image.codecs.ico.decoder.DecoderError→image.images.flat.Error
- Direction
- codecs.ico.decoder uses images.flat, so a change to images.flat can break codecs.ico.decoder, while a change to codecs.ico.decoder can't break images.flat.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→2 images.generic_image uses math.rect✕
- Connections
- 2 pairs of types, where a type in images.generic_image uses a type in math.rect.
- The types involved
image.images.generic_image.GenericImage→image.math.rect.Rectimage.images.generic_image.GenericImageView→image.math.rect.Rect
- Direction
- images.generic_image uses math.rect, so a change to math.rect can break images.generic_image, while a change to images.generic_image can't break math.rect.
- Position
- Below the diagonal: images.generic_image uses a module listed above it, which is the healthy direction.
14→10 images.generic_image uses traits✕
- Connections
- 2 pairs of types, where a type in images.generic_image uses a type in traits.
- The types involved
image.images.generic_image.GenericImage→image.traits.Pixelimage.images.generic_image.GenericImageView→image.traits.Pixel
- Direction
- images.generic_image uses traits, so a change to traits can break images.generic_image, while a change to images.generic_image can't break traits.
- Position
- Below the diagonal: images.generic_image uses a module listed above it, which is the healthy direction.
14→11 images.generic_image uses images.sub_image✕
- Connections
- 2 pairs of types, where a type in images.generic_image uses a type in images.sub_image.
- The types involved
image.images.generic_image.GenericImage→image.images.sub_image.SubImageimage.images.generic_image.GenericImageView→image.images.sub_image.SubImage
- Direction
- images.generic_image uses images.sub_image, so a change to images.sub_image can break images.generic_image, while a change to images.generic_image can't break images.sub_image.
- Position
- Below the diagonal: images.generic_image uses a module listed above it, which is the healthy direction.
14→16 images.generic_image uses images.buffer part of a loop✕
- Connections
- 1 pair of types, where a type in images.generic_image uses a type in images.buffer.
- The types involved
image.images.generic_image.GenericImageView→image.images.buffer.ImageBuffer
- Direction
- images.generic_image uses images.buffer, so a change to images.buffer can break images.generic_image, while a change to images.generic_image can't break images.buffer.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→13 io.format uses codecs.ico.decoder✕
- Connections
- 1 pair of types, where a type in io.format uses a type in codecs.ico.decoder.
- The types involved
image.io.format.ImageFormat→image.codecs.ico.decoder.IcoEntryImageFormat
- Direction
- io.format uses codecs.ico.decoder, so a change to codecs.ico.decoder can break io.format, while a change to io.format can't break codecs.ico.decoder.
- Position
- Below the diagonal: io.format uses a module listed above it, which is the healthy direction.
16→2 images.buffer uses math.rect✕
- Connections
- 1 pair of types, where a type in images.buffer uses a type in math.rect.
- The types involved
image.images.buffer.ImageBuffer→image.math.rect.Rect
- Direction
- images.buffer uses math.rect, so a change to math.rect can break images.buffer, while a change to images.buffer can't break math.rect.
- Position
- Below the diagonal: images.buffer uses a module listed above it, which is the healthy direction.
16→14 images.buffer uses images.generic_image✕
- Connections
- 2 pairs of types, where a type in images.buffer uses a type in images.generic_image.
- The types involved
image.images.buffer.ImageBuffer→image.images.generic_image.GenericImageimage.images.buffer.ImageBuffer→image.images.generic_image.GenericImageView
- Direction
- images.buffer uses images.generic_image, so a change to images.generic_image can break images.buffer, while a change to images.buffer can't break images.generic_image.
- Position
- Below the diagonal: images.buffer uses a module listed above it, which is the healthy direction.
16→15 images.buffer uses io.format✕
- Connections
- 1 pair of types, where a type in images.buffer uses a type in io.format.
- The types involved
image.images.buffer.ImageBuffer→image.io.format.ImageFormat
- Direction
- images.buffer uses io.format, so a change to io.format can break images.buffer, while a change to images.buffer can't break io.format.
- Position
- Below the diagonal: images.buffer uses a module listed above it, which is the healthy direction.
16→24 images.buffer uses metadata.cicp part of a loop✕
- Connections
- 6 pairs of types, where a type in images.buffer uses a type in metadata.cicp.
- The types involved
image.images.buffer.ConvertColorOptions→image.metadata.cicp.Cicpimage.images.buffer.ConvertColorOptions→image.metadata.cicp.CicpTransformimage.images.buffer.ImageBuffer→image.metadata.cicp.Cicpimage.images.buffer.ImageBuffer→image.metadata.cicp.CicpColorPrimariesimage.images.buffer.ImageBuffer→image.metadata.cicp.CicpRgbimage.images.buffer.ImageBuffer→image.metadata.cicp.CicpTransferCharacteristics
- Direction
- images.buffer uses metadata.cicp, so a change to metadata.cicp can break images.buffer, while a change to images.buffer can't break metadata.cicp.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→29 images.buffer uses codecs.pnm.encoder part of a loop✕
- Connections
- 1 pair of types, where a type in images.buffer uses a type in codecs.pnm.encoder.
- The types involved
image.images.buffer.ImageBuffer→image.codecs.pnm.encoder.FlatSamples
- Direction
- images.buffer uses codecs.pnm.encoder, so a change to codecs.pnm.encoder can break images.buffer, while a change to images.buffer can't break codecs.pnm.encoder.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→32 images.buffer uses images.flat part of a loop✕
- Connections
- 1 pair of types, where a type in images.buffer uses a type in images.flat.
- The types involved
image.images.buffer.ImageBuffer→image.images.flat.SampleLayout
- Direction
- images.buffer uses images.flat, so a change to images.flat can break images.buffer, while a change to images.buffer can't break images.flat.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→1 io.image_reader_type uses animation✕
- Connections
- 1 pair of types, where a type in io.image_reader_type uses a type in animation.
- The types involved
image.io.image_reader_type.ImageReader→image.animation.Frames
- Direction
- io.image_reader_type uses animation, so a change to animation can break io.image_reader_type, while a change to io.image_reader_type can't break animation.
- Position
- Below the diagonal: io.image_reader_type uses a module listed above it, which is the healthy direction.
17→8 io.image_reader_type uses io.limits✕
- Connections
- 2 pairs of types, where a type in io.image_reader_type uses a type in io.limits.
- The types involved
image.io.image_reader_type.ImageReader→image.io.limits.Limitsimage.io.image_reader_type.ImageReaderOptions→image.io.limits.Limits
- Direction
- io.image_reader_type uses io.limits, so a change to io.limits can break io.image_reader_type, while a change to io.image_reader_type can't break io.limits.
- Position
- Below the diagonal: io.image_reader_type uses a module listed above it, which is the healthy direction.
17→12 io.image_reader_type uses io.decoder✕
- Connections
- 4 pairs of types, where a type in io.image_reader_type uses a type in io.decoder.
- The types involved
image.io.image_reader_type.DecodedImageMetadata→image.io.decoder.DecodedImageAttributesimage.io.image_reader_type.DecodedImageMetadata→image.io.decoder.DecodedMetadataHintimage.io.image_reader_type.ImageReader→image.io.decoder.DecodedAnimationAttributesimage.io.image_reader_type.ImageReader→image.io.decoder.DecodedImageAttributes
- Direction
- io.image_reader_type uses io.decoder, so a change to io.decoder can break io.image_reader_type, while a change to io.image_reader_type can't break io.decoder.
- Position
- Below the diagonal: io.image_reader_type uses a module listed above it, which is the healthy direction.
17→15 io.image_reader_type uses io.format✕
- Connections
- 1 pair of types, where a type in io.image_reader_type uses a type in io.format.
- The types involved
image.io.image_reader_type.ImageReaderOptions→image.io.format.ImageFormat
- Direction
- io.image_reader_type uses io.format, so a change to io.format can break io.image_reader_type, while a change to io.image_reader_type can't break io.format.
- Position
- Below the diagonal: io.image_reader_type uses a module listed above it, which is the healthy direction.
17→23 io.image_reader_type uses images.dynimage part of a loop✕
- Connections
- 2 pairs of types, where a type in io.image_reader_type uses a type in images.dynimage.
- The types involved
image.io.image_reader_type.DecodedImageMetadata→image.images.dynimage.DynamicImageimage.io.image_reader_type.ImageReader→image.images.dynimage.DynamicImage
- Direction
- io.image_reader_type uses images.dynimage, so a change to images.dynimage can break io.image_reader_type, while a change to io.image_reader_type can't break images.dynimage.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→9 codecs.bmp.decoder uses metadata.moxcms✕
- Connections
- 1 pair of types, where a type in codecs.bmp.decoder uses a type in metadata.moxcms.
- The types involved
image.codecs.bmp.decoder.CalibratedRgb→image.metadata.moxcms.ColorProfile
- Direction
- codecs.bmp.decoder uses metadata.moxcms, so a change to metadata.moxcms can break codecs.bmp.decoder, while a change to codecs.bmp.decoder can't break metadata.moxcms.
- Position
- Below the diagonal: codecs.bmp.decoder uses a module listed above it, which is the healthy direction.
18→12 codecs.bmp.decoder uses io.decoder✕
- Connections
- 1 pair of types, where a type in codecs.bmp.decoder uses a type in io.decoder.
- The types involved
image.codecs.bmp.decoder.BmpDecoder→image.io.decoder.ImageDecoder
- Direction
- codecs.bmp.decoder uses io.decoder, so a change to io.decoder can break codecs.bmp.decoder, while a change to codecs.bmp.decoder can't break io.decoder.
- Position
- Below the diagonal: codecs.bmp.decoder uses a module listed above it, which is the healthy direction.
18→17 codecs.bmp.decoder uses io.image_reader_type✕
- Connections
- 5 pairs of types, where a type in codecs.bmp.decoder uses a type in io.image_reader_type.
- The types involved
image.codecs.bmp.decoder.Bitfields→image.io.image_reader_type.SpecComplianceimage.codecs.bmp.decoder.BmpDecoder→image.io.image_reader_type.SpecComplianceimage.codecs.bmp.decoder.ParsedCoreHeader→image.io.image_reader_type.SpecComplianceimage.codecs.bmp.decoder.ParsedInfoHeader→image.io.image_reader_type.SpecComplianceimage.codecs.bmp.decoder.decoder$module→image.io.image_reader_type.SpecCompliance
- Direction
- codecs.bmp.decoder uses io.image_reader_type, so a change to io.image_reader_type can break codecs.bmp.decoder, while a change to codecs.bmp.decoder can't break io.image_reader_type.
- Position
- Below the diagonal: codecs.bmp.decoder uses a module listed above it, which is the healthy direction.
18→32 codecs.bmp.decoder uses images.flat part of a loop✕
- Connections
- 1 pair of types, where a type in codecs.bmp.decoder uses a type in images.flat.
- The types involved
image.codecs.bmp.decoder.DecoderError→image.images.flat.Error
- Direction
- codecs.bmp.decoder uses images.flat, so a change to images.flat can break codecs.bmp.decoder, while a change to codecs.bmp.decoder can't break images.flat.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→8 codecs.jpeg.decoder uses io.limits✕
- Connections
- 1 pair of types, where a type in codecs.jpeg.decoder uses a type in io.limits.
- The types involved
image.codecs.jpeg.decoder.JpegDecoder→image.io.limits.Limits
- Direction
- codecs.jpeg.decoder uses io.limits, so a change to io.limits can break codecs.jpeg.decoder, while a change to codecs.jpeg.decoder can't break io.limits.
- Position
- Below the diagonal: codecs.jpeg.decoder uses a module listed above it, which is the healthy direction.
19→12 codecs.jpeg.decoder uses io.decoder✕
- Connections
- 2 pairs of types, where a type in codecs.jpeg.decoder uses a type in io.decoder.
- The types involved
image.codecs.jpeg.decoder.JpegDecoder→image.io.decoder.FormatAttributesimage.codecs.jpeg.decoder.JpegDecoder→image.io.decoder.ImageDecoder
- Direction
- codecs.jpeg.decoder uses io.decoder, so a change to io.decoder can break codecs.jpeg.decoder, while a change to codecs.jpeg.decoder can't break io.decoder.
- Position
- Below the diagonal: codecs.jpeg.decoder uses a module listed above it, which is the healthy direction.
19→17 codecs.jpeg.decoder uses io.image_reader_type✕
- Connections
- 1 pair of types, where a type in codecs.jpeg.decoder uses a type in io.image_reader_type.
- The types involved
image.codecs.jpeg.decoder.JpegDecoder→image.io.image_reader_type.SpecCompliance
- Direction
- codecs.jpeg.decoder uses io.image_reader_type, so a change to io.image_reader_type can break codecs.jpeg.decoder, while a change to codecs.jpeg.decoder can't break io.image_reader_type.
- Position
- Below the diagonal: codecs.jpeg.decoder uses a module listed above it, which is the healthy direction.
20→7 error uses codecs.jpeg.encoder✕
- Connections
- 1 pair of types, where a type in error uses a type in codecs.jpeg.encoder.
- The types involved
image.error.ImageError→image.codecs.jpeg.encoder.EncoderError
- Direction
- error uses codecs.jpeg.encoder, so a change to codecs.jpeg.encoder can break error, while a change to error can't break codecs.jpeg.encoder.
- Position
- Below the diagonal: error uses a module listed above it, which is the healthy direction.
20→15 error uses io.format✕
- Connections
- 1 pair of types, where a type in error uses a type in io.format.
- The types involved
image.error.ImageFormatHint→image.io.format.ImageFormat
- Direction
- error uses io.format, so a change to io.format can break error, while a change to error can't break io.format.
- Position
- Below the diagonal: error uses a module listed above it, which is the healthy direction.
20→18 error uses codecs.bmp.decoder✕
- Connections
- 1 pair of types, where a type in error uses a type in codecs.bmp.decoder.
- The types involved
image.error.ImageError→image.codecs.bmp.decoder.DecoderError
- Direction
- error uses codecs.bmp.decoder, so a change to codecs.bmp.decoder can break error, while a change to error can't break codecs.bmp.decoder.
- Position
- Below the diagonal: error uses a module listed above it, which is the healthy direction.
20→25 error uses color part of a loop✕
- Connections
- 1 pair of types, where a type in error uses a type in color.
- The types involved
image.error.TryFromExtendedColorError→image.color.ExtendedColorType
- Direction
- error uses color, so a change to color can break error, while a change to error can't break color.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→32 error uses images.flat part of a loop✕
- Connections
- 7 pairs of types, where a type in error uses a type in images.flat.
- The types involved
image.error.DecodingError→image.images.flat.Errorimage.error.EncodingError→image.images.flat.Errorimage.error.ImageError→image.images.flat.Errorimage.error.LimitError→image.images.flat.Errorimage.error.ParameterError→image.images.flat.Errorimage.error.TryFromExtendedColorError→image.images.flat.Errorimage.error.UnsupportedError→image.images.flat.Error
- Direction
- error uses images.flat, so a change to images.flat can break error, while a change to error can't break images.flat.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→2 codecs.png uses math.rect✕
- Connections
- 2 pairs of types, where a type in codecs.png uses a type in math.rect.
- The types involved
image.codecs.png.ApngDecoder→image.math.rect.Rectimage.codecs.png.png$module→image.math.rect.Rect
- Direction
- codecs.png uses math.rect, so a change to math.rect can break codecs.png, while a change to codecs.png can't break math.rect.
- Position
- Below the diagonal: codecs.png uses a module listed above it, which is the healthy direction.
21→3 codecs.png uses io✕
- Connections
- 1 pair of types, where a type in codecs.png uses a type in io.
- The types involved
image.codecs.png.png$module→image.io.ImageLayout
- Direction
- codecs.png uses io, so a change to io can break codecs.png, while a change to codecs.png can't break io.
- Position
- Below the diagonal: codecs.png uses a module listed above it, which is the healthy direction.
21→4 codecs.png uses io.encoder✕
- Connections
- 2 pairs of types, where a type in codecs.png uses a type in io.encoder.
- The types involved
image.codecs.png.PngEncoder→image.io.encoder.ImageEncoderimage.codecs.png.PngEncoder→image.io.encoder.MethodSealedToImage
- Direction
- codecs.png uses io.encoder, so a change to io.encoder can break codecs.png, while a change to codecs.png can't break io.encoder.
- Position
- Below the diagonal: codecs.png uses a module listed above it, which is the healthy direction.
21→8 codecs.png uses io.limits✕
- Connections
- 1 pair of types, where a type in codecs.png uses a type in io.limits.
- The types involved
image.codecs.png.PngDecoder→image.io.limits.Limits
- Direction
- codecs.png uses io.limits, so a change to io.limits can break codecs.png, while a change to codecs.png can't break io.limits.
- Position
- Below the diagonal: codecs.png uses a module listed above it, which is the healthy direction.
21→12 codecs.png uses io.decoder✕
- Connections
- 8 pairs of types, where a type in codecs.png uses a type in io.decoder.
- The types involved
image.codecs.png.ApngDecoder→image.io.decoder.DecodedAnimationAttributesimage.codecs.png.ApngDecoder→image.io.decoder.FormatAttributesimage.codecs.png.ApngDecoder→image.io.decoder.ImageDecoderimage.codecs.png.ApngDecoder→image.io.decoder.SequenceControlimage.codecs.png.PngDecoder→image.io.decoder.DecodedAnimationAttributesimage.codecs.png.PngDecoder→image.io.decoder.FormatAttributesimage.codecs.png.PngDecoder→image.io.decoder.ImageDecoderimage.codecs.png.png$module→image.io.decoder.DecodedImageAttributes
- Direction
- codecs.png uses io.decoder, so a change to io.decoder can break codecs.png, while a change to codecs.png can't break io.decoder.
- Position
- Below the diagonal: codecs.png uses a module listed above it, which is the healthy direction.
21→20 codecs.png uses error✕
- Connections
- 1 pair of types, where a type in codecs.png uses a type in error.
- The types involved
image.codecs.png.png$module→image.error.ImageError
- Direction
- codecs.png uses error, so a change to error can break codecs.png, while a change to codecs.png can't break error.
- Position
- Below the diagonal: codecs.png uses a module listed above it, which is the healthy direction.
21→23 codecs.png uses images.dynimage part of a loop✕
- Connections
- 2 pairs of types, where a type in codecs.png uses a type in images.dynimage.
- The types involved
image.codecs.png.ApngDecoder→image.images.dynimage.DynamicImageimage.codecs.png.PngEncoder→image.images.dynimage.DynamicImage
- Direction
- codecs.png uses images.dynimage, so a change to images.dynimage can break codecs.png, while a change to codecs.png can't break images.dynimage.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→25 codecs.png uses color part of a loop✕
- Connections
- 5 pairs of types, where a type in codecs.png uses a type in color.
- The types involved
image.codecs.png.PngDecoder→image.color.ColorTypeimage.codecs.png.PngDecoder→image.color.ExtendedColorTypeimage.codecs.png.PngEncoder→image.color.ExtendedColorTypeimage.codecs.png.png$module→image.color.ColorTypeimage.codecs.png.png$module→image.color.ExtendedColorType
- Direction
- codecs.png uses color, so a change to color can break codecs.png, while a change to codecs.png can't break color.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→16 imageops.sample uses images.buffer✕
- Connections
- 1 pair of types, where a type in imageops.sample uses a type in images.buffer.
- The types involved
image.imageops.sample.sample$module→image.images.buffer.ImageBuffer
- Direction
- imageops.sample uses images.buffer, so a change to images.buffer can break imageops.sample, while a change to imageops.sample can't break images.buffer.
- Position
- Below the diagonal: imageops.sample uses a module listed above it, which is the healthy direction.
22→21 imageops.sample uses codecs.png✕
- Connections
- 1 pair of types, where a type in imageops.sample uses a type in codecs.png.
- The types involved
image.imageops.sample.sample$module→image.codecs.png.FilterType
- Direction
- imageops.sample uses codecs.png, so a change to codecs.png can break imageops.sample, while a change to imageops.sample can't break codecs.png.
- Position
- Below the diagonal: imageops.sample uses a module listed above it, which is the healthy direction.
22→23 imageops.sample uses images.dynimage part of a loop✕
- Connections
- 1 pair of types, where a type in imageops.sample uses a type in images.dynimage.
- The types involved
image.imageops.sample.sample$module→image.images.dynimage.DynamicImage
- Direction
- imageops.sample uses images.dynimage, so a change to images.dynimage can break imageops.sample, while a change to imageops.sample can't break images.dynimage.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→2 images.dynimage uses math.rect✕
- Connections
- 1 pair of types, where a type in images.dynimage uses a type in math.rect.
- The types involved
image.images.dynimage.DynamicImage→image.math.rect.Rect
- Direction
- images.dynimage uses math.rect, so a change to math.rect can break images.dynimage, while a change to images.dynimage can't break math.rect.
- Position
- Below the diagonal: images.dynimage uses a module listed above it, which is the healthy direction.
23→3 images.dynimage uses io✕
- Connections
- 2 pairs of types, where a type in images.dynimage uses a type in io.
- The types involved
image.images.dynimage.DynamicImage→image.io.DecoderPreparedImageimage.images.dynimage.dynimage$module→image.io.DecoderPreparedImage
- Direction
- images.dynimage uses io, so a change to io can break images.dynimage, while a change to images.dynimage can't break io.
- Position
- Below the diagonal: images.dynimage uses a module listed above it, which is the healthy direction.
23→5 images.dynimage uses metadata✕
- Connections
- 1 pair of types, where a type in images.dynimage uses a type in metadata.
- The types involved
image.images.dynimage.DynamicImage→image.metadata.Orientation
- Direction
- images.dynimage uses metadata, so a change to metadata can break images.dynimage, while a change to images.dynimage can't break metadata.
- Position
- Below the diagonal: images.dynimage uses a module listed above it, which is the healthy direction.
23→14 images.dynimage uses images.generic_image✕
- Connections
- 2 pairs of types, where a type in images.dynimage uses a type in images.generic_image.
- The types involved
image.images.dynimage.DynamicImage→image.images.generic_image.GenericImageimage.images.dynimage.DynamicImage→image.images.generic_image.GenericImageView
- Direction
- images.dynimage uses images.generic_image, so a change to images.generic_image can break images.dynimage, while a change to images.dynimage can't break images.generic_image.
- Position
- Below the diagonal: images.dynimage uses a module listed above it, which is the healthy direction.
23→15 images.dynimage uses io.format✕
- Connections
- 2 pairs of types, where a type in images.dynimage uses a type in io.format.
- The types involved
image.images.dynimage.DynamicImage→image.io.format.ImageFormatimage.images.dynimage.dynimage$module→image.io.format.ImageFormat
- Direction
- images.dynimage uses io.format, so a change to io.format can break images.dynimage, while a change to images.dynimage can't break io.format.
- Position
- Below the diagonal: images.dynimage uses a module listed above it, which is the healthy direction.
23→16 images.dynimage uses images.buffer✕
- Connections
- 2 pairs of types, where a type in images.dynimage uses a type in images.buffer.
- The types involved
image.images.dynimage.DynamicImage→image.images.buffer.ConvertColorOptionsimage.images.dynimage.DynamicImage→image.images.buffer.ImageBuffer
- Direction
- images.dynimage uses images.buffer, so a change to images.buffer can break images.dynimage, while a change to images.dynimage can't break images.buffer.
- Position
- Below the diagonal: images.dynimage uses a module listed above it, which is the healthy direction.
23→21 images.dynimage uses codecs.png✕
- Connections
- 1 pair of types, where a type in images.dynimage uses a type in codecs.png.
- The types involved
image.images.dynimage.DynamicImage→image.codecs.png.FilterType
- Direction
- images.dynimage uses codecs.png, so a change to codecs.png can break images.dynimage, while a change to images.dynimage can't break codecs.png.
- Position
- Below the diagonal: images.dynimage uses a module listed above it, which is the healthy direction.
23→22 images.dynimage uses imageops.sample✕
- Connections
- 1 pair of types, where a type in images.dynimage uses a type in imageops.sample.
- The types involved
image.images.dynimage.DynamicImage→image.imageops.sample.GaussianBlurParameters
- Direction
- images.dynimage uses imageops.sample, so a change to imageops.sample can break images.dynimage, while a change to images.dynimage can't break imageops.sample.
- Position
- Below the diagonal: images.dynimage uses a module listed above it, which is the healthy direction.
23→24 images.dynimage uses metadata.cicp part of a loop✕
- Connections
- 3 pairs of types, where a type in images.dynimage uses a type in metadata.cicp.
- The types involved
image.images.dynimage.DynamicImage→image.metadata.cicp.Cicpimage.images.dynimage.DynamicImage→image.metadata.cicp.CicpColorPrimariesimage.images.dynimage.DynamicImage→image.metadata.cicp.CicpTransferCharacteristics
- Direction
- images.dynimage uses metadata.cicp, so a change to metadata.cicp can break images.dynimage, while a change to images.dynimage can't break metadata.cicp.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→25 images.dynimage uses color part of a loop✕
- Connections
- 2 pairs of types, where a type in images.dynimage uses a type in color.
- The types involved
image.images.dynimage.DynamicImage→image.color.ColorTypeimage.images.dynimage.DynamicImage→image.color.Rgba
- Direction
- images.dynimage uses color, so a change to color can break images.dynimage, while a change to images.dynimage can't break color.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→29 images.dynimage uses codecs.pnm.encoder part of a loop✕
- Connections
- 1 pair of types, where a type in images.dynimage uses a type in codecs.pnm.encoder.
- The types involved
image.images.dynimage.DynamicImage→image.codecs.pnm.encoder.FlatSamples
- Direction
- images.dynimage uses codecs.pnm.encoder, so a change to codecs.pnm.encoder can break images.dynimage, while a change to images.dynimage can't break codecs.pnm.encoder.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→6 metadata.cicp uses traits.private✕
- Connections
- 3 pairs of types, where a type in metadata.cicp uses a type in traits.private.
- The types involved
image.metadata.cicp.CicpRgb→image.traits.private.LayoutWithColorimage.metadata.cicp.CicpTransform→image.traits.private.LayoutWithColorimage.metadata.cicp.RgbTransforms→image.traits.private.LayoutWithColor
- Direction
- metadata.cicp uses traits.private, so a change to traits.private can break metadata.cicp, while a change to metadata.cicp can't break traits.private.
- Position
- Below the diagonal: metadata.cicp uses a module listed above it, which is the healthy direction.
24→9 metadata.cicp uses metadata.moxcms✕
- Connections
- 1 pair of types, where a type in metadata.cicp uses a type in metadata.moxcms.
- The types involved
image.metadata.cicp.Cicp→image.metadata.moxcms.ColorProfile
- Direction
- metadata.cicp uses metadata.moxcms, so a change to metadata.moxcms can break metadata.cicp, while a change to metadata.cicp can't break metadata.moxcms.
- Position
- Below the diagonal: metadata.cicp uses a module listed above it, which is the healthy direction.
24→23 metadata.cicp uses images.dynimage✕
- Connections
- 1 pair of types, where a type in metadata.cicp uses a type in images.dynimage.
- The types involved
image.metadata.cicp.CicpTransform→image.images.dynimage.DynamicImage
- Direction
- metadata.cicp uses images.dynimage, so a change to images.dynimage can break metadata.cicp, while a change to metadata.cicp can't break images.dynimage.
- Position
- Below the diagonal: metadata.cicp uses a module listed above it, which is the healthy direction.
25→6 color uses traits.private✕
- Connections
- 12 pairs of types, where a type in color uses a type in traits.private.
- The types involved
image.color.Luma→image.traits.private.LayoutWithColorimage.color.Luma→image.traits.private.PrivateTokenimage.color.Luma→image.traits.private.SealedPixelWithColorTypeimage.color.LumaA→image.traits.private.LayoutWithColorimage.color.LumaA→image.traits.private.PrivateTokenimage.color.LumaA→image.traits.private.SealedPixelWithColorTypeimage.color.Rgb→image.traits.private.LayoutWithColorimage.color.Rgb→image.traits.private.PrivateTokenimage.color.Rgb→image.traits.private.SealedPixelWithColorTypeimage.color.Rgba→image.traits.private.LayoutWithColorimage.color.Rgba→image.traits.private.PrivateTokenimage.color.Rgba→image.traits.private.SealedPixelWithColorType
- Direction
- color uses traits.private, so a change to traits.private can break color, while a change to color can't break traits.private.
- Position
- Below the diagonal: color uses a module listed above it, which is the healthy direction.
25→10 color uses traits✕
- Connections
- 8 pairs of types, where a type in color uses a type in traits.
- The types involved
image.color.Luma→image.traits.Pixelimage.color.Luma→image.traits.PixelWithColorTypeimage.color.LumaA→image.traits.Pixelimage.color.LumaA→image.traits.PixelWithColorTypeimage.color.Rgb→image.traits.Pixelimage.color.Rgb→image.traits.PixelWithColorTypeimage.color.Rgba→image.traits.Pixelimage.color.Rgba→image.traits.PixelWithColorType
- Direction
- color uses traits, so a change to traits can break color, while a change to color can't break traits.
- Position
- Below the diagonal: color uses a module listed above it, which is the healthy direction.
25→24 color uses metadata.cicp✕
- Connections
- 1 pair of types, where a type in color uses a type in metadata.cicp.
- The types involved
image.color.IntoColor→image.metadata.cicp.CicpPixelCast
- Direction
- color uses metadata.cicp, so a change to metadata.cicp can break color, while a change to color can't break metadata.cicp.
- Position
- Below the diagonal: color uses a module listed above it, which is the healthy direction.
26→4 codecs.bmp.encoder uses io.encoder✕
- Connections
- 2 pairs of types, where a type in codecs.bmp.encoder uses a type in io.encoder.
- The types involved
image.codecs.bmp.encoder.BmpEncoder→image.io.encoder.ImageEncoderimage.codecs.bmp.encoder.BmpEncoder→image.io.encoder.MethodSealedToImage
- Direction
- codecs.bmp.encoder uses io.encoder, so a change to io.encoder can break codecs.bmp.encoder, while a change to codecs.bmp.encoder can't break io.encoder.
- Position
- Below the diagonal: codecs.bmp.encoder uses a module listed above it, which is the healthy direction.
26→23 codecs.bmp.encoder uses images.dynimage✕
- Connections
- 1 pair of types, where a type in codecs.bmp.encoder uses a type in images.dynimage.
- The types involved
image.codecs.bmp.encoder.BmpEncoder→image.images.dynimage.DynamicImage
- Direction
- codecs.bmp.encoder uses images.dynimage, so a change to images.dynimage can break codecs.bmp.encoder, while a change to codecs.bmp.encoder can't break images.dynimage.
- Position
- Below the diagonal: codecs.bmp.encoder uses a module listed above it, which is the healthy direction.
26→25 codecs.bmp.encoder uses color✕
- Connections
- 2 pairs of types, where a type in codecs.bmp.encoder uses a type in color.
- The types involved
image.codecs.bmp.encoder.BmpEncoder→image.color.ExtendedColorTypeimage.codecs.bmp.encoder.encoder$module→image.color.ExtendedColorType
- Direction
- codecs.bmp.encoder uses color, so a change to color can break codecs.bmp.encoder, while a change to codecs.bmp.encoder can't break color.
- Position
- Below the diagonal: codecs.bmp.encoder uses a module listed above it, which is the healthy direction.
27→4 codecs.farbfeld uses io.encoder✕
- Connections
- 1 pair of types, where a type in codecs.farbfeld uses a type in io.encoder.
- The types involved
image.codecs.farbfeld.FarbfeldEncoder→image.io.encoder.ImageEncoder
- Direction
- codecs.farbfeld uses io.encoder, so a change to io.encoder can break codecs.farbfeld, while a change to codecs.farbfeld can't break io.encoder.
- Position
- Below the diagonal: codecs.farbfeld uses a module listed above it, which is the healthy direction.
27→12 codecs.farbfeld uses io.decoder✕
- Connections
- 1 pair of types, where a type in codecs.farbfeld uses a type in io.decoder.
- The types involved
image.codecs.farbfeld.FarbfeldDecoder→image.io.decoder.ImageDecoder
- Direction
- codecs.farbfeld uses io.decoder, so a change to io.decoder can break codecs.farbfeld, while a change to codecs.farbfeld can't break io.decoder.
- Position
- Below the diagonal: codecs.farbfeld uses a module listed above it, which is the healthy direction.
27→25 codecs.farbfeld uses color✕
- Connections
- 1 pair of types, where a type in codecs.farbfeld uses a type in color.
- The types involved
image.codecs.farbfeld.FarbfeldEncoder→image.color.ExtendedColorType
- Direction
- codecs.farbfeld uses color, so a change to color can break codecs.farbfeld, while a change to codecs.farbfeld can't break color.
- Position
- Below the diagonal: codecs.farbfeld uses a module listed above it, which is the healthy direction.
28→1 codecs.gif uses animation✕
- Connections
- 3 pairs of types, where a type in codecs.gif uses a type in animation.
- The types involved
image.codecs.gif.FrameInfo→image.animation.Delayimage.codecs.gif.FrameInfo→image.animation.Frameimage.codecs.gif.GifEncoder→image.animation.Frame
- Direction
- codecs.gif uses animation, so a change to animation can break codecs.gif, while a change to codecs.gif can't break animation.
- Position
- Below the diagonal: codecs.gif uses a module listed above it, which is the healthy direction.
28→3 codecs.gif uses io✕
- Connections
- 1 pair of types, where a type in codecs.gif uses a type in io.
- The types involved
image.codecs.gif.GifDecoder→image.io.ImageLayout
- Direction
- codecs.gif uses io, so a change to io can break codecs.gif, while a change to codecs.gif can't break io.
- Position
- Below the diagonal: codecs.gif uses a module listed above it, which is the healthy direction.
28→4 codecs.gif uses io.encoder✕
- Connections
- 1 pair of types, where a type in codecs.gif uses a type in io.encoder.
- The types involved
image.codecs.gif.GifEncoder→image.io.encoder.ImageEncoder
- Direction
- codecs.gif uses io.encoder, so a change to io.encoder can break codecs.gif, while a change to codecs.gif can't break io.encoder.
- Position
- Below the diagonal: codecs.gif uses a module listed above it, which is the healthy direction.
28→8 codecs.gif uses io.limits✕
- Connections
- 1 pair of types, where a type in codecs.gif uses a type in io.limits.
- The types involved
image.codecs.gif.GifDecoder→image.io.limits.Limits
- Direction
- codecs.gif uses io.limits, so a change to io.limits can break codecs.gif, while a change to codecs.gif can't break io.limits.
- Position
- Below the diagonal: codecs.gif uses a module listed above it, which is the healthy direction.
28→12 codecs.gif uses io.decoder✕
- Connections
- 3 pairs of types, where a type in codecs.gif uses a type in io.decoder.
- The types involved
image.codecs.gif.GifDecoder→image.io.decoder.DecodedAnimationAttributesimage.codecs.gif.GifDecoder→image.io.decoder.FormatAttributesimage.codecs.gif.GifDecoder→image.io.decoder.ImageDecoder
- Direction
- codecs.gif uses io.decoder, so a change to io.decoder can break codecs.gif, while a change to codecs.gif can't break io.decoder.
- Position
- Below the diagonal: codecs.gif uses a module listed above it, which is the healthy direction.
28→16 codecs.gif uses images.buffer✕
- Connections
- 1 pair of types, where a type in codecs.gif uses a type in images.buffer.
- The types involved
image.codecs.gif.GifDecoder→image.images.buffer.ImageBuffer
- Direction
- codecs.gif uses images.buffer, so a change to images.buffer can break codecs.gif, while a change to codecs.gif can't break images.buffer.
- Position
- Below the diagonal: codecs.gif uses a module listed above it, which is the healthy direction.
28→25 codecs.gif uses color✕
- Connections
- 2 pairs of types, where a type in codecs.gif uses a type in color.
- The types involved
image.codecs.gif.GifEncoder→image.color.ExtendedColorTypeimage.codecs.gif.gif$module→image.color.Rgba
- Direction
- codecs.gif uses color, so a change to color can break codecs.gif, while a change to codecs.gif can't break color.
- Position
- Below the diagonal: codecs.gif uses a module listed above it, which is the healthy direction.
29→4 codecs.pnm.encoder uses io.encoder✕
- Connections
- 1 pair of types, where a type in codecs.pnm.encoder uses a type in io.encoder.
- The types involved
image.codecs.pnm.encoder.PnmEncoder→image.io.encoder.ImageEncoder
- Direction
- codecs.pnm.encoder uses io.encoder, so a change to io.encoder can break codecs.pnm.encoder, while a change to codecs.pnm.encoder can't break io.encoder.
- Position
- Below the diagonal: codecs.pnm.encoder uses a module listed above it, which is the healthy direction.
29→25 codecs.pnm.encoder uses color✕
- Connections
- 4 pairs of types, where a type in codecs.pnm.encoder uses a type in color.
- The types involved
image.codecs.pnm.encoder.CheckedDimensions→image.color.ExtendedColorTypeimage.codecs.pnm.encoder.CheckedHeaderColor→image.color.ExtendedColorTypeimage.codecs.pnm.encoder.CheckedImageBuffer→image.color.ExtendedColorTypeimage.codecs.pnm.encoder.PnmEncoder→image.color.ExtendedColorType
- Direction
- codecs.pnm.encoder uses color, so a change to color can break codecs.pnm.encoder, while a change to codecs.pnm.encoder can't break color.
- Position
- Below the diagonal: codecs.pnm.encoder uses a module listed above it, which is the healthy direction.
30→12 codecs.tga.decoder uses io.decoder✕
- Connections
- 1 pair of types, where a type in codecs.tga.decoder uses a type in io.decoder.
- The types involved
image.codecs.tga.decoder.TgaDecoder→image.io.decoder.ImageDecoder
- Direction
- codecs.tga.decoder uses io.decoder, so a change to io.decoder can break codecs.tga.decoder, while a change to codecs.tga.decoder can't break io.decoder.
- Position
- Below the diagonal: codecs.tga.decoder uses a module listed above it, which is the healthy direction.
30→18 codecs.tga.decoder uses codecs.bmp.decoder✕
- Connections
- 1 pair of types, where a type in codecs.tga.decoder uses a type in codecs.bmp.decoder.
- The types involved
image.codecs.tga.decoder.TgaDecoder→image.codecs.bmp.decoder.ImageType
- Direction
- codecs.tga.decoder uses codecs.bmp.decoder, so a change to codecs.bmp.decoder can break codecs.tga.decoder, while a change to codecs.tga.decoder can't break codecs.bmp.decoder.
- Position
- Below the diagonal: codecs.tga.decoder uses a module listed above it, which is the healthy direction.
30→25 codecs.tga.decoder uses color✕
- Connections
- 2 pairs of types, where a type in codecs.tga.decoder uses a type in color.
- The types involved
image.codecs.tga.decoder.TgaDecoder→image.color.ColorTypeimage.codecs.tga.decoder.TgaDecoder→image.color.ExtendedColorType
- Direction
- codecs.tga.decoder uses color, so a change to color can break codecs.tga.decoder, while a change to codecs.tga.decoder can't break color.
- Position
- Below the diagonal: codecs.tga.decoder uses a module listed above it, which is the healthy direction.
31→4 codecs.tiff uses io.encoder✕
- Connections
- 1 pair of types, where a type in codecs.tiff uses a type in io.encoder.
- The types involved
image.codecs.tiff.TiffEncoder→image.io.encoder.ImageEncoder
- Direction
- codecs.tiff uses io.encoder, so a change to io.encoder can break codecs.tiff, while a change to codecs.tiff can't break io.encoder.
- Position
- Below the diagonal: codecs.tiff uses a module listed above it, which is the healthy direction.
31→8 codecs.tiff uses io.limits✕
- Connections
- 1 pair of types, where a type in codecs.tiff uses a type in io.limits.
- The types involved
image.codecs.tiff.TiffDecoder→image.io.limits.Limits
- Direction
- codecs.tiff uses io.limits, so a change to io.limits can break codecs.tiff, while a change to codecs.tiff can't break io.limits.
- Position
- Below the diagonal: codecs.tiff uses a module listed above it, which is the healthy direction.
31→12 codecs.tiff uses io.decoder✕
- Connections
- 3 pairs of types, where a type in codecs.tiff uses a type in io.decoder.
- The types involved
image.codecs.tiff.TiffDecoder→image.io.decoder.FormatAttributesimage.codecs.tiff.TiffDecoder→image.io.decoder.ImageDecoderimage.codecs.tiff.TiffDecoder→image.io.decoder.SequenceControl
- Direction
- codecs.tiff uses io.decoder, so a change to io.decoder can break codecs.tiff, while a change to codecs.tiff can't break io.decoder.
- Position
- Below the diagonal: codecs.tiff uses a module listed above it, which is the healthy direction.
31→25 codecs.tiff uses color✕
- Connections
- 3 pairs of types, where a type in codecs.tiff uses a type in color.
- The types involved
image.codecs.tiff.ImageInfo→image.color.ColorTypeimage.codecs.tiff.ImageInfo→image.color.ExtendedColorTypeimage.codecs.tiff.TiffEncoder→image.color.ExtendedColorType
- Direction
- codecs.tiff uses color, so a change to color can break codecs.tiff, while a change to codecs.tiff can't break color.
- Position
- Below the diagonal: codecs.tiff uses a module listed above it, which is the healthy direction.
32→10 images.flat uses traits✕
- Connections
- 2 pairs of types, where a type in images.flat uses a type in traits.
- The types involved
image.images.flat.View→image.traits.Pixelimage.images.flat.ViewMut→image.traits.Pixel
- Direction
- images.flat uses traits, so a change to traits can break images.flat, while a change to images.flat can't break traits.
- Position
- Below the diagonal: images.flat uses a module listed above it, which is the healthy direction.
32→14 images.flat uses images.generic_image✕
- Connections
- 3 pairs of types, where a type in images.flat uses a type in images.generic_image.
- The types involved
image.images.flat.View→image.images.generic_image.GenericImageViewimage.images.flat.ViewMut→image.images.generic_image.GenericImageimage.images.flat.ViewMut→image.images.generic_image.GenericImageView
- Direction
- images.flat uses images.generic_image, so a change to images.generic_image can break images.flat, while a change to images.flat can't break images.generic_image.
- Position
- Below the diagonal: images.flat uses a module listed above it, which is the healthy direction.
32→25 images.flat uses color✕
- Connections
- 1 pair of types, where a type in images.flat uses a type in color.
- The types involved
image.images.flat.FlatSamples→image.color.ColorType
- Direction
- images.flat uses color, so a change to color can break images.flat, while a change to images.flat can't break color.
- Position
- Below the diagonal: images.flat uses a module listed above it, which is the healthy direction.
32→29 images.flat uses codecs.pnm.encoder✕
- Connections
- 3 pairs of types, where a type in images.flat uses a type in codecs.pnm.encoder.
- The types involved
image.images.flat.FlatSamples→image.codecs.pnm.encoder.FlatSamplesimage.images.flat.View→image.codecs.pnm.encoder.FlatSamplesimage.images.flat.ViewMut→image.codecs.pnm.encoder.FlatSamples
- Direction
- images.flat uses codecs.pnm.encoder, so a change to codecs.pnm.encoder can break images.flat, while a change to images.flat can't break codecs.pnm.encoder.
- Position
- Below the diagonal: images.flat uses a module listed above it, which is the healthy direction.
33→32 codecs.avif.yuv uses images.flat✕
- Connections
- 1 pair of types, where a type in codecs.avif.yuv uses a type in images.flat.
- The types involved
image.codecs.avif.yuv.YuvConversionError→image.images.flat.Error
- Direction
- codecs.avif.yuv uses images.flat, so a change to images.flat can break codecs.avif.yuv, while a change to codecs.avif.yuv can't break images.flat.
- Position
- Below the diagonal: codecs.avif.yuv uses a module listed above it, which is the healthy direction.
34→8 codecs.hdr.decoder uses io.limits✕
- Connections
- 1 pair of types, where a type in codecs.hdr.decoder uses a type in io.limits.
- The types involved
image.codecs.hdr.decoder.HdrDecoder→image.io.limits.Limits
- Direction
- codecs.hdr.decoder uses io.limits, so a change to io.limits can break codecs.hdr.decoder, while a change to codecs.hdr.decoder can't break io.limits.
- Position
- Below the diagonal: codecs.hdr.decoder uses a module listed above it, which is the healthy direction.
34→12 codecs.hdr.decoder uses io.decoder✕
- Connections
- 1 pair of types, where a type in codecs.hdr.decoder uses a type in io.decoder.
- The types involved
image.codecs.hdr.decoder.HdrDecoder→image.io.decoder.ImageDecoder
- Direction
- codecs.hdr.decoder uses io.decoder, so a change to io.decoder can break codecs.hdr.decoder, while a change to codecs.hdr.decoder can't break io.decoder.
- Position
- Below the diagonal: codecs.hdr.decoder uses a module listed above it, which is the healthy direction.
34→17 codecs.hdr.decoder uses io.image_reader_type✕
- Connections
- 1 pair of types, where a type in codecs.hdr.decoder uses a type in io.image_reader_type.
- The types involved
image.codecs.hdr.decoder.HdrDecoder→image.io.image_reader_type.SpecCompliance
- Direction
- codecs.hdr.decoder uses io.image_reader_type, so a change to io.image_reader_type can break codecs.hdr.decoder, while a change to codecs.hdr.decoder can't break io.image_reader_type.
- Position
- Below the diagonal: codecs.hdr.decoder uses a module listed above it, which is the healthy direction.
34→25 codecs.hdr.decoder uses color✕
- Connections
- 1 pair of types, where a type in codecs.hdr.decoder uses a type in color.
- The types involved
image.codecs.hdr.decoder.Rgbe8Pixel→image.color.Rgb
- Direction
- codecs.hdr.decoder uses color, so a change to color can break codecs.hdr.decoder, while a change to codecs.hdr.decoder can't break color.
- Position
- Below the diagonal: codecs.hdr.decoder uses a module listed above it, which is the healthy direction.
34→32 codecs.hdr.decoder uses images.flat✕
- Connections
- 1 pair of types, where a type in codecs.hdr.decoder uses a type in images.flat.
- The types involved
image.codecs.hdr.decoder.DecoderError→image.images.flat.Error
- Direction
- codecs.hdr.decoder uses images.flat, so a change to images.flat can break codecs.hdr.decoder, while a change to codecs.hdr.decoder can't break images.flat.
- Position
- Below the diagonal: codecs.hdr.decoder uses a module listed above it, which is the healthy direction.
35→4 codecs.openexr uses io.encoder✕
- Connections
- 1 pair of types, where a type in codecs.openexr uses a type in io.encoder.
- The types involved
image.codecs.openexr.OpenExrEncoder→image.io.encoder.ImageEncoder
- Direction
- codecs.openexr uses io.encoder, so a change to io.encoder can break codecs.openexr, while a change to codecs.openexr can't break io.encoder.
- Position
- Below the diagonal: codecs.openexr uses a module listed above it, which is the healthy direction.
35→12 codecs.openexr uses io.decoder✕
- Connections
- 1 pair of types, where a type in codecs.openexr uses a type in io.decoder.
- The types involved
image.codecs.openexr.OpenExrDecoder→image.io.decoder.ImageDecoder
- Direction
- codecs.openexr uses io.decoder, so a change to io.decoder can break codecs.openexr, while a change to codecs.openexr can't break io.decoder.
- Position
- Below the diagonal: codecs.openexr uses a module listed above it, which is the healthy direction.
35→20 codecs.openexr uses error✕
- Connections
- 1 pair of types, where a type in codecs.openexr uses a type in error.
- The types involved
image.codecs.openexr.openexr$module→image.error.ImageError
- Direction
- codecs.openexr uses error, so a change to error can break codecs.openexr, while a change to codecs.openexr can't break error.
- Position
- Below the diagonal: codecs.openexr uses a module listed above it, which is the healthy direction.
35→25 codecs.openexr uses color✕
- Connections
- 2 pairs of types, where a type in codecs.openexr uses a type in color.
- The types involved
image.codecs.openexr.OpenExrEncoder→image.color.ExtendedColorTypeimage.codecs.openexr.openexr$module→image.color.ExtendedColorType
- Direction
- codecs.openexr uses color, so a change to color can break codecs.openexr, while a change to codecs.openexr can't break color.
- Position
- Below the diagonal: codecs.openexr uses a module listed above it, which is the healthy direction.
35→32 codecs.openexr uses images.flat✕
- Connections
- 1 pair of types, where a type in codecs.openexr uses a type in images.flat.
- The types involved
image.codecs.openexr.openexr$module→image.images.flat.Error
- Direction
- codecs.openexr uses images.flat, so a change to images.flat can break codecs.openexr, while a change to codecs.openexr can't break images.flat.
- Position
- Below the diagonal: codecs.openexr uses a module listed above it, which is the healthy direction.
36→12 codecs.pnm.decoder uses io.decoder✕
- Connections
- 1 pair of types, where a type in codecs.pnm.decoder uses a type in io.decoder.
- The types involved
image.codecs.pnm.decoder.PnmDecoder→image.io.decoder.ImageDecoder
- Direction
- codecs.pnm.decoder uses io.decoder, so a change to io.decoder can break codecs.pnm.decoder, while a change to codecs.pnm.decoder can't break io.decoder.
- Position
- Below the diagonal: codecs.pnm.decoder uses a module listed above it, which is the healthy direction.
36→25 codecs.pnm.decoder uses color✕
- Connections
- 2 pairs of types, where a type in codecs.pnm.decoder uses a type in color.
- The types involved
image.codecs.pnm.decoder.TupleType→image.color.ColorTypeimage.codecs.pnm.decoder.TupleType→image.color.ExtendedColorType
- Direction
- codecs.pnm.decoder uses color, so a change to color can break codecs.pnm.decoder, while a change to codecs.pnm.decoder can't break color.
- Position
- Below the diagonal: codecs.pnm.decoder uses a module listed above it, which is the healthy direction.
36→32 codecs.pnm.decoder uses images.flat✕
- Connections
- 1 pair of types, where a type in codecs.pnm.decoder uses a type in images.flat.
- The types involved
image.codecs.pnm.decoder.DecoderError→image.images.flat.Error
- Direction
- codecs.pnm.decoder uses images.flat, so a change to images.flat can break codecs.pnm.decoder, while a change to codecs.pnm.decoder can't break images.flat.
- Position
- Below the diagonal: codecs.pnm.decoder uses a module listed above it, which is the healthy direction.
37→4 codecs.qoi uses io.encoder✕
- Connections
- 1 pair of types, where a type in codecs.qoi uses a type in io.encoder.
- The types involved
image.codecs.qoi.QoiEncoder→image.io.encoder.ImageEncoder
- Direction
- codecs.qoi uses io.encoder, so a change to io.encoder can break codecs.qoi, while a change to codecs.qoi can't break io.encoder.
- Position
- Below the diagonal: codecs.qoi uses a module listed above it, which is the healthy direction.
37→12 codecs.qoi uses io.decoder✕
- Connections
- 1 pair of types, where a type in codecs.qoi uses a type in io.decoder.
- The types involved
image.codecs.qoi.QoiDecoder→image.io.decoder.ImageDecoder
- Direction
- codecs.qoi uses io.decoder, so a change to io.decoder can break codecs.qoi, while a change to codecs.qoi can't break io.decoder.
- Position
- Below the diagonal: codecs.qoi uses a module listed above it, which is the healthy direction.
37→20 codecs.qoi uses error✕
- Connections
- 1 pair of types, where a type in codecs.qoi uses a type in error.
- The types involved
image.codecs.qoi.qoi$module→image.error.ImageError
- Direction
- codecs.qoi uses error, so a change to error can break codecs.qoi, while a change to codecs.qoi can't break error.
- Position
- Below the diagonal: codecs.qoi uses a module listed above it, which is the healthy direction.
37→25 codecs.qoi uses color✕
- Connections
- 1 pair of types, where a type in codecs.qoi uses a type in color.
- The types involved
image.codecs.qoi.QoiEncoder→image.color.ExtendedColorType
- Direction
- codecs.qoi uses color, so a change to color can break codecs.qoi, while a change to codecs.qoi can't break color.
- Position
- Below the diagonal: codecs.qoi uses a module listed above it, which is the healthy direction.
37→32 codecs.qoi uses images.flat✕
- Connections
- 1 pair of types, where a type in codecs.qoi uses a type in images.flat.
- The types involved
image.codecs.qoi.qoi$module→image.images.flat.Error
- Direction
- codecs.qoi uses images.flat, so a change to images.flat can break codecs.qoi, while a change to codecs.qoi can't break images.flat.
- Position
- Below the diagonal: codecs.qoi uses a module listed above it, which is the healthy direction.
38→4 codecs.tga.encoder uses io.encoder✕
- Connections
- 2 pairs of types, where a type in codecs.tga.encoder uses a type in io.encoder.
- The types involved
image.codecs.tga.encoder.TgaEncoder→image.io.encoder.ImageEncoderimage.codecs.tga.encoder.TgaEncoder→image.io.encoder.MethodSealedToImage
- Direction
- codecs.tga.encoder uses io.encoder, so a change to io.encoder can break codecs.tga.encoder, while a change to codecs.tga.encoder can't break io.encoder.
- Position
- Below the diagonal: codecs.tga.encoder uses a module listed above it, which is the healthy direction.
38→23 codecs.tga.encoder uses images.dynimage✕
- Connections
- 1 pair of types, where a type in codecs.tga.encoder uses a type in images.dynimage.
- The types involved
image.codecs.tga.encoder.TgaEncoder→image.images.dynimage.DynamicImage
- Direction
- codecs.tga.encoder uses images.dynimage, so a change to images.dynimage can break codecs.tga.encoder, while a change to codecs.tga.encoder can't break images.dynimage.
- Position
- Below the diagonal: codecs.tga.encoder uses a module listed above it, which is the healthy direction.
38→25 codecs.tga.encoder uses color✕
- Connections
- 1 pair of types, where a type in codecs.tga.encoder uses a type in color.
- The types involved
image.codecs.tga.encoder.TgaEncoder→image.color.ExtendedColorType
- Direction
- codecs.tga.encoder uses color, so a change to color can break codecs.tga.encoder, while a change to codecs.tga.encoder can't break color.
- Position
- Below the diagonal: codecs.tga.encoder uses a module listed above it, which is the healthy direction.
38→32 codecs.tga.encoder uses images.flat✕
- Connections
- 1 pair of types, where a type in codecs.tga.encoder uses a type in images.flat.
- The types involved
image.codecs.tga.encoder.EncoderError→image.images.flat.Error
- Direction
- codecs.tga.encoder uses images.flat, so a change to images.flat can break codecs.tga.encoder, while a change to codecs.tga.encoder can't break images.flat.
- Position
- Below the diagonal: codecs.tga.encoder uses a module listed above it, which is the healthy direction.
39→5 codecs.avif.decoder uses metadata✕
- Connections
- 2 pairs of types, where a type in codecs.avif.decoder uses a type in metadata.
- The types involved
image.codecs.avif.decoder.AvifDecoder→image.metadata.Orientationimage.codecs.avif.decoder.decoder$module→image.metadata.Orientation
- Direction
- codecs.avif.decoder uses metadata, so a change to metadata can break codecs.avif.decoder, while a change to codecs.avif.decoder can't break metadata.
- Position
- Below the diagonal: codecs.avif.decoder uses a module listed above it, which is the healthy direction.
39→8 codecs.avif.decoder uses io.limits✕
- Connections
- 2 pairs of types, where a type in codecs.avif.decoder uses a type in io.limits.
- The types involved
image.codecs.avif.decoder.AvifDecoder→image.io.limits.Limitsimage.codecs.avif.decoder.decoder$module→image.io.limits.Limits
- Direction
- codecs.avif.decoder uses io.limits, so a change to io.limits can break codecs.avif.decoder, while a change to codecs.avif.decoder can't break io.limits.
- Position
- Below the diagonal: codecs.avif.decoder uses a module listed above it, which is the healthy direction.
39→12 codecs.avif.decoder uses io.decoder✕
- Connections
- 1 pair of types, where a type in codecs.avif.decoder uses a type in io.decoder.
- The types involved
image.codecs.avif.decoder.AvifDecoder→image.io.decoder.ImageDecoder
- Direction
- codecs.avif.decoder uses io.decoder, so a change to io.decoder can break codecs.avif.decoder, while a change to codecs.avif.decoder can't break io.decoder.
- Position
- Below the diagonal: codecs.avif.decoder uses a module listed above it, which is the healthy direction.
39→20 codecs.avif.decoder uses error✕
- Connections
- 1 pair of types, where a type in codecs.avif.decoder uses a type in error.
- The types involved
image.codecs.avif.decoder.decoder$module→image.error.ImageError
- Direction
- codecs.avif.decoder uses error, so a change to error can break codecs.avif.decoder, while a change to codecs.avif.decoder can't break error.
- Position
- Below the diagonal: codecs.avif.decoder uses a module listed above it, which is the healthy direction.
39→32 codecs.avif.decoder uses images.flat✕
- Connections
- 1 pair of types, where a type in codecs.avif.decoder uses a type in images.flat.
- The types involved
image.codecs.avif.decoder.AvifDecoderError→image.images.flat.Error
- Direction
- codecs.avif.decoder uses images.flat, so a change to images.flat can break codecs.avif.decoder, while a change to codecs.avif.decoder can't break images.flat.
- Position
- Below the diagonal: codecs.avif.decoder uses a module listed above it, which is the healthy direction.
39→33 codecs.avif.decoder uses codecs.avif.yuv✕
- Connections
- 1 pair of types, where a type in codecs.avif.decoder uses a type in codecs.avif.yuv.
- The types involved
image.codecs.avif.decoder.AvifDecoder→image.codecs.avif.yuv.YuvIntensityRange
- Direction
- codecs.avif.decoder uses codecs.avif.yuv, so a change to codecs.avif.yuv can break codecs.avif.decoder, while a change to codecs.avif.decoder can't break codecs.avif.yuv.
- Position
- Below the diagonal: codecs.avif.decoder uses a module listed above it, which is the healthy direction.
40→4 codecs.hdr.encoder uses io.encoder✕
- Connections
- 1 pair of types, where a type in codecs.hdr.encoder uses a type in io.encoder.
- The types involved
image.codecs.hdr.encoder.HdrEncoder→image.io.encoder.ImageEncoder
- Direction
- codecs.hdr.encoder uses io.encoder, so a change to io.encoder can break codecs.hdr.encoder, while a change to codecs.hdr.encoder can't break io.encoder.
- Position
- Below the diagonal: codecs.hdr.encoder uses a module listed above it, which is the healthy direction.
40→25 codecs.hdr.encoder uses color✕
- Connections
- 2 pairs of types, where a type in codecs.hdr.encoder uses a type in color.
- The types involved
image.codecs.hdr.encoder.HdrEncoder→image.color.ExtendedColorTypeimage.codecs.hdr.encoder.encoder$module→image.color.Rgb
- Direction
- codecs.hdr.encoder uses color, so a change to color can break codecs.hdr.encoder, while a change to codecs.hdr.encoder can't break color.
- Position
- Below the diagonal: codecs.hdr.encoder uses a module listed above it, which is the healthy direction.
40→34 codecs.hdr.encoder uses codecs.hdr.decoder✕
- Connections
- 1 pair of types, where a type in codecs.hdr.encoder uses a type in codecs.hdr.decoder.
- The types involved
image.codecs.hdr.encoder.encoder$module→image.codecs.hdr.decoder.Rgbe8Pixel
- Direction
- codecs.hdr.encoder uses codecs.hdr.decoder, so a change to codecs.hdr.decoder can break codecs.hdr.encoder, while a change to codecs.hdr.encoder can't break codecs.hdr.decoder.
- Position
- Below the diagonal: codecs.hdr.encoder uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 33 | High / Critical |
Roadmap
First, address the lack of architectural decision records by documenting significant design choices in a dedicated folder to ensure clarity and traceability. Next, implement robust observability by adding diagnostic logging accessible via debug flags, focusing on error paths that currently provide no feedback. Finally, improve onboarding and project structure by adding a quick-start section to the README and resolving issues related to oversized project cohesion.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +11.0 pts | Low | ADR Quality |
| 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. | +10.2 pts | Medium | Architecture documentation |
| Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce. | +6.4 pts | Medium | Observability |
| Add a build/run (quick start) section to the root README — the first thing a newcomer needs. | +4.2 pts | Medium | Documentation (README) |
| Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. | +0.8 pts | Low | Project Cohesion |
| Resolve the 1 Off the main sequence finding(s) in Coupling. | +0.7 pts | Low | Coupling |
| Resolve the 2 Orphaned file finding(s) in Knowledge Freshness — start with encoder.rs, affine.rs. | +0.3 pts | Low | Knowledge Freshness |
| Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. | +0.2 pts | Low | Bus Factor |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| src/codecs/pnm/decoder.rs | 6.0 | Mixed | Explicit Debt: FixmeComment |
| src/codecs/tiff.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/codecs/tga/decoder.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/codecs/gif.rs | 6.0 | Mixed | Explicit Debt: FixmeComment |
| src/imageops/sample.rs | 6.0 | Mixed | Explicit Debt: HackComment |
| src/images/flat.rs | 6.0 | Mixed | Explicit Debt: FixmeComment |
| src/images/dynimage.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/images/buffer.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/metadata/moxcms.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/codecs/png.rs | 6.0 | Mixed | Explicit Debt: FixmeComment |
| src/color.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/imageops/colorops.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/codecs/openexr.rs | 6.4 | Mixed | Explicit Debt: TodoComment |
| src/codecs/tga/encoder.rs | 6.7 | Mixed | Explicit Debt: TodoComment |
| src/io/image_reader_type.rs | 6.9 | Mixed | Explicit Debt: FixmeComment |
| fuzz/fuzzers/fuzzer_script_exr.rs | 6.9 | Mixed | Explicit Debt: TodoComment |
| src/codecs/bmp/decoder.rs | 7.0 | Near-clean | Cyclomatic Complexity: BmpDecoder::read_rle_data (cyclomatic 41) |
| src/codecs/avif/yuv.rs | 7.0 | Near-clean | Cognitive Complexity: image::codecs::avif::yuv::gbr_to_rgbx_impl (cognitive 19) |
| src/codecs/avif/ycgco.rs | 7.0 | Near-clean | Code Duplication: Members sharing a duplicated core (6 members, 50+ identical tokens) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 42 of 42 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 42 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, 233 of 243 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Watchdog duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.rs) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. This repository's source is written only in languages whose packages are published through a manifest, and no manifest in the tree makes a publication act: either there is no package manifest of any ecosystem (no package.json, pyproject.toml, setup.py, gemspec, Cargo.toml, pom.xml, build.gradle, composer.json, pubspec.yaml or mix.exs), or every one present declares in its package manager's own terms that it is not published (an npm package marked "private": true, a Cargo package with publish = false, a pubspec with publish_to: none, a Composer "project", a Poetry project with package-mode = false, or the "Private :: Do Not Upload" classifier). With no publication act there is no intentionally-exposed surface for API consistency to be judged over.
- D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- AX6 Interface segregation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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.
- GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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.
- X12 Unreachable branch — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X16 Unfloored truncation loop — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X19 Unrestored process-global state — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X22 Contradicted release guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, TypeScript/JavaScript, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X23 Unguarded diagnostic materialisation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X25 Inert configuration knob — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart and Ruby source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart or Ruby was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X3 Exception handling — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go and JavaScript/TypeScript source only, and no C# was loaded and no PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go, JavaScript or TypeScript was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X5 Nullable reference types — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- 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.
- D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- 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.
- 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
14 function(s) exceeded the cyclomatic complexity threshold of 15; the worst was BmpDecoder::read_rle_data at 41. A further 16 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 Moxcms::parse_icc at 42 — they are counted neither in the figure above nor in this dimension's score. 8 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: src/metadata/moxcms.rs (Moxcms::parse_icc at 42), src/color.rs (ExtendedColorType::bits_per_pixel at 32), src/metadata/cicp.rs (CicpTransform::transform_dynamic at 27), src/codecs/png.rs (PngDecoder::color_type_info at 25), src/codecs/pnm/encoder.rs (CheckedDimensions::check_header_color at 20), and 3 more not listed here. 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 30 down to 30 or less in Cyclomatic Complexity — start with BmpDecoder::read_rle_data (cyclomatic 41). — Refactoring it lifts Cyclomatic Complexity from 7.8 to about 8.2/10.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
22 function(s) exceeded the cognitive complexity threshold of 15; the worst was BmpDecoder::read_rle_data at 132.
What to do
- Bring the 1 body over 60 down to 60 or less in Cognitive Complexity — start with BmpDecoder::read_rle_data (cognitive 132). — Refactoring it lifts Cognitive Complexity from 6.0 to about 6.8/10.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
25 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 12 FileTooLong finding(s) in God Classes — start with decoder.rs (3), buffer.rs, sample.rs. — One of this dimension's main actionable groups (12 warning-level).
- Resolve the 6 MethodTooLong finding(s) in God Classes — start with decoder.rs (2), moxcms.rs, cicp.rs. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 3 TooManyMethods finding(s) in God Classes — start with dynimage.rs, buffer.rs, decoder.rs. — One of this dimension's main actionable groups (3 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
66 duplicated block group(s) detected. A further 5 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
What to do
- Resolve the 8 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with yuv.rs, header.rs, color.rs. — One of this dimension's main actionable groups (8 warning-level).
- Resolve the 7 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with ycgco.rs, yuv.rs, decoder.rs. — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 6 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with buffer.rs (2), yuv.rs, mod.rs. — One of this dimension's main actionable groups (6 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
2 production modules (Cargo), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence, with abstractness counted on 1 of the 2 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
4 of 74 classes have LCOM4 above 3.
What to do
- Resolve the 4 Low cohesion finding(s) in Cohesion (LCOM4) — start with color.rs (4). — One of this dimension's main actionable groups (4 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
370 test methods: 319 unit, 51 integration, 0 BDD, 0 e2e. The Rust suite contributes 370 `#[test]` function(s) across 55 file(s) declaring at least one; its unit/integration split is Cargo's own — 10 of those file(s) are integration-test targets under a crate's tests/ directory, and the rest are #[test] functions compiled into the crate they test.
D11 · Test Reliability
0 flaky across 1 measured tier(s). Rust (repository root, 55 test files): measured (0 flaky).
D12 · Dependency Hygiene
0 outdated, 0 yanked direct Cargo dependencies. 22 of 23 direct crates were graded against crates.io (0 not published there, 1 not resolved by a committed Cargo.lock). Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from Cargo.lock there.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 173 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.
D16 · Bus Factor
2 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/codecs/ico/encoder.rs. Counted over 62 of the 88 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
59 deducted task-comment markers across 36561 LoC (0.2/KLoC) → score 9.7. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 39 TodoComment finding(s) in Explicit Debt — start with openexr.rs (8), colorops.rs (5), buffer.rs (4). — One of this dimension's main actionable groups (39 warning-level).
- Resolve the 19 FixmeComment finding(s) in Explicit Debt — start with gif.rs (4), dynimage.rs (3), image_reader_type.rs (2). — One of this dimension's main actionable groups (19 warning-level).
- Resolve the 1 HackComment finding(s) in Explicit Debt — start with sample.rs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 7 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 2 build units (Cargo) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
33 finding(s): 0 critical, 33 high, 0 medium, 0 low. 32 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 3 file(s) — `src/codecs/png.rs` (line 813), `src/images/dynimage.rs` (line 130), `src/io/free_functions.rs` (line 171) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 32 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 (32 issue-level, 0 of them charged here).
D34 · Knowledge Freshness
2 of 62 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/codecs/hdr/encoder.rs. Counted over 62 of the 88 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.
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
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX9 · CQS / query purity
M1 · Documentation (README)
- 52 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Review the README against recent changes; refresh the parts that drifted.
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
P1 · CI/CD gates
P2 · Observability
- No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
What to do
- Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
P3 · Security & performance tooling
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
PF1 · Benchmark discipline
X1 · Async correctness
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X21 · Side-effecting pattern guard
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X30 · Support guard that admits what it rejects
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 89% | Exemplary | Solid. |
| Architecture | 87% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 53% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 62% | Adequate — gated by P2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 95% | Exemplary | Strongest area. |
| Performance | 90% | Exemplary | Solid. |
Unscored — 2 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- X10 Duplicated predicate — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 72 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: 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 — ~2173 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.
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# only; Rust not measured.
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .rs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- 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.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- 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 included — suite not readable by the collector
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (29 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
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- M4 Documentation accuracy — Not applicable: the 7 current-state document(s) make no claim of a kind M4 checks.
- 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'.
- 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 — no coverage report found on disk — produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF2 Allocation hygiene — Not applicable: Rust spells out every heap allocation and makes borrowed slices (&[T], &str) its ordinary parameter types, so the allocation-aware style this card rewards elsewhere is the language's baseline rather than a rung to climb.
- 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: 73 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.
- X12 Unreachable branch — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X13 Undrained process stream — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X16 Unfloored truncation loop — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X17 Uncapped recursion over a caller-supplied document — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X18 Disposal-pattern correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X19 Unrestored process-global state — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X2 Cancellation propagation — no C# was loaded; this repository's Rust was read, and no request in it can be cancelled by a caller — a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X23 Unguarded diagnostic materialisation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X25 Inert configuration knob — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. Rust's compiler refuses the unsynchronised version: a collection shared between a callback's thread and the waiting body must be `Sync`, which a `Vec`, `VecDeque` or `HashMap` is only behind a `Mutex`/`RwLock`, so the race this check looks for cannot be written in safe Rust. Not a gap in the analyzer and not a finding about your code.
- X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- 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.
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 33 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 199 finding(s)
- TodoComment tests/reference_images.rs:205
- TodoComment src/color.rs:156
- TodoComment src/lib.rs:273
- TodoComment src/traits.rs:38
- TodoComment src/metadata/moxcms.rs:50
- TodoComment src/io/image_reader_type.rs:620
- TodoComment src/images/buffer.rs:682
- TodoComment src/images/buffer.rs:694
- TodoComment src/images/buffer.rs:736
- TodoComment src/images/buffer.rs:1438
- TodoComment src/images/dynimage.rs:1748
- TodoComment src/images/flat.rs:1005
- TodoComment src/imageops/colorops.rs:72
- TodoComment src/imageops/colorops.rs:134
- TodoComment src/imageops/colorops.rs:197
- TodoComment src/imageops/colorops.rs:324
- TodoComment src/imageops/colorops.rs:195
- TodoComment src/imageops/sample.rs:944
- TodoComment src/codecs/gif.rs:599
- TodoComment src/codecs/openexr.rs:190
- TodoComment src/codecs/openexr.rs:205
- TodoComment src/codecs/openexr.rs:209
- TodoComment src/codecs/openexr.rs:214
- TodoComment src/codecs/openexr.rs:248
- TodoComment src/codecs/openexr.rs:269
- FixmeComment src/color.rs:614
- FixmeComment src/io.rs:100
- FixmeComment src/io/image_reader_type.rs:551
- FixmeComment src/io/image_reader_type.rs:637
- FixmeComment src/images/buffer.rs:1664
- FixmeComment src/images/dynimage.rs:1792
- FixmeComment src/images/dynimage.rs:1887
- FixmeComment src/images/dynimage.rs:2223
- FixmeComment src/images/flat.rs:621
- FixmeComment src/images/flat.rs:734
- FixmeComment src/imageops/sample.rs:1656
- FixmeComment src/codecs/gif.rs:82
- FixmeComment src/codecs/gif.rs:117
- FixmeComment src/codecs/gif.rs:121
- FixmeComment src/codecs/gif.rs:378
- FixmeComment src/codecs/png.rs:289
- FixmeComment src/codecs/png.rs:292
- FixmeComment src/codecs/pnm/decoder.rs:318
- FixmeComment fuzz/fuzzers/fuzzer_script_exr.rs:70
- FileTooLong: bmp/decoder.rs src/codecs/bmp/decoder.rs
- FileTooLong: images/buffer.rs src/images/buffer.rs
- FileTooLong: imageops/sample.rs src/imageops/sample.rs
- FileTooLong: images/dynimage.rs src/images/dynimage.rs
- FileTooLong: avif/yuv.rs src/codecs/avif/yuv.rs
- FileTooLong: images/flat.rs src/images/flat.rs
- FileTooLong: metadata/cicp.rs src/metadata/cicp.rs
- FileTooLong: pnm/decoder.rs src/codecs/pnm/decoder.rs
- FileTooLong: codecs/png.rs src/codecs/png.rs
- FileTooLong: imageops/filter_1d.rs src/imageops/filter_1d.rs
- FileTooLong: src/color.rs src/color.rs
- FileTooLong: avif/decoder.rs src/codecs/avif/decoder.rs
- image::imageops::filter_1d::filter_symmetric_column (cognitive 42) src/imageops/filter_1d.rs:171
- image::imageops::fast_blur::box_blur_horizontal_pass (cognitive 38) src/imageops/fast_blur.rs:303
- image::imageops::sample::horizontal_sample (cognitive 29) src/imageops/sample.rs:217
- image::codecs::hdr::decoder::decode_old_rle (cognitive 27) src/codecs/hdr/decoder.rs:427
- image::codecs::bmp::decoder::set_2bit_pixel_run (cognitive 21) src/codecs/bmp/decoder.rs:871
- image::codecs::avif::yuv::gbr_to_rgbx_impl (cognitive 19) src/codecs/avif/yuv.rs:1178
- image::codecs::hdr::decoder::decode_component (cognitive 17) src/codecs/hdr/decoder.rs:380
- image::codecs::avif::yuv::yuv400_to_rgbx_impl (cognitive 16) src/codecs/avif/yuv.rs:321
- image::imageops::sample::vertical_sample (cognitive 16) src/imageops/sample.rs:494
- Duplicated block (6 lines × 2) src/codecs/avif/yuv.rs:365
- Duplicated block (6 lines × 2) src/codecs/pnm/header.rs:195
- Duplicated block (6 lines × 2) src/color.rs:896
- Duplicated block (6 lines × 2) src/imageops/colorops.rs:269
- Duplicated block (6 lines × 2) src/imageops/filter_1d.rs:209
- Duplicated block (6 lines × 2) src/imageops/sample.rs:614
- Duplicated block (6 lines × 2) src/images/flat.rs:1473
- Duplicated block (6 lines × 2) src/metadata/moxcms.rs:296
- Duplicated block (5 lines × 2) src/codecs/avif/ycgco.rs:130
- Duplicated block (5 lines × 2) src/codecs/avif/yuv.rs:1241
- Duplicated block (5 lines × 2) src/codecs/bmp/decoder.rs:120
- Duplicated block (5 lines × 2) src/imageops/colorops.rs:34
- Duplicated block (5 lines × 2) src/imageops/filter_1d.rs:357
- Duplicated block (5 lines × 2) src/imageops/sample.rs:1530
- Duplicated block (5 lines × 2) src/metadata/moxcms.rs:189
- MethodTooLong: Moxcms.build_transforms src/metadata/moxcms.rs:154
- MethodTooLong: BmpDecoder.read_rle_data src/codecs/bmp/decoder.rs:2119
- MethodTooLong: CicpTransform.transform_dynamic src/metadata/cicp.rs:366
- MethodTooLong: AvifDecoder.process_16bit_picture src/codecs/avif/decoder.rs:600
- MethodTooLong: GifDecoder.read_image src/codecs/gif.rs:156
- MethodTooLong: BmpEncoder.encode_with_palette src/codecs/bmp/encoder.rs:52
- Duplicated block (10 lines × 2) src/codecs/avif/yuv.rs:681
- Duplicated block (10 lines × 2) src/imageops/mod.rs:190
- Duplicated block (10 lines × 2) src/imageops/sample.rs:396
- Duplicated block (10 lines × 2) src/images/buffer.rs:1023
- Duplicated block (10 lines × 2) src/images/buffer.rs:1396
- Duplicated block (10 lines × 2) src/images/flat.rs:706
- Duplicated block (12 lines × 2) src/codecs/avif/yuv.rs:385
- Duplicated block (12 lines × 2) src/codecs/avif/yuv.rs:731
- Duplicated block (12 lines × 2) src/codecs/png.rs:985
- Duplicated block (12 lines × 2) src/imageops/fast_blur.rs:352
- Duplicated block (12 lines × 2) src/codecs/pnm/encoder.rs:417
- Duplicated block (11 lines × 2) fuzz-afl/fuzzers/fuzz_webp.rs:11
- Duplicated block (11 lines × 2) src/codecs/avif/ycgco.rs:168
- Duplicated block (11 lines × 2) src/codecs/bmp/encoder.rs:213
- Duplicated block (11 lines × 2) src/codecs/tiff.rs:350
- Duplicated block (11 lines × 2) src/images/flat.rs:668
- Duplicated block (9 lines × 2) src/codecs/avif/ycgco.rs:225
- Duplicated block (9 lines × 2) src/codecs/avif/ycgco.rs:236
- Duplicated block (9 lines × 2) src/codecs/avif/yuv.rs:940
- Duplicated block (9 lines × 2) src/codecs/gif.rs:306
- Duplicated block (9 lines × 2) src/images/generic_image.rs:277
- Duplicated block (8 lines × 2) src/codecs/avif/decoder.rs:525
- Duplicated block (8 lines × 2) src/codecs/avif/yuv.rs:755
- Duplicated block (8 lines × 2) src/codecs/bmp/decoder.rs:1364
- Duplicated block (8 lines × 2) src/images/buffer.rs:190
- Duplicated block (8 lines × 2) src/imageops/fast_blur.rs:312
- Duplicated block (7 lines × 2) src/imageops/sample.rs:757
- Duplicated block (7 lines × 2) src/codecs/gif.rs:145
- Duplicated block (7 lines × 2) src/imageops/filter_1d.rs:281
- Duplicated block (7 lines × 2) src/metadata/cicp.rs:835
- Low cohesion: Rgb (LCOM4 5) src/color.rs:512
- Low cohesion: Luma (LCOM4 5) src/color.rs:514
- Low cohesion: Rgba (LCOM4 5) src/color.rs:516
- Low cohesion: LumaA (LCOM4 5) src/color.rs:518
- BmpDecoder::read_rle_data (cyclomatic 41) src/codecs/bmp/decoder.rs:2119
- BmpDecoder::read_headers (cyclomatic 25) src/codecs/bmp/decoder.rs:1596
- BmpDecoder::image_type_from_compression (cyclomatic 20) src/codecs/bmp/decoder.rs:1261
- TooManyMethods: DynamicImage src/images/dynimage.rs:73
- TooManyMethods: ImageBuffer src/images/buffer.rs:492
- TooManyMethods: BmpDecoder src/codecs/bmp/decoder.rs:1087
- ClassTooLong: BmpDecoder src/codecs/bmp/decoder.rs:1087
- ClassTooLong: DynamicImage src/images/dynimage.rs:73
- ClassTooLong: ImageBuffer src/images/buffer.rs:492
- AvifDecoder::read_image (cyclomatic 28) src/codecs/avif/decoder.rs:445
- AvifDecoder::process_16bit_picture (cyclomatic 28) src/codecs/avif/decoder.rs:600
- image::imageops::filter_1d::filter_symmetric_column (cyclomatic 19) src/imageops/filter_1d.rs:171
- image::imageops::fast_blur::box_blur_horizontal_pass (cyclomatic 16) src/imageops/fast_blur.rs:303
- BmpDecoder::read_rle_data (cognitive 132) src/codecs/bmp/decoder.rs:2119
- BmpDecoder::read_headers (cognitive 24) src/codecs/bmp/decoder.rs:1596
- AvifDecoder::process_16bit_picture (cognitive 52) src/codecs/avif/decoder.rs:600
- AvifDecoder::read_image (cognitive 38) src/codecs/avif/decoder.rs:445
- TgaDecoder::new (cognitive 22) src/codecs/tga/decoder.rs:101
- TgaDecoder::fixup_orientation (cognitive 20) src/codecs/tga/decoder.rs:342
- Members sharing a duplicated core (5 members, 50+ identical tokens) src/color.rs:728
- Members sharing a duplicated core (5 members, 50+ identical tokens) src/imageops/affine.rs:45
- Duplicated block (18 lines × 2) src/codecs/avif/ycgco.rs:201
- Duplicated block (18 lines × 2) src/imageops/colorops.rs:249
- Duplicated block (13 lines × 2) src/codecs/avif/ycgco.rs:36
- Duplicated block (13 lines × 2) src/imageops/affine.rs:48
- Duplicated block (5 lines × 4) src/codecs/avif/ycgco.rs:168
- Duplicated block (5 lines × 4) src/metadata/moxcms.rs:251
- ArbitraryHeader::tuple_type (cyclomatic 29) src/codecs/pnm/decoder.rs:911
- HeaderReader::read_arbitrary_header (cyclomatic 24) src/codecs/pnm/decoder.rs:525
- IcoDecoder::read_image (cyclomatic 22) src/codecs/ico/decoder.rs:318
- TiffDecoder::read_image (cyclomatic 21) src/codecs/tiff.rs:459
- TgaDecoder::new (cyclomatic 20) src/codecs/tga/decoder.rs:101
- GifDecoder::read_image (cyclomatic 18) src/codecs/gif.rs:156
- HdrMetadata::update_header_info (cyclomatic 16) src/codecs/hdr/decoder.rs:544
- HackComment src/imageops/sample.rs:454
- IcoDecoder::read_image (cognitive 59) src/codecs/ico/decoder.rs:318
- GifDecoder::read_image (cognitive 34) src/codecs/gif.rs:156
- HdrMetadata::update_header_info (cognitive 23) src/codecs/hdr/decoder.rs:544
- TgaEncoder::run_length_encode (cognitive 20) src/codecs/tga/encoder.rs:88
- SampleLayout::is_normal (cognitive 18) src/images/flat.rs:337
- HeaderReader::read_arbitrary_header (cognitive 16) src/codecs/pnm/decoder.rs:525
- SampleWriter::write_pbm_bits (cognitive 16) src/codecs/pnm/encoder.rs:592
- FunctionTooLong: image::imageops::sample::gaussian_blur_dyn_image src/imageops/sample.rs:1312
- REDACTED
- Edited copy of a member (20 corresponding lines) src/codecs/bmp/encoder.rs:212
- Members sharing a duplicated core (6 members, 50+ identical tokens) src/codecs/avif/ycgco.rs:200
- Members sharing a duplicated core (4 members, 50+ identical tokens) src/codecs/avif/ycgco.rs:105
- Duplicated block (30 lines × 3) src/codecs/bmp/decoder.rs:1930
- Duplicated block (26–28 lines × 2) src/codecs/avif/decoder.rs:535
- Duplicated block (24 lines × 2) src/imageops/sample.rs:766
- Duplicated block (22 lines × 2) src/codecs/avif/ycgco.rs:149
- Duplicated block (21 lines × 2) src/codecs/avif/decoder.rs:252
- Duplicated block (20 lines × 2) src/images/flat.rs:1644
- Duplicated block (16–17 lines × 5) src/codecs/avif/ycgco.rs:204
- Duplicated block (17 lines × 2) src/codecs/bmp/decoder.rs:847
- Duplicated block (12–14 lines × 6) src/codecs/avif/ycgco.rs:208
- Duplicated block (13–14 lines × 2) src/imageops/sample.rs:1316
- Duplicated block (10–11 lines × 2) src/imageops/colorops.rs:169
- Duplicated block (10 lines × 5) src/imageops/affine.rs:46
- Duplicated block (9–10 lines × 2) src/imageops/colorops.rs:105
- Duplicated block (5–9 lines × 2) src/codecs/avif/yuv.rs:615
- Duplicated block (4–5 lines × 5) src/color.rs:729
- Off the main sequence: image
- README may be stale
- No structured logging
Minor — 11 finding(s)
- Orphaned file src/codecs/hdr/encoder.rs:1
- Orphaned file src/imageops/affine.rs:1
- Duplicated predicate src/images/buffer.rs:1406
- Duplicated predicate src/images/buffer.rs:1405
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- No ADRs found
- Projects may be oversized for their cohesion
- Orphaned files with no living knowledge
- No ADRs
- No architecture diagram/doc
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-2b097b7afeab449a8986f498aad153da/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/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-2b097b7afeab449a8986f498aad153da/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/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 33 | 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 | — |