Executive summary
milessabin/shapeless falls short of our standard for production, in part because we found no recorded design decisions and no architecture document or diagram. It scores 56 out of 100 and is rated Adequate, and all nine of its critical findings are security problems in the build pipeline.
Maturity, at 48, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 7 points. Having someone learn and document the 19 files no active contributor knows is another step, worth about 6 points. Raising Maturity to 70 would lift the score to about 61.
Seven pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One pipeline step runs a download nobody checks. Pinning each tool to an exact version and checking the download against a checksum would close both risks. Correcting the flagged pipeline settings would fix the weakness in the build pipeline's configuration.
The product code is 20,743 lines, about €38,000 to rebuild.
If Maturity rose from 48 to 70, the lowest score rated Strong, the score would rise from 56 to about 61.
New since the last survey: 1 finding
- Supply-chain Provenance & Signing · REDACTED
Fixed since the last survey: 1 finding
- Supply-chain Provenance & Signing REDACTED
Rebuild cost: about €38,000 · Estimate
| Cost to rebuild | €13,000 to €63,000, for 208 to 661 hours of work, about 0.3 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 56. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 20,743 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 shapeless.CaseClassMacros | 2 shapeless.LP1 | 3 shapeless.LabelledProductTypeClassCompanion | 4 shapeless.Lazy | 5 shapeless.ProductISOFacet | 6 shapeless.~?> | 7 shapeless.ApplyUnapplyFacet | 8 shapeless.CopyFacet | 9 shapeless.FieldPoly | 10 shapeless.LazyMacros | 11 shapeless.Poly | 12 shapeless.PolymorphicEqualityFacet | 13 shapeless.ProductFacet | 14 shapeless.labelled | 15 shapeless.ops.adjoin | 16 shapeless.ops.nat | 17 shapeless.ops.zipper | 18 shapeless.ToStringFacet | 19 shapeless.ops.coproduct | 20 shapeless.Coproduct | 21 shapeless.DefaultCaseClassDefns | 22 shapeless.ops.coproduct.LiftAll | 23 shapeless.PolyDefns | 24 shapeless.ops.hlist | 25 shapeless.HList | 26 shapeless.ops.record | 27 shapeless.syntax | 28 shapeless | 29 (global) | 30 shapeless.Default | 31 shapeless.Default.AsOptions | 32 shapeless.Default.AsRecord | 33 shapeless.Zipper | 34 shapeless.ops.function | 35 shapeless.ops.product | 36 shapeless.ops.tuple | 37 shapeless.ops.union | 38 shapeless.syntax.HListOps | 39 shapeless.ops | 40 shapeless.syntax.std |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 shapeless.CaseClassMacros | ||||||||||||||||||||||||||||||||||||||||
| 2 shapeless.LP1 | ||||||||||||||||||||||||||||||||||||||||
| 3 shapeless.LabelledProductTypeClassCompanion | ||||||||||||||||||||||||||||||||||||||||
| 4 shapeless.Lazy | ||||||||||||||||||||||||||||||||||||||||
| 5 shapeless.ProductISOFacet | ||||||||||||||||||||||||||||||||||||||||
| 6 shapeless.~?> | ||||||||||||||||||||||||||||||||||||||||
| 7 shapeless.ApplyUnapplyFacet | 1 | |||||||||||||||||||||||||||||||||||||||
| 8 shapeless.CopyFacet | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 shapeless.FieldPoly | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 shapeless.LazyMacros | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 shapeless.Poly | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 shapeless.PolymorphicEqualityFacet | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 13 shapeless.ProductFacet | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 shapeless.labelled | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 shapeless.ops.adjoin | 3 | |||||||||||||||||||||||||||||||||||||||
| 16 shapeless.ops.nat | 3 | |||||||||||||||||||||||||||||||||||||||
| 17 shapeless.ops.zipper | 17 | |||||||||||||||||||||||||||||||||||||||
| 18 shapeless.ToStringFacet | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 shapeless.ops.coproduct | 1 | 42 | ||||||||||||||||||||||||||||||||||||||
| 20 shapeless.Coproduct | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 shapeless.DefaultCaseClassDefns | 2 | 2 | 2 | 2 | 2 | |||||||||||||||||||||||||||||||||||
| 22 shapeless.ops.coproduct.LiftAll | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 shapeless.PolyDefns | 1 | 10 | ||||||||||||||||||||||||||||||||||||||
| 24 shapeless.ops.hlist | 2 | 2 | 3 | 4 | 100 | |||||||||||||||||||||||||||||||||||
| 25 shapeless.HList | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 shapeless.ops.record | 1 | 1 | 1 | 34 | ||||||||||||||||||||||||||||||||||||
| 27 shapeless.syntax | 2 | 2 | 1 | 2 | 2 | 53 | 49 | 14 | 16 | |||||||||||||||||||||||||||||||
| 28 shapeless | 1 | 2 | 1 | 2 | 1 | 1 | 1 | 2 | 1 | 1 | 1 | 6 | 14 | 1 | 2 | 1 | 4 | 2 | ||||||||||||||||||||||
| 29 (global) | 4 | |||||||||||||||||||||||||||||||||||||||
| 30 shapeless.Default | 2 | |||||||||||||||||||||||||||||||||||||||
| 31 shapeless.Default.AsOptions | 1 | |||||||||||||||||||||||||||||||||||||||
| 32 shapeless.Default.AsRecord | 1 | |||||||||||||||||||||||||||||||||||||||
| 33 shapeless.Zipper | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 34 shapeless.ops.function | 1 | |||||||||||||||||||||||||||||||||||||||
| 35 shapeless.ops.product | 7 | |||||||||||||||||||||||||||||||||||||||
| 36 shapeless.ops.tuple | 52 | |||||||||||||||||||||||||||||||||||||||
| 37 shapeless.ops.union | 1 | 1 | 1 | 6 | ||||||||||||||||||||||||||||||||||||
| 38 shapeless.syntax.HListOps | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 39 shapeless.ops | 3 | 2 | ||||||||||||||||||||||||||||||||||||||
| 40 shapeless.syntax.std | 1 | 1 | 20 | 33 | 1 | 7 | 1 | 1 | 1 |
7→5 shapeless.ApplyUnapplyFacet uses shapeless.ProductISOFacet✕
- Connections
- 1 pair of types, where a type in shapeless.ApplyUnapplyFacet uses a type in shapeless.ProductISOFacet.
- The types involved
shapeless.ApplyUnapplyFacet.ApplyUnapplyOps→shapeless.ProductISOFacet.ProductISOOps
- Direction
- shapeless.ApplyUnapplyFacet uses shapeless.ProductISOFacet, so a change to shapeless.ProductISOFacet can break shapeless.ApplyUnapplyFacet, while a change to shapeless.ApplyUnapplyFacet can't break shapeless.ProductISOFacet.
- Position
- Below the diagonal: shapeless.ApplyUnapplyFacet uses a module listed above it, which is the healthy direction.
8→28 shapeless.CopyFacet uses shapeless part of a loop✕
- Connections
- 1 pair of types, where a type in shapeless.CopyFacet uses a type in shapeless.
- The types involved
shapeless.CopyFacet.CopyMethods→shapeless.RecordArgs
- Direction
- shapeless.CopyFacet uses shapeless, so a change to shapeless can break shapeless.CopyFacet, while a change to shapeless.CopyFacet can't break shapeless.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→1 shapeless.FieldPoly uses shapeless.CaseClassMacros✕
- Connections
- 1 pair of types, where a type in shapeless.FieldPoly uses a type in shapeless.CaseClassMacros.
- The types involved
shapeless.FieldPoly.FieldCaseBuilder→shapeless.CaseClassMacros.FieldType
- Direction
- shapeless.FieldPoly uses shapeless.CaseClassMacros, so a change to shapeless.CaseClassMacros can break shapeless.FieldPoly, while a change to shapeless.FieldPoly can't break shapeless.CaseClassMacros.
- Position
- Below the diagonal: shapeless.FieldPoly uses a module listed above it, which is the healthy direction.
10→3 shapeless.LazyMacros uses shapeless.LabelledProductTypeClassCompanion✕
- Connections
- 1 pair of types, where a type in shapeless.LazyMacros uses a type in shapeless.LabelledProductTypeClassCompanion.
- The types involved
shapeless.LazyMacros.DerivationContext→shapeless.LabelledProductTypeClassCompanion.Instance
- Direction
- shapeless.LazyMacros uses shapeless.LabelledProductTypeClassCompanion, so a change to shapeless.LabelledProductTypeClassCompanion can break shapeless.LazyMacros, while a change to shapeless.LazyMacros can't break shapeless.LabelledProductTypeClassCompanion.
- Position
- Below the diagonal: shapeless.LazyMacros uses a module listed above it, which is the healthy direction.
11→28 shapeless.Poly uses shapeless part of a loop✕
- Connections
- 1 pair of types, where a type in shapeless.Poly uses a type in shapeless.
- The types involved
shapeless.Poly.LowPriorityCaseBuilder→shapeless.HNil
- Direction
- shapeless.Poly uses shapeless, so a change to shapeless can break shapeless.Poly, while a change to shapeless.Poly can't break shapeless.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→5 shapeless.PolymorphicEqualityFacet uses shapeless.ProductISOFacet✕
- Connections
- 1 pair of types, where a type in shapeless.PolymorphicEqualityFacet uses a type in shapeless.ProductISOFacet.
- The types involved
shapeless.PolymorphicEqualityFacet.PolymorphicEqualityOps→shapeless.ProductISOFacet.ProductISOOps
- Direction
- shapeless.PolymorphicEqualityFacet uses shapeless.ProductISOFacet, so a change to shapeless.ProductISOFacet can break shapeless.PolymorphicEqualityFacet, while a change to shapeless.PolymorphicEqualityFacet can't break shapeless.ProductISOFacet.
- Position
- Below the diagonal: shapeless.PolymorphicEqualityFacet uses a module listed above it, which is the healthy direction.
12→28 shapeless.PolymorphicEqualityFacet uses shapeless part of a loop✕
- Connections
- 1 pair of types, where a type in shapeless.PolymorphicEqualityFacet uses a type in shapeless.
- The types involved
shapeless.PolymorphicEqualityFacet.PolymorphicEqualityOps→shapeless.Typeable
- Direction
- shapeless.PolymorphicEqualityFacet uses shapeless, so a change to shapeless can break shapeless.PolymorphicEqualityFacet, while a change to shapeless.PolymorphicEqualityFacet can't break shapeless.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→5 shapeless.ProductFacet uses shapeless.ProductISOFacet✕
- Connections
- 1 pair of types, where a type in shapeless.ProductFacet uses a type in shapeless.ProductISOFacet.
- The types involved
shapeless.ProductFacet.ProductOps→shapeless.ProductISOFacet.ProductISOOps
- Direction
- shapeless.ProductFacet uses shapeless.ProductISOFacet, so a change to shapeless.ProductISOFacet can break shapeless.ProductFacet, while a change to shapeless.ProductFacet can't break shapeless.ProductISOFacet.
- Position
- Below the diagonal: shapeless.ProductFacet uses a module listed above it, which is the healthy direction.
14→1 shapeless.labelled uses shapeless.CaseClassMacros✕
- Connections
- 1 pair of types, where a type in shapeless.labelled uses a type in shapeless.CaseClassMacros.
- The types involved
shapeless.labelled.FieldBuilder→shapeless.CaseClassMacros.FieldType
- Direction
- shapeless.labelled uses shapeless.CaseClassMacros, so a change to shapeless.CaseClassMacros can break shapeless.labelled, while a change to shapeless.labelled can't break shapeless.CaseClassMacros.
- Position
- Below the diagonal: shapeless.labelled uses a module listed above it, which is the healthy direction.
15→28 shapeless.ops.adjoin uses shapeless part of a loop✕
- Connections
- 3 pairs of types, where a type in shapeless.ops.adjoin uses a type in shapeless.
- The types involved
shapeless.ops.adjoin.Adjoin→shapeless.DepFn1shapeless.ops.adjoin.LowPriorityAdjoin→shapeless.:+:shapeless.ops.adjoin.LowPriorityAdjoin→shapeless.::
- Direction
- shapeless.ops.adjoin uses shapeless, so a change to shapeless can break shapeless.ops.adjoin, while a change to shapeless.ops.adjoin can't break shapeless.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→28 shapeless.ops.nat uses shapeless part of a loop✕
- Connections
- 3 pairs of types, where a type in shapeless.ops.nat uses a type in shapeless.
- The types involved
shapeless.ops.nat.BoundedRange→shapeless.DepFn0shapeless.ops.nat.Range→shapeless.DepFn0shapeless.ops.nat.ToIntMacros→shapeless.CaseClassMacros
- Direction
- shapeless.ops.nat uses shapeless, so a change to shapeless can break shapeless.ops.nat, while a change to shapeless.ops.nat can't break shapeless.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→28 shapeless.ops.zipper uses shapeless part of a loop✕
- Connections
- 17 pairs of types, where a type in shapeless.ops.zipper uses a type in shapeless.
- The types involved
shapeless.ops.zipper.Delete→shapeless.DepFn1shapeless.ops.zipper.Down→shapeless.DepFn1shapeless.ops.zipper.First→shapeless.DepFn1shapeless.ops.zipper.Get→shapeless.DepFn1shapeless.ops.zipper.Insert→shapeless.DepFn2shapeless.ops.zipper.Last→shapeless.DepFn1shapeless.ops.zipper.Left→shapeless.DepFn1shapeless.ops.zipper.LeftBy→shapeless.DepFn1shapeless.ops.zipper.LeftTo→shapeless.DepFn1shapeless.ops.zipper.Modify→shapeless.DepFn2shapeless.ops.zipper.Put→shapeless.DepFn2shapeless.ops.zipper.Reify→shapeless.DepFn1shapeless.ops.zipper.Right→shapeless.DepFn1shapeless.ops.zipper.RightBy→shapeless.DepFn1shapeless.ops.zipper.RightTo→shapeless.DepFn1shapeless.ops.zipper.Root→shapeless.DepFn1shapeless.ops.zipper.Up→shapeless.DepFn1
- Direction
- shapeless.ops.zipper uses shapeless, so a change to shapeless can break shapeless.ops.zipper, while a change to shapeless.ops.zipper can't break shapeless.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→13 shapeless.ToStringFacet uses shapeless.ProductFacet✕
- Connections
- 1 pair of types, where a type in shapeless.ToStringFacet uses a type in shapeless.ProductFacet.
- The types involved
shapeless.ToStringFacet.ToStringOps→shapeless.ProductFacet.ProductOps
- Direction
- shapeless.ToStringFacet uses shapeless.ProductFacet, so a change to shapeless.ProductFacet can break shapeless.ToStringFacet, while a change to shapeless.ToStringFacet can't break shapeless.ProductFacet.
- Position
- Below the diagonal: shapeless.ToStringFacet uses a module listed above it, which is the healthy direction.
19→16 shapeless.ops.coproduct uses shapeless.ops.nat✕
- Connections
- 1 pair of types, where a type in shapeless.ops.coproduct uses a type in shapeless.ops.nat.
- The types involved
shapeless.ops.coproduct.IndexOf→shapeless.ops.nat.ToInt
- Direction
- shapeless.ops.coproduct uses shapeless.ops.nat, so a change to shapeless.ops.nat can break shapeless.ops.coproduct, while a change to shapeless.ops.coproduct can't break shapeless.ops.nat.
- Position
- Below the diagonal: shapeless.ops.coproduct uses a module listed above it, which is the healthy direction.
19→28 shapeless.ops.coproduct uses shapeless part of a loop✕
- Connections
- 42 pairs of types, where a type in shapeless.ops.coproduct uses a type in shapeless. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
shapeless.ops.coproduct.At→shapeless.DepFn1shapeless.ops.coproduct.Basis→shapeless.DepFn1shapeless.ops.coproduct.CoproductToEither→shapeless.DepFn1shapeless.ops.coproduct.Drop→shapeless.DepFn1shapeless.ops.coproduct.EitherToCoproduct→shapeless.DepFn1shapeless.ops.coproduct.EitherToCoproductLowPrio→shapeless.:+:shapeless.ops.coproduct.ExtendLeftBy→shapeless.DepFn1shapeless.ops.coproduct.ExtendRight→shapeless.DepFn1shapeless.ops.coproduct.ExtendRightBy→shapeless.DepFn1shapeless.ops.coproduct.Filter→shapeless.DepFn1shapeless.ops.coproduct.FilterNot→shapeless.DepFn1shapeless.ops.coproduct.FlatMap→shapeless.DepFn1shapeless.ops.coproduct.Folder→shapeless.DepFn1shapeless.ops.coproduct.IndexOf→shapeless.DepFn0shapeless.ops.coproduct.LeftFolder→shapeless.DepFn2shapeless.ops.coproduct.Length→shapeless.DepFn0shapeless.ops.coproduct.LowPriorityPrepend→shapeless.CNilshapeless.ops.coproduct.LowPriorityRemove→shapeless.:+:shapeless.ops.coproduct.LowPriorityRemoveLast→shapeless.:+:shapeless.ops.coproduct.LowestPriorityPrepend→shapeless.:+:shapeless.ops.coproduct.Mapper→shapeless.DepFn1shapeless.ops.coproduct.Partition→shapeless.:+:shapeless.ops.coproduct.Partition→shapeless.DepFn1shapeless.ops.coproduct.Prepend→shapeless.DepFn1shapeless.ops.coproduct.Reify→shapeless.DepFn0
- Direction
- shapeless.ops.coproduct uses shapeless, so a change to shapeless can break shapeless.ops.coproduct, while a change to shapeless.ops.coproduct can't break shapeless.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→19 shapeless.Coproduct uses shapeless.ops.coproduct✕
- Connections
- 1 pair of types, where a type in shapeless.Coproduct uses a type in shapeless.ops.coproduct.
- The types involved
shapeless.Coproduct.MkCoproduct→shapeless.ops.coproduct.Inject
- Direction
- shapeless.Coproduct uses shapeless.ops.coproduct, so a change to shapeless.ops.coproduct can break shapeless.Coproduct, while a change to shapeless.Coproduct can't break shapeless.ops.coproduct.
- Position
- Below the diagonal: shapeless.Coproduct uses a module listed above it, which is the healthy direction.
21→7 shapeless.DefaultCaseClassDefns uses shapeless.ApplyUnapplyFacet✕
- Connections
- 2 pairs of types, where a type in shapeless.DefaultCaseClassDefns uses a type in shapeless.ApplyUnapplyFacet.
- The types involved
shapeless.DefaultCaseClassDefns.CaseClassCompanion→shapeless.ApplyUnapplyFacet.ApplyUnapplyCompanionshapeless.DefaultCaseClassDefns.CaseClassOps→shapeless.ApplyUnapplyFacet.ApplyUnapplyOps
- Direction
- shapeless.DefaultCaseClassDefns uses shapeless.ApplyUnapplyFacet, so a change to shapeless.ApplyUnapplyFacet can break shapeless.DefaultCaseClassDefns, while a change to shapeless.DefaultCaseClassDefns can't break shapeless.ApplyUnapplyFacet.
- Position
- Below the diagonal: shapeless.DefaultCaseClassDefns uses a module listed above it, which is the healthy direction.
21→8 shapeless.DefaultCaseClassDefns uses shapeless.CopyFacet✕
- Connections
- 2 pairs of types, where a type in shapeless.DefaultCaseClassDefns uses a type in shapeless.CopyFacet.
- The types involved
shapeless.DefaultCaseClassDefns.CaseClass→shapeless.CopyFacet.CopyMethodsshapeless.DefaultCaseClassDefns.CaseClassOps→shapeless.CopyFacet.CopyOps
- Direction
- shapeless.DefaultCaseClassDefns uses shapeless.CopyFacet, so a change to shapeless.CopyFacet can break shapeless.DefaultCaseClassDefns, while a change to shapeless.DefaultCaseClassDefns can't break shapeless.CopyFacet.
- Position
- Below the diagonal: shapeless.DefaultCaseClassDefns uses a module listed above it, which is the healthy direction.
21→12 shapeless.DefaultCaseClassDefns uses shapeless.PolymorphicEqualityFacet✕
- Connections
- 2 pairs of types, where a type in shapeless.DefaultCaseClassDefns uses a type in shapeless.PolymorphicEqualityFacet.
- The types involved
shapeless.DefaultCaseClassDefns.CaseClass→shapeless.PolymorphicEqualityFacet.PolymorphicEqualityMethodsshapeless.DefaultCaseClassDefns.CaseClassOps→shapeless.PolymorphicEqualityFacet.PolymorphicEqualityOps
- Direction
- shapeless.DefaultCaseClassDefns uses shapeless.PolymorphicEqualityFacet, so a change to shapeless.PolymorphicEqualityFacet can break shapeless.DefaultCaseClassDefns, while a change to shapeless.DefaultCaseClassDefns can't break shapeless.PolymorphicEqualityFacet.
- Position
- Below the diagonal: shapeless.DefaultCaseClassDefns uses a module listed above it, which is the healthy direction.
21→13 shapeless.DefaultCaseClassDefns uses shapeless.ProductFacet✕
- Connections
- 2 pairs of types, where a type in shapeless.DefaultCaseClassDefns uses a type in shapeless.ProductFacet.
- The types involved
shapeless.DefaultCaseClassDefns.CaseClass→shapeless.ProductFacet.ProductMethodsshapeless.DefaultCaseClassDefns.CaseClassOps→shapeless.ProductFacet.ProductOps
- Direction
- shapeless.DefaultCaseClassDefns uses shapeless.ProductFacet, so a change to shapeless.ProductFacet can break shapeless.DefaultCaseClassDefns, while a change to shapeless.DefaultCaseClassDefns can't break shapeless.ProductFacet.
- Position
- Below the diagonal: shapeless.DefaultCaseClassDefns uses a module listed above it, which is the healthy direction.
21→18 shapeless.DefaultCaseClassDefns uses shapeless.ToStringFacet✕
- Connections
- 2 pairs of types, where a type in shapeless.DefaultCaseClassDefns uses a type in shapeless.ToStringFacet.
- The types involved
shapeless.DefaultCaseClassDefns.CaseClass→shapeless.ToStringFacet.ToStringMethodsshapeless.DefaultCaseClassDefns.CaseClassOps→shapeless.ToStringFacet.ToStringOps
- Direction
- shapeless.DefaultCaseClassDefns uses shapeless.ToStringFacet, so a change to shapeless.ToStringFacet can break shapeless.DefaultCaseClassDefns, while a change to shapeless.DefaultCaseClassDefns can't break shapeless.ToStringFacet.
- Position
- Below the diagonal: shapeless.DefaultCaseClassDefns uses a module listed above it, which is the healthy direction.
22→19 shapeless.ops.coproduct.LiftAll uses shapeless.ops.coproduct✕
- Connections
- 1 pair of types, where a type in shapeless.ops.coproduct.LiftAll uses a type in shapeless.ops.coproduct.
- The types involved
shapeless.ops.coproduct.LiftAll.Curried→shapeless.ops.coproduct.LiftAll
- Direction
- shapeless.ops.coproduct.LiftAll uses shapeless.ops.coproduct, so a change to shapeless.ops.coproduct can break shapeless.ops.coproduct.LiftAll, while a change to shapeless.ops.coproduct.LiftAll can't break shapeless.ops.coproduct.
- Position
- Below the diagonal: shapeless.ops.coproduct.LiftAll uses a module listed above it, which is the healthy direction.
23→22 shapeless.PolyDefns uses shapeless.ops.coproduct.LiftAll✕
- Connections
- 1 pair of types, where a type in shapeless.PolyDefns uses a type in shapeless.ops.coproduct.LiftAll.
- The types involved
shapeless.PolyDefns.LowPriorityCurried→shapeless.ops.coproduct.LiftAll.Curried
- Direction
- shapeless.PolyDefns uses shapeless.ops.coproduct.LiftAll, so a change to shapeless.ops.coproduct.LiftAll can break shapeless.PolyDefns, while a change to shapeless.PolyDefns can't break shapeless.ops.coproduct.LiftAll.
- Position
- Below the diagonal: shapeless.PolyDefns uses a module listed above it, which is the healthy direction.
23→28 shapeless.PolyDefns uses shapeless part of a loop✕
- Connections
- 10 pairs of types, where a type in shapeless.PolyDefns uses a type in shapeless.
- The types involved
shapeless.PolyDefns.>->→shapeless.::shapeless.PolyDefns.BindFirst→shapeless.Polyshapeless.PolyDefns.Compose→shapeless.Polyshapeless.PolyDefns.LiftU→shapeless.::shapeless.PolyDefns.LowPriorityCurried→shapeless.::shapeless.PolyDefns.LowPriorityLiftFunction1→shapeless.HNilshapeless.PolyDefns.LowPriorityLiftU→shapeless.HNilshapeless.PolyDefns.LowPriorityLiftU→shapeless.Polyshapeless.PolyDefns.RotateLeft→shapeless.Polyshapeless.PolyDefns.RotateRight→shapeless.Poly
- Direction
- shapeless.PolyDefns uses shapeless, so a change to shapeless can break shapeless.PolyDefns, while a change to shapeless.PolyDefns can't break shapeless.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→6 shapeless.ops.hlist uses shapeless.~?>✕
- Connections
- 2 pairs of types, where a type in shapeless.ops.hlist uses a type in shapeless.~?>.
- The types involved
shapeless.ops.hlist.HKernel→shapeless.~?>.λshapeless.ops.hlist.LowPriorityMapped→shapeless.~?>.λ
- Direction
- shapeless.ops.hlist uses shapeless.~?>, so a change to shapeless.~?> can break shapeless.ops.hlist, while a change to shapeless.ops.hlist can't break shapeless.~?>.
- Position
- Below the diagonal: shapeless.ops.hlist uses a module listed above it, which is the healthy direction.
24→16 shapeless.ops.hlist uses shapeless.ops.nat✕
- Connections
- 2 pairs of types, where a type in shapeless.ops.hlist uses a type in shapeless.ops.nat.
- The types involved
shapeless.ops.hlist.LowPriorityCollect→shapeless.ops.nat.LTshapeless.ops.hlist.LowPriorityToCoproductTraversable→shapeless.ops.nat.LT
- Direction
- shapeless.ops.hlist uses shapeless.ops.nat, so a change to shapeless.ops.nat can break shapeless.ops.hlist, while a change to shapeless.ops.hlist can't break shapeless.ops.nat.
- Position
- Below the diagonal: shapeless.ops.hlist uses a module listed above it, which is the healthy direction.
24→19 shapeless.ops.hlist uses shapeless.ops.coproduct✕
- Connections
- 3 pairs of types, where a type in shapeless.ops.hlist uses a type in shapeless.ops.coproduct.
- The types involved
shapeless.ops.hlist.LowPriorityPrepend→shapeless.ops.coproduct.LowestPriorityPrependshapeless.ops.hlist.LowPriorityReversePrepend→shapeless.ops.coproduct.Reverseshapeless.ops.hlist.LowPriorityToCoproductTraversable→shapeless.ops.coproduct.Inject
- Direction
- shapeless.ops.hlist uses shapeless.ops.coproduct, so a change to shapeless.ops.coproduct can break shapeless.ops.hlist, while a change to shapeless.ops.hlist can't break shapeless.ops.coproduct.
- Position
- Below the diagonal: shapeless.ops.hlist uses a module listed above it, which is the healthy direction.
24→23 shapeless.ops.hlist uses shapeless.PolyDefns✕
- Connections
- 4 pairs of types, where a type in shapeless.ops.hlist uses a type in shapeless.PolyDefns.
- The types involved
shapeless.ops.hlist.HConsHKernel→shapeless.PolyDefns.~>shapeless.ops.hlist.HKernel→shapeless.PolyDefns.~>shapeless.ops.hlist.HNilHKernel→shapeless.PolyDefns.~>shapeless.ops.hlist.NatTRel→shapeless.PolyDefns.~>
- Direction
- shapeless.ops.hlist uses shapeless.PolyDefns, so a change to shapeless.PolyDefns can break shapeless.ops.hlist, while a change to shapeless.ops.hlist can't break shapeless.PolyDefns.
- Position
- Below the diagonal: shapeless.ops.hlist uses a module listed above it, which is the healthy direction.
24→28 shapeless.ops.hlist uses shapeless part of a loop✕
- Connections
- 100 pairs of types, where a type in shapeless.ops.hlist uses a type in shapeless. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
shapeless.ops.hlist.At→shapeless.DepFn1shapeless.ops.hlist.Collect→shapeless.DepFn1shapeless.ops.hlist.CollectFirst→shapeless.DepFn1shapeless.ops.hlist.Combinations→shapeless.DepFn1shapeless.ops.hlist.ConstMapper→shapeless.DepFn2shapeless.ops.hlist.Diff→shapeless.DepFn1shapeless.ops.hlist.Drop→shapeless.DepFn1shapeless.ops.hlist.Fill→shapeless.DepFn1shapeless.ops.hlist.FillWith→shapeless.DepFn0shapeless.ops.hlist.Filter→shapeless.DepFn1shapeless.ops.hlist.FilterNot→shapeless.DepFn1shapeless.ops.hlist.FlatMapInterleave→shapeless.DepFn2shapeless.ops.hlist.FlatMapper→shapeless.DepFn1shapeless.ops.hlist.Grouper→shapeless.DepFn1shapeless.ops.hlist.HConsHKernel→shapeless.::shapeless.ops.hlist.HKernelAux→shapeless.DepFn0shapeless.ops.hlist.HListToProduct→shapeless.DepFn1shapeless.ops.hlist.HNilHKernel→shapeless.HNilshapeless.ops.hlist.Init→shapeless.DepFn1shapeless.ops.hlist.Interleave→shapeless.DepFn2shapeless.ops.hlist.Intersection→shapeless.DepFn1shapeless.ops.hlist.Last→shapeless.DepFn1shapeless.ops.hlist.LeftFolder→shapeless.DepFn2shapeless.ops.hlist.LeftReducer→shapeless.DepFn1shapeless.ops.hlist.LeftScanner→shapeless.DepFn2
- Direction
- shapeless.ops.hlist uses shapeless, so a change to shapeless can break shapeless.ops.hlist, while a change to shapeless.ops.hlist can't break shapeless.
- 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→24 shapeless.HList uses shapeless.ops.hlist✕
- Connections
- 1 pair of types, where a type in shapeless.HList uses a type in shapeless.ops.hlist.
- The types involved
shapeless.HList.FillWithOps→shapeless.ops.hlist.FillWith
- Direction
- shapeless.HList uses shapeless.ops.hlist, so a change to shapeless.ops.hlist can break shapeless.HList, while a change to shapeless.HList can't break shapeless.ops.hlist.
- Position
- Below the diagonal: shapeless.HList uses a module listed above it, which is the healthy direction.
26→4 shapeless.ops.record uses shapeless.Lazy✕
- Connections
- 1 pair of types, where a type in shapeless.ops.record uses a type in shapeless.Lazy.
- The types involved
shapeless.ops.record.UnzipFields→shapeless.Lazy.Values
- Direction
- shapeless.ops.record uses shapeless.Lazy, so a change to shapeless.Lazy can break shapeless.ops.record, while a change to shapeless.ops.record can't break shapeless.Lazy.
- Position
- Below the diagonal: shapeless.ops.record uses a module listed above it, which is the healthy direction.
26→19 shapeless.ops.record uses shapeless.ops.coproduct✕
- Connections
- 1 pair of types, where a type in shapeless.ops.record uses a type in shapeless.ops.coproduct.
- The types involved
shapeless.ops.record.UnsafeSelector→shapeless.ops.coproduct.Selector
- Direction
- shapeless.ops.record uses shapeless.ops.coproduct, so a change to shapeless.ops.coproduct can break shapeless.ops.record, while a change to shapeless.ops.record can't break shapeless.ops.coproduct.
- Position
- Below the diagonal: shapeless.ops.record uses a module listed above it, which is the healthy direction.
26→24 shapeless.ops.record uses shapeless.ops.hlist✕
- Connections
- 1 pair of types, where a type in shapeless.ops.record uses a type in shapeless.ops.hlist.
- The types involved
shapeless.ops.record.UnsafeModifier→shapeless.ops.hlist.Modifier
- Direction
- shapeless.ops.record uses shapeless.ops.hlist, so a change to shapeless.ops.hlist can break shapeless.ops.record, while a change to shapeless.ops.record can't break shapeless.ops.hlist.
- Position
- Below the diagonal: shapeless.ops.record uses a module listed above it, which is the healthy direction.
26→28 shapeless.ops.record uses shapeless part of a loop✕
- Connections
- 34 pairs of types, where a type in shapeless.ops.record uses a type in shapeless. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
shapeless.ops.record.AlignByKeys→shapeless.DepFn1shapeless.ops.record.DeepMerger→shapeless.DepFn2shapeless.ops.record.Fields→shapeless.DepFn1shapeless.ops.record.Keys→shapeless.DepFn0shapeless.ops.record.LacksKeyMacros→shapeless.CaseClassMacrosshapeless.ops.record.LowPriorityDeepMerger→shapeless.::shapeless.ops.record.LowPriorityDeepMerger0→shapeless.::shapeless.ops.record.LowPriorityExtractor→shapeless.::shapeless.ops.record.LowPriorityExtractor→shapeless.=:!=shapeless.ops.record.LowPriorityMergeWith→shapeless.::shapeless.ops.record.LowPriorityMerger→shapeless.::shapeless.ops.record.LowPriorityRemove→shapeless.::shapeless.ops.record.MapValues→shapeless.DepFn1shapeless.ops.record.MergeWith→shapeless.DepFn2shapeless.ops.record.Merger→shapeless.DepFn2shapeless.ops.record.Modifier→shapeless.DepFn2shapeless.ops.record.ModifierMacros→shapeless.CaseClassMacrosshapeless.ops.record.Remove→shapeless.DepFn1shapeless.ops.record.RemoveAll→shapeless.DepFn1shapeless.ops.record.Remover→shapeless.DepFn1shapeless.ops.record.RemoverMacros→shapeless.CaseClassMacrosshapeless.ops.record.Renamer→shapeless.DepFn1shapeless.ops.record.SelectAll→shapeless.DepFn1shapeless.ops.record.Selector→shapeless.DepFn1shapeless.ops.record.SelectorMacros→shapeless.CaseClassMacros
- Direction
- shapeless.ops.record uses shapeless, so a change to shapeless can break shapeless.ops.record, while a change to shapeless.ops.record can't break shapeless.
- 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.
27→1 shapeless.syntax uses shapeless.CaseClassMacros✕
- Connections
- 2 pairs of types, where a type in shapeless.syntax uses a type in shapeless.CaseClassMacros.
- The types involved
shapeless.syntax.RecordOps→shapeless.CaseClassMacros.FieldTypeshapeless.syntax.SingletonOps→shapeless.CaseClassMacros.FieldType
- Direction
- shapeless.syntax uses shapeless.CaseClassMacros, so a change to shapeless.CaseClassMacros can break shapeless.syntax, while a change to shapeless.syntax can't break shapeless.CaseClassMacros.
- Position
- Below the diagonal: shapeless.syntax uses a module listed above it, which is the healthy direction.
27→4 shapeless.syntax uses shapeless.Lazy✕
- Connections
- 2 pairs of types, where a type in shapeless.syntax uses a type in shapeless.Lazy.
- The types involved
shapeless.syntax.RecordOps→shapeless.Lazy.Valuesshapeless.syntax.UnionOps→shapeless.Lazy.Values
- Direction
- shapeless.syntax uses shapeless.Lazy, so a change to shapeless.Lazy can break shapeless.syntax, while a change to shapeless.syntax can't break shapeless.Lazy.
- Position
- Below the diagonal: shapeless.syntax uses a module listed above it, which is the healthy direction.
27→6 shapeless.syntax uses shapeless.~?>✕
- Connections
- 1 pair of types, where a type in shapeless.syntax uses a type in shapeless.~?>.
- The types involved
shapeless.syntax.HListOps→shapeless.~?>.λ
- Direction
- shapeless.syntax uses shapeless.~?>, so a change to shapeless.~?> can break shapeless.syntax, while a change to shapeless.syntax can't break shapeless.~?>.
- Position
- Below the diagonal: shapeless.syntax uses a module listed above it, which is the healthy direction.
27→15 shapeless.syntax uses shapeless.ops.adjoin✕
- Connections
- 2 pairs of types, where a type in shapeless.syntax uses a type in shapeless.ops.adjoin.
- The types involved
shapeless.syntax.CoproductOps→shapeless.ops.adjoin.Adjoinshapeless.syntax.HListOps→shapeless.ops.adjoin.Adjoin
- Direction
- shapeless.syntax uses shapeless.ops.adjoin, so a change to shapeless.ops.adjoin can break shapeless.syntax, while a change to shapeless.syntax can't break shapeless.ops.adjoin.
- Position
- Below the diagonal: shapeless.syntax uses a module listed above it, which is the healthy direction.
27→16 shapeless.syntax uses shapeless.ops.nat✕
- Connections
- 2 pairs of types, where a type in shapeless.syntax uses a type in shapeless.ops.nat.
- The types involved
shapeless.syntax.NatOps→shapeless.ops.nat.ToIntshapeless.syntax.SizedConv→shapeless.ops.nat.ToInt
- Direction
- shapeless.syntax uses shapeless.ops.nat, so a change to shapeless.ops.nat can break shapeless.syntax, while a change to shapeless.syntax can't break shapeless.ops.nat.
- Position
- Below the diagonal: shapeless.syntax uses a module listed above it, which is the healthy direction.
27→19 shapeless.syntax uses shapeless.ops.coproduct✕
- Connections
- 53 pairs of types, where a type in shapeless.syntax uses a type in shapeless.ops.coproduct. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
shapeless.syntax.CoproductOps→shapeless.ops.coproduct.Alignshapeless.syntax.CoproductOps→shapeless.ops.coproduct.Atshapeless.syntax.CoproductOps→shapeless.ops.coproduct.Basisshapeless.syntax.CoproductOps→shapeless.ops.coproduct.CoproductToEithershapeless.syntax.CoproductOps→shapeless.ops.coproduct.Dropshapeless.syntax.CoproductOps→shapeless.ops.coproduct.ExtendLeftByshapeless.syntax.CoproductOps→shapeless.ops.coproduct.ExtendRightshapeless.syntax.CoproductOps→shapeless.ops.coproduct.ExtendRightByshapeless.syntax.CoproductOps→shapeless.ops.coproduct.FlatMapshapeless.syntax.CoproductOps→shapeless.ops.coproduct.Foldershapeless.syntax.CoproductOps→shapeless.ops.coproduct.IndexOfshapeless.syntax.CoproductOps→shapeless.ops.coproduct.InitLastshapeless.syntax.CoproductOps→shapeless.ops.coproduct.IsCConsshapeless.syntax.CoproductOps→shapeless.ops.coproduct.LeftFoldershapeless.syntax.CoproductOps→shapeless.ops.coproduct.Lengthshapeless.syntax.CoproductOps→shapeless.ops.coproduct.Mappershapeless.syntax.CoproductOps→shapeless.ops.coproduct.Partitionshapeless.syntax.CoproductOps→shapeless.ops.coproduct.Removeshapeless.syntax.CoproductOps→shapeless.ops.coproduct.Reverseshapeless.syntax.CoproductOps→shapeless.ops.coproduct.RotateLeftshapeless.syntax.CoproductOps→shapeless.ops.coproduct.RotateRightshapeless.syntax.CoproductOps→shapeless.ops.coproduct.Selectorshapeless.syntax.CoproductOps→shapeless.ops.coproduct.Splitshapeless.syntax.CoproductOps→shapeless.ops.coproduct.Takeshapeless.syntax.CoproductOps→shapeless.ops.coproduct.Unifier
- Direction
- shapeless.syntax uses shapeless.ops.coproduct, so a change to shapeless.ops.coproduct can break shapeless.syntax, while a change to shapeless.syntax can't break shapeless.ops.coproduct.
- Position
- Below the diagonal: shapeless.syntax uses a module listed above it, which is the healthy direction.
27→24 shapeless.syntax uses shapeless.ops.hlist✕
- Connections
- 49 pairs of types, where a type in shapeless.syntax uses a type in shapeless.ops.hlist. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
shapeless.syntax.HListOps→shapeless.ops.hlist.Collectshapeless.syntax.HListOps→shapeless.ops.hlist.CollectFirstshapeless.syntax.HListOps→shapeless.ops.hlist.Combinationsshapeless.syntax.HListOps→shapeless.ops.hlist.ConstMappershapeless.syntax.HListOps→shapeless.ops.hlist.Diffshapeless.syntax.HListOps→shapeless.ops.hlist.FlatMappershapeless.syntax.HListOps→shapeless.ops.hlist.Groupershapeless.syntax.HListOps→shapeless.ops.hlist.HListToProductshapeless.syntax.HListOps→shapeless.ops.hlist.Initshapeless.syntax.HListOps→shapeless.ops.hlist.Intersectionshapeless.syntax.HListOps→shapeless.ops.hlist.IsHConsshapeless.syntax.HListOps→shapeless.ops.hlist.Lastshapeless.syntax.HListOps→shapeless.ops.hlist.LeftReducershapeless.syntax.HListOps→shapeless.ops.hlist.LeftScannershapeless.syntax.HListOps→shapeless.ops.hlist.MapConsshapeless.syntax.HListOps→shapeless.ops.hlist.MapFoldershapeless.syntax.HListOps→shapeless.ops.hlist.ModifierAtshapeless.syntax.HListOps→shapeless.ops.hlist.PadToshapeless.syntax.HListOps→shapeless.ops.hlist.PaddedGroupershapeless.syntax.HListOps→shapeless.ops.hlist.Patchershapeless.syntax.HListOps→shapeless.ops.hlist.Permutationsshapeless.syntax.HListOps→shapeless.ops.hlist.RemoveAllshapeless.syntax.HListOps→shapeless.ops.hlist.Repeatshapeless.syntax.HListOps→shapeless.ops.hlist.Replacershapeless.syntax.HListOps→shapeless.ops.hlist.ReversePrepend
- Direction
- shapeless.syntax uses shapeless.ops.hlist, so a change to shapeless.ops.hlist can break shapeless.syntax, while a change to shapeless.syntax can't break shapeless.ops.hlist.
- Position
- Below the diagonal: shapeless.syntax uses a module listed above it, which is the healthy direction.
27→26 shapeless.syntax uses shapeless.ops.record✕
- Connections
- 14 pairs of types, where a type in shapeless.syntax uses a type in shapeless.ops.record.
- The types involved
shapeless.syntax.RecordOps→shapeless.ops.record.AlignByKeysshapeless.syntax.RecordOps→shapeless.ops.record.DeepMergershapeless.syntax.RecordOps→shapeless.ops.record.Extractorshapeless.syntax.RecordOps→shapeless.ops.record.Fieldsshapeless.syntax.RecordOps→shapeless.ops.record.Keysshapeless.syntax.RecordOps→shapeless.ops.record.MapValuesshapeless.syntax.RecordOps→shapeless.ops.record.MergeWithshapeless.syntax.RecordOps→shapeless.ops.record.Mergershapeless.syntax.RecordOps→shapeless.ops.record.Removershapeless.syntax.RecordOps→shapeless.ops.record.Renamershapeless.syntax.RecordOps→shapeless.ops.record.Updatershapeless.syntax.UnionOps→shapeless.ops.record.Fieldsshapeless.syntax.UnionOps→shapeless.ops.record.Keysshapeless.syntax.UnionOps→shapeless.ops.record.MapValues
- Direction
- shapeless.syntax uses shapeless.ops.record, so a change to shapeless.ops.record can break shapeless.syntax, while a change to shapeless.syntax can't break shapeless.ops.record.
- Position
- Below the diagonal: shapeless.syntax uses a module listed above it, which is the healthy direction.
27→28 shapeless.syntax uses shapeless part of a loop✕
- Connections
- 16 pairs of types, where a type in shapeless.syntax uses a type in shapeless.
- The types involved
shapeless.syntax.CoproductOps→shapeless.:+:shapeless.syntax.CoproductOps→shapeless.Natshapeless.syntax.CoproductOps→shapeless.Polyshapeless.syntax.HListOps→shapeless.::shapeless.syntax.HListOps→shapeless.Lubshapeless.syntax.HListOps→shapeless.Natshapeless.syntax.HListOps→shapeless.NatWithshapeless.syntax.HListOps→shapeless.Polyshapeless.syntax.RecordOps→shapeless.Polyshapeless.syntax.RecordOps→shapeless.Witnessshapeless.syntax.RecordOps→shapeless.WitnessWithshapeless.syntax.SizedConv→shapeless.Natshapeless.syntax.TypeableOps→shapeless.Typeableshapeless.syntax.UnionOps→shapeless.Polyshapeless.syntax.UnionOps→shapeless.Witnessshapeless.syntax.sized→shapeless.AdditiveCollection
- Direction
- shapeless.syntax uses shapeless, so a change to shapeless can break shapeless.syntax, while a change to shapeless.syntax can't break shapeless.
- 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.
28→1 shapeless uses shapeless.CaseClassMacros✕
- Connections
- 1 pair of types, where a type in shapeless uses a type in shapeless.CaseClassMacros.
- The types involved
shapeless.FieldOf→shapeless.CaseClassMacros.FieldType
- Direction
- shapeless uses shapeless.CaseClassMacros, so a change to shapeless.CaseClassMacros can break shapeless, while a change to shapeless can't break shapeless.CaseClassMacros.
- Position
- Below the diagonal: shapeless uses a module listed above it, which is the healthy direction.
28→2 shapeless uses shapeless.LP1✕
- Connections
- 2 pairs of types, where a type in shapeless uses a type in shapeless.LP1.
- The types involved
shapeless.LP0→shapeless.LP1.CanBuildFromOpsshapeless.LP1→shapeless.LP1.CanBuildFromOps
- Direction
- shapeless uses shapeless.LP1, so a change to shapeless.LP1 can break shapeless, while a change to shapeless can't break shapeless.LP1.
- Position
- Below the diagonal: shapeless uses a module listed above it, which is the healthy direction.
28→5 shapeless uses shapeless.ProductISOFacet✕
- Connections
- 1 pair of types, where a type in shapeless uses a type in shapeless.ProductISOFacet.
- The types involved
shapeless.ProductISOFacet→shapeless.ProductISOFacet.ProductISOOps
- Direction
- shapeless uses shapeless.ProductISOFacet, so a change to shapeless.ProductISOFacet can break shapeless, while a change to shapeless can't break shapeless.ProductISOFacet.
- Position
- Below the diagonal: shapeless uses a module listed above it, which is the healthy direction.
28→6 shapeless uses shapeless.~?>✕
- Connections
- 2 pairs of types, where a type in shapeless uses a type in shapeless.~?>.
- The types involved
shapeless.LowPriorityUnaryTCConstraint→shapeless.~?>.λshapeless.NatTRel0→shapeless.~?>.λ
- Direction
- shapeless uses shapeless.~?>, so a change to shapeless.~?> can break shapeless, while a change to shapeless can't break shapeless.~?>.
- Position
- Below the diagonal: shapeless uses a module listed above it, which is the healthy direction.
28→7 shapeless uses shapeless.ApplyUnapplyFacet✕
- Connections
- 1 pair of types, where a type in shapeless uses a type in shapeless.ApplyUnapplyFacet.
- The types involved
shapeless.ApplyUnapplyFacet→shapeless.ApplyUnapplyFacet.ApplyUnapplyOps
- Direction
- shapeless uses shapeless.ApplyUnapplyFacet, so a change to shapeless.ApplyUnapplyFacet can break shapeless, while a change to shapeless can't break shapeless.ApplyUnapplyFacet.
- Position
- Below the diagonal: shapeless uses a module listed above it, which is the healthy direction.
28→8 shapeless uses shapeless.CopyFacet✕
- Connections
- 1 pair of types, where a type in shapeless uses a type in shapeless.CopyFacet.
- The types involved
shapeless.CopyFacet→shapeless.CopyFacet.CopyOps
- Direction
- shapeless uses shapeless.CopyFacet, so a change to shapeless.CopyFacet can break shapeless, while a change to shapeless can't break shapeless.CopyFacet.
- Position
- Below the diagonal: shapeless uses a module listed above it, which is the healthy direction.
28→9 shapeless uses shapeless.FieldPoly✕
- Connections
- 1 pair of types, where a type in shapeless uses a type in shapeless.FieldPoly.
- The types involved
shapeless.FieldPoly→shapeless.FieldPoly.FieldCaseBuilder
- Direction
- shapeless uses shapeless.FieldPoly, so a change to shapeless.FieldPoly can break shapeless, while a change to shapeless can't break shapeless.FieldPoly.
- Position
- Below the diagonal: shapeless uses a module listed above it, which is the healthy direction.
28→11 shapeless uses shapeless.Poly✕
- Connections
- 2 pairs of types, where a type in shapeless uses a type in shapeless.Poly.
- The types involved
shapeless.Poly→shapeless.Poly.CaseBuildershapeless.Poly→shapeless.Poly.ProductCase
- Direction
- shapeless uses shapeless.Poly, so a change to shapeless.Poly can break shapeless, while a change to shapeless can't break shapeless.Poly.
- Position
- Below the diagonal: shapeless uses a module listed above it, which is the healthy direction.
28→12 shapeless uses shapeless.PolymorphicEqualityFacet✕
- Connections
- 1 pair of types, where a type in shapeless uses a type in shapeless.PolymorphicEqualityFacet.
- The types involved
shapeless.PolymorphicEqualityFacet→shapeless.PolymorphicEqualityFacet.PolymorphicEqualityOps
- Direction
- shapeless uses shapeless.PolymorphicEqualityFacet, so a change to shapeless.PolymorphicEqualityFacet can break shapeless, while a change to shapeless can't break shapeless.PolymorphicEqualityFacet.
- Position
- Below the diagonal: shapeless uses a module listed above it, which is the healthy direction.
28→13 shapeless uses shapeless.ProductFacet✕
- Connections
- 1 pair of types, where a type in shapeless uses a type in shapeless.ProductFacet.
- The types involved
shapeless.ProductFacet→shapeless.ProductFacet.ProductOps
- Direction
- shapeless uses shapeless.ProductFacet, so a change to shapeless.ProductFacet can break shapeless, while a change to shapeless can't break shapeless.ProductFacet.
- Position
- Below the diagonal: shapeless uses a module listed above it, which is the healthy direction.
28→14 shapeless uses shapeless.labelled✕
- Connections
- 1 pair of types, where a type in shapeless uses a type in shapeless.labelled.
- The types involved
shapeless.labelled→shapeless.labelled.FieldBuilder
- Direction
- shapeless uses shapeless.labelled, so a change to shapeless.labelled can break shapeless, while a change to shapeless can't break shapeless.labelled.
- Position
- Below the diagonal: shapeless uses a module listed above it, which is the healthy direction.
28→16 shapeless uses shapeless.ops.nat✕
- Connections
- 6 pairs of types, where a type in shapeless uses a type in shapeless.ops.nat.
- The types involved
shapeless.DefaultCaseClassDefns→shapeless.ops.nat.ToIntshapeless.ProductLensBuilder→shapeless.ops.nat.LTshapeless.ProductPrismBuilder→shapeless.ops.nat.LTshapeless.SizedOps→shapeless.ops.nat.Predshapeless.SizedOps→shapeless.ops.nat.Sumshapeless.SizedOps→shapeless.ops.nat.ToInt
- Direction
- shapeless uses shapeless.ops.nat, so a change to shapeless.ops.nat can break shapeless, while a change to shapeless can't break shapeless.ops.nat.
- Position
- Below the diagonal: shapeless uses a module listed above it, which is the healthy direction.
28→17 shapeless uses shapeless.ops.zipper✕
- Connections
- 14 pairs of types, where a type in shapeless uses a type in shapeless.ops.zipper.
- The types involved
shapeless.Zipper→shapeless.ops.zipper.Deleteshapeless.Zipper→shapeless.ops.zipper.Downshapeless.Zipper→shapeless.ops.zipper.Firstshapeless.Zipper→shapeless.ops.zipper.Getshapeless.Zipper→shapeless.ops.zipper.Insertshapeless.Zipper→shapeless.ops.zipper.Leftshapeless.Zipper→shapeless.ops.zipper.LeftByshapeless.Zipper→shapeless.ops.zipper.LeftToshapeless.Zipper→shapeless.ops.zipper.Putshapeless.Zipper→shapeless.ops.zipper.Rightshapeless.Zipper→shapeless.ops.zipper.RightByshapeless.Zipper→shapeless.ops.zipper.RightToshapeless.Zipper→shapeless.ops.zipper.Rootshapeless.Zipper→shapeless.ops.zipper.Up
- Direction
- shapeless uses shapeless.ops.zipper, so a change to shapeless.ops.zipper can break shapeless, while a change to shapeless can't break shapeless.ops.zipper.
- Position
- Below the diagonal: shapeless uses a module listed above it, which is the healthy direction.
28→18 shapeless uses shapeless.ToStringFacet✕
- Connections
- 1 pair of types, where a type in shapeless uses a type in shapeless.ToStringFacet.
- The types involved
shapeless.ToStringFacet→shapeless.ToStringFacet.ToStringOps
- Direction
- shapeless uses shapeless.ToStringFacet, so a change to shapeless.ToStringFacet can break shapeless, while a change to shapeless can't break shapeless.ToStringFacet.
- Position
- Below the diagonal: shapeless uses a module listed above it, which is the healthy direction.
28→19 shapeless uses shapeless.ops.coproduct✕
- Connections
- 2 pairs of types, where a type in shapeless uses a type in shapeless.ops.coproduct.
- The types involved
shapeless.SizedOps→shapeless.ops.coproduct.ToHListshapeless.Zipper→shapeless.ops.coproduct.Reify
- Direction
- shapeless uses shapeless.ops.coproduct, so a change to shapeless.ops.coproduct can break shapeless, while a change to shapeless can't break shapeless.ops.coproduct.
- Position
- Below the diagonal: shapeless uses a module listed above it, which is the healthy direction.
28→21 shapeless uses shapeless.DefaultCaseClassDefns✕
- Connections
- 1 pair of types, where a type in shapeless uses a type in shapeless.DefaultCaseClassDefns.
- The types involved
shapeless.DefaultCaseClassDefns→shapeless.DefaultCaseClassDefns.CaseClassOps
- Direction
- shapeless uses shapeless.DefaultCaseClassDefns, so a change to shapeless.DefaultCaseClassDefns can break shapeless, while a change to shapeless can't break shapeless.DefaultCaseClassDefns.
- Position
- Below the diagonal: shapeless uses a module listed above it, which is the healthy direction.
28→24 shapeless uses shapeless.ops.hlist✕
- Connections
- 4 pairs of types, where a type in shapeless uses a type in shapeless.ops.hlist.
- The types involved
shapeless.SizedOps→shapeless.ops.hlist.Diffshapeless.Tuple→shapeless.ops.hlist.Fillshapeless.Zipper→shapeless.ops.hlist.Lastshapeless.tupled→shapeless.ops.hlist.Tupler
- Direction
- shapeless uses shapeless.ops.hlist, so a change to shapeless.ops.hlist can break shapeless, while a change to shapeless can't break shapeless.ops.hlist.
- Position
- Below the diagonal: shapeless uses a module listed above it, which is the healthy direction.
28→27 shapeless uses shapeless.syntax✕
- Connections
- 2 pairs of types, where a type in shapeless uses a type in shapeless.syntax.
- The types involved
shapeless.record→shapeless.syntax.RecordOpsshapeless.union→shapeless.syntax.UnionOps
- Direction
- shapeless uses shapeless.syntax, so a change to shapeless.syntax can break shapeless, while a change to shapeless can't break shapeless.syntax.
- Position
- Below the diagonal: shapeless uses a module listed above it, which is the healthy direction.
29→28 (global) uses shapeless✕
- Connections
- 4 pairs of types, where a type in (global) uses a type in shapeless.
- The types involved
shapeless→shapeless.<:!<shapeless→shapeless.=:!=shapeless→shapeless.Polyshapeless→shapeless.ScalaVersionSpecifics
- Direction
- (global) uses shapeless, so a change to shapeless can break (global), while a change to (global) can't break shapeless.
- Position
- Below the diagonal: (global) uses a module listed above it, which is the healthy direction.
30→28 shapeless.Default uses shapeless✕
- Connections
- 2 pairs of types, where a type in shapeless.Default uses a type in shapeless.
- The types involved
shapeless.Default.AsOptions→shapeless.DepFn0shapeless.Default.AsRecord→shapeless.DepFn0
- Direction
- shapeless.Default uses shapeless, so a change to shapeless can break shapeless.Default, while a change to shapeless.Default can't break shapeless.
- Position
- Below the diagonal: shapeless.Default uses a module listed above it, which is the healthy direction.
31→28 shapeless.Default.AsOptions uses shapeless✕
- Connections
- 1 pair of types, where a type in shapeless.Default.AsOptions uses a type in shapeless.
- The types involved
shapeless.Default.AsOptions.Helper→shapeless.DepFn1
- Direction
- shapeless.Default.AsOptions uses shapeless, so a change to shapeless can break shapeless.Default.AsOptions, while a change to shapeless.Default.AsOptions can't break shapeless.
- Position
- Below the diagonal: shapeless.Default.AsOptions uses a module listed above it, which is the healthy direction.
32→28 shapeless.Default.AsRecord uses shapeless✕
- Connections
- 1 pair of types, where a type in shapeless.Default.AsRecord uses a type in shapeless.
- The types involved
shapeless.Default.AsRecord.Helper→shapeless.DepFn1
- Direction
- shapeless.Default.AsRecord uses shapeless, so a change to shapeless can break shapeless.Default.AsRecord, while a change to shapeless.Default.AsRecord can't break shapeless.
- Position
- Below the diagonal: shapeless.Default.AsRecord uses a module listed above it, which is the healthy direction.
33→17 shapeless.Zipper uses shapeless.ops.zipper✕
- Connections
- 1 pair of types, where a type in shapeless.Zipper uses a type in shapeless.ops.zipper.
- The types involved
shapeless.Zipper.Modifier→shapeless.ops.zipper.Modify
- Direction
- shapeless.Zipper uses shapeless.ops.zipper, so a change to shapeless.ops.zipper can break shapeless.Zipper, while a change to shapeless.Zipper can't break shapeless.ops.zipper.
- Position
- Below the diagonal: shapeless.Zipper uses a module listed above it, which is the healthy direction.
33→28 shapeless.Zipper uses shapeless✕
- Connections
- 2 pairs of types, where a type in shapeless.Zipper uses a type in shapeless.
- The types involved
shapeless.Zipper.Modifier→shapeless.::shapeless.Zipper.Modifier→shapeless.Zipper
- Direction
- shapeless.Zipper uses shapeless, so a change to shapeless can break shapeless.Zipper, while a change to shapeless.Zipper can't break shapeless.
- Position
- Below the diagonal: shapeless.Zipper uses a module listed above it, which is the healthy direction.
34→28 shapeless.ops.function uses shapeless✕
- Connections
- 1 pair of types, where a type in shapeless.ops.function uses a type in shapeless.
- The types involved
shapeless.ops.function.FnFromProduct→shapeless.DepFn1
- Direction
- shapeless.ops.function uses shapeless, so a change to shapeless can break shapeless.ops.function, while a change to shapeless.ops.function can't break shapeless.
- Position
- Below the diagonal: shapeless.ops.function uses a module listed above it, which is the healthy direction.
35→28 shapeless.ops.product uses shapeless✕
- Connections
- 7 pairs of types, where a type in shapeless.ops.product uses a type in shapeless.
- The types involved
shapeless.ops.product.ProductLength→shapeless.DepFn1shapeless.ops.product.ToHList→shapeless.DepFn1shapeless.ops.product.ToMap→shapeless.DepFn1shapeless.ops.product.ToRecord→shapeless.DepFn1shapeless.ops.product.ToSized→shapeless.DepFn1shapeless.ops.product.ToTraversable→shapeless.DepFn1shapeless.ops.product.ToTuple→shapeless.DepFn1
- Direction
- shapeless.ops.product uses shapeless, so a change to shapeless can break shapeless.ops.product, while a change to shapeless.ops.product can't break shapeless.
- Position
- Below the diagonal: shapeless.ops.product uses a module listed above it, which is the healthy direction.
36→28 shapeless.ops.tuple uses shapeless✕
- Connections
- 52 pairs of types, where a type in shapeless.ops.tuple uses a type in shapeless. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
shapeless.ops.tuple.At→shapeless.DepFn1shapeless.ops.tuple.Collect→shapeless.DepFn1shapeless.ops.tuple.ConstMapper→shapeless.DepFn2shapeless.ops.tuple.Drop→shapeless.DepFn1shapeless.ops.tuple.Fill→shapeless.DepFn1shapeless.ops.tuple.Filter→shapeless.DepFn1shapeless.ops.tuple.FilterNot→shapeless.DepFn1shapeless.ops.tuple.FlatMapper→shapeless.DepFn1shapeless.ops.tuple.Grouper→shapeless.DepFn1shapeless.ops.tuple.Init→shapeless.DepFn1shapeless.ops.tuple.Last→shapeless.DepFn1shapeless.ops.tuple.LeftFolder→shapeless.DepFn2shapeless.ops.tuple.LeftReducer→shapeless.DepFn1shapeless.ops.tuple.LeftScanner→shapeless.DepFn2shapeless.ops.tuple.Length→shapeless.DepFn1shapeless.ops.tuple.Mapper→shapeless.DepFn1shapeless.ops.tuple.Modifier→shapeless.DepFn2shapeless.ops.tuple.ModifierAt→shapeless.DepFn2shapeless.ops.tuple.PaddedGrouper→shapeless.DepFn2shapeless.ops.tuple.Patcher→shapeless.DepFn2shapeless.ops.tuple.Permutations→shapeless.DepFn1shapeless.ops.tuple.Prepend→shapeless.DepFn2shapeless.ops.tuple.Remove→shapeless.DepFn1shapeless.ops.tuple.RemoveAll→shapeless.DepFn1shapeless.ops.tuple.ReplaceAt→shapeless.DepFn2
- Direction
- shapeless.ops.tuple uses shapeless, so a change to shapeless can break shapeless.ops.tuple, while a change to shapeless.ops.tuple can't break shapeless.
- Position
- Below the diagonal: shapeless.ops.tuple uses a module listed above it, which is the healthy direction.
37→4 shapeless.ops.union uses shapeless.Lazy✕
- Connections
- 1 pair of types, where a type in shapeless.ops.union uses a type in shapeless.Lazy.
- The types involved
shapeless.ops.union.UnzipFields→shapeless.Lazy.Values
- Direction
- shapeless.ops.union uses shapeless.Lazy, so a change to shapeless.Lazy can break shapeless.ops.union, while a change to shapeless.ops.union can't break shapeless.Lazy.
- Position
- Below the diagonal: shapeless.ops.union uses a module listed above it, which is the healthy direction.
37→19 shapeless.ops.union uses shapeless.ops.coproduct✕
- Connections
- 1 pair of types, where a type in shapeless.ops.union uses a type in shapeless.ops.coproduct.
- The types involved
shapeless.ops.union.LowPrioritySelector→shapeless.ops.coproduct.Selector
- Direction
- shapeless.ops.union uses shapeless.ops.coproduct, so a change to shapeless.ops.coproduct can break shapeless.ops.union, while a change to shapeless.ops.union can't break shapeless.ops.coproduct.
- Position
- Below the diagonal: shapeless.ops.union uses a module listed above it, which is the healthy direction.
37→26 shapeless.ops.union uses shapeless.ops.record✕
- Connections
- 1 pair of types, where a type in shapeless.ops.union uses a type in shapeless.ops.record.
- The types involved
shapeless.ops.union.UnzipFields→shapeless.ops.record.Keys
- Direction
- shapeless.ops.union uses shapeless.ops.record, so a change to shapeless.ops.record can break shapeless.ops.union, while a change to shapeless.ops.union can't break shapeless.ops.record.
- Position
- Below the diagonal: shapeless.ops.union uses a module listed above it, which is the healthy direction.
37→28 shapeless.ops.union uses shapeless✕
- Connections
- 6 pairs of types, where a type in shapeless.ops.union uses a type in shapeless.
- The types involved
shapeless.ops.union.Fields→shapeless.DepFn1shapeless.ops.union.Keys→shapeless.DepFn0shapeless.ops.union.LowPrioritySelector→shapeless.:+:shapeless.ops.union.MapValues→shapeless.DepFn1shapeless.ops.union.ToMap→shapeless.DepFn1shapeless.ops.union.Values→shapeless.DepFn1
- Direction
- shapeless.ops.union uses shapeless, so a change to shapeless can break shapeless.ops.union, while a change to shapeless.ops.union can't break shapeless.
- Position
- Below the diagonal: shapeless.ops.union uses a module listed above it, which is the healthy direction.
38→24 shapeless.syntax.HListOps uses shapeless.ops.hlist✕
- Connections
- 3 pairs of types, where a type in shapeless.syntax.HListOps uses a type in shapeless.ops.hlist.
- The types involved
shapeless.syntax.HListOps.PatchAux→shapeless.ops.hlist.Patchershapeless.syntax.HListOps.ReplaceTypeAux→shapeless.ops.hlist.Replacershapeless.syntax.HListOps.SelectManyAux→shapeless.ops.hlist.SelectMany
- Direction
- shapeless.syntax.HListOps uses shapeless.ops.hlist, so a change to shapeless.ops.hlist can break shapeless.syntax.HListOps, while a change to shapeless.syntax.HListOps can't break shapeless.ops.hlist.
- Position
- Below the diagonal: shapeless.syntax.HListOps uses a module listed above it, which is the healthy direction.
38→28 shapeless.syntax.HListOps uses shapeless✕
- Connections
- 1 pair of types, where a type in shapeless.syntax.HListOps uses a type in shapeless.
- The types involved
shapeless.syntax.HListOps.SelectManyAux→shapeless.NatProductArgs
- Direction
- shapeless.syntax.HListOps uses shapeless, so a change to shapeless can break shapeless.syntax.HListOps, while a change to shapeless.syntax.HListOps can't break shapeless.
- Position
- Below the diagonal: shapeless.syntax.HListOps uses a module listed above it, which is the healthy direction.
39→28 shapeless.ops uses shapeless✕
- Connections
- 3 pairs of types, where a type in shapeless.ops uses a type in shapeless.
- The types involved
shapeless.ops.coproduct→shapeless.:+:shapeless.ops.hlist→shapeless.::shapeless.ops.hlist→shapeless.Lub
- Direction
- shapeless.ops uses shapeless, so a change to shapeless can break shapeless.ops, while a change to shapeless.ops can't break shapeless.
- Position
- Below the diagonal: shapeless.ops uses a module listed above it, which is the healthy direction.
39→36 shapeless.ops uses shapeless.ops.tuple✕
- Connections
- 2 pairs of types, where a type in shapeless.ops uses a type in shapeless.ops.tuple.
- The types involved
shapeless.ops.hlist→shapeless.ops.tuple.ToArrayshapeless.ops.hlist→shapeless.ops.tuple.ToList
- Direction
- shapeless.ops uses shapeless.ops.tuple, so a change to shapeless.ops.tuple can break shapeless.ops, while a change to shapeless.ops can't break shapeless.ops.tuple.
- Position
- Below the diagonal: shapeless.ops uses a module listed above it, which is the healthy direction.
40→6 shapeless.syntax.std uses shapeless.~?>✕
- Connections
- 1 pair of types, where a type in shapeless.syntax.std uses a type in shapeless.~?>.
- The types involved
shapeless.syntax.std.TupleOps→shapeless.~?>.λ
- Direction
- shapeless.syntax.std uses shapeless.~?>, so a change to shapeless.~?> can break shapeless.syntax.std, while a change to shapeless.syntax.std can't break shapeless.~?>.
- Position
- Below the diagonal: shapeless.syntax.std uses a module listed above it, which is the healthy direction.
40→13 shapeless.syntax.std uses shapeless.ProductFacet✕
- Connections
- 1 pair of types, where a type in shapeless.syntax.std uses a type in shapeless.ProductFacet.
- The types involved
shapeless.syntax.std.product→shapeless.ProductFacet.ProductOps
- Direction
- shapeless.syntax.std uses shapeless.ProductFacet, so a change to shapeless.ProductFacet can break shapeless.syntax.std, while a change to shapeless.syntax.std can't break shapeless.ProductFacet.
- Position
- Below the diagonal: shapeless.syntax.std uses a module listed above it, which is the healthy direction.
40→19 shapeless.syntax.std uses shapeless.ops.coproduct✕
- Connections
- 20 pairs of types, where a type in shapeless.syntax.std uses a type in shapeless.ops.coproduct.
- The types involved
shapeless.syntax.std.EitherOps→shapeless.ops.coproduct.EitherToCoproductshapeless.syntax.std.TupleOps→shapeless.ops.coproduct.Alignshapeless.syntax.std.TupleOps→shapeless.ops.coproduct.Atshapeless.syntax.std.TupleOps→shapeless.ops.coproduct.Dropshapeless.syntax.std.TupleOps→shapeless.ops.coproduct.Filtershapeless.syntax.std.TupleOps→shapeless.ops.coproduct.FilterNotshapeless.syntax.std.TupleOps→shapeless.ops.coproduct.LeftFoldershapeless.syntax.std.TupleOps→shapeless.ops.coproduct.Lengthshapeless.syntax.std.TupleOps→shapeless.ops.coproduct.Mappershapeless.syntax.std.TupleOps→shapeless.ops.coproduct.Prependshapeless.syntax.std.TupleOps→shapeless.ops.coproduct.Removeshapeless.syntax.std.TupleOps→shapeless.ops.coproduct.Reverseshapeless.syntax.std.TupleOps→shapeless.ops.coproduct.RotateLeftshapeless.syntax.std.TupleOps→shapeless.ops.coproduct.RotateRightshapeless.syntax.std.TupleOps→shapeless.ops.coproduct.Selectorshapeless.syntax.std.TupleOps→shapeless.ops.coproduct.Splitshapeless.syntax.std.TupleOps→shapeless.ops.coproduct.Takeshapeless.syntax.std.TupleOps→shapeless.ops.coproduct.Unifiershapeless.syntax.std.TupleOps→shapeless.ops.coproduct.ZipConstshapeless.syntax.std.TupleOps→shapeless.ops.coproduct.ZipWithIndex
- Direction
- shapeless.syntax.std uses shapeless.ops.coproduct, so a change to shapeless.ops.coproduct can break shapeless.syntax.std, while a change to shapeless.syntax.std can't break shapeless.ops.coproduct.
- Position
- Below the diagonal: shapeless.syntax.std uses a module listed above it, which is the healthy direction.
40→24 shapeless.syntax.std uses shapeless.ops.hlist✕
- Connections
- 33 pairs of types, where a type in shapeless.syntax.std uses a type in shapeless.ops.hlist. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
shapeless.syntax.std.ProductOps→shapeless.ops.hlist.ToSizedshapeless.syntax.std.ProductOps→shapeless.ops.hlist.ToTraversableshapeless.syntax.std.TupleOps→shapeless.ops.hlist.Collectshapeless.syntax.std.TupleOps→shapeless.ops.hlist.ConstMappershapeless.syntax.std.TupleOps→shapeless.ops.hlist.FlatMappershapeless.syntax.std.TupleOps→shapeless.ops.hlist.Groupershapeless.syntax.std.TupleOps→shapeless.ops.hlist.Initshapeless.syntax.std.TupleOps→shapeless.ops.hlist.Lastshapeless.syntax.std.TupleOps→shapeless.ops.hlist.LeftReducershapeless.syntax.std.TupleOps→shapeless.ops.hlist.LeftScannershapeless.syntax.std.TupleOps→shapeless.ops.hlist.MapFoldershapeless.syntax.std.TupleOps→shapeless.ops.hlist.ModifierAtshapeless.syntax.std.TupleOps→shapeless.ops.hlist.PaddedGroupershapeless.syntax.std.TupleOps→shapeless.ops.hlist.Patchershapeless.syntax.std.TupleOps→shapeless.ops.hlist.Permutationsshapeless.syntax.std.TupleOps→shapeless.ops.hlist.ProductToHListshapeless.syntax.std.TupleOps→shapeless.ops.hlist.RemoveAllshapeless.syntax.std.TupleOps→shapeless.ops.hlist.Replacershapeless.syntax.std.TupleOps→shapeless.ops.hlist.ReversePrependshapeless.syntax.std.TupleOps→shapeless.ops.hlist.ReverseSplitshapeless.syntax.std.TupleOps→shapeless.ops.hlist.ReverseSplitLeftshapeless.syntax.std.TupleOps→shapeless.ops.hlist.ReverseSplitRightshapeless.syntax.std.TupleOps→shapeless.ops.hlist.RightFoldershapeless.syntax.std.TupleOps→shapeless.ops.hlist.RightReducershapeless.syntax.std.TupleOps→shapeless.ops.hlist.RightScanner
- Direction
- shapeless.syntax.std uses shapeless.ops.hlist, so a change to shapeless.ops.hlist can break shapeless.syntax.std, while a change to shapeless.syntax.std can't break shapeless.ops.hlist.
- Position
- Below the diagonal: shapeless.syntax.std uses a module listed above it, which is the healthy direction.
40→27 shapeless.syntax.std uses shapeless.syntax✕
- Connections
- 1 pair of types, where a type in shapeless.syntax.std uses a type in shapeless.syntax.
- The types involved
shapeless.syntax.std.tuple→shapeless.syntax.HListOps
- Direction
- shapeless.syntax.std uses shapeless.syntax, so a change to shapeless.syntax can break shapeless.syntax.std, while a change to shapeless.syntax.std can't break shapeless.syntax.
- Position
- Below the diagonal: shapeless.syntax.std uses a module listed above it, which is the healthy direction.
40→28 shapeless.syntax.std uses shapeless✕
- Connections
- 7 pairs of types, where a type in shapeless.syntax.std uses a type in shapeless.
- The types involved
shapeless.syntax.std.ProductOps→shapeless.Genericshapeless.syntax.std.TraversableOps2→shapeless.Natshapeless.syntax.std.TupleOps→shapeless.Genericshapeless.syntax.std.TupleOps→shapeless.Lubshapeless.syntax.std.TupleOps→shapeless.Natshapeless.syntax.std.TupleOps→shapeless.NatWithshapeless.syntax.std.TupleOps→shapeless.Poly
- Direction
- shapeless.syntax.std uses shapeless, so a change to shapeless can break shapeless.syntax.std, while a change to shapeless.syntax.std can't break shapeless.
- Position
- Below the diagonal: shapeless.syntax.std uses a module listed above it, which is the healthy direction.
40→34 shapeless.syntax.std uses shapeless.ops.function✕
- Connections
- 1 pair of types, where a type in shapeless.syntax.std uses a type in shapeless.ops.function.
- The types involved
shapeless.syntax.std.function→shapeless.ops.function.FnFromProduct
- Direction
- shapeless.syntax.std uses shapeless.ops.function, so a change to shapeless.ops.function can break shapeless.syntax.std, while a change to shapeless.syntax.std can't break shapeless.ops.function.
- Position
- Below the diagonal: shapeless.syntax.std uses a module listed above it, which is the healthy direction.
40→35 shapeless.syntax.std uses shapeless.ops.product✕
- Connections
- 1 pair of types, where a type in shapeless.syntax.std uses a type in shapeless.ops.product.
- The types involved
shapeless.syntax.std.ProductOps→shapeless.ops.product.ProductLength
- Direction
- shapeless.syntax.std uses shapeless.ops.product, so a change to shapeless.ops.product can break shapeless.syntax.std, while a change to shapeless.syntax.std can't break shapeless.ops.product.
- Position
- Below the diagonal: shapeless.syntax.std uses a module listed above it, which is the healthy direction.
40→36 shapeless.syntax.std uses shapeless.ops.tuple✕
- Connections
- 1 pair of types, where a type in shapeless.syntax.std uses a type in shapeless.ops.tuple.
- The types involved
shapeless.syntax.std.TupleOps→shapeless.ops.tuple.IsComposite
- Direction
- shapeless.syntax.std uses shapeless.ops.tuple, so a change to shapeless.ops.tuple can break shapeless.syntax.std, while a change to shapeless.syntax.std can't break shapeless.ops.tuple.
- Position
- Below the diagonal: shapeless.syntax.std 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 | 9 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 5 | Medium |
Roadmap
First, address the missing Architecture Decision Records by documenting significant design choices in a dedicated folder to ensure traceability. Next, resolve the nineteen orphaned files, prioritizing ShapelessPlugin.scala, nat.scala, and lenses.scala, to improve codebase freshness. Then, integrate a static analysis tool into the CI pipeline to automatically fail builds on security regressions. Finally, update the README with a clear Testing section so developers know how to run the test suite.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +7.1 pts | Low | ADR Quality |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +6.5 pts | Medium | Architecture documentation |
| Resolve the 19 Orphaned file finding(s) in Knowledge Freshness — start with ShapelessPlugin.scala (2), nat.scala, lenses.scala. | +5.9 pts | Medium | Knowledge Freshness |
| 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.3 pts | Medium | Security & performance tooling |
| Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with hlists.scala, tuples.scala, generic.scala. | +1.8 pts | Low | Knowledge Freshness |
| 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. | +2.6 pts | Medium | Documentation (README) |
| Raise allocation-aware density on the hot paths — currently 13 use(s) across 19,102 production line(s) (~0.7/1k). More of the idioms below on the allocation-heavy paths climbs this toward 10. | +2.6 pts | Medium | Allocation hygiene |
| Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it. | +2.1 pts | Medium | Deployment & Rollback |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| core/shared/src/main/scala/shapeless/generic.scala | 5.6 | Mixed | Cyclomatic Complexity: CaseClassMacros.ctorsOfAux (cyclomatic 23) |
| core/shared/src/test/scala/shapeless/product.scala | 6.5 | Mixed | Explicit Debt: FixmeComment |
| core/shared/src/main/scala/shapeless/syntax/hlists.scala | 6.7 | Mixed | Explicit Debt: TodoComment |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| core/shared/src/main/scala/shapeless/typeable.scala | 7.4 | Mixed | Cyclomatic Complexity: TypeableMacros.dfltTypeableImpl (cyclomatic 19) |
| core/shared/src/test/scala/shapeless/labelledgeneric.scala | 8.2 | Near-clean | Explicit Debt: FixmeComment |
| core/shared/src/main/scala/shapeless/default.scala | 8.5 | Near-clean | Cognitive Complexity: DefaultMacros.materialize (cognitive 21) |
| core/shared/src/main/scala/shapeless/ops/hlists.scala | 8.5 | Near-clean | God Classes: FileTooLong: ops/hlists.scala |
| core/shared/src/main/scala/shapeless/syntax/std/tuples.scala | 8.5 | Near-clean | God Classes: TooManyMethods: TupleOps |
| core/shared/src/main/scala/shapeless/syntax/coproduct.scala | 8.5 | Near-clean | God Classes: TooManyMethods: CoproductOps |
| core/shared/src/main/scala/shapeless/ops/coproduct.scala | 8.5 | Near-clean | God Classes: FileTooLong: ops/coproduct.scala |
| core/shared/src/main/scala/shapeless/ops/tuples.scala | 8.5 | Near-clean | God Classes: FileTooLong: ops/tuples.scala |
| core/shared/src/main/scala/shapeless/lenses.scala | 8.5 | Near-clean | Code Duplication: Duplicated block (6 lines × 2) |
| core/shared/src/main/scala/shapeless/ops/records.scala | 8.5 | Near-clean | Code Duplication: Duplicated block (6 lines × 2) |
| plugin/src/main/scala_2.13+/shapeless/ShapelessPlugin.scala | 8.5 | Near-clean | Code Duplication: Duplicated block (5 lines × 2) |
| examples/src/main/scala/shapeless/examples/sybclass.scala | 8.5 | Near-clean | Code Duplication: Duplicated block (15 lines × 2) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 57 of 57 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.8 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 57 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, 63 of 76 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Watchdog duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT READ here — but this repository measures it: a Codecov configuration (.codecov.yml) shows that coverage is collected and tracked in your own CI. The built-in collector has no runner for this ecosystem (.scala), so the analyzer could not read the number — a gap in the analyzer's language coverage, not an unmeasured repo. Not scored. To have the real number read, produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.scala) and this repository declares an sbt build (repository root, 44 test files), but it was not re-run: no test result was produced. 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — 1 direct sbt declaration(s) were read, but the outdated signal needs repo1.maven.org, which publishes none of these artifacts, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 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: it declares a published package (project/plugins.sbt), but 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.
- D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `core/shared/src/main/scala/shapeless/package.scala` 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This 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.
- C1 Data Protection — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- 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
2 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was CaseClassMacros.ctorsOfAux at 23.
What to do
- Bring the 2 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with CaseClassMacros.ctorsOfAux (cyclomatic 23), TypeableMacros.dfltTypeableImpl (cyclomatic 19). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 9.4 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
5 method(s) exceeded the cognitive complexity threshold of 15; the worst was CaseClassMacros.ctorsOfAux at 63.
What to do
- Bring the 1 body over 30 down to 30 or less in Cognitive Complexity — start with CaseClassMacros.ctorsOfAux (cognitive 63). — Refactoring it lifts Cognitive Complexity from 8.1 to about 8.9/10.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
8 god class(es) detected.
What to do
- Resolve the 4 TooManyMethods finding(s) in God Classes — start with hlists.scala, tuples.scala, generic.scala. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 4 FileTooLong finding(s) in God Classes — start with hlists.scala, coproduct.scala, tuples.scala. — One of this dimension's main actionable groups (4 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
4 duplicated block group(s) detected. 1 of the 4 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
What to do
- Resolve the 2 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with lenses.scala, records.scala. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with ShapelessPlugin.scala. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (15 lines × 2) finding(s) in Code Duplication — start with sybclass.scala. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
4 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; 0 module(s) off the main sequence, with abstractness counted on 3 of the 4 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
D6 · Cohesion (LCOM4)
1 of 13 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with generic.scala. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
637 test methods: 637 unit, 0 integration, 0 BDD, 0 e2e. The Scala suite contributes 637 test case(s) across 41 file(s) in a test source set declaring at least one — every `test("…")`, `it("…")`, `property("…")` and `"…" in {…}` registration and every JUnit `@Test`, which is how munit, ScalaTest, utest, ZIO Test and specs2 declare a case; a case registered under a computed name is not counted, so this is a floor. Its tier split is INFERRED from paths and file names, except sbt's src/it source set, which the build declares.
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
No source file's living knowledge is concentrated in a single author. Counted over 21 of the 73 production source files in this repository: 48 are under the ~2,400-byte size floor this dimension measures over, and the remaining 4 have no attributable history left to measure.
D17 · Explicit Debt
8 deducted task-comment markers across 20743 LoC (0.0/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 7 FixmeComment finding(s) in Explicit Debt — start with product.scala (6), labelledgeneric.scala. — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 1 TodoComment finding(s) in Explicit Debt — start with hlists.scala. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 1 build units (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)
9 finding(s): 0 critical, 9 high, 0 medium, 0 low. 7 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `core/shared/src/main/scala/shapeless/package.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 7 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 (7 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in any ecosystem this repository declares.
D34 · Knowledge Freshness
22 of 25 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is core/shared/src/main/scala/shapeless/ops/hlists.scala. Counted over 25 of the 73 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 19 Orphaned file finding(s) in Knowledge Freshness — start with ShapelessPlugin.scala (2), nat.scala, lenses.scala. — One of this dimension's main actionable groups (19 recommendation-level).
- Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with hlists.scala, tuples.scala, generic.scala. — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 1 Concentrated knowledge decay 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 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 — start with REDACTED. — 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
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
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. (×2) — core/shared/src/main/scala/shapeless/ops/coproduct.scala:1284, core/shared/src/main/scala/shapeless/ops/hlists.scala:717
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)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
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
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 5181 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.
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.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF2 · Allocation hygiene
What to do
- Raise allocation-aware density on the hot paths — currently 13 use(s) across 19,102 production line(s) (~0.7/1k). More of the idioms below on the allocation-heavy paths climbs this toward 10.
- Scala: on hot paths, make small wrappers value classes (extends AnyVal), @specialized generic code over primitives, use primitive collections, and presize builders.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
- No build over this repository's 73 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 | 73% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 90% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 48% | Weak — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 52% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 79% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 63% | Adequate | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 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 — 60 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: 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.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- C1 Data Protection — 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 — ~16696 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 — 1 direct sbt declaration(s) were read, but the outdated signal needs repo1.maven.org, which publishes none of these artifacts, 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 1 pinned sbt dependency coordinate(s) were read from its 2 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.
- D21 Naming Consistency — Naming consistency is measured on C# only; Scala not measured.
- 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+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .scala, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.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) — 1 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.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- 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 (2 signals for this style, 2 needed — the count is met but a required primary signal is absent): 176 value object(s); 1 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- 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 1 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'.
- P2 Observability — This repository's JVM source (1 module(s), 71 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- 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: 69 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.
- 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
- 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 — 9 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 31 finding(s)
- FixmeComment core/shared/src/test/scala/shapeless/labelledgeneric.scala:131
- FixmeComment core/shared/src/test/scala/shapeless/product.scala:23
- FixmeComment core/shared/src/test/scala/shapeless/product.scala:70
- FixmeComment core/shared/src/test/scala/shapeless/product.scala:117
- FixmeComment core/shared/src/test/scala/shapeless/product.scala:167
- FixmeComment core/shared/src/test/scala/shapeless/product.scala:228
- FixmeComment core/shared/src/test/scala/shapeless/product.scala:288
- TooManyMethods: HListOps core/shared/src/main/scala/shapeless/syntax/hlists.scala:30
- TooManyMethods: TupleOps core/shared/src/main/scala/shapeless/syntax/std/tuples.scala:30
- TooManyMethods: CaseClassMacros core/shared/src/main/scala/shapeless/generic.scala:275
- TooManyMethods: CoproductOps core/shared/src/main/scala/shapeless/syntax/coproduct.scala:28
- FileTooLong: ops/hlists.scala core/shared/src/main/scala/shapeless/ops/hlists.scala
- FileTooLong: ops/coproduct.scala core/shared/src/main/scala/shapeless/ops/coproduct.scala
- FileTooLong: ops/tuples.scala core/shared/src/main/scala/shapeless/ops/tuples.scala
- FileTooLong: shapeless/generic.scala core/shared/src/main/scala/shapeless/generic.scala
- Duplicated block (6 lines × 2) core/shared/src/main/scala/shapeless/lenses.scala:375
- Duplicated block (6 lines × 2) core/shared/src/main/scala/shapeless/ops/records.scala:178
- CaseClassMacros.ctorsOfAux (cyclomatic 23) core/shared/src/main/scala/shapeless/generic.scala:370
- TypeableMacros.dfltTypeableImpl (cyclomatic 19) core/shared/src/main/scala/shapeless/typeable.scala:316
- TodoComment core/shared/src/main/scala/shapeless/syntax/hlists.scala:615
- CaseClassMacros.ctorsOfAux (cognitive 63) core/shared/src/main/scala/shapeless/generic.scala:370
- TypeableMacros.dfltTypeableImpl (cognitive 23) core/shared/src/main/scala/shapeless/typeable.scala:316
- DefaultMacros.materialize (cognitive 21) core/shared/src/main/scala/shapeless/default.scala:214
- FromTo.of (cognitive 17) core/shared/src/main/scala/shapeless/generic.scala:844
- TypeableMacros.mkCaseClassTypeable (cognitive 16) core/shared/src/main/scala/shapeless/typeable.scala:386
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (5 lines × 2) plugin/src/main/scala_2.13+/shapeless/ShapelessPlugin.scala:43
- Duplicated block (15 lines × 2) examples/src/main/scala/shapeless/examples/sybclass.scala:47
- Low cohesion: GenericMacros (LCOM4 4) core/shared/src/main/scala/shapeless/generic.scala:928
Minor — 36 finding(s)
- Orphaned file core/shared/src/main/scala/shapeless/ops/nat.scala:1
- Orphaned file core/shared/src/main/scala/shapeless/lenses.scala:1
- Orphaned file core/shared/src/main/scala/shapeless/typeable.scala:1
- Orphaned file core/shared/src/main/scala/shapeless/annotation.scala:1
- Orphaned file project/Boilerplate.scala:1
- Orphaned file core/shared/src/main/scala/shapeless/generic1.scala:1
- Orphaned file core/shared/src/main/scala/shapeless/ops/zipper.scala:1
- Orphaned file core/shared/src/main/scala_2.13-/shapeless/LazyMacros.scala:1
- Orphaned file core/shared/src/main/scala/shapeless/poly.scala:1
- Orphaned file core/shared/src/main/scala/shapeless/constraints.scala:1
- Orphaned file core/shared/src/main/scala/shapeless/typeoperators.scala:1
- Orphaned file core/shared/src/main/scala/shapeless/coproduct.scala:1
- Orphaned file core/shared/src/main/scala_2.13-/shapeless/versionspecifics.scala:1
- Orphaned file plugin/src/main/scala_2.13+/shapeless/ShapelessPlugin.scala:1
- Orphaned file core/shared/src/main/scala/shapeless/ops/adjoin.scala:1
- Orphaned file core/shared/src/main/scala/shapeless/hmap.scala:1
- Orphaned file core/shared/src/main/scala/shapeless/ops/traversables.scala:1
- Orphaned file plugin/src/main/scala_2.13-/shapeless/ShapelessPlugin.scala:1
- Orphaned file core/shared/src/main/scala/shapeless/unwrapped.scala:1
- Most significant orphaned file core/shared/src/main/scala/shapeless/ops/hlists.scala:1
- Most significant orphaned file core/shared/src/main/scala/shapeless/ops/tuples.scala:1
- Most significant orphaned file core/shared/src/main/scala/shapeless/generic.scala:1
- Blanket warning suppression core/shared/src/main/scala/shapeless/ops/coproduct.scala:1284
- Blanket warning suppression core/shared/src/main/scala/shapeless/ops/hlists.scala:717
- No ADRs found
- Projects may be oversized for their cohesion
- Concentrated knowledge decay
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- No SAST
- No release approval gate
- No changelog
- Duplicated predicate plugin/src/main/scala_2.13+/shapeless/ShapelessPlugin.scala:47
- 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/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-879f8d7626384be08d80b258dc043d80/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-879f8d7626384be08d80b258dc043d80/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 9 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-45a7bbaa8be740d4b4986361d4dc3792 | 0 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 1 file(s) — `core/shared/src/main/scala/shapeless/package.scala` — 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 | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-45a7bbaa8be740d4b4986361d4dc3792 | 0 | artifacts/raw/osv-scanner.json |