Executive summary
j-mie6/parsley falls short of our standard for production, held back most by its Security and Compliance lens, the code's security and compliance. It scores 68 out of 100 and is rated Adequate, and all 34 of its critical findings are security problems in the build pipeline.
Security and Compliance, at 65, is the weakest lens by a small margin, and the weakest lens counts most in the score. The best first step is restricting the build's access tokens, worth about 2 points. Pinning the build actions that handle secrets comes next, worth about 1 point.
Thirty-two pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One secret can leak from the build pipeline. Pinning each tool to an exact version and limiting the secret to its own step would close both risks. Correcting the flagged pipeline settings would fix the weakness in the build pipeline's configuration.
The product code is 28,423 lines, about €42,000 to rebuild. The check for the health of its packages couldn't finish, so that result is missing, not a clean pass.
The weakest lenses score close to each other, so improving any of them moves the score.
Rebuild cost: about €42,000 · Estimate
| Cost to rebuild | €14,000 to €71,000, for 235 to 746 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 | ×1.0 at a score of 68. 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: 28,423 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 debugger.frontend | 2 internal.collection.immutable | 3 internal.collection.mutable | 4 internal.deepembedding | 5 token.descriptions.numeric | 6 debug | 7 state | 8 token.predicate | 9 internal.deepembedding.backend | 10 token.descriptions | 11 token.descriptions.text | 12 internal.deepembedding.singletons | 13 internal.deepembedding.singletons.token | 14 internal.deepembedding.frontend | 15 errors | 16 internal.errors | 17 internal.machine.errors | 18 internal.machine.errors.TrivialErrorBuilder | 19 token.errors | 20 parsley | 21 debugger | 22 debugger.combinator | 23 errors.combinator | 24 errors.patterns | 25 errors.tokenextractors | 26 internal.machine | 27 token | 28 token.names | 29 token.numeric | 30 token.symbol | 31 token.text | 32 debugger.util | 33 internal.machine.instructions | 34 token.Lexer | 35 token.Lexer.lexeme | 36 debugger.internal | 37 internal.machine.instructions.token | 38 internal.machine.stacks | 39 internal.deepembedding.frontend.debugger | 40 internal.deepembedding.frontend.debugger.helper |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 debugger.frontend | ||||||||||||||||||||||||||||||||||||||||
| 2 internal.collection.immutable | ||||||||||||||||||||||||||||||||||||||||
| 3 internal.collection.mutable | ||||||||||||||||||||||||||||||||||||||||
| 4 internal.deepembedding | ||||||||||||||||||||||||||||||||||||||||
| 5 token.descriptions.numeric | ||||||||||||||||||||||||||||||||||||||||
| 6 debug | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 7 state | 2 | |||||||||||||||||||||||||||||||||||||||
| 8 token.predicate | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 internal.deepembedding.backend | 4 | 2 | ||||||||||||||||||||||||||||||||||||||
| 10 token.descriptions | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 11 token.descriptions.text | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 internal.deepembedding.singletons | 1 | 4 | 24 | 5 | ||||||||||||||||||||||||||||||||||||
| 13 internal.deepembedding.singletons.token | 5 | 5 | 2 | |||||||||||||||||||||||||||||||||||||
| 14 internal.deepembedding.frontend | 2 | 1 | 2 | 4 | 7 | 2 | 2 | 39 | 10 | 2 | 2 | 6 | ||||||||||||||||||||||||||||
| 15 errors | 3 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 16 internal.errors | 3 | |||||||||||||||||||||||||||||||||||||||
| 17 internal.machine.errors | 18 | |||||||||||||||||||||||||||||||||||||||
| 18 internal.machine.errors.TrivialErrorBuilder | 4 | 4 | ||||||||||||||||||||||||||||||||||||||
| 19 token.errors | 3 | 6 | 21 | |||||||||||||||||||||||||||||||||||||
| 20 parsley | 2 | |||||||||||||||||||||||||||||||||||||||
| 21 debugger | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 22 debugger.combinator | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 23 errors.combinator | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 24 errors.patterns | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 25 errors.tokenextractors | 4 | 1 | ||||||||||||||||||||||||||||||||||||||
| 26 internal.machine | 4 | 3 | 1 | |||||||||||||||||||||||||||||||||||||
| 27 token | 2 | |||||||||||||||||||||||||||||||||||||||
| 28 token.names | 3 | 3 | ||||||||||||||||||||||||||||||||||||||
| 29 token.numeric | 3 | 4 | 13 | |||||||||||||||||||||||||||||||||||||
| 30 token.symbol | 1 | 4 | ||||||||||||||||||||||||||||||||||||||
| 31 token.text | 3 | 1 | 4 | 10 | ||||||||||||||||||||||||||||||||||||
| 32 debugger.util | 2 | 1 | 3 | |||||||||||||||||||||||||||||||||||||
| 33 internal.machine.instructions | 3 | 9 | 8 | 106 | ||||||||||||||||||||||||||||||||||||
| 34 token.Lexer | 1 | 2 | 1 | 2 | 6 | 2 | 4 | |||||||||||||||||||||||||||||||||
| 35 token.Lexer.lexeme | 2 | 3 | 2 | |||||||||||||||||||||||||||||||||||||
| 36 debugger.internal | 2 | 3 | 1 | |||||||||||||||||||||||||||||||||||||
| 37 internal.machine.instructions.token | 2 | 4 | 2 | 1 | 11 | 3 | ||||||||||||||||||||||||||||||||||
| 38 internal.machine.stacks | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 39 internal.deepembedding.frontend.debugger | 2 | 8 | 1 | |||||||||||||||||||||||||||||||||||||
| 40 internal.deepembedding.frontend.debugger.helper | 15 | 1 |
6→15 debug uses errors part of a loop✕
- Connections
- 1 pair of types, where a type in debug uses a type in errors.
- The types involved
parsley.debug.DebugCombinators→parsley.errors.ErrorBuilder
- Direction
- debug uses errors, so a change to errors can break debug, while a change to debug can't break errors.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→20 debug uses parsley part of a loop✕
- Connections
- 1 pair of types, where a type in debug uses a type in parsley.
- The types involved
parsley.debug.DebugCombinators→parsley.Parsley
- Direction
- debug uses parsley, so a change to parsley can break debug, while a change to debug can't break parsley.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→20 state uses parsley part of a loop✕
- Connections
- 2 pairs of types, where a type in state uses a type in parsley.
- The types involved
parsley.state.RefMaker→parsley.Parsleyparsley.state.StateCombinators→parsley.Parsley
- Direction
- state uses parsley, so a change to parsley can break state, while a change to state can't break parsley.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→20 token.predicate uses parsley part of a loop✕
- Connections
- 1 pair of types, where a type in token.predicate uses a type in parsley.
- The types involved
parsley.token.predicate.CharPredicate→parsley.Parsley
- Direction
- token.predicate uses parsley, so a change to parsley can break token.predicate, while a change to token.predicate can't break parsley.
- 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→3 internal.deepembedding.backend uses internal.collection.mutable✕
- Connections
- 4 pairs of types, where a type in internal.deepembedding.backend uses a type in internal.collection.mutable.
- The types involved
parsley.internal.deepembedding.backend.*>→parsley.internal.collection.mutable.DoublyLinkedListparsley.internal.deepembedding.backend.<*→parsley.internal.collection.mutable.DoublyLinkedListparsley.internal.deepembedding.backend.Choice→parsley.internal.collection.mutable.SinglyLinkedListparsley.internal.deepembedding.backend.Seq→parsley.internal.collection.mutable.DoublyLinkedList
- Direction
- internal.deepembedding.backend uses internal.collection.mutable, so a change to internal.collection.mutable can break internal.deepembedding.backend, while a change to internal.deepembedding.backend can't break internal.collection.mutable.
- Position
- Below the diagonal: internal.deepembedding.backend uses a module listed above it, which is the healthy direction.
9→7 internal.deepembedding.backend uses state✕
- Connections
- 2 pairs of types, where a type in internal.deepembedding.backend uses a type in state.
- The types involved
parsley.internal.deepembedding.backend.CodeGenState→parsley.state.Refparsley.internal.deepembedding.backend.StrictParsley→parsley.state.Ref
- Direction
- internal.deepembedding.backend uses state, so a change to state can break internal.deepembedding.backend, while a change to internal.deepembedding.backend can't break state.
- Position
- Below the diagonal: internal.deepembedding.backend uses a module listed above it, which is the healthy direction.
10→2 token.descriptions uses internal.collection.immutable✕
- Connections
- 1 pair of types, where a type in token.descriptions uses a type in internal.collection.immutable.
- The types involved
parsley.token.descriptions.SymbolDesc→parsley.internal.collection.immutable.Trie
- Direction
- token.descriptions uses internal.collection.immutable, so a change to internal.collection.immutable can break token.descriptions, while a change to token.descriptions can't break internal.collection.immutable.
- Position
- Below the diagonal: token.descriptions uses a module listed above it, which is the healthy direction.
10→8 token.descriptions uses token.predicate✕
- Connections
- 2 pairs of types, where a type in token.descriptions uses a type in token.predicate.
- The types involved
parsley.token.descriptions.NameDesc→parsley.token.predicate.CharPredicateparsley.token.descriptions.SpaceDesc→parsley.token.predicate.CharPredicate
- Direction
- token.descriptions uses token.predicate, so a change to token.predicate can break token.descriptions, while a change to token.descriptions can't break token.predicate.
- Position
- Below the diagonal: token.descriptions uses a module listed above it, which is the healthy direction.
11→8 token.descriptions.text uses token.predicate✕
- Connections
- 1 pair of types, where a type in token.descriptions.text uses a type in token.predicate.
- The types involved
parsley.token.descriptions.text.TextDesc→parsley.token.predicate.CharPredicate
- Direction
- token.descriptions.text uses token.predicate, so a change to token.predicate can break token.descriptions.text, while a change to token.descriptions.text can't break token.predicate.
- Position
- Below the diagonal: token.descriptions.text uses a module listed above it, which is the healthy direction.
12→7 internal.deepembedding.singletons uses state✕
- Connections
- 1 pair of types, where a type in internal.deepembedding.singletons uses a type in state.
- The types involved
parsley.internal.deepembedding.singletons.Modify→parsley.state.Ref
- Direction
- internal.deepembedding.singletons uses state, so a change to state can break internal.deepembedding.singletons, while a change to internal.deepembedding.singletons can't break state.
- Position
- Below the diagonal: internal.deepembedding.singletons uses a module listed above it, which is the healthy direction.
12→9 internal.deepembedding.singletons uses internal.deepembedding.backend✕
- Connections
- 4 pairs of types, where a type in internal.deepembedding.singletons uses a type in internal.deepembedding.backend.
- The types involved
parsley.internal.deepembedding.singletons.Empty→parsley.internal.deepembedding.backend.MZeroparsley.internal.deepembedding.singletons.Fail→parsley.internal.deepembedding.backend.MZeroparsley.internal.deepembedding.singletons.StringTok→parsley.internal.deepembedding.backend.StrictParsleyparsley.internal.deepembedding.singletons.Unexpected→parsley.internal.deepembedding.backend.MZero
- Direction
- internal.deepembedding.singletons uses internal.deepembedding.backend, so a change to internal.deepembedding.backend can break internal.deepembedding.singletons, while a change to internal.deepembedding.singletons can't break internal.deepembedding.backend.
- Position
- Below the diagonal: internal.deepembedding.singletons uses a module listed above it, which is the healthy direction.
12→14 internal.deepembedding.singletons uses internal.deepembedding.frontend part of a loop✕
- Connections
- 24 pairs of types, where a type in internal.deepembedding.singletons uses a type in internal.deepembedding.frontend.
- The types involved
parsley.internal.deepembedding.singletons.CharTok→parsley.internal.deepembedding.frontend.LazyParsleyIVisitorparsley.internal.deepembedding.singletons.Col→parsley.internal.deepembedding.frontend.LazyParsleyIVisitorparsley.internal.deepembedding.singletons.Comment→parsley.internal.deepembedding.frontend.LazyParsleyIVisitorparsley.internal.deepembedding.singletons.Empty→parsley.internal.deepembedding.frontend.LazyParsleyIVisitorparsley.internal.deepembedding.singletons.Eof→parsley.internal.deepembedding.frontend.LazyParsleyIVisitorparsley.internal.deepembedding.singletons.Fail→parsley.internal.deepembedding.frontend.LazyParsleyIVisitorparsley.internal.deepembedding.singletons.Fresh→parsley.internal.deepembedding.frontend.LazyParsleyIVisitorparsley.internal.deepembedding.singletons.Get→parsley.internal.deepembedding.frontend.LazyParsleyIVisitorparsley.internal.deepembedding.singletons.Line→parsley.internal.deepembedding.frontend.LazyParsleyIVisitorparsley.internal.deepembedding.singletons.Modify→parsley.internal.deepembedding.frontend.LazyParsleyIVisitorparsley.internal.deepembedding.singletons.Modify→parsley.internal.deepembedding.frontend.UsesRefparsley.internal.deepembedding.singletons.NonSpecific→parsley.internal.deepembedding.frontend.LazyParsleyIVisitorparsley.internal.deepembedding.singletons.Offset→parsley.internal.deepembedding.frontend.LazyParsleyIVisitorparsley.internal.deepembedding.singletons.Pure→parsley.internal.deepembedding.frontend.LazyParsleyIVisitorparsley.internal.deepembedding.singletons.Satisfy→parsley.internal.deepembedding.frontend.LazyParsleyIVisitorparsley.internal.deepembedding.singletons.Sign→parsley.internal.deepembedding.frontend.LazyParsleyIVisitorparsley.internal.deepembedding.singletons.SkipComments→parsley.internal.deepembedding.frontend.LazyParsleyIVisitorparsley.internal.deepembedding.singletons.SpecialisedGen→parsley.internal.deepembedding.frontend.LazyParsleyIVisitorparsley.internal.deepembedding.singletons.StringTok→parsley.internal.deepembedding.frontend.LazyParsleyIVisitorparsley.internal.deepembedding.singletons.SupplementaryCharTok→parsley.internal.deepembedding.frontend.LazyParsleyIVisitorparsley.internal.deepembedding.singletons.Unexpected→parsley.internal.deepembedding.frontend.LazyParsleyIVisitorparsley.internal.deepembedding.singletons.UniSatisfy→parsley.internal.deepembedding.frontend.LazyParsleyIVisitorparsley.internal.deepembedding.singletons.VanillaGen→parsley.internal.deepembedding.frontend.LazyParsleyIVisitorparsley.internal.deepembedding.singletons.WhiteSpace→parsley.internal.deepembedding.frontend.LazyParsleyIVisitor
- Direction
- internal.deepembedding.singletons uses internal.deepembedding.frontend, so a change to internal.deepembedding.frontend can break internal.deepembedding.singletons, while a change to internal.deepembedding.singletons can't break internal.deepembedding.frontend.
- 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→19 internal.deepembedding.singletons uses token.errors part of a loop✕
- Connections
- 5 pairs of types, where a type in internal.deepembedding.singletons uses a type in token.errors.
- The types involved
parsley.internal.deepembedding.singletons.CharTok→parsley.token.errors.LabelConfigparsley.internal.deepembedding.singletons.Satisfy→parsley.token.errors.LabelConfigparsley.internal.deepembedding.singletons.StringTok→parsley.token.errors.LabelConfigparsley.internal.deepembedding.singletons.SupplementaryCharTok→parsley.token.errors.LabelConfigparsley.internal.deepembedding.singletons.UniSatisfy→parsley.token.errors.LabelConfig
- Direction
- internal.deepembedding.singletons uses token.errors, so a change to token.errors can break internal.deepembedding.singletons, while a change to internal.deepembedding.singletons can't break token.errors.
- 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→12 internal.deepembedding.singletons.token uses internal.deepembedding.singletons✕
- Connections
- 5 pairs of types, where a type in internal.deepembedding.singletons.token uses a type in internal.deepembedding.singletons.
- The types involved
parsley.internal.deepembedding.singletons.token.EscapeAtMost→parsley.internal.deepembedding.singletons.Singletonparsley.internal.deepembedding.singletons.token.EscapeMapped→parsley.internal.deepembedding.singletons.Singletonparsley.internal.deepembedding.singletons.token.EscapeOneOfExactly→parsley.internal.deepembedding.singletons.Singletonparsley.internal.deepembedding.singletons.token.SoftKeyword→parsley.internal.deepembedding.singletons.Singletonparsley.internal.deepembedding.singletons.token.SoftOperator→parsley.internal.deepembedding.singletons.Singleton
- Direction
- internal.deepembedding.singletons.token uses internal.deepembedding.singletons, so a change to internal.deepembedding.singletons can break internal.deepembedding.singletons.token, while a change to internal.deepembedding.singletons.token can't break internal.deepembedding.singletons.
- Position
- Below the diagonal: internal.deepembedding.singletons.token uses a module listed above it, which is the healthy direction.
13→14 internal.deepembedding.singletons.token uses internal.deepembedding.frontend part of a loop✕
- Connections
- 5 pairs of types, where a type in internal.deepembedding.singletons.token uses a type in internal.deepembedding.frontend.
- The types involved
parsley.internal.deepembedding.singletons.token.EscapeAtMost→parsley.internal.deepembedding.frontend.LazyParsleyIVisitorparsley.internal.deepembedding.singletons.token.EscapeMapped→parsley.internal.deepembedding.frontend.LazyParsleyIVisitorparsley.internal.deepembedding.singletons.token.EscapeOneOfExactly→parsley.internal.deepembedding.frontend.LazyParsleyIVisitorparsley.internal.deepembedding.singletons.token.SoftKeyword→parsley.internal.deepembedding.frontend.LazyParsleyIVisitorparsley.internal.deepembedding.singletons.token.SoftOperator→parsley.internal.deepembedding.frontend.LazyParsleyIVisitor
- Direction
- internal.deepembedding.singletons.token uses internal.deepembedding.frontend, so a change to internal.deepembedding.frontend can break internal.deepembedding.singletons.token, while a change to internal.deepembedding.singletons.token can't break internal.deepembedding.frontend.
- 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→19 internal.deepembedding.singletons.token uses token.errors part of a loop✕
- Connections
- 2 pairs of types, where a type in internal.deepembedding.singletons.token uses a type in token.errors.
- The types involved
parsley.internal.deepembedding.singletons.token.SoftKeyword→parsley.token.errors.LabelConfigparsley.internal.deepembedding.singletons.token.SoftOperator→parsley.token.errors.LabelConfig
- Direction
- internal.deepembedding.singletons.token uses token.errors, so a change to token.errors can break internal.deepembedding.singletons.token, while a change to internal.deepembedding.singletons.token can't break token.errors.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→2 internal.deepembedding.frontend uses internal.collection.immutable✕
- Connections
- 2 pairs of types, where a type in internal.deepembedding.frontend uses a type in internal.collection.immutable.
- The types involved
parsley.internal.deepembedding.frontend.GenericLazyParsleyIVisitor→parsley.internal.collection.immutable.Trieparsley.internal.deepembedding.frontend.LazyParsleyIVisitor→parsley.internal.collection.immutable.Trie
- Direction
- internal.deepembedding.frontend uses internal.collection.immutable, so a change to internal.collection.immutable can break internal.deepembedding.frontend, while a change to internal.deepembedding.frontend can't break internal.collection.immutable.
- Position
- Below the diagonal: internal.deepembedding.frontend uses a module listed above it, which is the healthy direction.
14→4 internal.deepembedding.frontend uses internal.deepembedding✕
- Connections
- 1 pair of types, where a type in internal.deepembedding.frontend uses a type in internal.deepembedding.
- The types involved
parsley.internal.deepembedding.frontend.LazyParsley→parsley.internal.deepembedding.ContOps
- Direction
- internal.deepembedding.frontend uses internal.deepembedding, so a change to internal.deepembedding can break internal.deepembedding.frontend, while a change to internal.deepembedding.frontend can't break internal.deepembedding.
- Position
- Below the diagonal: internal.deepembedding.frontend uses a module listed above it, which is the healthy direction.
14→5 internal.deepembedding.frontend uses token.descriptions.numeric✕
- Connections
- 2 pairs of types, where a type in internal.deepembedding.frontend uses a type in token.descriptions.numeric.
- The types involved
parsley.internal.deepembedding.frontend.GenericLazyParsleyIVisitor→parsley.token.descriptions.numeric.PlusSignPresenceparsley.internal.deepembedding.frontend.LazyParsleyIVisitor→parsley.token.descriptions.numeric.PlusSignPresence
- Direction
- internal.deepembedding.frontend uses token.descriptions.numeric, so a change to token.descriptions.numeric can break internal.deepembedding.frontend, while a change to internal.deepembedding.frontend can't break token.descriptions.numeric.
- Position
- Below the diagonal: internal.deepembedding.frontend uses a module listed above it, which is the healthy direction.
14→6 internal.deepembedding.frontend uses debug✕
- Connections
- 4 pairs of types, where a type in internal.deepembedding.frontend uses a type in debug.
- The types involved
parsley.internal.deepembedding.frontend.GenericLazyParsleyIVisitor→parsley.debug.Breakpointparsley.internal.deepembedding.frontend.GenericLazyParsleyIVisitor→parsley.debug.Profilerparsley.internal.deepembedding.frontend.LazyParsleyIVisitor→parsley.debug.Breakpointparsley.internal.deepembedding.frontend.LazyParsleyIVisitor→parsley.debug.Profiler
- Direction
- internal.deepembedding.frontend uses debug, so a change to debug can break internal.deepembedding.frontend, while a change to internal.deepembedding.frontend can't break debug.
- Position
- Below the diagonal: internal.deepembedding.frontend uses a module listed above it, which is the healthy direction.
14→7 internal.deepembedding.frontend uses state✕
- Connections
- 7 pairs of types, where a type in internal.deepembedding.frontend uses a type in state.
- The types involved
parsley.internal.deepembedding.frontend.GenericLazyParsleyIVisitor→parsley.state.Refparsley.internal.deepembedding.frontend.LazyParsleyIVisitor→parsley.state.Refparsley.internal.deepembedding.frontend.LetFinderState→parsley.state.Refparsley.internal.deepembedding.frontend.Local→parsley.state.Refparsley.internal.deepembedding.frontend.NewReg→parsley.state.Refparsley.internal.deepembedding.frontend.Put→parsley.state.Refparsley.internal.deepembedding.frontend.UsesRef→parsley.state.Ref
- Direction
- internal.deepembedding.frontend uses state, so a change to state can break internal.deepembedding.frontend, while a change to internal.deepembedding.frontend can't break state.
- Position
- Below the diagonal: internal.deepembedding.frontend uses a module listed above it, which is the healthy direction.
14→8 internal.deepembedding.frontend uses token.predicate✕
- Connections
- 2 pairs of types, where a type in internal.deepembedding.frontend uses a type in token.predicate.
- The types involved
parsley.internal.deepembedding.frontend.GenericLazyParsleyIVisitor→parsley.token.predicate.CharPredicateparsley.internal.deepembedding.frontend.LazyParsleyIVisitor→parsley.token.predicate.CharPredicate
- Direction
- internal.deepembedding.frontend uses token.predicate, so a change to token.predicate can break internal.deepembedding.frontend, while a change to internal.deepembedding.frontend can't break token.predicate.
- Position
- Below the diagonal: internal.deepembedding.frontend uses a module listed above it, which is the healthy direction.
14→10 internal.deepembedding.frontend uses token.descriptions✕
- Connections
- 2 pairs of types, where a type in internal.deepembedding.frontend uses a type in token.descriptions.
- The types involved
parsley.internal.deepembedding.frontend.GenericLazyParsleyIVisitor→parsley.token.descriptions.SpaceDescparsley.internal.deepembedding.frontend.LazyParsleyIVisitor→parsley.token.descriptions.SpaceDesc
- Direction
- internal.deepembedding.frontend uses token.descriptions, so a change to token.descriptions can break internal.deepembedding.frontend, while a change to internal.deepembedding.frontend can't break token.descriptions.
- Position
- Below the diagonal: internal.deepembedding.frontend uses a module listed above it, which is the healthy direction.
14→12 internal.deepembedding.frontend uses internal.deepembedding.singletons✕
- Connections
- 39 pairs of types, where a type in internal.deepembedding.frontend uses a type in internal.deepembedding.singletons. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
parsley.internal.deepembedding.frontend.GenericLazyParsleyIVisitor→parsley.internal.deepembedding.singletons.CharTokparsley.internal.deepembedding.frontend.GenericLazyParsleyIVisitor→parsley.internal.deepembedding.singletons.Commentparsley.internal.deepembedding.frontend.GenericLazyParsleyIVisitor→parsley.internal.deepembedding.singletons.Emptyparsley.internal.deepembedding.frontend.GenericLazyParsleyIVisitor→parsley.internal.deepembedding.singletons.Failparsley.internal.deepembedding.frontend.GenericLazyParsleyIVisitor→parsley.internal.deepembedding.singletons.Freshparsley.internal.deepembedding.frontend.GenericLazyParsleyIVisitor→parsley.internal.deepembedding.singletons.Getparsley.internal.deepembedding.frontend.GenericLazyParsleyIVisitor→parsley.internal.deepembedding.singletons.Modifyparsley.internal.deepembedding.frontend.GenericLazyParsleyIVisitor→parsley.internal.deepembedding.singletons.NonSpecificparsley.internal.deepembedding.frontend.GenericLazyParsleyIVisitor→parsley.internal.deepembedding.singletons.Pureparsley.internal.deepembedding.frontend.GenericLazyParsleyIVisitor→parsley.internal.deepembedding.singletons.Satisfyparsley.internal.deepembedding.frontend.GenericLazyParsleyIVisitor→parsley.internal.deepembedding.singletons.Signparsley.internal.deepembedding.frontend.GenericLazyParsleyIVisitor→parsley.internal.deepembedding.singletons.Singletonparsley.internal.deepembedding.frontend.GenericLazyParsleyIVisitor→parsley.internal.deepembedding.singletons.SkipCommentsparsley.internal.deepembedding.frontend.GenericLazyParsleyIVisitor→parsley.internal.deepembedding.singletons.SpecialisedGenparsley.internal.deepembedding.frontend.GenericLazyParsleyIVisitor→parsley.internal.deepembedding.singletons.StringTokparsley.internal.deepembedding.frontend.GenericLazyParsleyIVisitor→parsley.internal.deepembedding.singletons.SupplementaryCharTokparsley.internal.deepembedding.frontend.GenericLazyParsleyIVisitor→parsley.internal.deepembedding.singletons.Unexpectedparsley.internal.deepembedding.frontend.GenericLazyParsleyIVisitor→parsley.internal.deepembedding.singletons.UniSatisfyparsley.internal.deepembedding.frontend.GenericLazyParsleyIVisitor→parsley.internal.deepembedding.singletons.VanillaGenparsley.internal.deepembedding.frontend.GenericLazyParsleyIVisitor→parsley.internal.deepembedding.singletons.WhiteSpaceparsley.internal.deepembedding.frontend.LazyParsleyIVisitor→parsley.internal.deepembedding.singletons.CharTokparsley.internal.deepembedding.frontend.LazyParsleyIVisitor→parsley.internal.deepembedding.singletons.Commentparsley.internal.deepembedding.frontend.LazyParsleyIVisitor→parsley.internal.deepembedding.singletons.Emptyparsley.internal.deepembedding.frontend.LazyParsleyIVisitor→parsley.internal.deepembedding.singletons.Failparsley.internal.deepembedding.frontend.LazyParsleyIVisitor→parsley.internal.deepembedding.singletons.Fresh
- Direction
- internal.deepembedding.frontend uses internal.deepembedding.singletons, so a change to internal.deepembedding.singletons can break internal.deepembedding.frontend, while a change to internal.deepembedding.frontend can't break internal.deepembedding.singletons.
- Position
- Below the diagonal: internal.deepembedding.frontend uses a module listed above it, which is the healthy direction.
14→13 internal.deepembedding.frontend uses internal.deepembedding.singletons.token✕
- Connections
- 10 pairs of types, where a type in internal.deepembedding.frontend uses a type in internal.deepembedding.singletons.token.
- The types involved
parsley.internal.deepembedding.frontend.GenericLazyParsleyIVisitor→parsley.internal.deepembedding.singletons.token.EscapeAtMostparsley.internal.deepembedding.frontend.GenericLazyParsleyIVisitor→parsley.internal.deepembedding.singletons.token.EscapeMappedparsley.internal.deepembedding.frontend.GenericLazyParsleyIVisitor→parsley.internal.deepembedding.singletons.token.EscapeOneOfExactlyparsley.internal.deepembedding.frontend.GenericLazyParsleyIVisitor→parsley.internal.deepembedding.singletons.token.SoftKeywordparsley.internal.deepembedding.frontend.GenericLazyParsleyIVisitor→parsley.internal.deepembedding.singletons.token.SoftOperatorparsley.internal.deepembedding.frontend.LazyParsleyIVisitor→parsley.internal.deepembedding.singletons.token.EscapeAtMostparsley.internal.deepembedding.frontend.LazyParsleyIVisitor→parsley.internal.deepembedding.singletons.token.EscapeMappedparsley.internal.deepembedding.frontend.LazyParsleyIVisitor→parsley.internal.deepembedding.singletons.token.EscapeOneOfExactlyparsley.internal.deepembedding.frontend.LazyParsleyIVisitor→parsley.internal.deepembedding.singletons.token.SoftKeywordparsley.internal.deepembedding.frontend.LazyParsleyIVisitor→parsley.internal.deepembedding.singletons.token.SoftOperator
- Direction
- internal.deepembedding.frontend uses internal.deepembedding.singletons.token, so a change to internal.deepembedding.singletons.token can break internal.deepembedding.frontend, while a change to internal.deepembedding.frontend can't break internal.deepembedding.singletons.token.
- Position
- Below the diagonal: internal.deepembedding.frontend uses a module listed above it, which is the healthy direction.
14→15 internal.deepembedding.frontend uses errors part of a loop✕
- Connections
- 2 pairs of types, where a type in internal.deepembedding.frontend uses a type in errors.
- The types involved
parsley.internal.deepembedding.frontend.GenericLazyParsleyIVisitor→parsley.errors.ErrorBuilderparsley.internal.deepembedding.frontend.LazyParsleyIVisitor→parsley.errors.ErrorBuilder
- Direction
- internal.deepembedding.frontend uses errors, so a change to errors can break internal.deepembedding.frontend, while a change to internal.deepembedding.frontend can't break errors.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→16 internal.deepembedding.frontend uses internal.errors part of a loop✕
- Connections
- 2 pairs of types, where a type in internal.deepembedding.frontend uses a type in internal.errors.
- The types involved
parsley.internal.deepembedding.frontend.GenericLazyParsleyIVisitor→parsley.internal.errors.CaretWidthparsley.internal.deepembedding.frontend.LazyParsleyIVisitor→parsley.internal.errors.CaretWidth
- Direction
- internal.deepembedding.frontend uses internal.errors, so a change to internal.errors can break internal.deepembedding.frontend, while a change to internal.deepembedding.frontend can't break internal.errors.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→19 internal.deepembedding.frontend uses token.errors part of a loop✕
- Connections
- 6 pairs of types, where a type in internal.deepembedding.frontend uses a type in token.errors.
- The types involved
parsley.internal.deepembedding.frontend.GenericLazyParsleyIVisitor→parsley.token.errors.ErrorConfigparsley.internal.deepembedding.frontend.GenericLazyParsleyIVisitor→parsley.token.errors.LabelConfigparsley.internal.deepembedding.frontend.GenericLazyParsleyIVisitor→parsley.token.errors.SpecialisedFilterConfigparsley.internal.deepembedding.frontend.LazyParsleyIVisitor→parsley.token.errors.ErrorConfigparsley.internal.deepembedding.frontend.LazyParsleyIVisitor→parsley.token.errors.LabelConfigparsley.internal.deepembedding.frontend.LazyParsleyIVisitor→parsley.token.errors.SpecialisedFilterConfig
- Direction
- internal.deepembedding.frontend uses token.errors, so a change to token.errors can break internal.deepembedding.frontend, while a change to internal.deepembedding.frontend can't break token.errors.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→14 errors uses internal.deepembedding.frontend✕
- Connections
- 3 pairs of types, where a type in errors uses a type in internal.deepembedding.frontend.
- The types involved
parsley.errors.ErrorGen→parsley.internal.deepembedding.frontend.LazyParsleyparsley.errors.SpecialisedGen→parsley.internal.deepembedding.frontend.LazyParsleyparsley.errors.VanillaGen→parsley.internal.deepembedding.frontend.LazyParsley
- Direction
- errors uses internal.deepembedding.frontend, so a change to internal.deepembedding.frontend can break errors, while a change to errors can't break internal.deepembedding.frontend.
- Position
- Below the diagonal: errors uses a module listed above it, which is the healthy direction.
15→16 errors uses internal.errors part of a loop✕
- Connections
- 1 pair of types, where a type in errors uses a type in internal.errors.
- The types involved
parsley.errors.combinator→parsley.internal.errors.CaretWidth
- Direction
- errors uses internal.errors, so a change to internal.errors can break errors, while a change to errors can't break internal.errors.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→20 errors uses parsley part of a loop✕
- Connections
- 2 pairs of types, where a type in errors uses a type in parsley.
- The types involved
parsley.errors.ErrorGen→parsley.Parsleyparsley.errors.combinator→parsley.Parsley
- Direction
- errors uses parsley, so a change to parsley can break errors, while a change to errors can't break parsley.
- 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→15 internal.errors uses errors✕
- Connections
- 3 pairs of types, where a type in internal.errors uses a type in errors.
- The types involved
parsley.internal.errors.FancyError→parsley.errors.ErrorBuilderparsley.internal.errors.ParseError→parsley.errors.ErrorBuilderparsley.internal.errors.TrivialError→parsley.errors.ErrorBuilder
- Direction
- internal.errors uses errors, so a change to errors can break internal.errors, while a change to internal.errors can't break errors.
- Position
- Below the diagonal: internal.errors uses a module listed above it, which is the healthy direction.
17→16 internal.machine.errors uses internal.errors✕
- Connections
- 18 pairs of types, where a type in internal.machine.errors uses a type in internal.errors.
- The types involved
parsley.internal.machine.errors.BaseError→parsley.internal.errors.ExpectItemparsley.internal.machine.errors.DefuncError→parsley.internal.errors.ParseErrorparsley.internal.machine.errors.DefuncHints→parsley.internal.errors.ExpectItemparsley.internal.machine.errors.EmptyError→parsley.internal.errors.ExpectItemparsley.internal.machine.errors.EmptyErrorWithReason→parsley.internal.errors.ExpectItemparsley.internal.machine.errors.ErrorItemBuilder→parsley.internal.errors.UnexpectItemparsley.internal.machine.errors.ExpectedError→parsley.internal.errors.ExpectItemparsley.internal.machine.errors.ExpectedErrorWithReason→parsley.internal.errors.ExpectItemparsley.internal.machine.errors.FancyDefuncError→parsley.internal.errors.FancyErrorparsley.internal.machine.errors.FancyErrorBuilder→parsley.internal.errors.CaretWidthparsley.internal.machine.errors.FancyErrorBuilder→parsley.internal.errors.FancyErrorparsley.internal.machine.errors.HintCollector→parsley.internal.errors.ExpectItemparsley.internal.machine.errors.TrivialDefuncError→parsley.internal.errors.TrivialErrorparsley.internal.machine.errors.TrivialErrorBuilder→parsley.internal.errors.ExpectItemparsley.internal.machine.errors.TrivialErrorBuilder→parsley.internal.errors.TrivialErrorparsley.internal.machine.errors.TrivialErrorBuilder→parsley.internal.errors.UnexpectDescparsley.internal.machine.errors.UnexpectedError→parsley.internal.errors.ExpectItemparsley.internal.machine.errors.UnexpectedError→parsley.internal.errors.UnexpectDesc
- Direction
- internal.machine.errors uses internal.errors, so a change to internal.errors can break internal.machine.errors, while a change to internal.machine.errors can't break internal.errors.
- Position
- Below the diagonal: internal.machine.errors uses a module listed above it, which is the healthy direction.
18→16 internal.machine.errors.TrivialErrorBuilder uses internal.errors✕
- Connections
- 4 pairs of types, where a type in internal.machine.errors.TrivialErrorBuilder uses a type in internal.errors.
- The types involved
parsley.internal.machine.errors.TrivialErrorBuilder.BuilderUnexpectItem→parsley.internal.errors.UnexpectItemparsley.internal.machine.errors.TrivialErrorBuilder.NoItem→parsley.internal.errors.UnexpectItemparsley.internal.machine.errors.TrivialErrorBuilder.Other→parsley.internal.errors.UnexpectItemparsley.internal.machine.errors.TrivialErrorBuilder.Raw→parsley.internal.errors.UnexpectItem
- Direction
- internal.machine.errors.TrivialErrorBuilder uses internal.errors, so a change to internal.errors can break internal.machine.errors.TrivialErrorBuilder, while a change to internal.machine.errors.TrivialErrorBuilder can't break internal.errors.
- Position
- Below the diagonal: internal.machine.errors.TrivialErrorBuilder uses a module listed above it, which is the healthy direction.
18→17 internal.machine.errors.TrivialErrorBuilder uses internal.machine.errors✕
- Connections
- 4 pairs of types, where a type in internal.machine.errors.TrivialErrorBuilder uses a type in internal.machine.errors.
- The types involved
parsley.internal.machine.errors.TrivialErrorBuilder.BuilderUnexpectItem→parsley.internal.machine.errors.ErrorItemBuilderparsley.internal.machine.errors.TrivialErrorBuilder.NoItem→parsley.internal.machine.errors.ErrorItemBuilderparsley.internal.machine.errors.TrivialErrorBuilder.Other→parsley.internal.machine.errors.ErrorItemBuilderparsley.internal.machine.errors.TrivialErrorBuilder.Raw→parsley.internal.machine.errors.ErrorItemBuilder
- Direction
- internal.machine.errors.TrivialErrorBuilder uses internal.machine.errors, so a change to internal.machine.errors can break internal.machine.errors.TrivialErrorBuilder, while a change to internal.machine.errors.TrivialErrorBuilder can't break internal.machine.errors.
- Position
- Below the diagonal: internal.machine.errors.TrivialErrorBuilder uses a module listed above it, which is the healthy direction.
19→16 token.errors uses internal.errors✕
- Connections
- 3 pairs of types, where a type in token.errors uses a type in internal.errors.
- The types involved
parsley.token.errors.Label→parsley.internal.errors.ExpectDescparsley.token.errors.LabelOps→parsley.internal.errors.ExpectDescparsley.token.errors.LabelOps→parsley.internal.errors.ExpectItem
- Direction
- token.errors uses internal.errors, so a change to internal.errors can break token.errors, while a change to token.errors can't break internal.errors.
- Position
- Below the diagonal: token.errors uses a module listed above it, which is the healthy direction.
19→17 token.errors uses internal.machine.errors✕
- Connections
- 6 pairs of types, where a type in token.errors uses a type in internal.machine.errors.
- The types involved
parsley.token.errors.BasicFilter→parsley.internal.machine.errors.DefuncErrorparsley.token.errors.Because→parsley.internal.machine.errors.DefuncErrorparsley.token.errors.FilterConfig→parsley.internal.machine.errors.DefuncErrorparsley.token.errors.SpecialisedMessage→parsley.internal.machine.errors.DefuncErrorparsley.token.errors.Unexpected→parsley.internal.machine.errors.DefuncErrorparsley.token.errors.UnexpectedBecause→parsley.internal.machine.errors.DefuncError
- Direction
- token.errors uses internal.machine.errors, so a change to internal.machine.errors can break token.errors, while a change to token.errors can't break internal.machine.errors.
- Position
- Below the diagonal: token.errors uses a module listed above it, which is the healthy direction.
19→20 token.errors uses parsley part of a loop✕
- Connections
- 21 pairs of types, where a type in token.errors uses a type in parsley.
- The types involved
parsley.token.errors.BadCharsFail→parsley.Parsleyparsley.token.errors.BadCharsReason→parsley.Parsleyparsley.token.errors.BasicFilter→parsley.Parsleyparsley.token.errors.Because→parsley.Parsleyparsley.token.errors.ConfigImplUntyped→parsley.Parsleyparsley.token.errors.FilterConfig→parsley.Parsleyparsley.token.errors.Hidden→parsley.Parsleyparsley.token.errors.Label→parsley.Parsleyparsley.token.errors.LabelAndReason→parsley.Parsleyparsley.token.errors.NotConfigured→parsley.Parsleyparsley.token.errors.PreventDotIsZeroConfig→parsley.Parsleyparsley.token.errors.Reason→parsley.Parsleyparsley.token.errors.SpecialisedMessage→parsley.Parsleyparsley.token.errors.Unexpected→parsley.Parsleyparsley.token.errors.UnexpectedBecause→parsley.Parsleyparsley.token.errors.UnexpectedZeroDot→parsley.Parsleyparsley.token.errors.UnexpectedZeroDotWithReason→parsley.Parsleyparsley.token.errors.Unverified→parsley.Parsleyparsley.token.errors.VerifiedBadChars→parsley.Parsleyparsley.token.errors.ZeroDotFail→parsley.Parsleyparsley.token.errors.ZeroDotReason→parsley.Parsley
- Direction
- token.errors uses parsley, so a change to parsley can break token.errors, while a change to token.errors can't break parsley.
- 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 parsley uses token.errors✕
- Connections
- 2 pairs of types, where a type in parsley uses a type in token.errors.
- The types involved
parsley.character→parsley.token.errors.LabelConfigparsley.unicode→parsley.token.errors.LabelConfig
- Direction
- parsley uses token.errors, so a change to token.errors can break parsley, while a change to parsley can't break token.errors.
- Position
- Below the diagonal: parsley uses a module listed above it, which is the healthy direction.
21→1 debugger uses debugger.frontend✕
- Connections
- 1 pair of types, where a type in debugger uses a type in debugger.frontend.
- The types involved
parsley.debugger.combinator→parsley.debugger.frontend.DebugFrontend
- Direction
- debugger uses debugger.frontend, so a change to debugger.frontend can break debugger, while a change to debugger can't break debugger.frontend.
- Position
- Below the diagonal: debugger uses a module listed above it, which is the healthy direction.
21→20 debugger uses parsley✕
- Connections
- 3 pairs of types, where a type in debugger uses a type in parsley.
- The types involved
parsley.debugger.ParseAttempt→parsley.Resultparsley.debugger.ParseAttempt→parsley.Successparsley.debugger.combinator→parsley.Parsley
- Direction
- debugger uses parsley, so a change to parsley can break debugger, while a change to debugger can't break parsley.
- Position
- Below the diagonal: debugger uses a module listed above it, which is the healthy direction.
22→1 debugger.combinator uses debugger.frontend✕
- Connections
- 1 pair of types, where a type in debugger.combinator uses a type in debugger.frontend.
- The types involved
parsley.debugger.combinator.DebuggerOps→parsley.debugger.frontend.DebugFrontend
- Direction
- debugger.combinator uses debugger.frontend, so a change to debugger.frontend can break debugger.combinator, while a change to debugger.combinator can't break debugger.frontend.
- Position
- Below the diagonal: debugger.combinator uses a module listed above it, which is the healthy direction.
22→20 debugger.combinator uses parsley✕
- Connections
- 1 pair of types, where a type in debugger.combinator uses a type in parsley.
- The types involved
parsley.debugger.combinator.DebuggerOps→parsley.Parsley
- Direction
- debugger.combinator uses parsley, so a change to parsley can break debugger.combinator, while a change to debugger.combinator can't break parsley.
- Position
- Below the diagonal: debugger.combinator uses a module listed above it, which is the healthy direction.
23→15 errors.combinator uses errors✕
- Connections
- 1 pair of types, where a type in errors.combinator uses a type in errors.
- The types involved
parsley.errors.combinator.ErrorMethods→parsley.errors.ErrorGen
- Direction
- errors.combinator uses errors, so a change to errors can break errors.combinator, while a change to errors.combinator can't break errors.
- Position
- Below the diagonal: errors.combinator uses a module listed above it, which is the healthy direction.
23→20 errors.combinator uses parsley✕
- Connections
- 1 pair of types, where a type in errors.combinator uses a type in parsley.
- The types involved
parsley.errors.combinator.ErrorMethods→parsley.Parsley
- Direction
- errors.combinator uses parsley, so a change to parsley can break errors.combinator, while a change to errors.combinator can't break parsley.
- Position
- Below the diagonal: errors.combinator uses a module listed above it, which is the healthy direction.
24→15 errors.patterns uses errors✕
- Connections
- 2 pairs of types, where a type in errors.patterns uses a type in errors.
- The types involved
parsley.errors.patterns.PreventativeErrors→parsley.errors.ErrorGenparsley.errors.patterns.VerifiedErrors→parsley.errors.ErrorGen
- Direction
- errors.patterns uses errors, so a change to errors can break errors.patterns, while a change to errors.patterns can't break errors.
- Position
- Below the diagonal: errors.patterns uses a module listed above it, which is the healthy direction.
24→20 errors.patterns uses parsley✕
- Connections
- 2 pairs of types, where a type in errors.patterns uses a type in parsley.
- The types involved
parsley.errors.patterns.PreventativeErrors→parsley.Parsleyparsley.errors.patterns.VerifiedErrors→parsley.Parsley
- Direction
- errors.patterns uses parsley, so a change to parsley can break errors.patterns, while a change to errors.patterns can't break parsley.
- Position
- Below the diagonal: errors.patterns uses a module listed above it, which is the healthy direction.
25→15 errors.tokenextractors uses errors✕
- Connections
- 4 pairs of types, where a type in errors.tokenextractors uses a type in errors.
- The types involved
parsley.errors.tokenextractors.LexToken→parsley.errors.Tokenparsley.errors.tokenextractors.MatchParserDemand→parsley.errors.Tokenparsley.errors.tokenextractors.SingleChar→parsley.errors.Tokenparsley.errors.tokenextractors.TillNextWhitespace→parsley.errors.Token
- Direction
- errors.tokenextractors uses errors, so a change to errors can break errors.tokenextractors, while a change to errors.tokenextractors can't break errors.
- Position
- Below the diagonal: errors.tokenextractors uses a module listed above it, which is the healthy direction.
25→20 errors.tokenextractors uses parsley✕
- Connections
- 1 pair of types, where a type in errors.tokenextractors uses a type in parsley.
- The types involved
parsley.errors.tokenextractors.LexToken→parsley.Parsley
- Direction
- errors.tokenextractors uses parsley, so a change to parsley can break errors.tokenextractors, while a change to errors.tokenextractors can't break parsley.
- Position
- Below the diagonal: errors.tokenextractors uses a module listed above it, which is the healthy direction.
26→16 internal.machine uses internal.errors✕
- Connections
- 4 pairs of types, where a type in internal.machine uses a type in internal.errors.
- The types involved
parsley.internal.machine.Context→parsley.internal.errors.CaretWidthparsley.internal.machine.Context→parsley.internal.errors.ExpectItemparsley.internal.machine.Context→parsley.internal.errors.LineBuilderparsley.internal.machine.Context→parsley.internal.errors.UnexpectDesc
- Direction
- internal.machine uses internal.errors, so a change to internal.errors can break internal.machine, while a change to internal.machine can't break internal.errors.
- Position
- Below the diagonal: internal.machine uses a module listed above it, which is the healthy direction.
26→17 internal.machine uses internal.machine.errors✕
- Connections
- 3 pairs of types, where a type in internal.machine uses a type in internal.machine.errors.
- The types involved
parsley.internal.machine.Context→parsley.internal.machine.errors.DefuncErrorparsley.internal.machine.Context→parsley.internal.machine.errors.DefuncHintsparsley.internal.machine.Context→parsley.internal.machine.errors.ErrorItemBuilder
- Direction
- internal.machine uses internal.machine.errors, so a change to internal.machine.errors can break internal.machine, while a change to internal.machine can't break internal.machine.errors.
- Position
- Below the diagonal: internal.machine uses a module listed above it, which is the healthy direction.
26→20 internal.machine uses parsley✕
- Connections
- 1 pair of types, where a type in internal.machine uses a type in parsley.
- The types involved
parsley.internal.machine.Context→parsley.Result
- Direction
- internal.machine uses parsley, so a change to parsley can break internal.machine, while a change to internal.machine can't break parsley.
- Position
- Below the diagonal: internal.machine uses a module listed above it, which is the healthy direction.
27→20 token uses parsley✕
- Connections
- 2 pairs of types, where a type in token uses a type in parsley.
- The types involved
parsley.token.Lexeme→parsley.Parsleyparsley.token.Lexer→parsley.Parsley
- Direction
- token uses parsley, so a change to parsley can break token, while a change to token can't break parsley.
- Position
- Below the diagonal: token uses a module listed above it, which is the healthy direction.
28→8 token.names uses token.predicate✕
- Connections
- 3 pairs of types, where a type in token.names uses a type in token.predicate.
- The types involved
parsley.token.names.ConcreteNames→parsley.token.predicate.CharPredicateparsley.token.names.LexemeNames→parsley.token.predicate.CharPredicateparsley.token.names.Names→parsley.token.predicate.CharPredicate
- Direction
- token.names uses token.predicate, so a change to token.predicate can break token.names, while a change to token.names can't break token.predicate.
- Position
- Below the diagonal: token.names uses a module listed above it, which is the healthy direction.
28→20 token.names uses parsley✕
- Connections
- 3 pairs of types, where a type in token.names uses a type in parsley.
- The types involved
parsley.token.names.ConcreteNames→parsley.Parsleyparsley.token.names.LexemeNames→parsley.Parsleyparsley.token.names.Names→parsley.Parsley
- Direction
- token.names uses parsley, so a change to parsley can break token.names, while a change to token.names can't break parsley.
- Position
- Below the diagonal: token.names uses a module listed above it, which is the healthy direction.
29→5 token.numeric uses token.descriptions.numeric✕
- Connections
- 3 pairs of types, where a type in token.numeric uses a type in token.descriptions.numeric.
- The types involved
parsley.token.numeric.Generic→parsley.token.descriptions.numeric.BreakCharDescparsley.token.numeric.Generic→parsley.token.descriptions.numeric.NumericDescparsley.token.numeric.Integer→parsley.token.descriptions.numeric.NumericDesc
- Direction
- token.numeric uses token.descriptions.numeric, so a change to token.descriptions.numeric can break token.numeric, while a change to token.numeric can't break token.descriptions.numeric.
- Position
- Below the diagonal: token.numeric uses a module listed above it, which is the healthy direction.
29→19 token.numeric uses token.errors✕
- Connections
- 4 pairs of types, where a type in token.numeric uses a type in token.errors.
- The types involved
parsley.token.numeric.Generic→parsley.token.errors.LabelConfigparsley.token.numeric.LexemeReal→parsley.token.errors.LabelWithExplainConfigparsley.token.numeric.Real→parsley.token.errors.LabelWithExplainConfigparsley.token.numeric.UnsignedReal→parsley.token.errors.LabelConfig
- Direction
- token.numeric uses token.errors, so a change to token.errors can break token.numeric, while a change to token.numeric can't break token.errors.
- Position
- Below the diagonal: token.numeric uses a module listed above it, which is the healthy direction.
29→20 token.numeric uses parsley✕
- Connections
- 13 pairs of types, where a type in token.numeric uses a type in parsley.
- The types involved
parsley.token.numeric.Combined→parsley.Parsleyparsley.token.numeric.Generic→parsley.Parsleyparsley.token.numeric.Integer→parsley.Parsleyparsley.token.numeric.LexemeCombined→parsley.Parsleyparsley.token.numeric.LexemeInteger→parsley.Parsleyparsley.token.numeric.LexemeReal→parsley.Parsleyparsley.token.numeric.Real→parsley.Parsleyparsley.token.numeric.SignedCombined→parsley.Parsleyparsley.token.numeric.SignedInteger→parsley.Parsleyparsley.token.numeric.SignedReal→parsley.Parsleyparsley.token.numeric.UnsignedCombined→parsley.Parsleyparsley.token.numeric.UnsignedInteger→parsley.Parsleyparsley.token.numeric.UnsignedReal→parsley.Parsley
- Direction
- token.numeric uses parsley, so a change to parsley can break token.numeric, while a change to token.numeric can't break parsley.
- Position
- Below the diagonal: token.numeric uses a module listed above it, which is the healthy direction.
30→19 token.symbol uses token.errors✕
- Connections
- 1 pair of types, where a type in token.symbol uses a type in token.errors.
- The types involved
parsley.token.symbol.Symbol→parsley.token.errors.LabelConfig
- Direction
- token.symbol uses token.errors, so a change to token.errors can break token.symbol, while a change to token.symbol can't break token.errors.
- Position
- Below the diagonal: token.symbol uses a module listed above it, which is the healthy direction.
30→20 token.symbol uses parsley✕
- Connections
- 4 pairs of types, where a type in token.symbol uses a type in parsley.
- The types involved
parsley.token.symbol.ConcreteSymbol→parsley.Parsleyparsley.token.symbol.ImplicitSymbol→parsley.Parsleyparsley.token.symbol.LexemeSymbol→parsley.Parsleyparsley.token.symbol.Symbol→parsley.Parsley
- Direction
- token.symbol uses parsley, so a change to parsley can break token.symbol, while a change to token.symbol can't break parsley.
- Position
- Below the diagonal: token.symbol uses a module listed above it, which is the healthy direction.
31→8 token.text uses token.predicate✕
- Connections
- 3 pairs of types, where a type in token.text uses a type in token.predicate.
- The types involved
parsley.token.text.EscapableCharacter→parsley.token.predicate.CharPredicateparsley.token.text.RawCharacter→parsley.token.predicate.CharPredicateparsley.token.text.StringCharacter→parsley.token.predicate.CharPredicate
- Direction
- token.text uses token.predicate, so a change to token.predicate can break token.text, while a change to token.text can't break token.predicate.
- Position
- Below the diagonal: token.text uses a module listed above it, which is the healthy direction.
31→11 token.text uses token.descriptions.text✕
- Connections
- 1 pair of types, where a type in token.text uses a type in token.descriptions.text.
- The types involved
parsley.token.text.Escape→parsley.token.descriptions.text.NumericEscape
- Direction
- token.text uses token.descriptions.text, so a change to token.descriptions.text can break token.text, while a change to token.text can't break token.descriptions.text.
- Position
- Below the diagonal: token.text uses a module listed above it, which is the healthy direction.
31→19 token.text uses token.errors✕
- Connections
- 4 pairs of types, where a type in token.text uses a type in token.errors.
- The types involved
parsley.token.text.ConcreteCharacter→parsley.token.errors.FilterConfigparsley.token.text.ConcreteCharacter→parsley.token.errors.LabelConfigparsley.token.text.ConcreteCharacter→parsley.token.errors.LabelWithExplainConfigparsley.token.text.StringCharacter→parsley.token.errors.ErrorConfig
- Direction
- token.text uses token.errors, so a change to token.errors can break token.text, while a change to token.text can't break token.errors.
- Position
- Below the diagonal: token.text uses a module listed above it, which is the healthy direction.
31→20 token.text uses parsley✕
- Connections
- 10 pairs of types, where a type in token.text uses a type in parsley.
- The types involved
parsley.token.text.Character→parsley.Parsleyparsley.token.text.ConcreteCharacter→parsley.Parsleyparsley.token.text.ConcreteString→parsley.Parsleyparsley.token.text.EscapableCharacter→parsley.Parsleyparsley.token.text.Escape→parsley.Parsleyparsley.token.text.LexemeCharacter→parsley.Parsleyparsley.token.text.LexemeString→parsley.Parsleyparsley.token.text.RawCharacter→parsley.Parsleyparsley.token.text.String→parsley.Parsleyparsley.token.text.StringCharacter→parsley.Parsley
- Direction
- token.text uses parsley, so a change to parsley can break token.text, while a change to token.text can't break parsley.
- Position
- Below the diagonal: token.text uses a module listed above it, which is the healthy direction.
32→14 debugger.util uses internal.deepembedding.frontend✕
- Connections
- 2 pairs of types, where a type in debugger.util uses a type in internal.deepembedding.frontend.
- The types involved
parsley.debugger.util.CollectorImpl→parsley.internal.deepembedding.frontend.LazyParsleyparsley.debugger.util.XDummyCollector→parsley.internal.deepembedding.frontend.LazyParsley
- Direction
- debugger.util uses internal.deepembedding.frontend, so a change to internal.deepembedding.frontend can break debugger.util, while a change to debugger.util can't break internal.deepembedding.frontend.
- Position
- Below the diagonal: debugger.util uses a module listed above it, which is the healthy direction.
32→20 debugger.util uses parsley✕
- Connections
- 1 pair of types, where a type in debugger.util uses a type in parsley.
- The types involved
parsley.debugger.util.Collector→parsley.Parsley
- Direction
- debugger.util uses parsley, so a change to parsley can break debugger.util, while a change to debugger.util can't break parsley.
- Position
- Below the diagonal: debugger.util uses a module listed above it, which is the healthy direction.
32→27 debugger.util uses token✕
- Connections
- 3 pairs of types, where a type in debugger.util uses a type in token.
- The types involved
parsley.debugger.util.Collector→parsley.token.Lexerparsley.debugger.util.CollectorImpl→parsley.token.Lexerparsley.debugger.util.XDummyCollector→parsley.token.Lexer
- Direction
- debugger.util uses token, so a change to token can break debugger.util, while a change to debugger.util can't break token.
- Position
- Below the diagonal: debugger.util uses a module listed above it, which is the healthy direction.
33→10 internal.machine.instructions uses token.descriptions✕
- Connections
- 3 pairs of types, where a type in internal.machine.instructions uses a type in token.descriptions.
- The types involved
parsley.internal.machine.instructions.TokenComment→parsley.token.descriptions.SpaceDescparsley.internal.machine.instructions.TokenSkipComments→parsley.token.descriptions.SpaceDescparsley.internal.machine.instructions.TokenWhiteSpace→parsley.token.descriptions.SpaceDesc
- Direction
- internal.machine.instructions uses token.descriptions, so a change to token.descriptions can break internal.machine.instructions, while a change to internal.machine.instructions can't break token.descriptions.
- Position
- Below the diagonal: internal.machine.instructions uses a module listed above it, which is the healthy direction.
33→16 internal.machine.instructions uses internal.errors✕
- Connections
- 9 pairs of types, where a type in internal.machine.instructions uses a type in internal.errors.
- The types involved
parsley.internal.machine.instructions.ErrLogData→parsley.internal.errors.ExpectItemparsley.internal.machine.instructions.JumpTable→parsley.internal.errors.ExpectItemparsley.internal.machine.instructions.TokenSign→parsley.internal.errors.ExpectItemparsley.internal.machine.instructions.TokenSkipComments→parsley.internal.errors.ExpectDescparsley.internal.machine.instructions.TokenSkipComments→parsley.internal.errors.ExpectItemparsley.internal.machine.instructions.TokenWhiteSpace→parsley.internal.errors.ExpectDescparsley.internal.machine.instructions.TokenWhiteSpace→parsley.internal.errors.ExpectItemparsley.internal.machine.instructions.WhiteSpaceLike→parsley.internal.errors.ExpectDescparsley.internal.machine.instructions.WhiteSpaceLike→parsley.internal.errors.ExpectItem
- Direction
- internal.machine.instructions uses internal.errors, so a change to internal.errors can break internal.machine.instructions, while a change to internal.machine.instructions can't break internal.errors.
- Position
- Below the diagonal: internal.machine.instructions uses a module listed above it, which is the healthy direction.
33→19 internal.machine.instructions uses token.errors✕
- Connections
- 8 pairs of types, where a type in internal.machine.instructions uses a type in token.errors.
- The types involved
parsley.internal.machine.instructions.CharTok→parsley.token.errors.LabelConfigparsley.internal.machine.instructions.Satisfies→parsley.token.errors.LabelConfigparsley.internal.machine.instructions.StringTok→parsley.token.errors.LabelConfigparsley.internal.machine.instructions.SupplementaryCharTok→parsley.token.errors.LabelConfigparsley.internal.machine.instructions.TokenComment→parsley.token.errors.ErrorConfigparsley.internal.machine.instructions.TokenSkipComments→parsley.token.errors.ErrorConfigparsley.internal.machine.instructions.TokenWhiteSpace→parsley.token.errors.ErrorConfigparsley.internal.machine.instructions.UniSat→parsley.token.errors.LabelConfig
- Direction
- internal.machine.instructions uses token.errors, so a change to token.errors can break internal.machine.instructions, while a change to internal.machine.instructions can't break token.errors.
- Position
- Below the diagonal: internal.machine.instructions uses a module listed above it, which is the healthy direction.
33→26 internal.machine.instructions uses internal.machine✕
- Connections
- 106 pairs of types, where a type in internal.machine.instructions uses a type in internal.machine. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
parsley.internal.machine.instructions.AlwaysRecoverWith→parsley.internal.machine.Contextparsley.internal.machine.instructions.AmendAndFail→parsley.internal.machine.Contextparsley.internal.machine.instructions.Apply→parsley.internal.machine.Contextparsley.internal.machine.instructions.ApplyReasonAndFail→parsley.internal.machine.Contextparsley.internal.machine.instructions.Call→parsley.internal.machine.Contextparsley.internal.machine.instructions.Case→parsley.internal.machine.Contextparsley.internal.machine.instructions.Catch→parsley.internal.machine.Contextparsley.internal.machine.instructions.ChainPost→parsley.internal.machine.Contextparsley.internal.machine.instructions.ChainPre→parsley.internal.machine.Contextparsley.internal.machine.instructions.Chainl→parsley.internal.machine.Contextparsley.internal.machine.instructions.ChainrJump→parsley.internal.machine.Contextparsley.internal.machine.instructions.ChainrOpHandler→parsley.internal.machine.Contextparsley.internal.machine.instructions.CharTok→parsley.internal.machine.Contextparsley.internal.machine.instructions.Col→parsley.internal.machine.Contextparsley.internal.machine.instructions.CommentLexer→parsley.internal.machine.Contextparsley.internal.machine.instructions.DislodgeAndFail→parsley.internal.machine.Contextparsley.internal.machine.instructions.DualHandler→parsley.internal.machine.Contextparsley.internal.machine.instructions.DynCall→parsley.internal.machine.Contextparsley.internal.machine.instructions.Empty→parsley.internal.machine.Contextparsley.internal.machine.instructions.EntrenchAndFail→parsley.internal.machine.Contextparsley.internal.machine.instructions.Eof→parsley.internal.machine.Contextparsley.internal.machine.instructions.ErrLogger→parsley.internal.machine.Contextparsley.internal.machine.instructions.ErrorToHints→parsley.internal.machine.Contextparsley.internal.machine.instructions.Exchange→parsley.internal.machine.Contextparsley.internal.machine.instructions.ExpandRefs→parsley.internal.machine.Context
- Direction
- internal.machine.instructions uses internal.machine, so a change to internal.machine can break internal.machine.instructions, while a change to internal.machine.instructions can't break internal.machine.
- Position
- Below the diagonal: internal.machine.instructions uses a module listed above it, which is the healthy direction.
34→8 token.Lexer uses token.predicate✕
- Connections
- 1 pair of types, where a type in token.Lexer uses a type in token.predicate.
- The types involved
parsley.token.Lexer.space→parsley.token.predicate.CharPredicate
- Direction
- token.Lexer uses token.predicate, so a change to token.predicate can break token.Lexer, while a change to token.Lexer can't break token.predicate.
- Position
- Below the diagonal: token.Lexer uses a module listed above it, which is the healthy direction.
34→20 token.Lexer uses parsley✕
- Connections
- 2 pairs of types, where a type in token.Lexer uses a type in parsley.
- The types involved
parsley.token.Lexer.lexeme→parsley.Parsleyparsley.token.Lexer.space→parsley.Parsley
- Direction
- token.Lexer uses parsley, so a change to parsley can break token.Lexer, while a change to token.Lexer can't break parsley.
- Position
- Below the diagonal: token.Lexer uses a module listed above it, which is the healthy direction.
34→27 token.Lexer uses token✕
- Connections
- 1 pair of types, where a type in token.Lexer uses a type in token.
- The types involved
parsley.token.Lexer.lexeme→parsley.token.Lexeme
- Direction
- token.Lexer uses token, so a change to token can break token.Lexer, while a change to token.Lexer can't break token.
- Position
- Below the diagonal: token.Lexer uses a module listed above it, which is the healthy direction.
34→28 token.Lexer uses token.names✕
- Connections
- 2 pairs of types, where a type in token.Lexer uses a type in token.names.
- The types involved
parsley.token.Lexer.lexeme→parsley.token.names.Namesparsley.token.Lexer.nonlexeme→parsley.token.names.Names
- Direction
- token.Lexer uses token.names, so a change to token.names can break token.Lexer, while a change to token.Lexer can't break token.names.
- Position
- Below the diagonal: token.Lexer uses a module listed above it, which is the healthy direction.
34→29 token.Lexer uses token.numeric✕
- Connections
- 6 pairs of types, where a type in token.Lexer uses a type in token.numeric.
- The types involved
parsley.token.Lexer.lexeme→parsley.token.numeric.Combinedparsley.token.Lexer.lexeme→parsley.token.numeric.Integerparsley.token.Lexer.lexeme→parsley.token.numeric.Realparsley.token.Lexer.nonlexeme→parsley.token.numeric.Combinedparsley.token.Lexer.nonlexeme→parsley.token.numeric.Integerparsley.token.Lexer.nonlexeme→parsley.token.numeric.Real
- Direction
- token.Lexer uses token.numeric, so a change to token.numeric can break token.Lexer, while a change to token.Lexer can't break token.numeric.
- Position
- Below the diagonal: token.Lexer uses a module listed above it, which is the healthy direction.
34→30 token.Lexer uses token.symbol✕
- Connections
- 2 pairs of types, where a type in token.Lexer uses a type in token.symbol.
- The types involved
parsley.token.Lexer.lexeme→parsley.token.symbol.Symbolparsley.token.Lexer.nonlexeme→parsley.token.symbol.Symbol
- Direction
- token.Lexer uses token.symbol, so a change to token.symbol can break token.Lexer, while a change to token.Lexer can't break token.symbol.
- Position
- Below the diagonal: token.Lexer uses a module listed above it, which is the healthy direction.
34→31 token.Lexer uses token.text✕
- Connections
- 4 pairs of types, where a type in token.Lexer uses a type in token.text.
- The types involved
parsley.token.Lexer.lexeme→parsley.token.text.Characterparsley.token.Lexer.lexeme→parsley.token.text.Stringparsley.token.Lexer.nonlexeme→parsley.token.text.Characterparsley.token.Lexer.nonlexeme→parsley.token.text.String
- Direction
- token.Lexer uses token.text, so a change to token.text can break token.Lexer, while a change to token.Lexer can't break token.text.
- Position
- Below the diagonal: token.Lexer uses a module listed above it, which is the healthy direction.
35→20 token.Lexer.lexeme uses parsley✕
- Connections
- 2 pairs of types, where a type in token.Lexer.lexeme uses a type in parsley.
- The types involved
parsley.token.Lexer.lexeme.enclosing→parsley.Parsleyparsley.token.Lexer.lexeme.separators→parsley.Parsley
- Direction
- token.Lexer.lexeme uses parsley, so a change to parsley can break token.Lexer.lexeme, while a change to token.Lexer.lexeme can't break parsley.
- Position
- Below the diagonal: token.Lexer.lexeme uses a module listed above it, which is the healthy direction.
35→29 token.Lexer.lexeme uses token.numeric✕
- Connections
- 3 pairs of types, where a type in token.Lexer.lexeme uses a type in token.numeric.
- The types involved
parsley.token.Lexer.lexeme.numeric→parsley.token.numeric.Combinedparsley.token.Lexer.lexeme.numeric→parsley.token.numeric.Integerparsley.token.Lexer.lexeme.numeric→parsley.token.numeric.Real
- Direction
- token.Lexer.lexeme uses token.numeric, so a change to token.numeric can break token.Lexer.lexeme, while a change to token.Lexer.lexeme can't break token.numeric.
- Position
- Below the diagonal: token.Lexer.lexeme uses a module listed above it, which is the healthy direction.
35→31 token.Lexer.lexeme uses token.text✕
- Connections
- 2 pairs of types, where a type in token.Lexer.lexeme uses a type in token.text.
- The types involved
parsley.token.Lexer.lexeme.text→parsley.token.text.Characterparsley.token.Lexer.lexeme.text→parsley.token.text.String
- Direction
- token.Lexer.lexeme uses token.text, so a change to token.text can break token.Lexer.lexeme, while a change to token.Lexer.lexeme can't break token.text.
- Position
- Below the diagonal: token.Lexer.lexeme uses a module listed above it, which is the healthy direction.
36→14 debugger.internal uses internal.deepembedding.frontend✕
- Connections
- 2 pairs of types, where a type in debugger.internal uses a type in internal.deepembedding.frontend.
- The types involved
parsley.debugger.internal.DebugContext→parsley.internal.deepembedding.frontend.LazyParsleyparsley.debugger.internal.Rename→parsley.internal.deepembedding.frontend.LazyParsley
- Direction
- debugger.internal uses internal.deepembedding.frontend, so a change to internal.deepembedding.frontend can break debugger.internal, while a change to debugger.internal can't break internal.deepembedding.frontend.
- Position
- Below the diagonal: debugger.internal uses a module listed above it, which is the healthy direction.
36→21 debugger.internal uses debugger✕
- Connections
- 3 pairs of types, where a type in debugger.internal uses a type in debugger.
- The types involved
parsley.debugger.internal.DebugContext→parsley.debugger.ParseAttemptparsley.debugger.internal.TransientDebugTree→parsley.debugger.DebugTreeparsley.debugger.internal.TransientDebugTree→parsley.debugger.ParseAttempt
- Direction
- debugger.internal uses debugger, so a change to debugger can break debugger.internal, while a change to debugger.internal can't break debugger.
- Position
- Below the diagonal: debugger.internal uses a module listed above it, which is the healthy direction.
36→32 debugger.internal uses debugger.util✕
- Connections
- 1 pair of types, where a type in debugger.internal uses a type in debugger.util.
- The types involved
parsley.debugger.internal.XWeakMap→parsley.debugger.util.XMutMap
- Direction
- debugger.internal uses debugger.util, so a change to debugger.util can break debugger.internal, while a change to debugger.internal can't break debugger.util.
- Position
- Below the diagonal: debugger.internal uses a module listed above it, which is the healthy direction.
37→2 internal.machine.instructions.token uses internal.collection.immutable✕
- Connections
- 2 pairs of types, where a type in internal.machine.instructions.token uses a type in internal.collection.immutable.
- The types involved
parsley.internal.machine.instructions.token.EscapeMapped→parsley.internal.collection.immutable.Trieparsley.internal.machine.instructions.token.SoftOperator→parsley.internal.collection.immutable.Trie
- Direction
- internal.machine.instructions.token uses internal.collection.immutable, so a change to internal.collection.immutable can break internal.machine.instructions.token, while a change to internal.machine.instructions.token can't break internal.collection.immutable.
- Position
- Below the diagonal: internal.machine.instructions.token uses a module listed above it, which is the healthy direction.
37→16 internal.machine.instructions.token uses internal.errors✕
- Connections
- 4 pairs of types, where a type in internal.machine.instructions.token uses a type in internal.errors.
- The types involved
parsley.internal.machine.instructions.token.EscapeSomeNumber→parsley.internal.errors.ExpectDescparsley.internal.machine.instructions.token.SoftKeyword→parsley.internal.errors.ExpectItemparsley.internal.machine.instructions.token.SoftOperator→parsley.internal.errors.ExpectItemparsley.internal.machine.instructions.token.Specific→parsley.internal.errors.ExpectItem
- Direction
- internal.machine.instructions.token uses internal.errors, so a change to internal.errors can break internal.machine.instructions.token, while a change to internal.machine.instructions.token can't break internal.errors.
- Position
- Below the diagonal: internal.machine.instructions.token uses a module listed above it, which is the healthy direction.
37→19 internal.machine.instructions.token uses token.errors✕
- Connections
- 2 pairs of types, where a type in internal.machine.instructions.token uses a type in token.errors.
- The types involved
parsley.internal.machine.instructions.token.SoftKeyword→parsley.token.errors.LabelConfigparsley.internal.machine.instructions.token.SoftOperator→parsley.token.errors.LabelConfig
- Direction
- internal.machine.instructions.token uses token.errors, so a change to token.errors can break internal.machine.instructions.token, while a change to internal.machine.instructions.token can't break token.errors.
- Position
- Below the diagonal: internal.machine.instructions.token uses a module listed above it, which is the healthy direction.
37→20 internal.machine.instructions.token uses parsley✕
- Connections
- 1 pair of types, where a type in internal.machine.instructions.token uses a type in parsley.
- The types involved
parsley.internal.machine.instructions.token.EscapeSomeNumber→parsley.Result
- Direction
- internal.machine.instructions.token uses parsley, so a change to parsley can break internal.machine.instructions.token, while a change to internal.machine.instructions.token can't break parsley.
- Position
- Below the diagonal: internal.machine.instructions.token uses a module listed above it, which is the healthy direction.
37→26 internal.machine.instructions.token uses internal.machine✕
- Connections
- 11 pairs of types, where a type in internal.machine.instructions.token uses a type in internal.machine.
- The types involved
parsley.internal.machine.instructions.token.Basic→parsley.internal.machine.Contextparsley.internal.machine.instructions.token.CharPredicate→parsley.internal.machine.Contextparsley.internal.machine.instructions.token.EscapeAtMost→parsley.internal.machine.Contextparsley.internal.machine.instructions.token.EscapeMapped→parsley.internal.machine.Contextparsley.internal.machine.instructions.token.EscapeOneOfExactly→parsley.internal.machine.Contextparsley.internal.machine.instructions.token.EscapeSomeNumber→parsley.internal.machine.Contextparsley.internal.machine.instructions.token.NotRequired→parsley.internal.machine.Contextparsley.internal.machine.instructions.token.SoftKeyword→parsley.internal.machine.Contextparsley.internal.machine.instructions.token.SoftOperator→parsley.internal.machine.Contextparsley.internal.machine.instructions.token.Specific→parsley.internal.machine.Contextparsley.internal.machine.instructions.token.Unicode→parsley.internal.machine.Context
- Direction
- internal.machine.instructions.token uses internal.machine, so a change to internal.machine can break internal.machine.instructions.token, while a change to internal.machine.instructions.token can't break internal.machine.
- Position
- Below the diagonal: internal.machine.instructions.token uses a module listed above it, which is the healthy direction.
37→33 internal.machine.instructions.token uses internal.machine.instructions✕
- Connections
- 3 pairs of types, where a type in internal.machine.instructions.token uses a type in internal.machine.instructions.
- The types involved
parsley.internal.machine.instructions.token.EscapeMapped→parsley.internal.machine.instructions.Instrparsley.internal.machine.instructions.token.EscapeSomeNumber→parsley.internal.machine.instructions.Instrparsley.internal.machine.instructions.token.Specific→parsley.internal.machine.instructions.Instr
- Direction
- internal.machine.instructions.token uses internal.machine.instructions, so a change to internal.machine.instructions can break internal.machine.instructions.token, while a change to internal.machine.instructions.token can't break internal.machine.instructions.
- Position
- Below the diagonal: internal.machine.instructions.token uses a module listed above it, which is the healthy direction.
38→17 internal.machine.stacks uses internal.machine.errors✕
- Connections
- 2 pairs of types, where a type in internal.machine.stacks uses a type in internal.machine.errors.
- The types involved
parsley.internal.machine.stacks.ErrorStack→parsley.internal.machine.errors.DefuncErrorparsley.internal.machine.stacks.HandlerStack→parsley.internal.machine.errors.DefuncHints
- Direction
- internal.machine.stacks uses internal.machine.errors, so a change to internal.machine.errors can break internal.machine.stacks, while a change to internal.machine.stacks can't break internal.machine.errors.
- Position
- Below the diagonal: internal.machine.stacks uses a module listed above it, which is the healthy direction.
38→33 internal.machine.stacks uses internal.machine.instructions✕
- Connections
- 2 pairs of types, where a type in internal.machine.stacks uses a type in internal.machine.instructions.
- The types involved
parsley.internal.machine.stacks.CallStack→parsley.internal.machine.instructions.Instrparsley.internal.machine.stacks.HandlerStack→parsley.internal.machine.instructions.Instr
- Direction
- internal.machine.stacks uses internal.machine.instructions, so a change to internal.machine.instructions can break internal.machine.stacks, while a change to internal.machine.stacks can't break internal.machine.instructions.
- Position
- Below the diagonal: internal.machine.stacks uses a module listed above it, which is the healthy direction.
39→9 internal.deepembedding.frontend.debugger uses internal.deepembedding.backend✕
- Connections
- 2 pairs of types, where a type in internal.deepembedding.frontend.debugger uses a type in internal.deepembedding.backend.
- The types involved
parsley.internal.deepembedding.frontend.debugger.Debugged→parsley.internal.deepembedding.backend.StrictParsleyparsley.internal.deepembedding.frontend.debugger.Named→parsley.internal.deepembedding.backend.StrictParsley
- Direction
- internal.deepembedding.frontend.debugger uses internal.deepembedding.backend, so a change to internal.deepembedding.backend can break internal.deepembedding.frontend.debugger, while a change to internal.deepembedding.frontend.debugger can't break internal.deepembedding.backend.
- Position
- Below the diagonal: internal.deepembedding.frontend.debugger uses a module listed above it, which is the healthy direction.
39→14 internal.deepembedding.frontend.debugger uses internal.deepembedding.frontend✕
- Connections
- 8 pairs of types, where a type in internal.deepembedding.frontend.debugger uses a type in internal.deepembedding.frontend.
- The types involved
parsley.internal.deepembedding.frontend.debugger.Debugged→parsley.internal.deepembedding.frontend.LazyParsleyparsley.internal.deepembedding.frontend.debugger.Debugged→parsley.internal.deepembedding.frontend.LazyParsleyIVisitorparsley.internal.deepembedding.frontend.debugger.Debugged→parsley.internal.deepembedding.frontend.LetFinderStateparsley.internal.deepembedding.frontend.debugger.Debugged→parsley.internal.deepembedding.frontend.LetMapparsley.internal.deepembedding.frontend.debugger.Named→parsley.internal.deepembedding.frontend.LazyParsleyparsley.internal.deepembedding.frontend.debugger.Named→parsley.internal.deepembedding.frontend.LazyParsleyIVisitorparsley.internal.deepembedding.frontend.debugger.Named→parsley.internal.deepembedding.frontend.Unaryparsley.internal.deepembedding.frontend.debugger.helper→parsley.internal.deepembedding.frontend.LazyParsley
- Direction
- internal.deepembedding.frontend.debugger uses internal.deepembedding.frontend, so a change to internal.deepembedding.frontend can break internal.deepembedding.frontend.debugger, while a change to internal.deepembedding.frontend.debugger can't break internal.deepembedding.frontend.
- Position
- Below the diagonal: internal.deepembedding.frontend.debugger uses a module listed above it, which is the healthy direction.
39→36 internal.deepembedding.frontend.debugger uses debugger.internal✕
- Connections
- 1 pair of types, where a type in internal.deepembedding.frontend.debugger uses a type in debugger.internal.
- The types involved
parsley.internal.deepembedding.frontend.debugger.helper→parsley.debugger.internal.DebugContext
- Direction
- internal.deepembedding.frontend.debugger uses debugger.internal, so a change to debugger.internal can break internal.deepembedding.frontend.debugger, while a change to internal.deepembedding.frontend.debugger can't break debugger.internal.
- Position
- Below the diagonal: internal.deepembedding.frontend.debugger uses a module listed above it, which is the healthy direction.
40→14 internal.deepembedding.frontend.debugger.helper uses internal.deepembedding.frontend✕
- Connections
- 15 pairs of types, where a type in internal.deepembedding.frontend.debugger.helper uses a type in internal.deepembedding.frontend.
- The types involved
parsley.internal.deepembedding.frontend.debugger.helper.DebugInjectingVisitorM→parsley.internal.deepembedding.frontend.<|>parsley.internal.deepembedding.frontend.debugger.helper.DebugInjectingVisitorM→parsley.internal.deepembedding.frontend.>>=parsley.internal.deepembedding.frontend.debugger.helper.DebugInjectingVisitorM→parsley.internal.deepembedding.frontend.Binaryparsley.internal.deepembedding.frontend.debugger.helper.DebugInjectingVisitorM→parsley.internal.deepembedding.frontend.ChainPostparsley.internal.deepembedding.frontend.debugger.helper.DebugInjectingVisitorM→parsley.internal.deepembedding.frontend.ChainPreparsley.internal.deepembedding.frontend.debugger.helper.DebugInjectingVisitorM→parsley.internal.deepembedding.frontend.Chainlparsley.internal.deepembedding.frontend.debugger.helper.DebugInjectingVisitorM→parsley.internal.deepembedding.frontend.Chainrparsley.internal.deepembedding.frontend.debugger.helper.DebugInjectingVisitorM→parsley.internal.deepembedding.frontend.GenericLazyParsleyIVisitorparsley.internal.deepembedding.frontend.debugger.helper.DebugInjectingVisitorM→parsley.internal.deepembedding.frontend.LazyParsleyparsley.internal.deepembedding.frontend.debugger.helper.DebugInjectingVisitorM→parsley.internal.deepembedding.frontend.Manyparsley.internal.deepembedding.frontend.debugger.helper.DebugInjectingVisitorM→parsley.internal.deepembedding.frontend.ManyUntilparsley.internal.deepembedding.frontend.debugger.helper.DebugInjectingVisitorM→parsley.internal.deepembedding.frontend.SepEndBy1parsley.internal.deepembedding.frontend.debugger.helper.DebugInjectingVisitorM→parsley.internal.deepembedding.frontend.Ternaryparsley.internal.deepembedding.frontend.debugger.helper.DebugInjectingVisitorM→parsley.internal.deepembedding.frontend.Unaryparsley.internal.deepembedding.frontend.debugger.helper.ParserTracker→parsley.internal.deepembedding.frontend.LazyParsley
- Direction
- internal.deepembedding.frontend.debugger.helper uses internal.deepembedding.frontend, so a change to internal.deepembedding.frontend can break internal.deepembedding.frontend.debugger.helper, while a change to internal.deepembedding.frontend.debugger.helper can't break internal.deepembedding.frontend.
- Position
- Below the diagonal: internal.deepembedding.frontend.debugger.helper uses a module listed above it, which is the healthy direction.
40→39 internal.deepembedding.frontend.debugger.helper uses internal.deepembedding.frontend.debugger✕
- Connections
- 1 pair of types, where a type in internal.deepembedding.frontend.debugger.helper uses a type in internal.deepembedding.frontend.debugger.
- The types involved
parsley.internal.deepembedding.frontend.debugger.helper.ParserTracker→parsley.internal.deepembedding.frontend.debugger.Debugged
- Direction
- internal.deepembedding.frontend.debugger.helper uses internal.deepembedding.frontend.debugger, so a change to internal.deepembedding.frontend.debugger can break internal.deepembedding.frontend.debugger.helper, while a change to internal.deepembedding.frontend.debugger.helper can't break internal.deepembedding.frontend.debugger.
- Position
- Below the diagonal: internal.deepembedding.frontend.debugger.helper uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 34 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 6 | Medium |
Roadmap
Top priorities: Resolve the 115 Orphaned file finding(s) in Knowledge Freshness — start with lift.scala (3), PrimitiveEmbedding.scala (3), ErrorEmbedding.scala (3); Your ecosystem's static analyzer is declared as a dependency but is not wired into CI — run it as a required step on push/PR (e.g. `composer phpstan` / `mix sobelow` / `bundle exec brakeman` / the spotbugs Gradle task / `sbt scalafixAll --check` / `golangci-lint run` / `rebar3 lint`) so a regression fails the build instead of relying on someone running it locally; Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. | +1.6 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +1.5 pts | Low | Static Analysis (SAST) |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +1.5 pts | Low | Static Analysis (SAST) |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +1.1 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +1.1 pts | Low | Supply-chain Provenance & Signing |
| Your ecosystem's static analyzer is declared as a dependency but is not wired into CI — run it as a required step on push/PR (e.g. `composer phpstan` / `mix sobelow` / `bundle exec brakeman` / the spotbugs Gradle task / `sbt scalafixAll --check` / `golangci-lint run` / `rebar3 lint`) so a regression fails the build instead of relying on someone running it locally. | +1.9 pts | Medium | Security & performance tooling |
| On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it. | +1.5 pts | Medium | Nullable reference types |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +1.4 pts | Medium | Release Hygiene |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| parsley/shared/src/main/scala/parsley/internal/deepembedding/backend/SequenceEmbedding.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| parsley/shared/src/main/scala/parsley/internal/deepembedding/backend/AlternativeEmbedding.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| parsley/shared/src/main/scala/parsley/combinator.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| parsley/shared/src/main/scala/parsley/ap.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| parsley/shared/src/main/scala/parsley/character.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| parsley/shared/src/main/scala/parsley/internal/machine/errors/DefuncError.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| parsley/shared/src/main/scala/parsley/token/numeric/UnsignedCombined.scala | 6.4 | Mixed | Explicit Debt: FixmeComment |
| parsley/shared/src/main/scala/parsley/unicode.scala | 6.5 | Mixed | Explicit Debt: TodoComment |
| parsley/shared/src/main/scala/parsley/errors/combinator.scala | 6.5 | Mixed | Explicit Debt: TodoComment |
| project/ParsleySitePlugin.scala | 6.6 | Mixed | Explicit Debt: FixmeComment |
| parsley-debug/jvm/src/main/scala-2/parsley/debugger/util/XCollector.scala | 6.6 | Mixed | Explicit Debt: XxxComment |
| parsley/shared/src/main/scala/parsley/token/errors/ErrorConfig.scala | 6.7 | Mixed | Explicit Debt: TodoComment |
| parsley/shared/src/main/scala/parsley/token/numeric/Combined.scala | 6.7 | Mixed | Explicit Debt: TodoComment |
| parsley/shared/src/main/scala/parsley/internal/deepembedding/frontend/Visitors.scala | 6.7 | Mixed | Explicit Debt: XxxComment |
| parsley/shared/src/main/scala/parsley/internal/machine/Context.scala | 6.7 | Mixed | Explicit Debt: TodoComment |
| parsley/shared/src/main/scala/parsley/implicits/lift.scala | 6.7 | Mixed | Explicit Debt: TodoComment |
| parsley/shared/src/main/scala/parsley/implicits/zipped.scala | 6.7 | Mixed | Explicit Debt: TodoComment |
| parsley/shared/src/main/scala/parsley/internal/errors/ParseError.scala | 6.9 | Mixed | Explicit Debt: TodoComment |
| parsley-debug/shared/src/main/scala/parsley/debugger/util/Collector.scala | 7.3 | Mixed | Explicit Debt: XxxComment |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 55 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 55 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, 291 of 302 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.scala) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.scala) and this repository declares an sbt build (repository root, 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository's dependency manifests WERE read and their pinning discipline assessed; what went unanswered is the currency half, because repo1.maven.org — the registry that answers it — was asked and did not reply (HTTP 429 Too Many Requests from http://172.31.7.1:8790/maven/com/github/j-mie6/parsley-cats_2.13/maven-metadata.xml). This is OUR side and it is an ENVIRONMENT fault, not a missing collector: the collector exists and ran. An HTTP 403 here is what this scan's egress allowlist returns for a host that is not on it, so the remedy is to add repo1.maven.org to the allowlist and re-run — not to build anything.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (build.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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- D44 Platform End-of-Life — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- 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.
- 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.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- 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 <*>.optimise at 16. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being Choice.tablable at 16 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: parsley/shared/src/main/scala/parsley/internal/deepembedding/backend/AlternativeEmbedding.scala (Choice.tablable at 16). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 2 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with <*>.optimise (cyclomatic 16), Seq.optimise (cyclomatic 16). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 9.8 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
1 method(s) exceeded the cognitive complexity threshold of 15; the worst was Choice.codeGenChain at 17.
What to do
- Bring the 1 body over 15 down to 15 or less in Cognitive Complexity — start with Choice.codeGenChain (cognitive 17). — Refactoring it lifts Cognitive Complexity from 9.8 to about 10.0/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
9 god class(es) detected.
What to do
- Resolve the 9 TooManyMethods finding(s) in God Classes — start with ErrorConfig.scala, Combined.scala, Visitors.scala. — One of this dimension's main actionable groups (9 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
7 duplicated block group(s) detected.
What to do
- Resolve the 2 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with character.scala, DefuncError.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 character.scala. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (377 lines × 2) finding(s) in Code Duplication — start with generic.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
2 production modules (sbt), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; a dependsOn spread (deps: _*) and a project whose directory a helper computes are not visible there; 1 module(s) off the main sequence.
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
0 of 91 classes have LCOM4 above 3.
D9 · Test Distribution
589 test methods: 589 unit, 0 integration, 0 BDD, 0 e2e. The Scala suite contributes 589 test case(s) across 36 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
1 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is build.sbt. Counted over 118 of the 196 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
109 deducted task-comment markers across 28423 LoC (0.4/KLoC) → score 9.3. 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 72 TodoComment finding(s) in Explicit Debt — start with combinator.scala (10), unicode.scala (6), SequenceEmbedding.scala (4). — One of this dimension's main actionable groups (72 warning-level).
- Resolve the 25 FixmeComment finding(s) in Explicit Debt — start with UnsignedCombined.scala (4), ParsleySitePlugin.scala (2), Result.scala (2). — One of this dimension's main actionable groups (25 warning-level).
- Resolve the 12 XxxComment finding(s) in Explicit Debt — start with XCollector.scala (4), Collector.scala (2), DebuggerInstrs.scala. — One of this dimension's main actionable groups (12 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.
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)
34 finding(s): 0 critical, 34 high, 0 medium, 0 low. 32 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. 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 32 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (32 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in any ecosystem this repository declares.
D34 · Knowledge Freshness
118 of 118 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is parsley/shared/src/main/scala/parsley/Parsley.scala. Counted over 118 of the 196 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 115 Orphaned file finding(s) in Knowledge Freshness — start with lift.scala (3), PrimitiveEmbedding.scala (3), ErrorEmbedding.scala (3). — One of this dimension's main actionable groups (115 recommendation-level).
- Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with Parsley.scala, Lexer.scala, combinator.scala. — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 1 Dormant codebase 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 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
Frontend & cross-cutting dimensions
AX10 · Code composition
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
- `ErrorBuilder[Err]` declares 18 abstract members: `format`, `pos`, `source`, `vanillaError`, `specialisedError`, `combineExpectedItems`, `combineMessages`, `unexpected`, `expected`, `reason`, `message`, `lineInfo`, `numLinesBefore`, `numLinesAfter`, `raw`, `named`, `endOfInput`, `unexpectedToken`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — parsley/shared/src/main/scala/parsley/errors/ErrorBuilder.scala:165
What to do
- Split fat interfaces into focused role-interfaces so clients depend only on what they use.
GD1 · Unfinished & placeholder code
- `iterator` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — parsley-debug/js/src/main/scala/parsley/debugger/internal/XWeakMap.scala:32
What to do
- Finish or delete the members whose body is still `???` or a "not implemented" throw where nothing overrides them, and replace placeholder text before shipping.
IC1 · Incompleteness & stubs
- `iterator` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. — parsley-debug/js/src/main/scala/parsley/debugger/internal/XWeakMap.scala:32
- 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. (×5) — parsley-debug/jvm/src/main/scala-2/parsley/debugger/util/XCollector.scala:28, parsley/shared/src/main/scala/parsley/Result.scala:45, parsley/shared/src/main/scala/parsley/internal/deepembedding/frontend/LazyParsley.scala:36, …
What to do
- Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live.
- 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
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- 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.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P3 · Security & performance tooling
What to do
- Your ecosystem's static analyzer is declared as a dependency but is not wired into CI — run it as a required step on push/PR (e.g. `composer phpstan` / `mix sobelow` / `bundle exec brakeman` / the spotbugs Gradle task / `sbt scalafixAll --check` / `golangci-lint run` / `rebar3 lint`) so a regression fails the build instead of relying on someone running it locally.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
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.
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 192 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 | 71% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 87% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 69% | Adequate — gated by D34 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 67% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 65% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
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 — 2 control(s) we could not find positive evidence for
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 61 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 — ~5686 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 — Dependency currency not established — repo1.maven.org did not answer
- D14 License Compliance — Not scored — this repository's 3 pinned sbt dependency coordinate(s) were read from its 3 sbt build file(s), but Maven Central could not be asked for the licence of 2 of them (HTTP 429 Too Many Requests from http://172.31.7.1:8790/maven/com/github/j-mie6/parsley-cats_2.13/1.4.0/parsley-cats_2.13-1.4.0.pom), and a licence verdict over part of a dependency graph is not a licence verdict. Nothing is asserted about this repository's licensing in either direction.
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D19 Documentation Quality — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript 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+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .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) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- 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): 52 value object(s); 6 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
- 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), 194 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.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — No web surface: 192 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 — 34 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 135 finding(s)
- TodoComment project/ParsleySitePlugin.scala:184
- TodoComment project/ParsleySitePlugin.scala:192
- TodoComment parsley-debug/jvm/src/main/scala-3/parsley/debugger/util/XCollector.scala:8
- TodoComment parsley-debug/js-native/src/main/scala/parsley/debugger/util/XCollector.scala:10
- TodoComment parsley/shared/src/test/scala/parsley/CharTests.scala:13
- TodoComment parsley/shared/src/test/scala/parsley/UnicodeTests.scala:13
- TodoComment parsley/shared/src/test/scala/parsley/token/descriptions/DescShrink.scala:14
- TodoComment parsley/shared/src/main/scala/parsley/ap.scala:59
- TodoComment parsley/shared/src/main/scala/parsley/ap.scala:69
- TodoComment parsley/shared/src/main/scala/parsley/character.scala:429
- TodoComment parsley/shared/src/main/scala/parsley/character.scala:485
- TodoComment parsley/shared/src/main/scala/parsley/combinator.scala:227
- TodoComment parsley/shared/src/main/scala/parsley/combinator.scala:229
- TodoComment parsley/shared/src/main/scala/parsley/combinator.scala:901
- TodoComment parsley/shared/src/main/scala/parsley/combinator.scala:971
- TodoComment parsley/shared/src/main/scala/parsley/combinator.scala:1103
- TodoComment parsley/shared/src/main/scala/parsley/internal/machine/errors/DefuncError.scala:347
- TodoComment parsley/shared/src/main/scala/parsley/registers.scala:463
- TodoComment parsley/shared/src/main/scala/parsley/unicode.scala:104
- TodoComment parsley/shared/src/main/scala/parsley/unicode.scala:130
- TodoComment parsley/shared/src/main/scala/parsley/unicode.scala:394
- TodoComment parsley/shared/src/main/scala/parsley/unicode.scala:451
- TodoComment parsley/shared/src/main/scala/parsley/unicode.scala:364
- TodoComment parsley/shared/src/main/scala/parsley/unicode.scala:423
- TodoComment parsley/shared/src/main/scala/parsley/token/Lexer.scala:31
- FixmeComment project/ParsleySitePlugin.scala:30
- FixmeComment project/ParsleySitePlugin.scala:241
- FixmeComment parsley-debug/shared/src/main/scala/parsley/debugger/ParseAttempt.scala:72
- FixmeComment parsley/shared/src/test/scala/parsley/CharTests.scala:39
- FixmeComment parsley/shared/src/test/scala/parsley/UnicodeTests.scala:41
- FixmeComment parsley/shared/src/test/scala/parsley/token/numeric/RealTests.scala:270
- FixmeComment parsley/shared/src/main/scala/parsley/Result.scala:28
- FixmeComment parsley/shared/src/main/scala/parsley/Result.scala:183
- FixmeComment parsley/shared/src/main/scala/parsley/token/numeric/UnsignedCombined.scala:21
- FixmeComment parsley/shared/src/main/scala/parsley/token/numeric/UnsignedCombined.scala:22
- FixmeComment parsley/shared/src/main/scala/parsley/token/numeric/UnsignedCombined.scala:23
- FixmeComment parsley/shared/src/main/scala/parsley/token/numeric/UnsignedCombined.scala:24
- FixmeComment parsley/shared/src/main/scala/parsley/token/descriptions/TextDesc.scala:39
- FixmeComment parsley/shared/src/main/scala/parsley/internal/machine/instructions/ErrorInstrs.scala:66
- FixmeComment parsley/shared/src/main/scala/parsley/internal/machine/instructions/IntrinsicInstrs.scala:110
- FixmeComment parsley/shared/src/main/scala/parsley/internal/machine/instructions/OptInstrs.scala:116
- FixmeComment parsley/shared/src/main/scala/parsley/internal/machine/errors/DefuncError.scala:360
- FixmeComment parsley/shared/src/main/scala/parsley/internal/machine/errors/DefuncError.scala:374
- FixmeComment parsley/shared/src/main/scala/parsley/internal/errors/Builders.scala:18
- FixmeComment parsley/shared/src/main/scala/parsley/internal/errors/ErrorItem.scala:50
- FixmeComment parsley/shared/src/main/scala/parsley/internal/errors/ParseError.scala:32
- FixmeComment parsley/shared/src/main/scala/parsley/internal/errors/ParseError.scala:39
- FixmeComment parsley/shared/src/main/scala/parsley/internal/deepembedding/backend/AlternativeEmbedding.scala:25
- FixmeComment parsley/shared/src/main/scala/parsley/internal/deepembedding/backend/AlternativeEmbedding.scala:108
- FixmeComment parsley/jvm-native/src/test/scala/parsley/CoreIOTests.scala:22
- XxxComment parsley-debug/shared/src/main/scala/parsley/internal/machine/instructions/debugger/DebuggerInstrs.scala:58
- XxxComment parsley-debug/shared/src/main/scala/parsley/internal/deepembedding/frontend/debugger/helper.scala:202
- XxxComment parsley-debug/shared/src/main/scala/parsley/debugger/combinator.scala:81
- XxxComment parsley-debug/shared/src/main/scala/parsley/debugger/util/Collector.scala:107
- XxxComment parsley-debug/shared/src/main/scala/parsley/debugger/util/Collector.scala:108
- XxxComment parsley-debug/shared/src/main/scala/parsley/debugger/frontend/DebugFrontend.scala:47
- XxxComment parsley-debug/jvm/src/main/scala-2/parsley/debugger/util/XCollector.scala:24
- XxxComment parsley-debug/jvm/src/main/scala-2/parsley/debugger/util/XCollector.scala:27
- XxxComment parsley-debug/jvm/src/main/scala-2/parsley/debugger/util/XCollector.scala:35
- XxxComment parsley-debug/jvm/src/main/scala-2/parsley/debugger/util/XCollector.scala:57
- XxxComment parsley/shared/src/main/scala/parsley/internal/deepembedding/frontend/AlternativeEmbedding.scala:24
- XxxComment parsley/shared/src/main/scala/parsley/internal/deepembedding/frontend/Visitors.scala:161
- TooManyMethods: ErrorConfig parsley/shared/src/main/scala/parsley/token/errors/ErrorConfig.scala:47
- TooManyMethods: Combined parsley/shared/src/main/scala/parsley/token/numeric/Combined.scala:36
- TooManyMethods: LazyParsleyIVisitor parsley/shared/src/main/scala/parsley/internal/deepembedding/frontend/Visitors.scala:40
- TooManyMethods: combinator parsley/shared/src/main/scala/parsley/combinator.scala:82
- TooManyMethods: Parsley parsley/shared/src/main/scala/parsley/Parsley.scala:121
- TooManyMethods: Context parsley/shared/src/main/scala/parsley/internal/machine/Context.scala:23
- TooManyMethods: ap parsley/shared/src/main/scala/parsley/ap.scala:39
- TooManyMethods: Integer parsley/shared/src/main/scala/parsley/token/numeric/Integer.scala:34
- TooManyMethods: character parsley/shared/src/main/scala/parsley/character.scala:81
- REDACTED
- REDACTED
- Duplicated block (8 lines × 2) parsley/shared/src/main/scala/parsley/character.scala:240
- Duplicated block (8 lines × 2) parsley/shared/src/main/scala/parsley/internal/machine/errors/DefuncError.scala:178
- <*>.optimise (cyclomatic 16) parsley/shared/src/main/scala/parsley/internal/deepembedding/backend/SequenceEmbedding.scala:22
- Seq.optimise (cyclomatic 16) parsley/shared/src/main/scala/parsley/internal/deepembedding/backend/SequenceEmbedding.scala:139
- Choice.codeGenChain (cognitive 17) parsley/shared/src/main/scala/parsley/internal/deepembedding/backend/AlternativeEmbedding.scala:133
- REDACTED
- REDACTED
- Duplicated block (5 lines × 2) parsley/shared/src/main/scala/parsley/character.scala:333
- Duplicated block (377 lines × 2) parsley/shared/src/main/scala/parsley/generic.scala:45
- Duplicated block (448 lines × 2) parsley/shared/src/main/scala/parsley/implicits/lift.scala:65
- Duplicated block (625 lines × 2) parsley/shared/src/main/scala/parsley/implicits/zipped.scala:79
- Duplicated block (9 lines × 2) parsley/shared/src/main/scala/parsley/internal/collection/mutable/DoublyLinkedList.scala:38
- Off the main sequence: parsley
- Unfinished stub — body is `???` parsley-debug/js/src/main/scala/parsley/debugger/internal/XWeakMap.scala:32
- Unfinished stub — body is ??? / NotImplementedError parsley-debug/js/src/main/scala/parsley/debugger/internal/XWeakMap.scala:32
Minor — 133 finding(s)
- Orphaned file parsley/shared/src/main/scala/parsley/implicits/zipped.scala:1
- Orphaned file parsley/shared/src/main/scala/parsley/syntax/zipped.scala:1
- Orphaned file parsley/shared/src/main/scala/parsley/errors/combinator.scala:1
- Orphaned file parsley/shared/src/main/scala/parsley/token/errors/ErrorConfig.scala:1
- Orphaned file parsley/shared/src/main/scala/parsley/character.scala:1
- Orphaned file parsley/shared/src/main/scala/parsley/registers.scala:1
- Orphaned file parsley/shared/src/main/scala/parsley/unicode.scala:1
- Orphaned file parsley/shared/src/main/scala/parsley/implicits/lift.scala:1
- Orphaned file parsley/shared/src/main/scala/parsley/syntax/lift.scala:1
- Orphaned file parsley/shared/src/main/scala/parsley/genericbridges.scala:1
- Orphaned file parsley/shared/src/main/scala/parsley/generic.scala:1
- Orphaned file parsley/shared/src/main/scala/parsley/internal/machine/errors/DefuncError.scala:1
- Orphaned file parsley/shared/src/main/scala/parsley/ap.scala:1
- Orphaned file parsley/shared/src/main/scala/parsley/token/numeric/Combined.scala:1
- Orphaned file parsley/shared/src/main/scala/parsley/errors/ErrorBuilder.scala:1
- Orphaned file parsley/shared/src/main/scala/parsley/internal/deepembedding/frontend/Visitors.scala:1
- Orphaned file parsley/shared/src/main/scala/parsley/debug.scala:1
- Orphaned file project/ParsleySitePlugin.scala:1
- Orphaned file parsley/shared/src/main/scala/parsley/internal/deepembedding/backend/StrictParsley.scala:1
- Orphaned file parsley-debug/shared/src/main/scala/parsley/debugger/combinator.scala:1
- Orphaned file parsley/shared/src/main/scala/parsley/internal/deepembedding/backend/AlternativeEmbedding.scala:1
- Orphaned file parsley/shared/src/main/scala/parsley/state.scala:1
- Orphaned file parsley/shared/src/main/scala/parsley/errors/patterns.scala:1
- Orphaned file parsley/shared/src/main/scala/parsley/expr/chain.scala:1
- Orphaned file parsley/shared/src/main/scala/parsley/internal/deepembedding/frontend/LazyParsley.scala:1
- Blanket warning suppression parsley-debug/jvm/src/main/scala-2/parsley/debugger/util/XCollector.scala:28
- Blanket warning suppression parsley/shared/src/main/scala/parsley/Result.scala:45
- Blanket warning suppression parsley/shared/src/main/scala/parsley/internal/deepembedding/frontend/LazyParsley.scala:36
- Blanket warning suppression parsley/shared/src/main/scala/parsley/internal/machine/instructions/DebugInstrs.scala:99
- Blanket warning suppression parsley/shared/src/main/scala/parsley/state.scala:81
- Most significant orphaned file parsley/shared/src/main/scala/parsley/Parsley.scala:1
- Most significant orphaned file parsley/shared/src/main/scala/parsley/token/Lexer.scala:1
- Most significant orphaned file parsley/shared/src/main/scala/parsley/combinator.scala:1
- Fat interface: ErrorBuilder[Err] (18 abstract members) parsley/shared/src/main/scala/parsley/errors/ErrorBuilder.scala:165
- Off-boarding risk: anonymized user #1
- Projects may be oversized for their cohesion
- Dormant codebase
- REDACTED
- REDACTED
- No ADRs
- No changelog
- Duplicated predicate parsley/shared/src/main/scala/parsley/token/numeric/SignedCombined.scala:27
- Scala's null is not held to the type system everywhere
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-190b1a619feb4379a49b4d9206faf092/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-190b1a619feb4379a49b4d9206faf092/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 34 | 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-9a21404733b34776b9af5dd950f77fc5 | 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. | 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-9a21404733b34776b9af5dd950f77fc5 | 0 | artifacts/raw/osv-scanner.json |