Executive summary
optics-dev/Monocle falls short of our standard for production, in part because we found no recorded design decisions and no architecture document or diagram. It scores 51 out of 100 and is rated Adequate, and all 26 of its critical findings are security problems in the build pipeline.
Maturity, at 41, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 8 points. Completing the README comes next, worth about 7 points. Raising Maturity to 70 would lift the score to about 59.
Twenty-four pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One secret can leak from the build pipeline. Pinning each tool to an exact version and limiting the secret to its own step would close both risks. Correcting the flagged pipeline settings would fix the weakness in the build pipeline's configuration.
The product code is 7,799 lines, about €14,000 to rebuild.
If Maturity rose from 41 to 70, the lowest score rated Strong, the score would rise from 51 to about 59.
New since the last survey: 22 findings
- Code Duplication · Edited copy of a member (16 corresponding lines) core/shared/src/main/scala/monocle/Optional.scala
- Code Duplication · Edited copy of a member (18 corresponding lines) core/shared/src/main/scala-3/monocle/internal/focus/features/selectfield/SelectFieldGenerator.scala
- Code Duplication · Edited copies of one member (3 members, 11+ corresponding lines) core/shared/src/main/scala/monocle/function/FilterIndex.scala
- Code Duplication · Edited copy of a member (8 corresponding lines) core/shared/src/main/scala/monocle/function/Each.scala
- Code Duplication · Edited copy of a member (6 corresponding lines) core/shared/src/main/scala/monocle/function/Plated.scala
- Code Duplication · Edited copies of one member (4 members, 4+ corresponding lines) core/shared/src/main/scala/monocle/Traversal.scala
- Code Duplication · Edited copy of a member (7 corresponding lines) core/shared/src/main/scala-3/monocle/internal/focus/features/at/AtGenerator.scala
- Code Duplication · Edited copies of one member (3 members, 5+ corresponding lines) core/shared/src/main/scala/monocle/function/Cons1.scala
- Code Duplication · Edited copies of one member (3 members, 5+ corresponding lines) core/shared/src/main/scala/monocle/function/Snoc1.scala
- Code Duplication · Edited copies of one member (3 members, 5+ corresponding lines) core/shared/src/main/scala/monocle/function/Each.scala
- Code Duplication · Edited copy of a member (5 corresponding lines) core/shared/src/main/scala/monocle/Iso.scala
- Code Duplication · Edited copies of one member (3 members, 12+ corresponding lines) macro/src/main/scala-2/monocle/macros/syntax/AppliedFocusSyntax.scala
- Code Duplication · Edited copies of one member (3 members, 15+ corresponding lines) core/shared/src/main/scala-3/monocle/internal/focus/features/at/AtParser.scala
- Code Duplication · Edited copy of a member (5 corresponding lines) core/shared/src/main/scala/monocle/Iso.scala
- Code Duplication · Edited copies of one member (3 members, 5+ corresponding lines) core/shared/src/main/scala/monocle/function/Reverse.scala
- Code Duplication · Edited copies of one member (3 members, 5+ corresponding lines) core/shared/src/main/scala/monocle/Iso.scala
- Code Duplication · Edited copy of a member (4 corresponding lines) core/shared/src/main/scala/monocle/law/OptionalLaws.scala
- Code Duplication · Edited copy of a member (8 corresponding lines) core/shared/src/main/scala-3/monocle/internal/focus/features/some/SomeParser.scala
- Code Duplication · Edited copy of a member (7 corresponding lines) core/shared/src/main/scala-3/monocle/internal/focus/features/as/AsGenerator.scala
- Code Duplication · Edited copies of one member (6 members, 3+ corresponding lines) core/shared/src/main/scala/monocle/function/Field1.scala
- Code Duplication · Edited copy of a member (1 corresponding lines) core/shared/src/main/scala/monocle/law/IsoLaws.scala
- Code Duplication · Edited copies of one member (3 members, 9+ corresponding lines) bench/src/main/scala/monocle/bench/StdLensBench.scala
Fixed since the last survey: 1 finding
- Churn × Complexity Hotspots · Hotspot: core/shared/src/main/scala-3/monocle/internal/focus/features/ParserLoop.scala core/shared/src/main/scala-3/monocle/internal/focus/features/ParserLoop.scala
Rebuild cost: about €14,000 · Estimate
| Cost to rebuild | €4,700 to €24,000, for 79 to 250 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 51. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 7,799 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 (global) | 2 monocle.docs | 3 monocle.generic.internal | 4 monocle.internal.focus.FocusBase | 5 monocle.internal.focus.FocusBase.NamedTuples | 6 monocle.internal.focus.LambdaConfigParser | 7 monocle.internal.focus.features.KeywordParserBase | 8 monocle.internal.focus.features.ParserBase | 9 monocle.internal.focus.features.ParserLoop | 10 monocle.internal.focus.features.SelectParserBase | 11 monocle.internal.focus.features.as | 12 monocle.internal.focus.features.as.AsParser | 13 monocle.internal.focus.features.at | 14 monocle.internal.focus.features.each | 15 monocle.internal.focus.features.index | 16 monocle.internal.focus.features.selectfield | 17 monocle.internal.focus.features.selectonlyfield | 18 monocle.internal.focus.features.some | 19 monocle.internal.focus.features.withdefault | 20 monocle.refined.internal | 21 monocle.function | 22 monocle.internal.focus.features | 23 monocle.law.discipline.function | 24 monocle.syntax | 25 monocle | 26 monocle.Focus | 27 monocle.generic | 28 monocle.generic.CoProductInstances | 29 monocle.internal | 30 monocle.internal.focus | 31 monocle.law.discipline | 32 monocle.macros | 33 monocle.macros.internal | 34 monocle.macros.syntax | 35 monocle.refined | 36 monocle.state | 37 monocle.std | 38 monocle.unsafe | 39 monocle.internal.IsEq | 40 monocle.law |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 (global) | ||||||||||||||||||||||||||||||||||||||||
| 2 monocle.docs | ||||||||||||||||||||||||||||||||||||||||
| 3 monocle.generic.internal | ||||||||||||||||||||||||||||||||||||||||
| 4 monocle.internal.focus.FocusBase | ||||||||||||||||||||||||||||||||||||||||
| 5 monocle.internal.focus.FocusBase.NamedTuples | ||||||||||||||||||||||||||||||||||||||||
| 6 monocle.internal.focus.LambdaConfigParser | ||||||||||||||||||||||||||||||||||||||||
| 7 monocle.internal.focus.features.KeywordParserBase | ||||||||||||||||||||||||||||||||||||||||
| 8 monocle.internal.focus.features.ParserBase | ||||||||||||||||||||||||||||||||||||||||
| 9 monocle.internal.focus.features.ParserLoop | ||||||||||||||||||||||||||||||||||||||||
| 10 monocle.internal.focus.features.SelectParserBase | ||||||||||||||||||||||||||||||||||||||||
| 11 monocle.internal.focus.features.as | ||||||||||||||||||||||||||||||||||||||||
| 12 monocle.internal.focus.features.as.AsParser | ||||||||||||||||||||||||||||||||||||||||
| 13 monocle.internal.focus.features.at | ||||||||||||||||||||||||||||||||||||||||
| 14 monocle.internal.focus.features.each | ||||||||||||||||||||||||||||||||||||||||
| 15 monocle.internal.focus.features.index | ||||||||||||||||||||||||||||||||||||||||
| 16 monocle.internal.focus.features.selectfield | ||||||||||||||||||||||||||||||||||||||||
| 17 monocle.internal.focus.features.selectonlyfield | ||||||||||||||||||||||||||||||||||||||||
| 18 monocle.internal.focus.features.some | ||||||||||||||||||||||||||||||||||||||||
| 19 monocle.internal.focus.features.withdefault | ||||||||||||||||||||||||||||||||||||||||
| 20 monocle.refined.internal | ||||||||||||||||||||||||||||||||||||||||
| 21 monocle.function | 47 | |||||||||||||||||||||||||||||||||||||||
| 22 monocle.internal.focus.features | 2 | 2 | 2 | 2 | 4 | 2 | 2 | 2 | 2 | |||||||||||||||||||||||||||||||
| 23 monocle.law.discipline.function | 10 | |||||||||||||||||||||||||||||||||||||||
| 24 monocle.syntax | 26 | 83 | ||||||||||||||||||||||||||||||||||||||
| 25 monocle | 40 | 2 | ||||||||||||||||||||||||||||||||||||||
| 26 monocle.Focus | 1 | |||||||||||||||||||||||||||||||||||||||
| 27 monocle.generic | 1 | 11 | 5 | |||||||||||||||||||||||||||||||||||||
| 28 monocle.generic.CoProductInstances | 4 | |||||||||||||||||||||||||||||||||||||||
| 29 monocle.internal | 4 | |||||||||||||||||||||||||||||||||||||||
| 30 monocle.internal.focus | 4 | 3 | ||||||||||||||||||||||||||||||||||||||
| 31 monocle.law.discipline | 6 | |||||||||||||||||||||||||||||||||||||||
| 32 monocle.macros | 3 | |||||||||||||||||||||||||||||||||||||||
| 33 monocle.macros.internal | 2 | |||||||||||||||||||||||||||||||||||||||
| 34 monocle.macros.syntax | 14 | |||||||||||||||||||||||||||||||||||||||
| 35 monocle.refined | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 36 monocle.state | 12 | |||||||||||||||||||||||||||||||||||||||
| 37 monocle.std | 41 | |||||||||||||||||||||||||||||||||||||||
| 38 monocle.unsafe | 2 | 3 | ||||||||||||||||||||||||||||||||||||||
| 39 monocle.internal.IsEq | 1 | |||||||||||||||||||||||||||||||||||||||
| 40 monocle.law | 6 | 7 |
21→25 monocle.function uses monocle part of a loop✕
- Connections
- 47 pairs of types, where a type in monocle.function uses a type in monocle. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
monocle.function.At→monocle.Lensmonocle.function.AtFunctions→monocle.Lensmonocle.function.CommonPlatedFunctions→monocle.Traversalmonocle.function.Cons→monocle.Optionalmonocle.function.Cons→monocle.Prismmonocle.function.Cons1→monocle.Isomonocle.function.Cons1→monocle.Lensmonocle.function.Cons1Functions→monocle.Isomonocle.function.Cons1Functions→monocle.Lensmonocle.function.ConsFunctions→monocle.Optionalmonocle.function.ConsFunctions→monocle.Prismmonocle.function.Curry→monocle.Isomonocle.function.CurryFunctions→monocle.Isomonocle.function.Each→monocle.Traversalmonocle.function.EachFunctions→monocle.Traversalmonocle.function.Empty→monocle.Prismmonocle.function.EmptyFunctions→monocle.Prismmonocle.function.Field1→monocle.Lensmonocle.function.Field1Functions→monocle.Lensmonocle.function.Field2→monocle.Lensmonocle.function.Field2Functions→monocle.Lensmonocle.function.Field3→monocle.Lensmonocle.function.Field3Functions→monocle.Lensmonocle.function.Field4→monocle.Lensmonocle.function.Field4Functions→monocle.Lens
- Direction
- monocle.function uses monocle, so a change to monocle can break monocle.function, while a change to monocle.function can't break monocle.
- 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→11 monocle.internal.focus.features uses monocle.internal.focus.features.as✕
- Connections
- 2 pairs of types, where a type in monocle.internal.focus.features uses a type in monocle.internal.focus.features.as.
- The types involved
monocle.internal.focus.features.AllFeatureGenerators→monocle.internal.focus.features.as.AsGeneratormonocle.internal.focus.features.AllFeatureParsers→monocle.internal.focus.features.as.AsParser
- Direction
- monocle.internal.focus.features uses monocle.internal.focus.features.as, so a change to monocle.internal.focus.features.as can break monocle.internal.focus.features, while a change to monocle.internal.focus.features can't break monocle.internal.focus.features.as.
- Position
- Below the diagonal: monocle.internal.focus.features uses a module listed above it, which is the healthy direction.
22→13 monocle.internal.focus.features uses monocle.internal.focus.features.at✕
- Connections
- 2 pairs of types, where a type in monocle.internal.focus.features uses a type in monocle.internal.focus.features.at.
- The types involved
monocle.internal.focus.features.AllFeatureGenerators→monocle.internal.focus.features.at.AtGeneratormonocle.internal.focus.features.AllFeatureParsers→monocle.internal.focus.features.at.AtParser
- Direction
- monocle.internal.focus.features uses monocle.internal.focus.features.at, so a change to monocle.internal.focus.features.at can break monocle.internal.focus.features, while a change to monocle.internal.focus.features can't break monocle.internal.focus.features.at.
- Position
- Below the diagonal: monocle.internal.focus.features uses a module listed above it, which is the healthy direction.
22→14 monocle.internal.focus.features uses monocle.internal.focus.features.each✕
- Connections
- 2 pairs of types, where a type in monocle.internal.focus.features uses a type in monocle.internal.focus.features.each.
- The types involved
monocle.internal.focus.features.AllFeatureGenerators→monocle.internal.focus.features.each.EachGeneratormonocle.internal.focus.features.AllFeatureParsers→monocle.internal.focus.features.each.EachParser
- Direction
- monocle.internal.focus.features uses monocle.internal.focus.features.each, so a change to monocle.internal.focus.features.each can break monocle.internal.focus.features, while a change to monocle.internal.focus.features can't break monocle.internal.focus.features.each.
- Position
- Below the diagonal: monocle.internal.focus.features uses a module listed above it, which is the healthy direction.
22→15 monocle.internal.focus.features uses monocle.internal.focus.features.index✕
- Connections
- 2 pairs of types, where a type in monocle.internal.focus.features uses a type in monocle.internal.focus.features.index.
- The types involved
monocle.internal.focus.features.AllFeatureGenerators→monocle.internal.focus.features.index.IndexGeneratormonocle.internal.focus.features.AllFeatureParsers→monocle.internal.focus.features.index.IndexParser
- Direction
- monocle.internal.focus.features uses monocle.internal.focus.features.index, so a change to monocle.internal.focus.features.index can break monocle.internal.focus.features, while a change to monocle.internal.focus.features can't break monocle.internal.focus.features.index.
- Position
- Below the diagonal: monocle.internal.focus.features uses a module listed above it, which is the healthy direction.
22→16 monocle.internal.focus.features uses monocle.internal.focus.features.selectfield✕
- Connections
- 4 pairs of types, where a type in monocle.internal.focus.features uses a type in monocle.internal.focus.features.selectfield.
- The types involved
monocle.internal.focus.features.AllFeatureGenerators→monocle.internal.focus.features.selectfield.SelectFieldGeneratormonocle.internal.focus.features.AllFeatureGenerators→monocle.internal.focus.features.selectfield.SelectNamedTupleFieldGeneratormonocle.internal.focus.features.AllFeatureParsers→monocle.internal.focus.features.selectfield.SelectFieldParsermonocle.internal.focus.features.AllFeatureParsers→monocle.internal.focus.features.selectfield.SelectNamedTupleFieldParser
- Direction
- monocle.internal.focus.features uses monocle.internal.focus.features.selectfield, so a change to monocle.internal.focus.features.selectfield can break monocle.internal.focus.features, while a change to monocle.internal.focus.features can't break monocle.internal.focus.features.selectfield.
- Position
- Below the diagonal: monocle.internal.focus.features uses a module listed above it, which is the healthy direction.
22→17 monocle.internal.focus.features uses monocle.internal.focus.features.selectonlyfield✕
- Connections
- 2 pairs of types, where a type in monocle.internal.focus.features uses a type in monocle.internal.focus.features.selectonlyfield.
- The types involved
monocle.internal.focus.features.AllFeatureGenerators→monocle.internal.focus.features.selectonlyfield.SelectOnlyFieldGeneratormonocle.internal.focus.features.AllFeatureParsers→monocle.internal.focus.features.selectonlyfield.SelectOnlyFieldParser
- Direction
- monocle.internal.focus.features uses monocle.internal.focus.features.selectonlyfield, so a change to monocle.internal.focus.features.selectonlyfield can break monocle.internal.focus.features, while a change to monocle.internal.focus.features can't break monocle.internal.focus.features.selectonlyfield.
- Position
- Below the diagonal: monocle.internal.focus.features uses a module listed above it, which is the healthy direction.
22→18 monocle.internal.focus.features uses monocle.internal.focus.features.some✕
- Connections
- 2 pairs of types, where a type in monocle.internal.focus.features uses a type in monocle.internal.focus.features.some.
- The types involved
monocle.internal.focus.features.AllFeatureGenerators→monocle.internal.focus.features.some.SomeGeneratormonocle.internal.focus.features.AllFeatureParsers→monocle.internal.focus.features.some.SomeParser
- Direction
- monocle.internal.focus.features uses monocle.internal.focus.features.some, so a change to monocle.internal.focus.features.some can break monocle.internal.focus.features, while a change to monocle.internal.focus.features can't break monocle.internal.focus.features.some.
- Position
- Below the diagonal: monocle.internal.focus.features uses a module listed above it, which is the healthy direction.
22→19 monocle.internal.focus.features uses monocle.internal.focus.features.withdefault✕
- Connections
- 2 pairs of types, where a type in monocle.internal.focus.features uses a type in monocle.internal.focus.features.withdefault.
- The types involved
monocle.internal.focus.features.AllFeatureGenerators→monocle.internal.focus.features.withdefault.WithDefaultGeneratormonocle.internal.focus.features.AllFeatureParsers→monocle.internal.focus.features.withdefault.WithDefaultParser
- Direction
- monocle.internal.focus.features uses monocle.internal.focus.features.withdefault, so a change to monocle.internal.focus.features.withdefault can break monocle.internal.focus.features, while a change to monocle.internal.focus.features can't break monocle.internal.focus.features.withdefault.
- Position
- Below the diagonal: monocle.internal.focus.features uses a module listed above it, which is the healthy direction.
22→30 monocle.internal.focus.features uses monocle.internal.focus part of a loop✕
- Connections
- 2 pairs of types, where a type in monocle.internal.focus.features uses a type in monocle.internal.focus.
- The types involved
monocle.internal.focus.features.AllFeatureGenerators→monocle.internal.focus.FocusBasemonocle.internal.focus.features.AllFeatureParsers→monocle.internal.focus.FocusBase
- Direction
- monocle.internal.focus.features uses monocle.internal.focus, so a change to monocle.internal.focus can break monocle.internal.focus.features, while a change to monocle.internal.focus.features can't break monocle.internal.focus.
- 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→21 monocle.law.discipline.function uses monocle.function✕
- Connections
- 10 pairs of types, where a type in monocle.law.discipline.function uses a type in monocle.function.
- The types involved
monocle.law.discipline.function.AtTests→monocle.function.Atmonocle.law.discipline.function.Cons1Tests→monocle.function.Cons1monocle.law.discipline.function.ConsTests→monocle.function.Consmonocle.law.discipline.function.EachTests→monocle.function.Eachmonocle.law.discipline.function.FilterIndexTests→monocle.function.FilterIndexmonocle.law.discipline.function.IndexTests→monocle.function.Indexmonocle.law.discipline.function.PossibleTests→monocle.function.Possiblemonocle.law.discipline.function.ReverseTests→monocle.function.Reversemonocle.law.discipline.function.Snoc1Tests→monocle.function.Snoc1monocle.law.discipline.function.SnocTests→monocle.function.Snoc
- Direction
- monocle.law.discipline.function uses monocle.function, so a change to monocle.function can break monocle.law.discipline.function, while a change to monocle.law.discipline.function can't break monocle.function.
- Position
- Below the diagonal: monocle.law.discipline.function uses a module listed above it, which is the healthy direction.
24→21 monocle.syntax uses monocle.function✕
- Connections
- 26 pairs of types, where a type in monocle.syntax uses a type in monocle.function. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
monocle.syntax.AppliedFoldSyntax→monocle.function.Atmonocle.syntax.AppliedFoldSyntax→monocle.function.Eachmonocle.syntax.AppliedFoldSyntax→monocle.function.FilterIndexmonocle.syntax.AppliedFoldSyntax→monocle.function.Indexmonocle.syntax.AppliedGetterSyntax→monocle.function.Atmonocle.syntax.AppliedIsoSyntax→monocle.function.Atmonocle.syntax.AppliedIsoSyntax→monocle.function.Eachmonocle.syntax.AppliedIsoSyntax→monocle.function.FilterIndexmonocle.syntax.AppliedIsoSyntax→monocle.function.Indexmonocle.syntax.AppliedLensSyntax→monocle.function.Atmonocle.syntax.AppliedOptionalSyntax→monocle.function.Atmonocle.syntax.AppliedOptionalSyntax→monocle.function.Indexmonocle.syntax.AppliedSetterSyntax→monocle.function.Atmonocle.syntax.AppliedSetterSyntax→monocle.function.Eachmonocle.syntax.AppliedSetterSyntax→monocle.function.FilterIndexmonocle.syntax.AppliedSetterSyntax→monocle.function.Indexmonocle.syntax.AppliedTraversalSyntax→monocle.function.Atmonocle.syntax.AppliedTraversalSyntax→monocle.function.Eachmonocle.syntax.AppliedTraversalSyntax→monocle.function.FilterIndexmonocle.syntax.AppliedTraversalSyntax→monocle.function.Indexmonocle.syntax.FieldsSyntax→monocle.function.Field1monocle.syntax.FieldsSyntax→monocle.function.Field2monocle.syntax.FieldsSyntax→monocle.function.Field3monocle.syntax.FieldsSyntax→monocle.function.Field4monocle.syntax.FieldsSyntax→monocle.function.Field5
- Direction
- monocle.syntax uses monocle.function, so a change to monocle.function can break monocle.syntax, while a change to monocle.syntax can't break monocle.function.
- Position
- Below the diagonal: monocle.syntax uses a module listed above it, which is the healthy direction.
24→25 monocle.syntax uses monocle part of a loop✕
- Connections
- 83 pairs of types, where a type in monocle.syntax uses a type in monocle. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
monocle.syntax.AppliedFold→monocle.Foldmonocle.syntax.AppliedFoldOps→monocle.Foldmonocle.syntax.AppliedFoldSyntax→monocle.Foldmonocle.syntax.AppliedFoldSyntax→monocle.Gettermonocle.syntax.AppliedFoldSyntax→monocle.PIsomonocle.syntax.AppliedFoldSyntax→monocle.PLensmonocle.syntax.AppliedFoldSyntax→monocle.POptionalmonocle.syntax.AppliedFoldSyntax→monocle.PPrismmonocle.syntax.AppliedFoldSyntax→monocle.PTraversalmonocle.syntax.AppliedGetter→monocle.Gettermonocle.syntax.AppliedGetterOps→monocle.Gettermonocle.syntax.AppliedGetterSyntax→monocle.Foldmonocle.syntax.AppliedGetterSyntax→monocle.Gettermonocle.syntax.AppliedGetterSyntax→monocle.PIsomonocle.syntax.AppliedGetterSyntax→monocle.PLensmonocle.syntax.AppliedGetterSyntax→monocle.POptionalmonocle.syntax.AppliedGetterSyntax→monocle.PPrismmonocle.syntax.AppliedGetterSyntax→monocle.PTraversalmonocle.syntax.AppliedIso→monocle.Isomonocle.syntax.AppliedIsoOps→monocle.PIsomonocle.syntax.AppliedLens→monocle.Lensmonocle.syntax.AppliedLensOps→monocle.PLensmonocle.syntax.AppliedOptional→monocle.Optionalmonocle.syntax.AppliedOptionalOps→monocle.POptionalmonocle.syntax.AppliedPIso→monocle.PIso
- Direction
- monocle.syntax uses monocle, so a change to monocle can break monocle.syntax, while a change to monocle.syntax can't break monocle.
- 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.
25→21 monocle uses monocle.function✕
- Connections
- 40 pairs of types, where a type in monocle uses a type in monocle.function. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
monocle.Fold→monocle.function.Indexmonocle.FoldSyntax→monocle.function.Atmonocle.FoldSyntax→monocle.function.Eachmonocle.FoldSyntax→monocle.function.FilterIndexmonocle.FoldSyntax→monocle.function.Indexmonocle.Getter→monocle.function.Indexmonocle.GetterSyntax→monocle.function.Atmonocle.GetterSyntax→monocle.function.Eachmonocle.GetterSyntax→monocle.function.FilterIndexmonocle.GetterSyntax→monocle.function.Indexmonocle.IsoSyntax→monocle.function.Atmonocle.IsoSyntax→monocle.function.Eachmonocle.IsoSyntax→monocle.function.FilterIndexmonocle.IsoSyntax→monocle.function.Indexmonocle.LensSyntax→monocle.function.Atmonocle.LensSyntax→monocle.function.Eachmonocle.LensSyntax→monocle.function.FilterIndexmonocle.LensSyntax→monocle.function.Indexmonocle.OptionalSyntax→monocle.function.Atmonocle.OptionalSyntax→monocle.function.Eachmonocle.OptionalSyntax→monocle.function.FilterIndexmonocle.OptionalSyntax→monocle.function.Indexmonocle.PIso→monocle.function.Indexmonocle.PLens→monocle.function.Indexmonocle.POptional→monocle.function.Index
- Direction
- monocle uses monocle.function, so a change to monocle.function can break monocle, while a change to monocle can't break monocle.function.
- Position
- Below the diagonal: monocle uses a module listed above it, which is the healthy direction.
25→24 monocle uses monocle.syntax✕
- Connections
- 2 pairs of types, where a type in monocle uses a type in monocle.syntax.
- The types involved
monocle.Focus→monocle.syntax.AppliedFocusSyntaxmonocle.Focus→monocle.syntax.ComposedFocusSyntax
- Direction
- monocle uses monocle.syntax, so a change to monocle.syntax can break monocle, while a change to monocle can't break monocle.syntax.
- Position
- Below the diagonal: monocle uses a module listed above it, which is the healthy direction.
26→25 monocle.Focus uses monocle✕
- Connections
- 1 pair of types, where a type in monocle.Focus uses a type in monocle.
- The types involved
monocle.Focus.MkFocus→monocle.Iso
- Direction
- monocle.Focus uses monocle, so a change to monocle can break monocle.Focus, while a change to monocle.Focus can't break monocle.
- Position
- Below the diagonal: monocle.Focus uses a module listed above it, which is the healthy direction.
27→3 monocle.generic uses monocle.generic.internal✕
- Connections
- 1 pair of types, where a type in monocle.generic uses a type in monocle.generic.internal.
- The types involved
monocle.generic.ProductOptics→monocle.generic.internal.TupleGeneric
- Direction
- monocle.generic uses monocle.generic.internal, so a change to monocle.generic.internal can break monocle.generic, while a change to monocle.generic can't break monocle.generic.internal.
- Position
- Below the diagonal: monocle.generic uses a module listed above it, which is the healthy direction.
27→21 monocle.generic uses monocle.function✕
- Connections
- 11 pairs of types, where a type in monocle.generic uses a type in monocle.function.
- The types involved
monocle.generic.HListInstances→monocle.function.Cons1monocle.generic.HListInstances→monocle.function.Field1monocle.generic.HListInstances→monocle.function.Field2monocle.generic.HListInstances→monocle.function.Field3monocle.generic.HListInstances→monocle.function.Field4monocle.generic.HListInstances→monocle.function.Field5monocle.generic.HListInstances→monocle.function.Field6monocle.generic.HListInstances→monocle.function.Reversemonocle.generic.HListInstances→monocle.function.Snoc1monocle.generic.ProductOptics→monocle.function.Eachmonocle.generic.TupleNInstances→monocle.function.Reverse
- Direction
- monocle.generic uses monocle.function, so a change to monocle.function can break monocle.generic, while a change to monocle.generic can't break monocle.function.
- Position
- Below the diagonal: monocle.generic uses a module listed above it, which is the healthy direction.
27→25 monocle.generic uses monocle✕
- Connections
- 5 pairs of types, where a type in monocle.generic uses a type in monocle.
- The types involved
monocle.generic.CoProductInstances→monocle.Prismmonocle.generic.GenericOptics→monocle.Isomonocle.generic.HListInstances→monocle.Isomonocle.generic.HListInstances→monocle.Lensmonocle.generic.ProductOptics→monocle.Iso
- Direction
- monocle.generic uses monocle, so a change to monocle can break monocle.generic, while a change to monocle.generic can't break monocle.
- Position
- Below the diagonal: monocle.generic uses a module listed above it, which is the healthy direction.
28→25 monocle.generic.CoProductInstances uses monocle✕
- Connections
- 4 pairs of types, where a type in monocle.generic.CoProductInstances uses a type in monocle.
- The types involved
monocle.generic.CoProductInstances.GenCoProductDisjunctionIso→monocle.Isomonocle.generic.CoProductInstances.GenCoProductEitherIso→monocle.Isomonocle.generic.CoProductInstances.GenCoProductToDisjunction→monocle.Isomonocle.generic.CoProductInstances.GenCoProductToEither→monocle.Iso
- Direction
- monocle.generic.CoProductInstances uses monocle, so a change to monocle can break monocle.generic.CoProductInstances, while a change to monocle.generic.CoProductInstances can't break monocle.
- Position
- Below the diagonal: monocle.generic.CoProductInstances uses a module listed above it, which is the healthy direction.
29→25 monocle.internal uses monocle✕
- Connections
- 4 pairs of types, where a type in monocle.internal uses a type in monocle.
- The types involved
monocle.internal.AsPrism→monocle.Prismmonocle.internal.AsPrismImpl→monocle.Prismmonocle.internal.IsoFields→monocle.PIsomonocle.internal.IsoFieldsImpl→monocle.PIso
- Direction
- monocle.internal uses monocle, so a change to monocle can break monocle.internal, while a change to monocle.internal can't break monocle.
- Position
- Below the diagonal: monocle.internal uses a module listed above it, which is the healthy direction.
30→22 monocle.internal.focus uses monocle.internal.focus.features✕
- Connections
- 4 pairs of types, where a type in monocle.internal.focus uses a type in monocle.internal.focus.features.
- The types involved
monocle.internal.focus.FocusImpl→monocle.internal.focus.features.AllFeatureGeneratorsmonocle.internal.focus.FocusImpl→monocle.internal.focus.features.AllFeatureParsersmonocle.internal.focus.FocusImpl→monocle.internal.focus.features.GeneratorLoopmonocle.internal.focus.FocusImpl→monocle.internal.focus.features.ParserLoop
- Direction
- monocle.internal.focus uses monocle.internal.focus.features, so a change to monocle.internal.focus.features can break monocle.internal.focus, while a change to monocle.internal.focus can't break monocle.internal.focus.features.
- Position
- Below the diagonal: monocle.internal.focus uses a module listed above it, which is the healthy direction.
30→25 monocle.internal.focus uses monocle✕
- Connections
- 3 pairs of types, where a type in monocle.internal.focus uses a type in monocle.
- The types involved
monocle.internal.focus.AppliedFocusImpl→monocle.Focusmonocle.internal.focus.ComposedFocusImpl→monocle.Focusmonocle.internal.focus.FocusImpl→monocle.Focus
- Direction
- monocle.internal.focus uses monocle, so a change to monocle can break monocle.internal.focus, while a change to monocle.internal.focus can't break monocle.
- Position
- Below the diagonal: monocle.internal.focus uses a module listed above it, which is the healthy direction.
31→25 monocle.law.discipline uses monocle✕
- Connections
- 6 pairs of types, where a type in monocle.law.discipline uses a type in monocle.
- The types involved
monocle.law.discipline.IsoTests→monocle.Isomonocle.law.discipline.LensTests→monocle.Lensmonocle.law.discipline.OptionalTests→monocle.Optionalmonocle.law.discipline.PrismTests→monocle.Prismmonocle.law.discipline.SetterTests→monocle.Settermonocle.law.discipline.TraversalTests→monocle.Traversal
- Direction
- monocle.law.discipline uses monocle, so a change to monocle can break monocle.law.discipline, while a change to monocle.law.discipline can't break monocle.
- Position
- Below the diagonal: monocle.law.discipline uses a module listed above it, which is the healthy direction.
32→25 monocle.macros uses monocle✕
- Connections
- 3 pairs of types, where a type in monocle.macros uses a type in monocle.
- The types involved
monocle.macros.GenIsoImpl→monocle.Isomonocle.macros.GenLens→monocle.Isomonocle.macros.GenPrismImpl→monocle.Prism
- Direction
- monocle.macros uses monocle, so a change to monocle can break monocle.macros, while a change to monocle.macros can't break monocle.
- Position
- Below the diagonal: monocle.macros uses a module listed above it, which is the healthy direction.
33→25 monocle.macros.internal uses monocle✕
- Connections
- 2 pairs of types, where a type in monocle.macros.internal uses a type in monocle.
- The types involved
monocle.macros.internal.MacroImpl→monocle.Lensmonocle.macros.internal.MacroImpl→monocle.PLens
- Direction
- monocle.macros.internal uses monocle, so a change to monocle can break monocle.macros.internal, while a change to monocle.macros.internal can't break monocle.
- Position
- Below the diagonal: monocle.macros.internal uses a module listed above it, which is the healthy direction.
34→25 monocle.macros.syntax uses monocle✕
- Connections
- 14 pairs of types, where a type in monocle.macros.syntax uses a type in monocle.
- The types involved
monocle.macros.syntax.MacroFoldOps→monocle.Foldmonocle.macros.syntax.MacroGetterOps→monocle.Gettermonocle.macros.syntax.MacroLensOps→monocle.Lensmonocle.macros.syntax.MacroOptionalOps→monocle.Optionalmonocle.macros.syntax.MacroPrismOps→monocle.Prismmonocle.macros.syntax.MacroSetterOps→monocle.Settermonocle.macros.syntax.MacroSyntax→monocle.Foldmonocle.macros.syntax.MacroSyntax→monocle.Gettermonocle.macros.syntax.MacroSyntax→monocle.Lensmonocle.macros.syntax.MacroSyntax→monocle.Optionalmonocle.macros.syntax.MacroSyntax→monocle.Prismmonocle.macros.syntax.MacroSyntax→monocle.Settermonocle.macros.syntax.MacroSyntax→monocle.Traversalmonocle.macros.syntax.MacroTraversalOps→monocle.Traversal
- Direction
- monocle.macros.syntax uses monocle, so a change to monocle can break monocle.macros.syntax, while a change to monocle.macros.syntax can't break monocle.
- Position
- Below the diagonal: monocle.macros.syntax uses a module listed above it, which is the healthy direction.
35→20 monocle.refined uses monocle.refined.internal✕
- Connections
- 1 pair of types, where a type in monocle.refined uses a type in monocle.refined.internal.
- The types involved
monocle.refined.BitsInstances→monocle.refined.internal.Bits
- Direction
- monocle.refined uses monocle.refined.internal, so a change to monocle.refined.internal can break monocle.refined, while a change to monocle.refined can't break monocle.refined.internal.
- Position
- Below the diagonal: monocle.refined uses a module listed above it, which is the healthy direction.
35→21 monocle.refined uses monocle.function✕
- Connections
- 1 pair of types, where a type in monocle.refined uses a type in monocle.function.
- The types involved
monocle.refined.BitsInstances→monocle.function.At
- Direction
- monocle.refined uses monocle.function, so a change to monocle.function can break monocle.refined, while a change to monocle.refined can't break monocle.function.
- Position
- Below the diagonal: monocle.refined uses a module listed above it, which is the healthy direction.
35→25 monocle.refined uses monocle✕
- Connections
- 2 pairs of types, where a type in monocle.refined uses a type in monocle.
- The types involved
monocle.refined.CharsInstances→monocle.Prismmonocle.refined.StringsInstances→monocle.Prism
- Direction
- monocle.refined uses monocle, so a change to monocle can break monocle.refined, while a change to monocle.refined can't break monocle.
- Position
- Below the diagonal: monocle.refined uses a module listed above it, which is the healthy direction.
36→25 monocle.state uses monocle✕
- Connections
- 12 pairs of types, where a type in monocle.state uses a type in monocle.
- The types involved
monocle.state.ReaderGetterOps→monocle.Gettermonocle.state.ReaderGetterSyntax→monocle.Gettermonocle.state.StateGetterOps→monocle.Gettermonocle.state.StateGetterSyntax→monocle.Gettermonocle.state.StateLensOps→monocle.PLensmonocle.state.StateLensSyntax→monocle.PLensmonocle.state.StateOptionalOps→monocle.POptionalmonocle.state.StateOptionalSyntax→monocle.POptionalmonocle.state.StateSetterOps→monocle.PSettermonocle.state.StateSetterSyntax→monocle.PSettermonocle.state.StateTraversalOps→monocle.PTraversalmonocle.state.StateTraversalSyntax→monocle.PTraversal
- Direction
- monocle.state uses monocle, so a change to monocle can break monocle.state, while a change to monocle.state can't break monocle.
- Position
- Below the diagonal: monocle.state uses a module listed above it, which is the healthy direction.
37→25 monocle.std uses monocle✕
- Connections
- 41 pairs of types, where a type in monocle.std uses a type in monocle. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
monocle.std.BigDecimalOptics→monocle.Prismmonocle.std.BigIntOptics→monocle.Prismmonocle.std.ByteOptics→monocle.Prismmonocle.std.ChainOptics→monocle.Isomonocle.std.ChainOptics→monocle.PIsomonocle.std.CharOptics→monocle.Prismmonocle.std.DoubleOptics→monocle.Prismmonocle.std.EitherOptics→monocle.PPrismmonocle.std.EitherOptics→monocle.Prismmonocle.std.FunctionOptics→monocle.Isomonocle.std.IntOptics→monocle.Prismmonocle.std.ListOptics→monocle.Isomonocle.std.ListOptics→monocle.PIsomonocle.std.LongOptics→monocle.Prismmonocle.std.MapOptics→monocle.Isomonocle.std.NonEmptyChainOptics→monocle.Isomonocle.std.NonEmptyChainOptics→monocle.PIsomonocle.std.NonEmptyChainOptics→monocle.PPrismmonocle.std.NonEmptyChainOptics→monocle.Prismmonocle.std.NonEmptyListOptics→monocle.Isomonocle.std.NonEmptyListOptics→monocle.PIsomonocle.std.NonEmptyVectorOptics→monocle.Isomonocle.std.NonEmptyVectorOptics→monocle.PIsomonocle.std.NonEmptyVectorOptics→monocle.PPrismmonocle.std.NonEmptyVectorOptics→monocle.Prism
- Direction
- monocle.std uses monocle, so a change to monocle can break monocle.std, while a change to monocle.std can't break monocle.
- Position
- Below the diagonal: monocle.std uses a module listed above it, which is the healthy direction.
38→21 monocle.unsafe uses monocle.function✕
- Connections
- 2 pairs of types, where a type in monocle.unsafe uses a type in monocle.function.
- The types involved
monocle.unsafe.MapTraversal→monocle.function.Eachmonocle.unsafe.MapTraversal→monocle.function.FilterIndex
- Direction
- monocle.unsafe uses monocle.function, so a change to monocle.function can break monocle.unsafe, while a change to monocle.unsafe can't break monocle.function.
- Position
- Below the diagonal: monocle.unsafe uses a module listed above it, which is the healthy direction.
38→25 monocle.unsafe uses monocle✕
- Connections
- 3 pairs of types, where a type in monocle.unsafe uses a type in monocle.
- The types involved
monocle.unsafe.MapTraversal→monocle.Isomonocle.unsafe.MapTraversal→monocle.Traversalmonocle.unsafe.UnsafeSelect→monocle.Prism
- Direction
- monocle.unsafe uses monocle, so a change to monocle can break monocle.unsafe, while a change to monocle.unsafe can't break monocle.
- Position
- Below the diagonal: monocle.unsafe uses a module listed above it, which is the healthy direction.
39→29 monocle.internal.IsEq uses monocle.internal✕
- Connections
- 1 pair of types, where a type in monocle.internal.IsEq uses a type in monocle.internal.
- The types involved
monocle.internal.IsEq.IsEqOps→monocle.internal.IsEq
- Direction
- monocle.internal.IsEq uses monocle.internal, so a change to monocle.internal can break monocle.internal.IsEq, while a change to monocle.internal.IsEq can't break monocle.internal.
- Position
- Below the diagonal: monocle.internal.IsEq uses a module listed above it, which is the healthy direction.
40→25 monocle.law uses monocle✕
- Connections
- 6 pairs of types, where a type in monocle.law uses a type in monocle.
- The types involved
monocle.law.IsoLaws→monocle.Isomonocle.law.LensLaws→monocle.Lensmonocle.law.OptionalLaws→monocle.Optionalmonocle.law.PrismLaws→monocle.Prismmonocle.law.SetterLaws→monocle.Settermonocle.law.TraversalLaws→monocle.Traversal
- Direction
- monocle.law uses monocle, so a change to monocle can break monocle.law, while a change to monocle.law can't break monocle.
- Position
- Below the diagonal: monocle.law uses a module listed above it, which is the healthy direction.
40→29 monocle.law uses monocle.internal✕
- Connections
- 7 pairs of types, where a type in monocle.law uses a type in monocle.internal.
- The types involved
monocle.law.IsoLaws→monocle.internal.IsEqmonocle.law.LensLaws→monocle.internal.IsEqmonocle.law.OptionalLaws→monocle.internal.IsEqmonocle.law.PrismLaws→monocle.internal.IsEqmonocle.law.SetterLaws→monocle.internal.IsEqmonocle.law.TraversalLaws→monocle.internal.IsEqmonocle.law.discipline→monocle.internal.IsEq
- Direction
- monocle.law uses monocle.internal, so a change to monocle.internal can break monocle.law, while a change to monocle.law can't break monocle.internal.
- Position
- Below the diagonal: monocle.law 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 | 26 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 8 | Medium |
Roadmap
Top priorities: Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them; Expand the README with getting-started, architecture overview and a project map; 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.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +8.1 pts | Medium | Architecture documentation |
| Expand the README with getting-started, architecture overview and a project map. | +6.8 pts | Medium | Documentation (README) |
| 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. | +5.0 pts | Medium | Observability |
| Add a SAST step to CI running what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +4.5 pts | Medium | Security & performance tooling |
| Resolve the 5 Orphaned file finding(s) in Knowledge Freshness — start with CoProduct.scala, StateTraversalSyntax.scala, ProductIsoBench.scala. | +1.4 pts | Low | Knowledge Freshness |
| On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it. | +1.6 pts | Medium | Nullable reference types |
| Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. | +0.7 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +0.5 pts | Low | Static Analysis (SAST) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| core/shared/src/main/scala/monocle/Iso.scala | 7.4 | Mixed | Code Duplication: Edited copy of a member (5 corresponding lines) |
| core/shared/src/main/scala-3/monocle/internal/focus/features/selectfield/SelectFieldGenerator.scala | 7.8 | Mixed | Code Duplication: Edited copy of a member (18 corresponding lines) |
| core/shared/src/main/scala/monocle/function/FilterIndex.scala | 7.8 | Mixed | Code Duplication: Edited copies of one member (3 members, 11+ corresponding lines) |
| core/shared/src/main/scala/monocle/function/Each.scala | 7.8 | Mixed | Code Duplication: Edited copy of a member (8 corresponding lines) |
| bench/src/main/scala/monocle/bench/StdLensBench.scala | 7.8 | Mixed | Code Duplication: Edited copies of one member (3 members, 9+ corresponding lines) |
| REDACTED | 7.9 | Mixed | Supply-chain Provenance & Signing: REDACTED |
| macro/src/main/scala-2/monocle/macros/Lenses.scala | 8.5 | Near-clean | Cognitive Complexity: LensesImpl.annotationMacro (cognitive 24) |
| core/shared/src/main/scala/monocle/Optional.scala | 8.5 | Near-clean | Code Duplication: Edited copy of a member (16 corresponding lines) |
| core/shared/src/main/scala/monocle/function/Plated.scala | 8.5 | Near-clean | Code Duplication: Edited copy of a member (6 corresponding lines) |
| core/shared/src/main/scala/monocle/Traversal.scala | 8.5 | Near-clean | Code Duplication: Edited copies of one member (4 members, 4+ corresponding lines) |
| core/shared/src/main/scala-3/monocle/internal/focus/features/at/AtGenerator.scala | 8.5 | Near-clean | Code Duplication: Edited copy of a member (7 corresponding lines) |
| core/shared/src/main/scala/monocle/function/Cons1.scala | 8.5 | Near-clean | Code Duplication: Edited copies of one member (3 members, 5+ corresponding lines) |
| core/shared/src/main/scala/monocle/function/Snoc1.scala | 8.5 | Near-clean | Code Duplication: Edited copies of one member (3 members, 5+ corresponding lines) |
| macro/src/main/scala-2/monocle/macros/syntax/AppliedFocusSyntax.scala | 8.5 | Near-clean | Code Duplication: Edited copies of one member (3 members, 12+ corresponding lines) |
| core/shared/src/main/scala-3/monocle/internal/focus/features/at/AtParser.scala | 8.5 | Near-clean | Code Duplication: Edited copies of one member (3 members, 15+ corresponding lines) |
| core/shared/src/main/scala/monocle/function/Reverse.scala | 8.5 | Near-clean | Code Duplication: Edited copies of one member (3 members, 5+ corresponding lines) |
| core/shared/src/main/scala/monocle/law/OptionalLaws.scala | 8.5 | Near-clean | Code Duplication: Edited copy of a member (4 corresponding lines) |
| core/shared/src/main/scala-3/monocle/internal/focus/features/some/SomeParser.scala | 8.5 | Near-clean | Code Duplication: Edited copy of a member (8 corresponding lines) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 38 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 38 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, 67 of 80 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.scala) 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.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.scala) and this repository declares an sbt build (repository root, 120 test files), but it was not re-run: the analyzer environment could not run it. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — 2 direct sbt declaration(s) were read, but the outdated signal needs repo1.maven.org, and no declaration here states an exact version to ask about, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- D20 ADR Quality — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. The ADR expectation is gated on whether a repository ships a deployable product. Our repo-kind classifier reads .NET project files and the host and package markers of the other ecosystems it knows (a Go `package main`, a Cargo binary, a package.json `bin`, `start` script or application dev server such as Vite or Next, Python console scripts or a Django/WSGI entry point, a Spring Boot / WAR / Gradle application build, a Rack or Rails app, a Composer project, an OTP release or escript, a Dockerfile, a Procfile, a Platform.sh `.platform/routes.yaml`, and the corresponding published-package manifests, including an OTP `*.app.src`, a Drupal module's `*.info` and a Claude Code `.claude-plugin/plugin.json`), and found none here, so we could not tell what kind of repository this is and did not assess its ADR log. This is a gap in our analyzer, not a finding about this repository. Read, stating neither a host nor a published package: `build.sbt`, `project/plugins.sbt`.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `core/shared/src/main/scala-3/monocle/Focus.scala`, `core/shared/src/main/scala-3/monocle/internal/IsoFields.scala`, `core/shared/src/main/scala-3/monocle/syntax/AppliedFocusSyntax.scala`, `core/shared/src/main/scala-3/monocle/syntax/ComposedFocusSyntax.scala`, `core/shared/src/main/scala-3/monocle/syntax/MacroSyntax.scala`, … (+1 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- D44 Platform End-of-Life — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
- AX7 Slice cohesion — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 8 slice(s) were resolved from namespaces or project layout, but not one field or property type reference in them resolved to a type this analyzer had read. Cross-slice coupling is detected by following those references, so scoring the set anyway would report every slice as perfectly cohesive on the strength of having followed nothing.
- AXB2 Runtime readiness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. (rule: no-root-manifest). The renderer reported: the dev server (`npm run start`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (start). the dev server (`npm run start`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- 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.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- 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.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- 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
0 method(s) exceeded the cyclomatic complexity threshold of 15. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being ParserLoop.parseFocusActions at 21 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: core/shared/src/main/scala-3/monocle/internal/focus/features/ParserLoop.scala (ParserLoop.parseFocusActions at 21). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
D2 · Cognitive Complexity
1 method(s) exceeded the cognitive complexity threshold of 15; the worst was LensesImpl.annotationMacro at 24.
What to do
- Bring the 1 body over 15 down to 15 or less in Cognitive Complexity — start with LensesImpl.annotationMacro (cognitive 24). — Refactoring it lifts Cognitive Complexity from 9.4 to about 10.0/10.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
4 duplicated block group(s) detected. 5.3 % of the production lines (413 of 7,799) are in a reported copy. A further 22 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 3 of the 26 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
What to do
- Resolve the 5 Edited copies of one member (3 members, 5+ corresponding lines) finding(s) in Code Duplication — start with Cons1.scala, Snoc1.scala, Each.scala. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 2 Edited copy of a member (8 corresponding lines) finding(s) in Code Duplication — start with Each.scala, SomeParser.scala. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Edited copy of a member (7 corresponding lines) finding(s) in Code Duplication — start with AtGenerator.scala, AsGenerator.scala. — One of this dimension's main actionable groups (2 warning-level).
D5 · Coupling
7 production modules (sbt), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; a dependsOn spread (deps: _*) and a project whose directory a helper computes are not visible there; 1 module(s) off the main sequence.
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
0 of 6 classes have LCOM4 above 3.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
1 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is core/shared/src/main/scala-3/monocle/internal/focus/features/GeneratorLoop.scala. Counted over 38 of the 169 production source files in this repository: 123 are under the ~2,400-byte size floor this dimension measures over, and the remaining 8 have no attributable history left to measure.
D17 · Explicit Debt
0 deducted task-comment markers across 7799 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
D26 · Project Cohesion
1 of 2 build units (npm, sbt) 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)
26 finding(s): 0 critical, 26 high, 0 medium, 0 low. 24 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 2 file(s) — `logo/m-symbol/m-symbol-inverted-raster-review-file.jpg`, `macro/src/main/scala-3/monocle/macros/GenIso.scala` — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 24 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 (24 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in any ecosystem this repository declares.
D34 · Knowledge Freshness
5 of 46 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is generic/src/main/scala-2/monocle/generic/CoProduct.scala. Counted over 46 of the 169 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 5 Orphaned file finding(s) in Knowledge Freshness — start with CoProduct.scala, StateTraversalSyntax.scala, ProductIsoBench.scala. — One of this dimension's main actionable groups (5 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX5 · Architecture & structure
AX6 · Interface segregation
AX8 · Test isolation
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- A bare `// scalastyle:off`, `// scalafix:off` or `@nowarn` (or Wartremover's `warts.All`) switches every rule or warning off — hidden debt. Suppress the specific rule on the specific line, with a justification, instead. — generic/src/main/scala-2/monocle/generic/CoProduct.scala:13
What to do
- Clear the softer debt: re-enable or delete `ignore`d and `pending` tests, decide whether each empty method or UnsupportedOperationException is deliberate (and say so in a comment), and replace a bare `// scalastyle:off` or `@nowarn` with targeted, justified suppressions.
M1 · Documentation (README)
- The root README is 9 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, in the README and in the repository documents it links, it found no a build/run or getting-started section, no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers. — README.md:1
What to do
- Expand the README with getting-started, architecture overview and a project map.
- 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.
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
P10 · Library API & versioning
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
- No static application security testing detected. For this repository's stack, add scalafix or scapegoat (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 3 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:11
- `website/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — website/package.json:12
What to do
- Add a SAST step to CI running what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
PF1 · Benchmark discipline
- A JMH/Jetpack Benchmark suite exists but nothing turns on its allocation measurement — allocations (the main way hot code pressures a garbage collector or allocator) aren't being measured. — bench/src/main/scala/monocle/bench/MonocleIsoBench.scala
What to do
- Run JMH with the GC profiler (`-prof gc`, or addProfiler(GCProfiler.class)) so allocation rate regressions are visible, not just time.
X12 · Unreachable branch
X21 · Side-effecting pattern guard
X5 · Nullable reference types
- No build over this repository's 151 Scala product file(s) passes `-Yexplicit-nulls`, enables WartRemover's `Null` wart or runs Scalafix's `DisableSyntax.noNulls`, so every reference type admits null and nothing reports a `null` written into the code or returned from a Java API — the first one to reach a method call is a `NullPointerException`. `Option` by convention is a habit no tool here holds the code to.
What to do
- On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 69% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 91% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 41% | Weak — gated by M1, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 47% | Weak — gated by P2, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 65% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 85% | Strong | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 78 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: this repository's Scala imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Scala code is a Play controller, a Cask routes object, a Scalatra servlet, a Finatra controller, an Akka/Pekko HTTP routes holder or a JSR-330/Spring singleton, so no instance is shared between request threads. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX4 Dependency direction — not applicable to a vertical-slice architecture (the inward-dependency rule is for layered/clean styles)
- AX7 Slice cohesion — 8 slice(s) were identified, but none of their field/property type references could be resolved to a type in this repository, so no cross-slice reference could be followed. This is a limitation of the analyzer's type resolution on this language, not a finding about the repository.
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the dev server (`npm run start`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, a MongoDB or Cassandra driver, JDBC) imported 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, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database or data-store client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, JDBC, MongoDB, Cassandra, …) imported 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, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database or data-store client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, JDBC, MongoDB, Cassandra, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~5884 lines of test source are present (.scala) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .scala suite was found but not re-run
- D12 Dependency Hygiene — Not scored — 2 direct sbt declaration(s) were read, but the outdated signal needs repo1.maven.org, and no declaration here states an exact version to ask about, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- D14 License Compliance — Not scored — this repository's 2 pinned sbt dependency coordinate(s) were read from its 1 sbt build file(s), but Maven Central could not be asked for the licence of 0 of them (no diagnostic), and a licence verdict over part of a dependency graph is not a licence verdict. Nothing is asserted about this repository's licensing in either direction.
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D19 Documentation Quality — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
- D20 ADR Quality — Repository kind not determined
- D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 1 candidate(s) found and not reported.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .scala source were not judged.
- 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 (.scala), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 6 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- 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 — applicable but not scored (1 of 2 signals for this style — below the bar we score at): 56 value object(s)
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- M4 Documentation accuracy — Not applicable: the 13 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 JVM, JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — No web surface: 151 Scala 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 artifact (akka-http, pekko-http, http4s, Play, Finagle, zio-http, cask, Scalatra, a tapir server, Jetty, Undertow, …) outside test scope in its build, and no server package imported or server bound in its production source — so HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library or worker. If this codebase starts serving HTTP, the dimension reactivates automatically.
- X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X16 Unfloored truncation loop — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no C# was loaded; this repository's Scala was read, and no request in it can be cancelled by a caller — a Scala request takes no token: a Future cannot be cancelled, and cats-effect, ZIO and Monix interrupt the fiber that made the request from outside the call, not through a parameter
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X3 Exception handling — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Scala was read, and it logs through none that an interpolated message defeats: scala-logging takes an `s"…"` message apart into SLF4J's pattern and arguments at compile time, and log4s, grizzled-slf4j, Play's Logger, Akka's LoggingAdapter, sbt's Logger and Spark's Logging take one finished message (as log4net does in C#). Calls made straight through SLF4J (`org.slf4j.Logger`) would be judged.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 26 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 — 35 finding(s)
- Edited copies of one member (3 members, 5+ corresponding lines) core/shared/src/main/scala/monocle/function/Cons1.scala:76
- Edited copies of one member (3 members, 5+ corresponding lines) core/shared/src/main/scala/monocle/function/Snoc1.scala:76
- Edited copies of one member (3 members, 5+ corresponding lines) core/shared/src/main/scala/monocle/function/Each.scala:113
- Edited copies of one member (3 members, 5+ corresponding lines) core/shared/src/main/scala/monocle/function/Reverse.scala:68
- Edited copies of one member (3 members, 5+ corresponding lines) core/shared/src/main/scala/monocle/Iso.scala:84
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (8 corresponding lines) core/shared/src/main/scala/monocle/function/Each.scala:61
- Edited copy of a member (8 corresponding lines) core/shared/src/main/scala-3/monocle/internal/focus/features/some/SomeParser.scala:11
- Edited copy of a member (7 corresponding lines) core/shared/src/main/scala-3/monocle/internal/focus/features/at/AtGenerator.scala:11
- Edited copy of a member (7 corresponding lines) core/shared/src/main/scala-3/monocle/internal/focus/features/as/AsGenerator.scala:11
- Edited copy of a member (5 corresponding lines) core/shared/src/main/scala/monocle/Iso.scala:76
- Edited copy of a member (5 corresponding lines) core/shared/src/main/scala/monocle/Iso.scala:92
- LensesImpl.annotationMacro (cognitive 24) macro/src/main/scala-2/monocle/macros/Lenses.scala:24
- REDACTED
- REDACTED
- Edited copy of a member (16 corresponding lines) core/shared/src/main/scala/monocle/Optional.scala:164
- Edited copy of a member (18 corresponding lines) core/shared/src/main/scala-3/monocle/internal/focus/features/selectfield/SelectFieldGenerator.scala:12
- Edited copies of one member (3 members, 11+ corresponding lines) core/shared/src/main/scala/monocle/function/FilterIndex.scala:64
- Edited copy of a member (6 corresponding lines) core/shared/src/main/scala/monocle/function/Plated.scala:157
- Edited copies of one member (4 members, 4+ corresponding lines) core/shared/src/main/scala/monocle/Traversal.scala:112
- Edited copies of one member (3 members, 12+ corresponding lines) macro/src/main/scala-2/monocle/macros/syntax/AppliedFocusSyntax.scala:21
- Edited copies of one member (3 members, 15+ corresponding lines) core/shared/src/main/scala-3/monocle/internal/focus/features/at/AtParser.scala:11
- Edited copy of a member (4 corresponding lines) core/shared/src/main/scala/monocle/law/OptionalLaws.scala:33
- Edited copies of one member (6 members, 3+ corresponding lines) core/shared/src/main/scala/monocle/function/Field1.scala:67
- Edited copy of a member (1 corresponding lines) core/shared/src/main/scala/monocle/law/IsoLaws.scala:31
- Duplicated block (5 lines × 2) core/shared/src/main/scala-3/monocle/internal/focus/features/selectfield/SelectFieldGenerator.scala:25
- Duplicated block (7 lines × 2) core/shared/src/main/scala/monocle/function/FilterIndex.scala:68
- Edited copies of one member (3 members, 9+ corresponding lines) bench/src/main/scala/monocle/bench/StdLensBench.scala:22
- Duplicated block (12 lines × 2) bench/src/main/scala/monocle/bench/MonocleLensBench.scala:27
- Duplicated block (6 lines × 3) bench/src/main/scala/monocle/bench/StdLensBench.scala:23
- Off the main sequence: core
- No structured logging
- JavaScript dependencies are not locked website/package.json:12
Minor — 19 finding(s)
- Orphaned file generic/src/main/scala-2/monocle/generic/CoProduct.scala:1
- Orphaned file state/src/main/scala/monocle/state/StateTraversalSyntax.scala:1
- Orphaned file bench/src/main/scala/monocle/bench/ProductIsoBench.scala:1
- Orphaned file state/src/main/scala/monocle/state/StateOptionalSyntax.scala:1
- Orphaned file core/shared/src/main/scala-3/monocle/internal/focus/features/KeywordParserBase.scala:1
- Off-boarding risk: anonymized user #1
- Projects may be oversized for their cohesion
- Orphaned files with no living knowledge
- REDACTED
- REDACTED
- REDACTED
- Blanket warning suppression generic/src/main/scala-2/monocle/generic/CoProduct.scala:13
- Thin README README.md:1
- No ADRs
- No architecture diagram/doc
- No SAST REDACTED:11
- No dependency-update automation website/package.json:12
- Benchmarks don't track allocations bench/src/main/scala/monocle/bench/MonocleIsoBench.scala
- Scala's null is not held to the type system everywhere
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-5381ccf2e30444228f2053da203826b2/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-5381ccf2e30444228f2053da203826b2/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 26 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 6 file(s) — `core/shared/src/main/scala-3/monocle/Focus.scala`, `core/shared/src/main/scala-3/monocle/internal/IsoFields.scala`, `core/shared/src/main/scala-3/monocle/syntax/AppliedFocusSyntax.scala`, `core/shared/src/main/scala-3/monocle/syntax/ComposedFocusSyntax.scala`, `core/shared/src/main/scala-3/monocle/syntax/MacroSyntax.scala`, … (+1 more) — so the PII/GDPR sweep did not cover them at all. | 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 | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |