Executive summary
makenowjust-labs/recheck is rated At risk because critical security findings are open, most of them in the build pipeline. Its score is held back because 27 of the dependencies have a known vulnerability and it has passwords or keys in the code's history. It scores 47 out of 100, which the At risk rating leaves unchanged.
Security and Compliance, at 36, is the weakest lens and counts most in the score. The best first step for the work it takes is improving the documentation, worth about 5 points. Replacing the 16 passwords or keys found in the code's history would lift Security and Compliance itself, worth about 6 points. Raising Security and Compliance to 70 would lift the score to about 56.
Fifty-two pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Thirty-two known security holes in the packages the code depends on can be used by attackers, and sixteen passwords or keys are open to anyone who can read the repository. Pinning each tool to an exact version, updating the vulnerable packages and replacing each exposed password or key would close these risks. Limiting each secret to its own step would fix the two secrets exposed to more of the pipeline than needed, and fixing the weaknesses the scanner points to would deal with the two security weaknesses in the code. The loop of files that import each other needs breaking.
The product code is 20,769 lines, about €32,000 to rebuild. The check for the health of its packages couldn't finish, so that result is missing, not a clean pass.
If Security and Compliance rose from 36 to 70, the lowest score rated Strong, the score would rise from 47 to about 56.
New since the last survey: 137 findings
- Cyclomatic Complexity · FeatureSet.from (cyclomatic 175) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/FeatureSet.scala
- Cyclomatic Complexity · IRFeatureSet.from (cyclomatic 69) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRFeatureSet.scala
- Cyclomatic Complexity · FlagSet.parse (cyclomatic 59) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ast/FlagSet.scala
- Cyclomatic Complexity · Parser.parseFlagSet (cyclomatic 52) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/Parser.scala
- Cyclomatic Complexity · Parser.scanRemovedComments (cyclomatic 50) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/Parser.scala
- Cyclomatic Complexity · Interpreter.inst (cyclomatic 46) modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/vm/Interpreter.scala
- Cyclomatic Complexity · IRPropertyLookup.javaForProperty (cyclomatic 41) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRPropertyLookup.scala
- Cyclomatic Complexity · Parser.parseConditionalGroupTest (cyclomatic 41) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/Parser.scala
- Cyclomatic Complexity · LookBehindAnalyzer.width (cyclomatic 40) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/LookBehindAnalyzer.scala
- Cyclomatic Complexity · IRCharResolver.escapeClassSet (cyclomatic 29) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRCharResolver.scala
- Cyclomatic Complexity · Parser.parseExtendedGroup (cyclomatic 25) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/Parser.scala
- Cyclomatic Complexity · IRCharResolver.foldPart (cyclomatic 24) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRCharResolver.scala
- Cyclomatic Complexity · IRPropertyLookup.javaUnicodePredicate (cyclomatic 24) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRPropertyLookup.scala
- Cyclomatic Complexity · SemanticAnalyzer.walk (cyclomatic 23) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/SemanticAnalyzer.scala
- Cyclomatic Complexity · PerlLiteralRewriter.scanChunk (cyclomatic 23) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/PerlLiteralRewriter.scala
- Cyclomatic Complexity · IRBuilder.buildConditional (cyclomatic 21) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRBuilder.scala
- Cyclomatic Complexity · IRCharResolver.determineCaseEquivalence (cyclomatic 21) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRCharResolver.scala
- Cyclomatic Complexity · IRPropertyLookup.perl (cyclomatic 21) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRPropertyLookup.scala
- Cyclomatic Complexity · LookBehindAnalyzer.validateLookBehind (cyclomatic 21) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/LookBehindAnalyzer.scala
- Cyclomatic Complexity · LookBehindAnalyzer.rubyWidth (cyclomatic 20) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/LookBehindAnalyzer.scala
- Cyclomatic Complexity · IRBuilder.charWidth (cyclomatic 18) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRBuilder.scala
- Cyclomatic Complexity · PerlLiteralRewriter.caseModifier (cyclomatic 18) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/PerlLiteralRewriter.scala
- Cyclomatic Complexity · IRCharResolver.property (cyclomatic 17) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRCharResolver.scala
- Cyclomatic Complexity · Parser.parseBackslashBackReference (cyclomatic 17) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/Parser.scala
- Cyclomatic Complexity · IRCharResolver.classItem (cyclomatic 16) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRCharResolver.scala
- Cyclomatic Complexity · Parser.determineUnitMode (cyclomatic 16) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/Parser.scala
- Cyclomatic Complexity · Parser.parseCurlyQuantifier (cyclomatic 16) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/Parser.scala
- Cyclomatic Complexity · Parser.parseClassItemAtom (cyclomatic 16) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/Parser.scala
- Cyclomatic Complexity · Parser.parseClassItemNonRange (cyclomatic 16) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/Parser.scala
- Cyclomatic Complexity · Parser.parseGroupNameBody (cyclomatic 16) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/Parser.scala
- Cognitive Complexity · FeatureSet.from (cognitive 170) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/FeatureSet.scala
- Cognitive Complexity · Parser.scanRemovedComments (cognitive 110) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/Parser.scala
- Cognitive Complexity · Parser.parseFlagSet (cognitive 77) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/Parser.scala
- Cognitive Complexity · Parser.parseConditionalGroupTest (cognitive 56) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/Parser.scala
- Cognitive Complexity · IRFeatureSet.from (cognitive 52) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRFeatureSet.scala
- Cognitive Complexity · FlagSet.parse (cognitive 50) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ast/FlagSet.scala
- Cognitive Complexity · IRCharResolver.foldPart (cognitive 50) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRCharResolver.scala
- Cognitive Complexity · GenerateRuntimeAttackScriptCommand.generate (cognitive 45) modules/recheck-cli/src/main/scala/codes/quine/labs/recheck/cli/GenerateRuntimeAttackScriptCommand.scala
- Cognitive Complexity · PerlLiteralRewriter.scanChunk (cognitive 43) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/PerlLiteralRewriter.scala
- Cognitive Complexity · LookBehindAnalyzer.validateLookBehind (cognitive 37) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/LookBehindAnalyzer.scala
- Cognitive Complexity · Interpreter.inst (cognitive 35) modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/vm/Interpreter.scala
- Cognitive Complexity · IRCharResolver.property (cognitive 33) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRCharResolver.scala
- Cognitive Complexity · LookBehindAnalyzer.width (cognitive 31) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/LookBehindAnalyzer.scala
- Cognitive Complexity · PerlLiteralRewriter.caseModifier (cognitive 31) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/PerlLiteralRewriter.scala
- Cognitive Complexity · IRPropertyLookup.perl (cognitive 30) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRPropertyLookup.scala
- Cognitive Complexity · AutomatonChecker.findEDA (cognitive 29) modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/automaton/AutomatonChecker.scala
- Cognitive Complexity · FString.admitsAnyRepeatCount (cognitive 28) modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/fuzz/FString.scala
- Cognitive Complexity · IRPropertyLookup.perlNumericValue (cognitive 25) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRPropertyLookup.scala
- Cognitive Complexity · EpsNFABuilder.rejectEmpty (cognitive 23) modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/automaton/EpsNFABuilder.scala
- Cognitive Complexity · IRBuilder.charWidth (cognitive 23) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRBuilder.scala
- Cognitive Complexity · Parser.parseClassItem (cognitive 23) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/Parser.scala
- Cognitive Complexity · Parser.parseClassItemAtom (cognitive 23) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/Parser.scala
- Cognitive Complexity · SemanticAnalyzer.walk (cognitive 22) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/SemanticAnalyzer.scala
- Cognitive Complexity · Parser.parseSignedInlineFlagGroup (cognitive 22) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/Parser.scala
- Cognitive Complexity · SourcePrescan.from (cognitive 22) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/SourcePrescan.scala
- Cognitive Complexity · LookBehindAnalyzer.studyJavaRepeat (cognitive 21) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/LookBehindAnalyzer.scala
- Cognitive Complexity · Parser.parseGroupNameBody (cognitive 21) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/Parser.scala
- Cognitive Complexity · IRCharResolver.determineCaseEquivalence (cognitive 20) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRCharResolver.scala
- Cognitive Complexity · LookBehindAnalyzer.rubyWidth (cognitive 20) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/LookBehindAnalyzer.scala
- Cognitive Complexity · main.selectBackend (cognitive 20) packages/recheck/src/main.ts
- Cognitive Complexity · Interpreter.compareFolded (cognitive 19) modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/vm/Interpreter.scala
- Cognitive Complexity · IRCharResolver.joinRubyByteRepeats (cognitive 19) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRCharResolver.scala
- Cognitive Complexity · Parser.determineUnitMode (cognitive 19) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/Parser.scala
- Cognitive Complexity · Parser.parseBackslashBackReference (cognitive 19) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/Parser.scala
- Cognitive Complexity · Parser.parseBackslashLowerU (cognitive 17) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/Parser.scala
- Cognitive Complexity · OrderedNFA.toNFAwLA (cognitive 16) modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/automaton/OrderedNFA.scala
- Cognitive Complexity · Alphabet.refine (cognitive 16) modules/resyntax-charset/shared/src/main/scala/codes/quine/labs/resyntax/charset/Alphabet.scala
- Cognitive Complexity · BuildingContext.charset (cognitive 16) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/BuildingContext.scala
- Cognitive Complexity · IRBuilder.buildSequence (cognitive 16) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRBuilder.scala
- Cognitive Complexity · IRCharResolver.literals (cognitive 16) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRCharResolver.scala
- Cognitive Complexity · Parser.skipLineComment (cognitive 16) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/Parser.scala
- Cognitive Complexity · PerlLiteralRewriter.pop (cognitive 16) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/PerlLiteralRewriter.scala
- God Classes · TooManyMethods: Parser modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/Parser.scala
- God Classes · FileTooLong: parser/Parser.scala modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/Parser.scala
- God Classes · TooManyMethods: IRCharResolver modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRCharResolver.scala
- God Classes · TooManyMethods: IRPropertyLookup modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRPropertyLookup.scala
- God Classes · FileTooLong: build/IRCharResolver.scala modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRCharResolver.scala
- God Classes · FileTooLong: vm/Interpreter.scala modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/vm/Interpreter.scala
- God Classes · FileTooLong: vm/ProgramBuilder.scala modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/vm/ProgramBuilder.scala
- God Classes · FileTooLong: build/IRPropertyLookup.scala modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRPropertyLookup.scala
- Code Duplication · Duplicated block (8–9 lines × 2) modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/vm/ProgramBuilder.scala
- Code Duplication · Duplicated block (5 lines × 2) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRCharResolver.scala
- Coupling · Off the main sequence: resyntaxCharset
- Code Coverage · Coverage not measured — JavaScript/TypeScript suite
- Churn × Complexity Hotspots · Hotspot: modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/FeatureSet.scala modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/FeatureSet.scala
- Churn × Complexity Hotspots · Hotspot: modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/Parser.scala modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/Parser.scala
- Churn × Complexity Hotspots · Hotspot: modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/vm/Interpreter.scala modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/vm/Interpreter.scala
- Churn × Complexity Hotspots · Hotspot: modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRCharResolver.scala modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRCharResolver.scala
- Churn × Complexity Hotspots · Hotspot: modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRBuilder.scala modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRBuilder.scala
- Churn × Complexity Hotspots · Hotspot: modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/LookBehindAnalyzer.scala modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/LookBehindAnalyzer.scala
- Churn × Complexity Hotspots · Hotspot: modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRPropertyLookup.scala modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRPropertyLookup.scala
- Churn × Complexity Hotspots · Hotspot: modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRFeatureSet.scala modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRFeatureSet.scala
- Churn × Complexity Hotspots · Hotspot: modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ast/FlagSet.scala modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ast/FlagSet.scala
- Churn × Complexity Hotspots · Hotspot: modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/vm/ProgramBuilder.scala modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/vm/ProgramBuilder.scala
- Churn × Complexity Hotspots · Hotspot: modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/automaton/EpsNFA.scala modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/automaton/EpsNFA.scala
- Churn × Complexity Hotspots · Hotspot: modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/fuzz/StaticSeeder.scala modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/fuzz/StaticSeeder.scala
- Churn × Complexity Hotspots · Hotspot: modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/automaton/EpsNFABuilder.scala modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/automaton/EpsNFABuilder.scala
- Churn × Complexity Hotspots · Hotspot: website/src/components/Demo/index.tsx website/src/components/Demo/index.tsx
- Churn × Complexity Hotspots · Hotspot: modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/SemanticAnalyzer.scala modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/SemanticAnalyzer.scala
- Churn × Complexity Hotspots · Hotspot: website/src/components/Demo/DemoResult.tsx website/src/components/Demo/DemoResult.tsx
Fixed since the last survey: 85 findings
- Cyclomatic Complexity · EpsNFABuilder.buildNode (cyclomatic 32) modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/automaton/EpsNFABuilder.scala
- Cyclomatic Complexity · ProgramBuilder.build (cyclomatic 28) modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/vm/ProgramBuilder.scala
- Cyclomatic Complexity · Parser.assignBackReferenceIndex (cyclomatic 24) modules/recheck-parse/shared/src/main/scala/codes/quine/labs/recheck/regexp/Parser.scala
- Cyclomatic Complexity · Parser.resolveUnicodeProperty (cyclomatic 22) modules/recheck-parse/shared/src/main/scala/codes/quine/labs/recheck/regexp/Parser.scala
- Cyclomatic Complexity · main.check (cyclomatic 19) packages/recheck/src/main.ts
- Cyclomatic Complexity · Demo.DemoResult (cyclomatic 19) website/src/components/Demo.tsx
- Cyclomatic Complexity · ReDoS.checkAutomaton (cyclomatic 16) modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/ReDoS.scala
- Cognitive Complexity · ReDoS.checkAutomaton (cognitive 39) modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/ReDoS.scala
- Cognitive Complexity · EpsNFABuilder.buildNode (cognitive 32) modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/automaton/EpsNFABuilder.scala
- Cognitive Complexity · AutomatonChecker.checkExponentialComponent (cognitive 29) modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/automaton/AutomatonChecker.scala
- Cognitive Complexity · Interpreter.instRead (cognitive 28) modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/vm/Interpreter.scala
- Cognitive Complexity · Interpreter.instReadBack (cognitive 28) modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/vm/Interpreter.scala
- Cognitive Complexity · Demo.DemoResult (cognitive 27) website/src/components/Demo.tsx
- Cognitive Complexity · main.check (cognitive 26) packages/recheck/src/main.ts
- Cognitive Complexity · ProgramBuilder.build (cognitive 25) modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/vm/ProgramBuilder.scala
- Cognitive Complexity · Parser.preprocessParen (cognitive 22) modules/recheck-parse/shared/src/main/scala/codes/quine/labs/recheck/regexp/Parser.scala
- Cognitive Complexity · Parser.resolveUnicodeProperty (cognitive 20) modules/recheck-parse/shared/src/main/scala/codes/quine/labs/recheck/regexp/Parser.scala
- Cognitive Complexity · FString.toString (cognitive 16) modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/fuzz/FString.scala
- God Classes · FunctionTooLong: Demo.DemoResult website/src/components/Demo.tsx
- God Classes · TooManyMethods: Parser modules/recheck-parse/shared/src/main/scala/codes/quine/labs/recheck/regexp/Parser.scala
- Code Duplication · Duplicated block (14 lines × 2) modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/fuzz/FString.scala
- Code Duplication · Duplicated block (6 lines × 2) modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/vm/Interpreter.scala
- Coupling · Off the main sequence: unicode
- Secret Scanning · Leaked secret: hardcoded-credential REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: REDACTED .github/workflows/scala-steward.yml
- Static Analysis (SAST) · High: watchdog-secret-into-unpinned-action .github/workflows/scala-steward.yml
- Dependency Vulnerabilities · Critical CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium vulnerability: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Supply-chain Provenance & Signing · REDACTED .github/workflows/scala-steward.yml
- Platform End-of-Life · End-of-life runtime: Scala 3.7 build.sbt
- Code Duplication · Duplicated block (12 lines × 2 locations) packages/eslint-plugin-redos/scripts/build.ts
- Code Duplication · Duplicated block (11 lines × 2 locations) packages/eslint-plugin-redos/scripts/build.ts
- Import Boundaries · Boundary violation [package:relative-cross-package] packages/recheck/src/lib/pure.ts
- Import Boundaries · Boundary violation [package:test-suite-dependency] packages/recheck/src/lib/pure.ts
- Cyclomatic Complexity · Complex function check (cyclomatic 21, cognitive 28) packages/recheck/src/main.ts
- Test Coverage · No test reaches this file packages/recheck/scripts/build.ts
- Test Coverage · No test reaches this file packages/eslint-plugin-redos/scripts/build.ts
- Dead Code · Dead file (~11 LoC) packages/recheck/src/inject/worker-node.ts
- Dead Code · Dead file (~9 LoC) packages/recheck/src/inject/worker-browser.ts
Rebuild cost: about €32,000 · Estimate
| Cost to rebuild | €10,000 to €53,000, for 175 to 555 hours of work, about 0.2 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 47. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 20,769 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 recheck.cli | 2 recheck.common | 3 recheck.data | 4 recheck.diagnostics.Hotspot | 5 resyntax.ast | 6 resyntax.charset | 7 resyntax.ir.build.LookBehindAnalyzer | 8 recheck.cli.Main | 9 recheck.diagnostics | 10 recheck.exec | 11 recheck.vm.Program | 12 resyntax.dialect | 13 resyntax.ir.alphabet | 14 recheck.automaton.EpsNFA | 15 recheck.cli.AgentCommand | 16 recheck.diagnostics.AttackComplexity | 17 recheck.diagnostics.AttackPatternStyle | 18 recheck.diagnostics.Diagnostics | 19 recheck.verification | 20 resyntax.ir | 21 resyntax.parser | 22 recheck | 23 recheck.automaton | 24 recheck.diagnostics.Diagnostics.ErrorKind | 25 recheck.vm.Inst | 26 resyntax.ir.IRAssertKind | 27 resyntax.ir.IRBackReferenceFolding | 28 resyntax.ir.IRCaseEquivalence | 29 resyntax.ir.IRNodeData | 30 resyntax.ir.IRQuantifier | 31 resyntax.ir.build.IRCharResolver | 32 recheck.automaton.Complexity | 33 recheck.automaton.EpsNFA.AssertKind | 34 recheck.vm.Inst.ReadKind | 35 recheck.vm.Interpreter | 36 resyntax.ir.build | 37 recheck.vm | 38 resyntax.ir.build.IRClassLookup | 39 recheck.vm.Inst.AssertKind | 40 recheck.vm.Interpreter.Rollback |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 recheck.cli | ||||||||||||||||||||||||||||||||||||||||
| 2 recheck.common | ||||||||||||||||||||||||||||||||||||||||
| 3 recheck.data | ||||||||||||||||||||||||||||||||||||||||
| 4 recheck.diagnostics.Hotspot | ||||||||||||||||||||||||||||||||||||||||
| 5 resyntax.ast | ||||||||||||||||||||||||||||||||||||||||
| 6 resyntax.charset | ||||||||||||||||||||||||||||||||||||||||
| 7 resyntax.ir.build.LookBehindAnalyzer | ||||||||||||||||||||||||||||||||||||||||
| 8 recheck.cli.Main | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 recheck.diagnostics | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 10 recheck.exec | 3 | |||||||||||||||||||||||||||||||||||||||
| 11 recheck.vm.Program | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 resyntax.dialect | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 resyntax.ir.alphabet | 3 | |||||||||||||||||||||||||||||||||||||||
| 14 recheck.automaton.EpsNFA | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 15 recheck.cli.AgentCommand | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 16 recheck.diagnostics.AttackComplexity | 2 | |||||||||||||||||||||||||||||||||||||||
| 17 recheck.diagnostics.AttackPatternStyle | 8 | 8 | ||||||||||||||||||||||||||||||||||||||
| 18 recheck.diagnostics.Diagnostics | 2 | 3 | 9 | 3 | ||||||||||||||||||||||||||||||||||||
| 19 recheck.verification | 1 | 1 | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 20 resyntax.ir | 1 | 5 | 2 | |||||||||||||||||||||||||||||||||||||
| 21 resyntax.parser | 9 | 3 | 2 | |||||||||||||||||||||||||||||||||||||
| 22 recheck | 2 | 2 | 1 | 3 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 23 recheck.automaton | 6 | 4 | 2 | 2 | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 24 recheck.diagnostics.Diagnostics.ErrorKind | 6 | |||||||||||||||||||||||||||||||||||||||
| 25 recheck.vm.Inst | 2 | 1 | 25 | |||||||||||||||||||||||||||||||||||||
| 26 resyntax.ir.IRAssertKind | 4 | 3 | 13 | |||||||||||||||||||||||||||||||||||||
| 27 resyntax.ir.IRBackReferenceFolding | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 28 resyntax.ir.IRCaseEquivalence | 13 | 7 | ||||||||||||||||||||||||||||||||||||||
| 29 resyntax.ir.IRNodeData | 1 | 2 | 36 | |||||||||||||||||||||||||||||||||||||
| 30 resyntax.ir.IRQuantifier | 2 | 3 | ||||||||||||||||||||||||||||||||||||||
| 31 resyntax.ir.build.IRCharResolver | 2 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 32 recheck.automaton.Complexity | 3 | 6 | 5 | |||||||||||||||||||||||||||||||||||||
| 33 recheck.automaton.EpsNFA.AssertKind | 10 | 1 | 10 | |||||||||||||||||||||||||||||||||||||
| 34 recheck.vm.Inst.ReadKind | 2 | 3 | 5 | |||||||||||||||||||||||||||||||||||||
| 35 recheck.vm.Interpreter | 3 | 2 | 3 | 1 | ||||||||||||||||||||||||||||||||||||
| 36 resyntax.ir.build | 22 | 10 | 3 | 3 | 17 | 2 | ||||||||||||||||||||||||||||||||||
| 37 recheck.vm | 2 | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 38 resyntax.ir.build.IRClassLookup | 10 | 8 | 7 | |||||||||||||||||||||||||||||||||||||
| 39 recheck.vm.Inst.AssertKind | 4 | 3 | 3 | 11 | 1 | |||||||||||||||||||||||||||||||||||
| 40 recheck.vm.Interpreter.Rollback | 4 | 1 |
8→1 recheck.cli.Main uses recheck.cli✕
- Connections
- 1 pair of types, where a type in recheck.cli.Main uses a type in recheck.cli.
- The types involved
codes.quine.labs.recheck.cli.Main.CheckAction→codes.quine.labs.recheck.cli.InputPattern
- Direction
- recheck.cli.Main uses recheck.cli, so a change to recheck.cli can break recheck.cli.Main, while a change to recheck.cli.Main can't break recheck.cli.
- Position
- Below the diagonal: recheck.cli.Main uses a module listed above it, which is the healthy direction.
9→4 recheck.diagnostics uses recheck.diagnostics.Hotspot✕
- Connections
- 1 pair of types, where a type in recheck.diagnostics uses a type in recheck.diagnostics.Hotspot.
- The types involved
codes.quine.labs.recheck.diagnostics.Hotspot→codes.quine.labs.recheck.diagnostics.Hotspot.Spot
- Direction
- recheck.diagnostics uses recheck.diagnostics.Hotspot, so a change to recheck.diagnostics.Hotspot can break recheck.diagnostics, while a change to recheck.diagnostics can't break recheck.diagnostics.Hotspot.
- Position
- Below the diagonal: recheck.diagnostics uses a module listed above it, which is the healthy direction.
9→6 recheck.diagnostics uses resyntax.charset✕
- Connections
- 3 pairs of types, where a type in recheck.diagnostics uses a type in resyntax.charset.
- The types involved
codes.quine.labs.recheck.diagnostics.AttackPattern→codes.quine.labs.resyntax.charset.UStringcodes.quine.labs.recheck.diagnostics.AttackPattern→codes.quine.labs.resyntax.charset.UnitModecodes.quine.labs.recheck.diagnostics.AttackPatternStyle→codes.quine.labs.resyntax.charset.UString
- Direction
- recheck.diagnostics uses resyntax.charset, so a change to resyntax.charset can break recheck.diagnostics, while a change to recheck.diagnostics can't break resyntax.charset.
- Position
- Below the diagonal: recheck.diagnostics uses a module listed above it, which is the healthy direction.
10→2 recheck.exec uses recheck.common✕
- Connections
- 3 pairs of types, where a type in recheck.exec uses a type in recheck.common.
- The types involved
codes.quine.labs.recheck.exec.Executor→codes.quine.labs.recheck.common.Contextcodes.quine.labs.recheck.exec.Platform→codes.quine.labs.recheck.common.Contextcodes.quine.labs.recheck.exec.RubyExecutor→codes.quine.labs.recheck.common.Context
- Direction
- recheck.exec uses recheck.common, so a change to recheck.common can break recheck.exec, while a change to recheck.exec can't break recheck.common.
- Position
- Below the diagonal: recheck.exec uses a module listed above it, which is the healthy direction.
11→37 recheck.vm.Program uses recheck.vm part of a loop✕
- Connections
- 1 pair of types, where a type in recheck.vm.Program uses a type in recheck.vm.
- The types involved
codes.quine.labs.recheck.vm.Program.Meta→codes.quine.labs.recheck.vm.Label
- Direction
- recheck.vm.Program uses recheck.vm, so a change to recheck.vm can break recheck.vm.Program, while a change to recheck.vm.Program can't break recheck.vm.
- 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→6 resyntax.dialect uses resyntax.charset✕
- Connections
- 1 pair of types, where a type in resyntax.dialect uses a type in resyntax.charset.
- The types involved
codes.quine.labs.resyntax.dialect.DotNetCharClass→codes.quine.labs.resyntax.charset.CharSet
- Direction
- resyntax.dialect uses resyntax.charset, so a change to resyntax.charset can break resyntax.dialect, while a change to resyntax.dialect can't break resyntax.charset.
- Position
- Below the diagonal: resyntax.dialect uses a module listed above it, which is the healthy direction.
13→6 resyntax.ir.alphabet uses resyntax.charset✕
- Connections
- 3 pairs of types, where a type in resyntax.ir.alphabet uses a type in resyntax.charset.
- The types involved
codes.quine.labs.resyntax.ir.alphabet.PatternAlphabet→codes.quine.labs.resyntax.charset.Alphabetcodes.quine.labs.resyntax.ir.alphabet.PatternAlphabet→codes.quine.labs.resyntax.charset.CharSetcodes.quine.labs.resyntax.ir.alphabet.PatternAlphabet→codes.quine.labs.resyntax.charset.UnitMode
- Direction
- resyntax.ir.alphabet uses resyntax.charset, so a change to resyntax.charset can break resyntax.ir.alphabet, while a change to resyntax.ir.alphabet can't break resyntax.charset.
- Position
- Below the diagonal: resyntax.ir.alphabet uses a module listed above it, which is the healthy direction.
14→5 recheck.automaton.EpsNFA uses resyntax.ast✕
- Connections
- 1 pair of types, where a type in recheck.automaton.EpsNFA uses a type in resyntax.ast.
- The types involved
codes.quine.labs.recheck.automaton.EpsNFA.Consume→codes.quine.labs.resyntax.ast.SourceLocation
- Direction
- recheck.automaton.EpsNFA uses resyntax.ast, so a change to resyntax.ast can break recheck.automaton.EpsNFA, while a change to recheck.automaton.EpsNFA can't break resyntax.ast.
- Position
- Below the diagonal: recheck.automaton.EpsNFA uses a module listed above it, which is the healthy direction.
14→13 recheck.automaton.EpsNFA uses resyntax.ir.alphabet✕
- Connections
- 1 pair of types, where a type in recheck.automaton.EpsNFA uses a type in resyntax.ir.alphabet.
- The types involved
codes.quine.labs.recheck.automaton.EpsNFA.AssertKind→codes.quine.labs.resyntax.ir.alphabet.CharKind
- Direction
- recheck.automaton.EpsNFA uses resyntax.ir.alphabet, so a change to resyntax.ir.alphabet can break recheck.automaton.EpsNFA, while a change to recheck.automaton.EpsNFA can't break resyntax.ir.alphabet.
- Position
- Below the diagonal: recheck.automaton.EpsNFA uses a module listed above it, which is the healthy direction.
14→23 recheck.automaton.EpsNFA uses recheck.automaton part of a loop✕
- Connections
- 1 pair of types, where a type in recheck.automaton.EpsNFA uses a type in recheck.automaton.
- The types involved
codes.quine.labs.recheck.automaton.EpsNFA.AssertKind→codes.quine.labs.recheck.automaton.CharKindState
- Direction
- recheck.automaton.EpsNFA uses recheck.automaton, so a change to recheck.automaton can break recheck.automaton.EpsNFA, while a change to recheck.automaton.EpsNFA can't break recheck.automaton.
- 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→2 recheck.cli.AgentCommand uses recheck.common✕
- Connections
- 1 pair of types, where a type in recheck.cli.AgentCommand uses a type in recheck.common.
- The types involved
codes.quine.labs.recheck.cli.AgentCommand.Token→codes.quine.labs.recheck.common.CancellationTokenSource
- Direction
- recheck.cli.AgentCommand uses recheck.common, so a change to recheck.common can break recheck.cli.AgentCommand, while a change to recheck.cli.AgentCommand can't break recheck.common.
- Position
- Below the diagonal: recheck.cli.AgentCommand uses a module listed above it, which is the healthy direction.
15→9 recheck.cli.AgentCommand uses recheck.diagnostics✕
- Connections
- 1 pair of types, where a type in recheck.cli.AgentCommand uses a type in recheck.diagnostics.
- The types involved
codes.quine.labs.recheck.cli.AgentCommand.Token→codes.quine.labs.recheck.diagnostics.Diagnostics
- Direction
- recheck.cli.AgentCommand uses recheck.diagnostics, so a change to recheck.diagnostics can break recheck.cli.AgentCommand, while a change to recheck.cli.AgentCommand can't break recheck.diagnostics.
- Position
- Below the diagonal: recheck.cli.AgentCommand uses a module listed above it, which is the healthy direction.
15→12 recheck.cli.AgentCommand uses resyntax.dialect✕
- Connections
- 1 pair of types, where a type in recheck.cli.AgentCommand uses a type in resyntax.dialect.
- The types involved
codes.quine.labs.recheck.cli.AgentCommand.Token→codes.quine.labs.resyntax.dialect.Dialect
- Direction
- recheck.cli.AgentCommand uses resyntax.dialect, so a change to resyntax.dialect can break recheck.cli.AgentCommand, while a change to recheck.cli.AgentCommand can't break resyntax.dialect.
- Position
- Below the diagonal: recheck.cli.AgentCommand uses a module listed above it, which is the healthy direction.
16→9 recheck.diagnostics.AttackComplexity uses recheck.diagnostics✕
- Connections
- 2 pairs of types, where a type in recheck.diagnostics.AttackComplexity uses a type in recheck.diagnostics.
- The types involved
codes.quine.labs.recheck.diagnostics.AttackComplexity.Safe→codes.quine.labs.recheck.diagnostics.AttackComplexitycodes.quine.labs.recheck.diagnostics.AttackComplexity.Vulnerable→codes.quine.labs.recheck.diagnostics.AttackComplexity
- Direction
- recheck.diagnostics.AttackComplexity uses recheck.diagnostics, so a change to recheck.diagnostics can break recheck.diagnostics.AttackComplexity, while a change to recheck.diagnostics.AttackComplexity can't break recheck.diagnostics.
- Position
- Below the diagonal: recheck.diagnostics.AttackComplexity uses a module listed above it, which is the healthy direction.
17→6 recheck.diagnostics.AttackPatternStyle uses resyntax.charset✕
- Connections
- 8 pairs of types, where a type in recheck.diagnostics.AttackPatternStyle uses a type in resyntax.charset.
- The types involved
codes.quine.labs.recheck.diagnostics.AttackPatternStyle.CSharp→codes.quine.labs.resyntax.charset.UStringcodes.quine.labs.recheck.diagnostics.AttackPatternStyle.Java→codes.quine.labs.resyntax.charset.UStringcodes.quine.labs.recheck.diagnostics.AttackPatternStyle.JavaScript→codes.quine.labs.resyntax.charset.UStringcodes.quine.labs.recheck.diagnostics.AttackPatternStyle.PHP→codes.quine.labs.resyntax.charset.UStringcodes.quine.labs.recheck.diagnostics.AttackPatternStyle.Perl→codes.quine.labs.resyntax.charset.UStringcodes.quine.labs.recheck.diagnostics.AttackPatternStyle.Python→codes.quine.labs.resyntax.charset.UStringcodes.quine.labs.recheck.diagnostics.AttackPatternStyle.Ruby→codes.quine.labs.resyntax.charset.UStringcodes.quine.labs.recheck.diagnostics.AttackPatternStyle.Superscript→codes.quine.labs.resyntax.charset.UString
- Direction
- recheck.diagnostics.AttackPatternStyle uses resyntax.charset, so a change to resyntax.charset can break recheck.diagnostics.AttackPatternStyle, while a change to recheck.diagnostics.AttackPatternStyle can't break resyntax.charset.
- Position
- Below the diagonal: recheck.diagnostics.AttackPatternStyle uses a module listed above it, which is the healthy direction.
17→9 recheck.diagnostics.AttackPatternStyle uses recheck.diagnostics✕
- Connections
- 8 pairs of types, where a type in recheck.diagnostics.AttackPatternStyle uses a type in recheck.diagnostics.
- The types involved
codes.quine.labs.recheck.diagnostics.AttackPatternStyle.CSharp→codes.quine.labs.recheck.diagnostics.AttackPatternStylecodes.quine.labs.recheck.diagnostics.AttackPatternStyle.Java→codes.quine.labs.recheck.diagnostics.AttackPatternStylecodes.quine.labs.recheck.diagnostics.AttackPatternStyle.JavaScript→codes.quine.labs.recheck.diagnostics.AttackPatternStylecodes.quine.labs.recheck.diagnostics.AttackPatternStyle.PHP→codes.quine.labs.recheck.diagnostics.AttackPatternStylecodes.quine.labs.recheck.diagnostics.AttackPatternStyle.Perl→codes.quine.labs.recheck.diagnostics.AttackPatternStylecodes.quine.labs.recheck.diagnostics.AttackPatternStyle.Python→codes.quine.labs.recheck.diagnostics.AttackPatternStylecodes.quine.labs.recheck.diagnostics.AttackPatternStyle.Ruby→codes.quine.labs.recheck.diagnostics.AttackPatternStylecodes.quine.labs.recheck.diagnostics.AttackPatternStyle.Superscript→codes.quine.labs.recheck.diagnostics.AttackPatternStyle
- Direction
- recheck.diagnostics.AttackPatternStyle uses recheck.diagnostics, so a change to recheck.diagnostics can break recheck.diagnostics.AttackPatternStyle, while a change to recheck.diagnostics.AttackPatternStyle can't break recheck.diagnostics.
- Position
- Below the diagonal: recheck.diagnostics.AttackPatternStyle uses a module listed above it, which is the healthy direction.
18→2 recheck.diagnostics.Diagnostics uses recheck.common✕
- Connections
- 2 pairs of types, where a type in recheck.diagnostics.Diagnostics uses a type in recheck.common.
- The types involved
codes.quine.labs.recheck.diagnostics.Diagnostics.Safe→codes.quine.labs.recheck.common.Checkercodes.quine.labs.recheck.diagnostics.Diagnostics.Unknown→codes.quine.labs.recheck.common.Checker
- Direction
- recheck.diagnostics.Diagnostics uses recheck.common, so a change to recheck.common can break recheck.diagnostics.Diagnostics, while a change to recheck.diagnostics.Diagnostics can't break recheck.common.
- Position
- Below the diagonal: recheck.diagnostics.Diagnostics uses a module listed above it, which is the healthy direction.
18→6 recheck.diagnostics.Diagnostics uses resyntax.charset✕
- Connections
- 3 pairs of types, where a type in recheck.diagnostics.Diagnostics uses a type in resyntax.charset.
- The types involved
codes.quine.labs.recheck.diagnostics.Diagnostics.Safe→codes.quine.labs.resyntax.charset.UnitModecodes.quine.labs.recheck.diagnostics.Diagnostics.Unknown→codes.quine.labs.resyntax.charset.UnitModecodes.quine.labs.recheck.diagnostics.Diagnostics.Vulnerable→codes.quine.labs.resyntax.charset.UnitMode
- Direction
- recheck.diagnostics.Diagnostics uses resyntax.charset, so a change to resyntax.charset can break recheck.diagnostics.Diagnostics, while a change to recheck.diagnostics.Diagnostics can't break resyntax.charset.
- Position
- Below the diagonal: recheck.diagnostics.Diagnostics uses a module listed above it, which is the healthy direction.
18→9 recheck.diagnostics.Diagnostics uses recheck.diagnostics✕
- Connections
- 9 pairs of types, where a type in recheck.diagnostics.Diagnostics uses a type in recheck.diagnostics.
- The types involved
codes.quine.labs.recheck.diagnostics.Diagnostics.Safe→codes.quine.labs.recheck.diagnostics.Diagnosticscodes.quine.labs.recheck.diagnostics.Diagnostics.Safe→codes.quine.labs.recheck.diagnostics.RefutedAttackcodes.quine.labs.recheck.diagnostics.Diagnostics.Unknown→codes.quine.labs.recheck.diagnostics.Diagnosticscodes.quine.labs.recheck.diagnostics.Diagnostics.Unknown→codes.quine.labs.recheck.diagnostics.RefutedAttackcodes.quine.labs.recheck.diagnostics.Diagnostics.Vulnerable→codes.quine.labs.recheck.diagnostics.AttackPatterncodes.quine.labs.recheck.diagnostics.Diagnostics.Vulnerable→codes.quine.labs.recheck.diagnostics.Diagnosticscodes.quine.labs.recheck.diagnostics.Diagnostics.Vulnerable→codes.quine.labs.recheck.diagnostics.Hotspotcodes.quine.labs.recheck.diagnostics.Diagnostics.Vulnerable→codes.quine.labs.recheck.diagnostics.RefutedAttackcodes.quine.labs.recheck.diagnostics.Diagnostics.Vulnerable→codes.quine.labs.recheck.diagnostics.RuntimeAttack
- Direction
- recheck.diagnostics.Diagnostics uses recheck.diagnostics, so a change to recheck.diagnostics can break recheck.diagnostics.Diagnostics, while a change to recheck.diagnostics.Diagnostics can't break recheck.diagnostics.
- Position
- Below the diagonal: recheck.diagnostics.Diagnostics uses a module listed above it, which is the healthy direction.
18→12 recheck.diagnostics.Diagnostics uses resyntax.dialect✕
- Connections
- 3 pairs of types, where a type in recheck.diagnostics.Diagnostics uses a type in resyntax.dialect.
- The types involved
codes.quine.labs.recheck.diagnostics.Diagnostics.Safe→codes.quine.labs.resyntax.dialect.Dialectcodes.quine.labs.recheck.diagnostics.Diagnostics.Unknown→codes.quine.labs.resyntax.dialect.Dialectcodes.quine.labs.recheck.diagnostics.Diagnostics.Vulnerable→codes.quine.labs.resyntax.dialect.Dialect
- Direction
- recheck.diagnostics.Diagnostics uses resyntax.dialect, so a change to resyntax.dialect can break recheck.diagnostics.Diagnostics, while a change to recheck.diagnostics.Diagnostics can't break resyntax.dialect.
- Position
- Below the diagonal: recheck.diagnostics.Diagnostics uses a module listed above it, which is the healthy direction.
19→2 recheck.verification uses recheck.common✕
- Connections
- 1 pair of types, where a type in recheck.verification uses a type in recheck.common.
- The types involved
codes.quine.labs.recheck.verification.RuntimeAttackVerifier→codes.quine.labs.recheck.common.Context
- Direction
- recheck.verification uses recheck.common, so a change to recheck.common can break recheck.verification, while a change to recheck.verification can't break recheck.common.
- Position
- Below the diagonal: recheck.verification uses a module listed above it, which is the healthy direction.
19→6 recheck.verification uses resyntax.charset✕
- Connections
- 1 pair of types, where a type in recheck.verification uses a type in resyntax.charset.
- The types involved
codes.quine.labs.recheck.verification.RuntimeAttackVerifier→codes.quine.labs.resyntax.charset.UnitMode
- Direction
- recheck.verification uses resyntax.charset, so a change to resyntax.charset can break recheck.verification, while a change to recheck.verification can't break resyntax.charset.
- Position
- Below the diagonal: recheck.verification uses a module listed above it, which is the healthy direction.
19→9 recheck.verification uses recheck.diagnostics✕
- Connections
- 2 pairs of types, where a type in recheck.verification uses a type in recheck.diagnostics.
- The types involved
codes.quine.labs.recheck.verification.RuntimeAttackVerifier→codes.quine.labs.recheck.diagnostics.AttackPatterncodes.quine.labs.recheck.verification.RuntimeAttackVerifier→codes.quine.labs.recheck.diagnostics.RuntimeAttack
- Direction
- recheck.verification uses recheck.diagnostics, so a change to recheck.diagnostics can break recheck.verification, while a change to recheck.verification can't break recheck.diagnostics.
- Position
- Below the diagonal: recheck.verification uses a module listed above it, which is the healthy direction.
19→10 recheck.verification uses recheck.exec✕
- Connections
- 2 pairs of types, where a type in recheck.verification uses a type in recheck.exec.
- The types involved
codes.quine.labs.recheck.verification.RuntimeAttackProgram→codes.quine.labs.recheck.exec.Executorcodes.quine.labs.recheck.verification.RuntimeAttackVerifier→codes.quine.labs.recheck.exec.ExecResult
- Direction
- recheck.verification uses recheck.exec, so a change to recheck.exec can break recheck.verification, while a change to recheck.verification can't break recheck.exec.
- Position
- Below the diagonal: recheck.verification uses a module listed above it, which is the healthy direction.
19→12 recheck.verification uses resyntax.dialect✕
- Connections
- 1 pair of types, where a type in recheck.verification uses a type in resyntax.dialect.
- The types involved
codes.quine.labs.recheck.verification.RuntimeAttackVerifier→codes.quine.labs.resyntax.dialect.Dialect
- Direction
- recheck.verification uses resyntax.dialect, so a change to resyntax.dialect can break recheck.verification, while a change to recheck.verification can't break resyntax.dialect.
- Position
- Below the diagonal: recheck.verification uses a module listed above it, which is the healthy direction.
20→5 resyntax.ir uses resyntax.ast✕
- Connections
- 1 pair of types, where a type in resyntax.ir uses a type in resyntax.ast.
- The types involved
codes.quine.labs.resyntax.ir.IRNode→codes.quine.labs.resyntax.ast.SourceLocation
- Direction
- resyntax.ir uses resyntax.ast, so a change to resyntax.ast can break resyntax.ir, while a change to resyntax.ir can't break resyntax.ast.
- Position
- Below the diagonal: resyntax.ir uses a module listed above it, which is the healthy direction.
20→6 resyntax.ir uses resyntax.charset✕
- Connections
- 5 pairs of types, where a type in resyntax.ir uses a type in resyntax.charset.
- The types involved
codes.quine.labs.resyntax.ir.IRCaseEquivalence→codes.quine.labs.resyntax.charset.CharSetcodes.quine.labs.resyntax.ir.IRPattern→codes.quine.labs.resyntax.charset.CharSetcodes.quine.labs.resyntax.ir.IRPattern→codes.quine.labs.resyntax.charset.UStringcodes.quine.labs.resyntax.ir.IRPattern→codes.quine.labs.resyntax.charset.UnitModecodes.quine.labs.resyntax.ir.IRWordMarkSet→codes.quine.labs.resyntax.charset.CharSet
- Direction
- resyntax.ir uses resyntax.charset, so a change to resyntax.charset can break resyntax.ir, while a change to resyntax.ir can't break resyntax.charset.
- Position
- Below the diagonal: resyntax.ir uses a module listed above it, which is the healthy direction.
20→12 resyntax.ir uses resyntax.dialect✕
- Connections
- 2 pairs of types, where a type in resyntax.ir uses a type in resyntax.dialect.
- The types involved
codes.quine.labs.resyntax.ir.IRCharFlagSet→codes.quine.labs.resyntax.dialect.LineTerminatorSetcodes.quine.labs.resyntax.ir.IRPattern→codes.quine.labs.resyntax.dialect.LineTerminatorSet
- Direction
- resyntax.ir uses resyntax.dialect, so a change to resyntax.dialect can break resyntax.ir, while a change to resyntax.ir can't break resyntax.dialect.
- Position
- Below the diagonal: resyntax.ir uses a module listed above it, which is the healthy direction.
21→5 resyntax.parser uses resyntax.ast✕
- Connections
- 9 pairs of types, where a type in resyntax.parser uses a type in resyntax.ast.
- The types involved
codes.quine.labs.resyntax.parser.Parser→codes.quine.labs.resyntax.ast.FlagSetcodes.quine.labs.resyntax.parser.Parser→codes.quine.labs.resyntax.ast.Nodecodes.quine.labs.resyntax.parser.Rewritten→codes.quine.labs.resyntax.ast.ClassItemcodes.quine.labs.resyntax.parser.Rewritten→codes.quine.labs.resyntax.ast.ClassItemDatacodes.quine.labs.resyntax.parser.Rewritten→codes.quine.labs.resyntax.ast.CommandKindcodes.quine.labs.resyntax.parser.Rewritten→codes.quine.labs.resyntax.ast.ConditionalTestcodes.quine.labs.resyntax.parser.Rewritten→codes.quine.labs.resyntax.ast.Nodecodes.quine.labs.resyntax.parser.Rewritten→codes.quine.labs.resyntax.ast.NodeDatacodes.quine.labs.resyntax.parser.Rewritten→codes.quine.labs.resyntax.ast.SourceLocation
- Direction
- resyntax.parser uses resyntax.ast, so a change to resyntax.ast can break resyntax.parser, while a change to resyntax.parser can't break resyntax.ast.
- Position
- Below the diagonal: resyntax.parser uses a module listed above it, which is the healthy direction.
21→6 resyntax.parser uses resyntax.charset✕
- Connections
- 3 pairs of types, where a type in resyntax.parser uses a type in resyntax.charset.
- The types involved
codes.quine.labs.resyntax.parser.Parser→codes.quine.labs.resyntax.charset.CharSetcodes.quine.labs.resyntax.parser.Parser→codes.quine.labs.resyntax.charset.UnitModecodes.quine.labs.resyntax.parser.PerlLiteralRewriter→codes.quine.labs.resyntax.charset.CharSet
- Direction
- resyntax.parser uses resyntax.charset, so a change to resyntax.charset can break resyntax.parser, while a change to resyntax.parser can't break resyntax.charset.
- Position
- Below the diagonal: resyntax.parser uses a module listed above it, which is the healthy direction.
21→12 resyntax.parser uses resyntax.dialect✕
- Connections
- 2 pairs of types, where a type in resyntax.parser uses a type in resyntax.dialect.
- The types involved
codes.quine.labs.resyntax.parser.FeatureSet→codes.quine.labs.resyntax.dialect.LineTerminatorSetcodes.quine.labs.resyntax.parser.Parser→codes.quine.labs.resyntax.dialect.Dialect
- Direction
- resyntax.parser uses resyntax.dialect, so a change to resyntax.dialect can break resyntax.parser, while a change to resyntax.parser can't break resyntax.dialect.
- Position
- Below the diagonal: resyntax.parser uses a module listed above it, which is the healthy direction.
22→2 recheck uses recheck.common✕
- Connections
- 2 pairs of types, where a type in recheck uses a type in recheck.common.
- The types involved
codes.quine.labs.recheck.ReDoS→codes.quine.labs.recheck.common.CancellationTokencodes.quine.labs.recheck.ReDoS→codes.quine.labs.recheck.common.Context
- Direction
- recheck uses recheck.common, so a change to recheck.common can break recheck, while a change to recheck can't break recheck.common.
- Position
- Below the diagonal: recheck uses a module listed above it, which is the healthy direction.
22→5 recheck uses resyntax.ast✕
- Connections
- 2 pairs of types, where a type in recheck uses a type in resyntax.ast.
- The types involved
codes.quine.labs.recheck.ReDoS→codes.quine.labs.resyntax.ast.FlagSetcodes.quine.labs.recheck.ReDoS→codes.quine.labs.resyntax.ast.Node
- Direction
- recheck uses resyntax.ast, so a change to resyntax.ast can break recheck, while a change to recheck can't break resyntax.ast.
- Position
- Below the diagonal: recheck uses a module listed above it, which is the healthy direction.
22→6 recheck uses resyntax.charset✕
- Connections
- 1 pair of types, where a type in recheck uses a type in resyntax.charset.
- The types involved
codes.quine.labs.recheck.ReDoS→codes.quine.labs.resyntax.charset.UnitMode
- Direction
- recheck uses resyntax.charset, so a change to resyntax.charset can break recheck, while a change to recheck can't break resyntax.charset.
- Position
- Below the diagonal: recheck uses a module listed above it, which is the healthy direction.
22→9 recheck uses recheck.diagnostics✕
- Connections
- 3 pairs of types, where a type in recheck uses a type in recheck.diagnostics.
- The types involved
codes.quine.labs.recheck.ReDoS→codes.quine.labs.recheck.diagnostics.Diagnosticscodes.quine.labs.recheck.ReDoS→codes.quine.labs.recheck.diagnostics.Hotspotcodes.quine.labs.recheck.ReDoS→codes.quine.labs.recheck.diagnostics.RefutedAttack
- Direction
- recheck uses recheck.diagnostics, so a change to recheck.diagnostics can break recheck, while a change to recheck can't break recheck.diagnostics.
- Position
- Below the diagonal: recheck uses a module listed above it, which is the healthy direction.
22→12 recheck uses resyntax.dialect✕
- Connections
- 1 pair of types, where a type in recheck uses a type in resyntax.dialect.
- The types involved
codes.quine.labs.recheck.ReDoS→codes.quine.labs.resyntax.dialect.Dialect
- Direction
- recheck uses resyntax.dialect, so a change to resyntax.dialect can break recheck, while a change to recheck can't break resyntax.dialect.
- Position
- Below the diagonal: recheck uses a module listed above it, which is the healthy direction.
22→20 recheck uses resyntax.ir✕
- Connections
- 1 pair of types, where a type in recheck uses a type in resyntax.ir.
- The types involved
codes.quine.labs.recheck.ReDoS→codes.quine.labs.resyntax.ir.IRPattern
- Direction
- recheck uses resyntax.ir, so a change to resyntax.ir can break recheck, while a change to recheck can't break resyntax.ir.
- Position
- Below the diagonal: recheck uses a module listed above it, which is the healthy direction.
23→2 recheck.automaton uses recheck.common✕
- Connections
- 6 pairs of types, where a type in recheck.automaton uses a type in recheck.common.
- The types involved
codes.quine.labs.recheck.automaton.AutomatonChecker→codes.quine.labs.recheck.common.Contextcodes.quine.labs.recheck.automaton.EpsNFA→codes.quine.labs.recheck.common.Contextcodes.quine.labs.recheck.automaton.EpsNFABuilder→codes.quine.labs.recheck.common.Contextcodes.quine.labs.recheck.automaton.NFA→codes.quine.labs.recheck.common.Contextcodes.quine.labs.recheck.automaton.NFAwLA→codes.quine.labs.recheck.common.Contextcodes.quine.labs.recheck.automaton.OrderedNFA→codes.quine.labs.recheck.common.Context
- Direction
- recheck.automaton uses recheck.common, so a change to recheck.common can break recheck.automaton, while a change to recheck.automaton can't break recheck.common.
- Position
- Below the diagonal: recheck.automaton uses a module listed above it, which is the healthy direction.
23→3 recheck.automaton uses recheck.data✕
- Connections
- 4 pairs of types, where a type in recheck.automaton uses a type in recheck.data.
- The types involved
codes.quine.labs.recheck.automaton.DFA→codes.quine.labs.recheck.data.Graphcodes.quine.labs.recheck.automaton.NFAwLA→codes.quine.labs.recheck.data.Graphcodes.quine.labs.recheck.automaton.NFAwLA→codes.quine.labs.recheck.data.MultiSetcodes.quine.labs.recheck.automaton.OrderedNFA→codes.quine.labs.recheck.data.Graph
- Direction
- recheck.automaton uses recheck.data, so a change to recheck.data can break recheck.automaton, while a change to recheck.automaton can't break recheck.data.
- Position
- Below the diagonal: recheck.automaton uses a module listed above it, which is the healthy direction.
23→5 recheck.automaton uses resyntax.ast✕
- Connections
- 2 pairs of types, where a type in recheck.automaton uses a type in resyntax.ast.
- The types involved
codes.quine.labs.recheck.automaton.NFAwLA→codes.quine.labs.resyntax.ast.SourceLocationcodes.quine.labs.recheck.automaton.OrderedNFA→codes.quine.labs.resyntax.ast.SourceLocation
- Direction
- recheck.automaton uses resyntax.ast, so a change to resyntax.ast can break recheck.automaton, while a change to recheck.automaton can't break resyntax.ast.
- Position
- Below the diagonal: recheck.automaton uses a module listed above it, which is the healthy direction.
23→6 recheck.automaton uses resyntax.charset✕
- Connections
- 2 pairs of types, where a type in recheck.automaton uses a type in resyntax.charset.
- The types involved
codes.quine.labs.recheck.automaton.EpsNFA→codes.quine.labs.resyntax.charset.CharSetcodes.quine.labs.recheck.automaton.Witness→codes.quine.labs.resyntax.charset.UnitMode
- Direction
- recheck.automaton uses resyntax.charset, so a change to resyntax.charset can break recheck.automaton, while a change to recheck.automaton can't break resyntax.charset.
- Position
- Below the diagonal: recheck.automaton uses a module listed above it, which is the healthy direction.
23→9 recheck.automaton uses recheck.diagnostics✕
- Connections
- 1 pair of types, where a type in recheck.automaton uses a type in recheck.diagnostics.
- The types involved
codes.quine.labs.recheck.automaton.Witness→codes.quine.labs.recheck.diagnostics.AttackPattern
- Direction
- recheck.automaton uses recheck.diagnostics, so a change to recheck.diagnostics can break recheck.automaton, while a change to recheck.automaton can't break recheck.diagnostics.
- Position
- Below the diagonal: recheck.automaton uses a module listed above it, which is the healthy direction.
23→13 recheck.automaton uses resyntax.ir.alphabet✕
- Connections
- 2 pairs of types, where a type in recheck.automaton uses a type in resyntax.ir.alphabet.
- The types involved
codes.quine.labs.recheck.automaton.CharKindState→codes.quine.labs.resyntax.ir.alphabet.CharKindcodes.quine.labs.recheck.automaton.EpsNFA→codes.quine.labs.resyntax.ir.alphabet.PatternAlphabet
- Direction
- recheck.automaton uses resyntax.ir.alphabet, so a change to resyntax.ir.alphabet can break recheck.automaton, while a change to recheck.automaton can't break resyntax.ir.alphabet.
- Position
- Below the diagonal: recheck.automaton uses a module listed above it, which is the healthy direction.
23→14 recheck.automaton uses recheck.automaton.EpsNFA✕
- Connections
- 1 pair of types, where a type in recheck.automaton uses a type in recheck.automaton.EpsNFA.
- The types involved
codes.quine.labs.recheck.automaton.EpsNFA→codes.quine.labs.recheck.automaton.EpsNFA.Transition
- Direction
- recheck.automaton uses recheck.automaton.EpsNFA, so a change to recheck.automaton.EpsNFA can break recheck.automaton, while a change to recheck.automaton can't break recheck.automaton.EpsNFA.
- Position
- Below the diagonal: recheck.automaton uses a module listed above it, which is the healthy direction.
23→20 recheck.automaton uses resyntax.ir✕
- Connections
- 1 pair of types, where a type in recheck.automaton uses a type in resyntax.ir.
- The types involved
codes.quine.labs.recheck.automaton.EpsNFABuilder→codes.quine.labs.resyntax.ir.IRPattern
- Direction
- recheck.automaton uses resyntax.ir, so a change to resyntax.ir can break recheck.automaton, while a change to recheck.automaton can't break resyntax.ir.
- Position
- Below the diagonal: recheck.automaton uses a module listed above it, which is the healthy direction.
24→18 recheck.diagnostics.Diagnostics.ErrorKind uses recheck.diagnostics.Diagnostics✕
- Connections
- 6 pairs of types, where a type in recheck.diagnostics.Diagnostics.ErrorKind uses a type in recheck.diagnostics.Diagnostics.
- The types involved
codes.quine.labs.recheck.diagnostics.Diagnostics.ErrorKind.Cancel→codes.quine.labs.recheck.diagnostics.Diagnostics.ErrorKindcodes.quine.labs.recheck.diagnostics.Diagnostics.ErrorKind.InvalidRegExp→codes.quine.labs.recheck.diagnostics.Diagnostics.ErrorKindcodes.quine.labs.recheck.diagnostics.Diagnostics.ErrorKind.RuntimeAttacksRefuted→codes.quine.labs.recheck.diagnostics.Diagnostics.ErrorKindcodes.quine.labs.recheck.diagnostics.Diagnostics.ErrorKind.Timeout→codes.quine.labs.recheck.diagnostics.Diagnostics.ErrorKindcodes.quine.labs.recheck.diagnostics.Diagnostics.ErrorKind.Unexpected→codes.quine.labs.recheck.diagnostics.Diagnostics.ErrorKindcodes.quine.labs.recheck.diagnostics.Diagnostics.ErrorKind.Unsupported→codes.quine.labs.recheck.diagnostics.Diagnostics.ErrorKind
- Direction
- recheck.diagnostics.Diagnostics.ErrorKind uses recheck.diagnostics.Diagnostics, so a change to recheck.diagnostics.Diagnostics can break recheck.diagnostics.Diagnostics.ErrorKind, while a change to recheck.diagnostics.Diagnostics.ErrorKind can't break recheck.diagnostics.Diagnostics.
- Position
- Below the diagonal: recheck.diagnostics.Diagnostics.ErrorKind uses a module listed above it, which is the healthy direction.
25→5 recheck.vm.Inst uses resyntax.ast✕
- Connections
- 2 pairs of types, where a type in recheck.vm.Inst uses a type in resyntax.ast.
- The types involved
codes.quine.labs.recheck.vm.Inst.Read→codes.quine.labs.resyntax.ast.SourceLocationcodes.quine.labs.recheck.vm.Inst.ReadBack→codes.quine.labs.resyntax.ast.SourceLocation
- Direction
- recheck.vm.Inst uses resyntax.ast, so a change to resyntax.ast can break recheck.vm.Inst, while a change to recheck.vm.Inst can't break resyntax.ast.
- Position
- Below the diagonal: recheck.vm.Inst uses a module listed above it, which is the healthy direction.
25→20 recheck.vm.Inst uses resyntax.ir✕
- Connections
- 1 pair of types, where a type in recheck.vm.Inst uses a type in resyntax.ir.
- The types involved
codes.quine.labs.recheck.vm.Inst.StepBack→codes.quine.labs.resyntax.ir.IRLookBehindStartRange
- Direction
- recheck.vm.Inst uses resyntax.ir, so a change to resyntax.ir can break recheck.vm.Inst, while a change to recheck.vm.Inst can't break resyntax.ir.
- Position
- Below the diagonal: recheck.vm.Inst uses a module listed above it, which is the healthy direction.
25→37 recheck.vm.Inst uses recheck.vm part of a loop✕
- Connections
- 25 pairs of types, where a type in recheck.vm.Inst uses a type in recheck.vm.
- The types involved
codes.quine.labs.recheck.vm.Inst.Cmp→codes.quine.labs.recheck.vm.CounterRegcodes.quine.labs.recheck.vm.Inst.Cmp→codes.quine.labs.recheck.vm.Labelcodes.quine.labs.recheck.vm.Inst.CmpCanary→codes.quine.labs.recheck.vm.CanaryRegcodes.quine.labs.recheck.vm.Inst.CmpCanary→codes.quine.labs.recheck.vm.Labelcodes.quine.labs.recheck.vm.Inst.Commit→codes.quine.labs.recheck.vm.Labelcodes.quine.labs.recheck.vm.Inst.Fail→codes.quine.labs.recheck.vm.Labelcodes.quine.labs.recheck.vm.Inst.IfCap→codes.quine.labs.recheck.vm.Labelcodes.quine.labs.recheck.vm.Inst.Inc→codes.quine.labs.recheck.vm.CounterRegcodes.quine.labs.recheck.vm.Inst.Jmp→codes.quine.labs.recheck.vm.Labelcodes.quine.labs.recheck.vm.Inst.Leave→codes.quine.labs.recheck.vm.Labelcodes.quine.labs.recheck.vm.Inst.NonTerminator→codes.quine.labs.recheck.vm.Instcodes.quine.labs.recheck.vm.Inst.Ok→codes.quine.labs.recheck.vm.Labelcodes.quine.labs.recheck.vm.Inst.RejectEmptyIteration→codes.quine.labs.recheck.vm.CanaryRegcodes.quine.labs.recheck.vm.Inst.Reset→codes.quine.labs.recheck.vm.CounterRegcodes.quine.labs.recheck.vm.Inst.Rollback→codes.quine.labs.recheck.vm.Labelcodes.quine.labs.recheck.vm.Inst.SetCanary→codes.quine.labs.recheck.vm.CanaryRegcodes.quine.labs.recheck.vm.Inst.StepBack→codes.quine.labs.recheck.vm.CounterRegcodes.quine.labs.recheck.vm.Inst.StepBack→codes.quine.labs.recheck.vm.Labelcodes.quine.labs.recheck.vm.Inst.Terminator→codes.quine.labs.recheck.vm.Instcodes.quine.labs.recheck.vm.Inst.Terminator→codes.quine.labs.recheck.vm.Labelcodes.quine.labs.recheck.vm.Inst.Try→codes.quine.labs.recheck.vm.Labelcodes.quine.labs.recheck.vm.Inst.TryBarrier→codes.quine.labs.recheck.vm.Labelcodes.quine.labs.recheck.vm.Inst.TryLA→codes.quine.labs.recheck.vm.Labelcodes.quine.labs.recheck.vm.Inst.TryLB→codes.quine.labs.recheck.vm.Labelcodes.quine.labs.recheck.vm.Inst.Tx→codes.quine.labs.recheck.vm.Label
- Direction
- recheck.vm.Inst uses recheck.vm, so a change to recheck.vm can break recheck.vm.Inst, while a change to recheck.vm.Inst can't break recheck.vm.
- 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.
26→6 resyntax.ir.IRAssertKind uses resyntax.charset✕
- Connections
- 4 pairs of types, where a type in resyntax.ir.IRAssertKind uses a type in resyntax.charset.
- The types involved
codes.quine.labs.resyntax.ir.IRAssertKind.MarkWordBoundary→codes.quine.labs.resyntax.charset.CharSetcodes.quine.labs.resyntax.ir.IRAssertKind.NotMarkWordBoundary→codes.quine.labs.resyntax.charset.CharSetcodes.quine.labs.resyntax.ir.IRAssertKind.NotWordBoundary→codes.quine.labs.resyntax.charset.CharSetcodes.quine.labs.resyntax.ir.IRAssertKind.WordBoundary→codes.quine.labs.resyntax.charset.CharSet
- Direction
- resyntax.ir.IRAssertKind uses resyntax.charset, so a change to resyntax.charset can break resyntax.ir.IRAssertKind, while a change to resyntax.ir.IRAssertKind can't break resyntax.charset.
- Position
- Below the diagonal: resyntax.ir.IRAssertKind uses a module listed above it, which is the healthy direction.
26→12 resyntax.ir.IRAssertKind uses resyntax.dialect✕
- Connections
- 3 pairs of types, where a type in resyntax.ir.IRAssertKind uses a type in resyntax.dialect.
- The types involved
codes.quine.labs.resyntax.ir.IRAssertKind.ChompTextEnd→codes.quine.labs.resyntax.dialect.LineTerminatorSetcodes.quine.labs.resyntax.ir.IRAssertKind.LineBegin→codes.quine.labs.resyntax.dialect.LineTerminatorSetcodes.quine.labs.resyntax.ir.IRAssertKind.LineEnd→codes.quine.labs.resyntax.dialect.LineTerminatorSet
- Direction
- resyntax.ir.IRAssertKind uses resyntax.dialect, so a change to resyntax.dialect can break resyntax.ir.IRAssertKind, while a change to resyntax.ir.IRAssertKind can't break resyntax.dialect.
- Position
- Below the diagonal: resyntax.ir.IRAssertKind uses a module listed above it, which is the healthy direction.
26→20 resyntax.ir.IRAssertKind uses resyntax.ir✕
- Connections
- 13 pairs of types, where a type in resyntax.ir.IRAssertKind uses a type in resyntax.ir.
- The types involved
codes.quine.labs.resyntax.ir.IRAssertKind.ChompTextEnd→codes.quine.labs.resyntax.ir.IRAssertKindcodes.quine.labs.resyntax.ir.IRAssertKind.LineBegin→codes.quine.labs.resyntax.ir.IRAssertKindcodes.quine.labs.resyntax.ir.IRAssertKind.LineBegin→codes.quine.labs.resyntax.ir.IRLineBeginAtEndcodes.quine.labs.resyntax.ir.IRAssertKind.LineEnd→codes.quine.labs.resyntax.ir.IRAssertKindcodes.quine.labs.resyntax.ir.IRAssertKind.MarkWordBoundary→codes.quine.labs.resyntax.ir.IRAssertKindcodes.quine.labs.resyntax.ir.IRAssertKind.MarkWordBoundary→codes.quine.labs.resyntax.ir.IRWordMarkSetcodes.quine.labs.resyntax.ir.IRAssertKind.NotBetweenCRLF→codes.quine.labs.resyntax.ir.IRAssertKindcodes.quine.labs.resyntax.ir.IRAssertKind.NotMarkWordBoundary→codes.quine.labs.resyntax.ir.IRAssertKindcodes.quine.labs.resyntax.ir.IRAssertKind.NotMarkWordBoundary→codes.quine.labs.resyntax.ir.IRWordMarkSetcodes.quine.labs.resyntax.ir.IRAssertKind.NotWordBoundary→codes.quine.labs.resyntax.ir.IRAssertKindcodes.quine.labs.resyntax.ir.IRAssertKind.TextBegin→codes.quine.labs.resyntax.ir.IRAssertKindcodes.quine.labs.resyntax.ir.IRAssertKind.TextEnd→codes.quine.labs.resyntax.ir.IRAssertKindcodes.quine.labs.resyntax.ir.IRAssertKind.WordBoundary→codes.quine.labs.resyntax.ir.IRAssertKind
- Direction
- resyntax.ir.IRAssertKind uses resyntax.ir, so a change to resyntax.ir can break resyntax.ir.IRAssertKind, while a change to resyntax.ir.IRAssertKind can't break resyntax.ir.
- Position
- Below the diagonal: resyntax.ir.IRAssertKind uses a module listed above it, which is the healthy direction.
27→6 resyntax.ir.IRBackReferenceFolding uses resyntax.charset✕
- Connections
- 1 pair of types, where a type in resyntax.ir.IRBackReferenceFolding uses a type in resyntax.charset.
- The types involved
codes.quine.labs.resyntax.ir.IRBackReferenceFolding.Full→codes.quine.labs.resyntax.charset.UString
- Direction
- resyntax.ir.IRBackReferenceFolding uses resyntax.charset, so a change to resyntax.charset can break resyntax.ir.IRBackReferenceFolding, while a change to resyntax.ir.IRBackReferenceFolding can't break resyntax.charset.
- Position
- Below the diagonal: resyntax.ir.IRBackReferenceFolding uses a module listed above it, which is the healthy direction.
27→20 resyntax.ir.IRBackReferenceFolding uses resyntax.ir✕
- Connections
- 2 pairs of types, where a type in resyntax.ir.IRBackReferenceFolding uses a type in resyntax.ir.
- The types involved
codes.quine.labs.resyntax.ir.IRBackReferenceFolding.Full→codes.quine.labs.resyntax.ir.IRBackReferenceFoldingcodes.quine.labs.resyntax.ir.IRBackReferenceFolding.Simple→codes.quine.labs.resyntax.ir.IRBackReferenceFolding
- Direction
- resyntax.ir.IRBackReferenceFolding uses resyntax.ir, so a change to resyntax.ir can break resyntax.ir.IRBackReferenceFolding, while a change to resyntax.ir.IRBackReferenceFolding can't break resyntax.ir.
- Position
- Below the diagonal: resyntax.ir.IRBackReferenceFolding uses a module listed above it, which is the healthy direction.
28→6 resyntax.ir.IRCaseEquivalence uses resyntax.charset✕
- Connections
- 13 pairs of types, where a type in resyntax.ir.IRCaseEquivalence uses a type in resyntax.charset.
- The types involved
codes.quine.labs.resyntax.ir.IRCaseEquivalence.Identity→codes.quine.labs.resyntax.charset.CharSetcodes.quine.labs.resyntax.ir.IRCaseEquivalence.JavaASCII→codes.quine.labs.resyntax.charset.CharSetcodes.quine.labs.resyntax.ir.IRCaseEquivalence.JavaUnicode→codes.quine.labs.resyntax.charset.CharSetcodes.quine.labs.resyntax.ir.IRCaseEquivalence.Keyed→codes.quine.labs.resyntax.charset.CaseMappingcodes.quine.labs.resyntax.ir.IRCaseEquivalence.Keyed→codes.quine.labs.resyntax.charset.CharSetcodes.quine.labs.resyntax.ir.IRCaseEquivalence.Keyed→codes.quine.labs.resyntax.charset.UnitModecodes.quine.labs.resyntax.ir.IRCaseEquivalence.PCRERestrict→codes.quine.labs.resyntax.charset.CaseMappingcodes.quine.labs.resyntax.ir.IRCaseEquivalence.PCRERestrict→codes.quine.labs.resyntax.charset.CharSetcodes.quine.labs.resyntax.ir.IRCaseEquivalence.PCRERestrict→codes.quine.labs.resyntax.charset.UnitModecodes.quine.labs.resyntax.ir.IRCaseEquivalence.PerlLocale→codes.quine.labs.resyntax.charset.CharSetcodes.quine.labs.resyntax.ir.IRCaseEquivalence.PerlLocale→codes.quine.labs.resyntax.charset.UnitModecodes.quine.labs.resyntax.ir.IRCaseEquivalence.PerlNative→codes.quine.labs.resyntax.charset.CharSetcodes.quine.labs.resyntax.ir.IRCaseEquivalence.PerlNative→codes.quine.labs.resyntax.charset.UnitMode
- Direction
- resyntax.ir.IRCaseEquivalence uses resyntax.charset, so a change to resyntax.charset can break resyntax.ir.IRCaseEquivalence, while a change to resyntax.ir.IRCaseEquivalence can't break resyntax.charset.
- Position
- Below the diagonal: resyntax.ir.IRCaseEquivalence uses a module listed above it, which is the healthy direction.
28→20 resyntax.ir.IRCaseEquivalence uses resyntax.ir✕
- Connections
- 7 pairs of types, where a type in resyntax.ir.IRCaseEquivalence uses a type in resyntax.ir.
- The types involved
codes.quine.labs.resyntax.ir.IRCaseEquivalence.Identity→codes.quine.labs.resyntax.ir.IRCaseEquivalencecodes.quine.labs.resyntax.ir.IRCaseEquivalence.JavaASCII→codes.quine.labs.resyntax.ir.IRCaseEquivalencecodes.quine.labs.resyntax.ir.IRCaseEquivalence.JavaUnicode→codes.quine.labs.resyntax.ir.IRCaseEquivalencecodes.quine.labs.resyntax.ir.IRCaseEquivalence.Keyed→codes.quine.labs.resyntax.ir.IRCaseEquivalencecodes.quine.labs.resyntax.ir.IRCaseEquivalence.PCRERestrict→codes.quine.labs.resyntax.ir.IRCaseEquivalencecodes.quine.labs.resyntax.ir.IRCaseEquivalence.PerlLocale→codes.quine.labs.resyntax.ir.IRCaseEquivalencecodes.quine.labs.resyntax.ir.IRCaseEquivalence.PerlNative→codes.quine.labs.resyntax.ir.IRCaseEquivalence
- Direction
- resyntax.ir.IRCaseEquivalence uses resyntax.ir, so a change to resyntax.ir can break resyntax.ir.IRCaseEquivalence, while a change to resyntax.ir.IRCaseEquivalence can't break resyntax.ir.
- Position
- Below the diagonal: resyntax.ir.IRCaseEquivalence uses a module listed above it, which is the healthy direction.
29→5 resyntax.ir.IRNodeData uses resyntax.ast✕
- Connections
- 1 pair of types, where a type in resyntax.ir.IRNodeData uses a type in resyntax.ast.
- The types involved
codes.quine.labs.resyntax.ir.IRNodeData.Unsupported→codes.quine.labs.resyntax.ast.NodeData
- Direction
- resyntax.ir.IRNodeData uses resyntax.ast, so a change to resyntax.ast can break resyntax.ir.IRNodeData, while a change to resyntax.ir.IRNodeData can't break resyntax.ast.
- Position
- Below the diagonal: resyntax.ir.IRNodeData uses a module listed above it, which is the healthy direction.
29→6 resyntax.ir.IRNodeData uses resyntax.charset✕
- Connections
- 2 pairs of types, where a type in resyntax.ir.IRNodeData uses a type in resyntax.charset.
- The types involved
codes.quine.labs.resyntax.ir.IRNodeData.Chars→codes.quine.labs.resyntax.charset.CharSetcodes.quine.labs.resyntax.ir.IRNodeData.Strings→codes.quine.labs.resyntax.charset.ClassSet
- Direction
- resyntax.ir.IRNodeData uses resyntax.charset, so a change to resyntax.charset can break resyntax.ir.IRNodeData, while a change to resyntax.ir.IRNodeData can't break resyntax.charset.
- Position
- Below the diagonal: resyntax.ir.IRNodeData uses a module listed above it, which is the healthy direction.
29→20 resyntax.ir.IRNodeData uses resyntax.ir✕
- Connections
- 36 pairs of types, where a type in resyntax.ir.IRNodeData uses a type in resyntax.ir. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
codes.quine.labs.resyntax.ir.IRNodeData.Assert→codes.quine.labs.resyntax.ir.IRAssertKindcodes.quine.labs.resyntax.ir.IRNodeData.Assert→codes.quine.labs.resyntax.ir.IRNodeDatacodes.quine.labs.resyntax.ir.IRNodeData.Atomic→codes.quine.labs.resyntax.ir.IRNodecodes.quine.labs.resyntax.ir.IRNodeData.Atomic→codes.quine.labs.resyntax.ir.IRNodeDatacodes.quine.labs.resyntax.ir.IRNodeData.BackReference→codes.quine.labs.resyntax.ir.IRBackReferenceFoldingcodes.quine.labs.resyntax.ir.IRNodeData.BackReference→codes.quine.labs.resyntax.ir.IRCaseEquivalencecodes.quine.labs.resyntax.ir.IRNodeData.BackReference→codes.quine.labs.resyntax.ir.IRNodeDatacodes.quine.labs.resyntax.ir.IRNodeData.BacktrackControl→codes.quine.labs.resyntax.ir.IRBacktrackControlcodes.quine.labs.resyntax.ir.IRNodeData.BacktrackControl→codes.quine.labs.resyntax.ir.IRNodeDatacodes.quine.labs.resyntax.ir.IRNodeData.Capture→codes.quine.labs.resyntax.ir.IRNodecodes.quine.labs.resyntax.ir.IRNodeData.Capture→codes.quine.labs.resyntax.ir.IRNodeDatacodes.quine.labs.resyntax.ir.IRNodeData.Chars→codes.quine.labs.resyntax.ir.IRNodeDatacodes.quine.labs.resyntax.ir.IRNodeData.Conditional→codes.quine.labs.resyntax.ir.IRConditioncodes.quine.labs.resyntax.ir.IRNodeData.Conditional→codes.quine.labs.resyntax.ir.IRNodecodes.quine.labs.resyntax.ir.IRNodeData.Conditional→codes.quine.labs.resyntax.ir.IRNodeDatacodes.quine.labs.resyntax.ir.IRNodeData.Disjunction→codes.quine.labs.resyntax.ir.IRNodecodes.quine.labs.resyntax.ir.IRNodeData.Disjunction→codes.quine.labs.resyntax.ir.IRNodeDatacodes.quine.labs.resyntax.ir.IRNodeData.Empty→codes.quine.labs.resyntax.ir.IRNodeDatacodes.quine.labs.resyntax.ir.IRNodeData.LookAhead→codes.quine.labs.resyntax.ir.IRNodecodes.quine.labs.resyntax.ir.IRNodeData.LookAhead→codes.quine.labs.resyntax.ir.IRNodeDatacodes.quine.labs.resyntax.ir.IRNodeData.LookBehind→codes.quine.labs.resyntax.ir.IRLookBehindMatchcodes.quine.labs.resyntax.ir.IRNodeData.LookBehind→codes.quine.labs.resyntax.ir.IRNodecodes.quine.labs.resyntax.ir.IRNodeData.LookBehind→codes.quine.labs.resyntax.ir.IRNodeDatacodes.quine.labs.resyntax.ir.IRNodeData.NonAtomicLookAhead→codes.quine.labs.resyntax.ir.IRNodecodes.quine.labs.resyntax.ir.IRNodeData.NonAtomicLookAhead→codes.quine.labs.resyntax.ir.IRNodeData
- Direction
- resyntax.ir.IRNodeData uses resyntax.ir, so a change to resyntax.ir can break resyntax.ir.IRNodeData, while a change to resyntax.ir.IRNodeData can't break resyntax.ir.
- Position
- Below the diagonal: resyntax.ir.IRNodeData uses a module listed above it, which is the healthy direction.
30→5 resyntax.ir.IRQuantifier uses resyntax.ast✕
- Connections
- 2 pairs of types, where a type in resyntax.ir.IRQuantifier uses a type in resyntax.ast.
- The types involved
codes.quine.labs.resyntax.ir.IRQuantifier.Bounded→codes.quine.labs.resyntax.ast.BacktrackStrategycodes.quine.labs.resyntax.ir.IRQuantifier.Unbounded→codes.quine.labs.resyntax.ast.BacktrackStrategy
- Direction
- resyntax.ir.IRQuantifier uses resyntax.ast, so a change to resyntax.ast can break resyntax.ir.IRQuantifier, while a change to resyntax.ir.IRQuantifier can't break resyntax.ast.
- Position
- Below the diagonal: resyntax.ir.IRQuantifier uses a module listed above it, which is the healthy direction.
30→20 resyntax.ir.IRQuantifier uses resyntax.ir✕
- Connections
- 3 pairs of types, where a type in resyntax.ir.IRQuantifier uses a type in resyntax.ir.
- The types involved
codes.quine.labs.resyntax.ir.IRQuantifier.Bounded→codes.quine.labs.resyntax.ir.IRQuantifiercodes.quine.labs.resyntax.ir.IRQuantifier.Exact→codes.quine.labs.resyntax.ir.IRQuantifiercodes.quine.labs.resyntax.ir.IRQuantifier.Unbounded→codes.quine.labs.resyntax.ir.IRQuantifier
- Direction
- resyntax.ir.IRQuantifier uses resyntax.ir, so a change to resyntax.ir can break resyntax.ir.IRQuantifier, while a change to resyntax.ir.IRQuantifier can't break resyntax.ir.
- Position
- Below the diagonal: resyntax.ir.IRQuantifier uses a module listed above it, which is the healthy direction.
31→5 resyntax.ir.build.IRCharResolver uses resyntax.ast✕
- Connections
- 2 pairs of types, where a type in resyntax.ir.build.IRCharResolver uses a type in resyntax.ast.
- The types involved
codes.quine.labs.resyntax.ir.build.IRCharResolver.Lit→codes.quine.labs.resyntax.ast.EscapeStylecodes.quine.labs.resyntax.ir.build.IRCharResolver.Lit→codes.quine.labs.resyntax.ast.SourceLocation
- Direction
- resyntax.ir.build.IRCharResolver uses resyntax.ast, so a change to resyntax.ast can break resyntax.ir.build.IRCharResolver, while a change to resyntax.ir.build.IRCharResolver can't break resyntax.ast.
- Position
- Below the diagonal: resyntax.ir.build.IRCharResolver uses a module listed above it, which is the healthy direction.
31→6 resyntax.ir.build.IRCharResolver uses resyntax.charset✕
- Connections
- 1 pair of types, where a type in resyntax.ir.build.IRCharResolver uses a type in resyntax.charset.
- The types involved
codes.quine.labs.resyntax.ir.build.IRCharResolver.Grammar→codes.quine.labs.resyntax.charset.CharSet
- Direction
- resyntax.ir.build.IRCharResolver uses resyntax.charset, so a change to resyntax.charset can break resyntax.ir.build.IRCharResolver, while a change to resyntax.ir.build.IRCharResolver can't break resyntax.charset.
- Position
- Below the diagonal: resyntax.ir.build.IRCharResolver uses a module listed above it, which is the healthy direction.
31→20 resyntax.ir.build.IRCharResolver uses resyntax.ir✕
- Connections
- 2 pairs of types, where a type in resyntax.ir.build.IRCharResolver uses a type in resyntax.ir.
- The types involved
codes.quine.labs.resyntax.ir.build.IRCharResolver.Grammar→codes.quine.labs.resyntax.ir.IRNodecodes.quine.labs.resyntax.ir.build.IRCharResolver.Lit→codes.quine.labs.resyntax.ir.IRCharFlagSet
- Direction
- resyntax.ir.build.IRCharResolver uses resyntax.ir, so a change to resyntax.ir can break resyntax.ir.build.IRCharResolver, while a change to resyntax.ir.build.IRCharResolver can't break resyntax.ir.
- Position
- Below the diagonal: resyntax.ir.build.IRCharResolver uses a module listed above it, which is the healthy direction.
32→6 recheck.automaton.Complexity uses resyntax.charset✕
- Connections
- 3 pairs of types, where a type in recheck.automaton.Complexity uses a type in resyntax.charset.
- The types involved
codes.quine.labs.recheck.automaton.Complexity.Exponential→codes.quine.labs.resyntax.charset.UnitModecodes.quine.labs.recheck.automaton.Complexity.Polynomial→codes.quine.labs.resyntax.charset.UnitModecodes.quine.labs.recheck.automaton.Complexity.Vulnerable→codes.quine.labs.resyntax.charset.UnitMode
- Direction
- recheck.automaton.Complexity uses resyntax.charset, so a change to resyntax.charset can break recheck.automaton.Complexity, while a change to recheck.automaton.Complexity can't break resyntax.charset.
- Position
- Below the diagonal: recheck.automaton.Complexity uses a module listed above it, which is the healthy direction.
32→9 recheck.automaton.Complexity uses recheck.diagnostics✕
- Connections
- 6 pairs of types, where a type in recheck.automaton.Complexity uses a type in recheck.diagnostics.
- The types involved
codes.quine.labs.recheck.automaton.Complexity.Exponential→codes.quine.labs.recheck.diagnostics.AttackPatterncodes.quine.labs.recheck.automaton.Complexity.Exponential→codes.quine.labs.recheck.diagnostics.Hotspotcodes.quine.labs.recheck.automaton.Complexity.Polynomial→codes.quine.labs.recheck.diagnostics.AttackPatterncodes.quine.labs.recheck.automaton.Complexity.Polynomial→codes.quine.labs.recheck.diagnostics.Hotspotcodes.quine.labs.recheck.automaton.Complexity.Vulnerable→codes.quine.labs.recheck.diagnostics.AttackPatterncodes.quine.labs.recheck.automaton.Complexity.Vulnerable→codes.quine.labs.recheck.diagnostics.Hotspot
- Direction
- recheck.automaton.Complexity uses recheck.diagnostics, so a change to recheck.diagnostics can break recheck.automaton.Complexity, while a change to recheck.automaton.Complexity can't break recheck.diagnostics.
- Position
- Below the diagonal: recheck.automaton.Complexity uses a module listed above it, which is the healthy direction.
32→23 recheck.automaton.Complexity uses recheck.automaton✕
- Connections
- 5 pairs of types, where a type in recheck.automaton.Complexity uses a type in recheck.automaton.
- The types involved
codes.quine.labs.recheck.automaton.Complexity.Exponential→codes.quine.labs.recheck.automaton.Witnesscodes.quine.labs.recheck.automaton.Complexity.Polynomial→codes.quine.labs.recheck.automaton.Witnesscodes.quine.labs.recheck.automaton.Complexity.Safe→codes.quine.labs.recheck.automaton.Complexitycodes.quine.labs.recheck.automaton.Complexity.Vulnerable→codes.quine.labs.recheck.automaton.Complexitycodes.quine.labs.recheck.automaton.Complexity.Vulnerable→codes.quine.labs.recheck.automaton.Witness
- Direction
- recheck.automaton.Complexity uses recheck.automaton, so a change to recheck.automaton can break recheck.automaton.Complexity, while a change to recheck.automaton.Complexity can't break recheck.automaton.
- Position
- Below the diagonal: recheck.automaton.Complexity uses a module listed above it, which is the healthy direction.
33→14 recheck.automaton.EpsNFA.AssertKind uses recheck.automaton.EpsNFA✕
- Connections
- 10 pairs of types, where a type in recheck.automaton.EpsNFA.AssertKind uses a type in recheck.automaton.EpsNFA.
- The types involved
codes.quine.labs.recheck.automaton.EpsNFA.AssertKind.ChompTextEnd→codes.quine.labs.recheck.automaton.EpsNFA.AssertKindcodes.quine.labs.recheck.automaton.EpsNFA.AssertKind.LineBegin→codes.quine.labs.recheck.automaton.EpsNFA.AssertKindcodes.quine.labs.recheck.automaton.EpsNFA.AssertKind.LineEnd→codes.quine.labs.recheck.automaton.EpsNFA.AssertKindcodes.quine.labs.recheck.automaton.EpsNFA.AssertKind.MarkWordBoundary→codes.quine.labs.recheck.automaton.EpsNFA.AssertKindcodes.quine.labs.recheck.automaton.EpsNFA.AssertKind.NotBetweenCRLF→codes.quine.labs.recheck.automaton.EpsNFA.AssertKindcodes.quine.labs.recheck.automaton.EpsNFA.AssertKind.NotMarkWordBoundary→codes.quine.labs.recheck.automaton.EpsNFA.AssertKindcodes.quine.labs.recheck.automaton.EpsNFA.AssertKind.NotWordBoundary→codes.quine.labs.recheck.automaton.EpsNFA.AssertKindcodes.quine.labs.recheck.automaton.EpsNFA.AssertKind.TextBegin→codes.quine.labs.recheck.automaton.EpsNFA.AssertKindcodes.quine.labs.recheck.automaton.EpsNFA.AssertKind.TextEnd→codes.quine.labs.recheck.automaton.EpsNFA.AssertKindcodes.quine.labs.recheck.automaton.EpsNFA.AssertKind.WordBoundary→codes.quine.labs.recheck.automaton.EpsNFA.AssertKind
- Direction
- recheck.automaton.EpsNFA.AssertKind uses recheck.automaton.EpsNFA, so a change to recheck.automaton.EpsNFA can break recheck.automaton.EpsNFA.AssertKind, while a change to recheck.automaton.EpsNFA.AssertKind can't break recheck.automaton.EpsNFA.
- Position
- Below the diagonal: recheck.automaton.EpsNFA.AssertKind uses a module listed above it, which is the healthy direction.
33→20 recheck.automaton.EpsNFA.AssertKind uses resyntax.ir✕
- Connections
- 1 pair of types, where a type in recheck.automaton.EpsNFA.AssertKind uses a type in resyntax.ir.
- The types involved
codes.quine.labs.recheck.automaton.EpsNFA.AssertKind.LineBegin→codes.quine.labs.resyntax.ir.IRLineBeginAtEnd
- Direction
- recheck.automaton.EpsNFA.AssertKind uses resyntax.ir, so a change to resyntax.ir can break recheck.automaton.EpsNFA.AssertKind, while a change to recheck.automaton.EpsNFA.AssertKind can't break resyntax.ir.
- Position
- Below the diagonal: recheck.automaton.EpsNFA.AssertKind uses a module listed above it, which is the healthy direction.
33→23 recheck.automaton.EpsNFA.AssertKind uses recheck.automaton✕
- Connections
- 10 pairs of types, where a type in recheck.automaton.EpsNFA.AssertKind uses a type in recheck.automaton.
- The types involved
codes.quine.labs.recheck.automaton.EpsNFA.AssertKind.ChompTextEnd→codes.quine.labs.recheck.automaton.CharKindStatecodes.quine.labs.recheck.automaton.EpsNFA.AssertKind.LineBegin→codes.quine.labs.recheck.automaton.CharKindStatecodes.quine.labs.recheck.automaton.EpsNFA.AssertKind.LineEnd→codes.quine.labs.recheck.automaton.CharKindStatecodes.quine.labs.recheck.automaton.EpsNFA.AssertKind.MarkWordBoundary→codes.quine.labs.recheck.automaton.CharKindStatecodes.quine.labs.recheck.automaton.EpsNFA.AssertKind.NotBetweenCRLF→codes.quine.labs.recheck.automaton.CharKindStatecodes.quine.labs.recheck.automaton.EpsNFA.AssertKind.NotMarkWordBoundary→codes.quine.labs.recheck.automaton.CharKindStatecodes.quine.labs.recheck.automaton.EpsNFA.AssertKind.NotWordBoundary→codes.quine.labs.recheck.automaton.CharKindStatecodes.quine.labs.recheck.automaton.EpsNFA.AssertKind.TextBegin→codes.quine.labs.recheck.automaton.CharKindStatecodes.quine.labs.recheck.automaton.EpsNFA.AssertKind.TextEnd→codes.quine.labs.recheck.automaton.CharKindStatecodes.quine.labs.recheck.automaton.EpsNFA.AssertKind.WordBoundary→codes.quine.labs.recheck.automaton.CharKindState
- Direction
- recheck.automaton.EpsNFA.AssertKind uses recheck.automaton, so a change to recheck.automaton can break recheck.automaton.EpsNFA.AssertKind, while a change to recheck.automaton.EpsNFA.AssertKind can't break recheck.automaton.
- Position
- Below the diagonal: recheck.automaton.EpsNFA.AssertKind uses a module listed above it, which is the healthy direction.
34→6 recheck.vm.Inst.ReadKind uses resyntax.charset✕
- Connections
- 2 pairs of types, where a type in recheck.vm.Inst.ReadKind uses a type in resyntax.charset.
- The types involved
codes.quine.labs.recheck.vm.Inst.ReadKind.Class→codes.quine.labs.resyntax.charset.CharSetcodes.quine.labs.recheck.vm.Inst.ReadKind.ClassNot→codes.quine.labs.resyntax.charset.CharSet
- Direction
- recheck.vm.Inst.ReadKind uses resyntax.charset, so a change to resyntax.charset can break recheck.vm.Inst.ReadKind, while a change to recheck.vm.Inst.ReadKind can't break resyntax.charset.
- Position
- Below the diagonal: recheck.vm.Inst.ReadKind uses a module listed above it, which is the healthy direction.
34→20 recheck.vm.Inst.ReadKind uses resyntax.ir✕
- Connections
- 3 pairs of types, where a type in recheck.vm.Inst.ReadKind uses a type in resyntax.ir.
- The types involved
codes.quine.labs.recheck.vm.Inst.ReadKind.Ref→codes.quine.labs.resyntax.ir.IRBackReferenceFoldingcodes.quine.labs.recheck.vm.Inst.ReadKind.Ref→codes.quine.labs.resyntax.ir.IRBackReferenceSemanticscodes.quine.labs.recheck.vm.Inst.ReadKind.Ref→codes.quine.labs.resyntax.ir.IRCaseEquivalence
- Direction
- recheck.vm.Inst.ReadKind uses resyntax.ir, so a change to resyntax.ir can break recheck.vm.Inst.ReadKind, while a change to recheck.vm.Inst.ReadKind can't break resyntax.ir.
- Position
- Below the diagonal: recheck.vm.Inst.ReadKind uses a module listed above it, which is the healthy direction.
34→25 recheck.vm.Inst.ReadKind uses recheck.vm.Inst✕
- Connections
- 5 pairs of types, where a type in recheck.vm.Inst.ReadKind uses a type in recheck.vm.Inst.
- The types involved
codes.quine.labs.recheck.vm.Inst.ReadKind.Any→codes.quine.labs.recheck.vm.Inst.ReadKindcodes.quine.labs.recheck.vm.Inst.ReadKind.Char→codes.quine.labs.recheck.vm.Inst.ReadKindcodes.quine.labs.recheck.vm.Inst.ReadKind.Class→codes.quine.labs.recheck.vm.Inst.ReadKindcodes.quine.labs.recheck.vm.Inst.ReadKind.ClassNot→codes.quine.labs.recheck.vm.Inst.ReadKindcodes.quine.labs.recheck.vm.Inst.ReadKind.Ref→codes.quine.labs.recheck.vm.Inst.ReadKind
- Direction
- recheck.vm.Inst.ReadKind uses recheck.vm.Inst, so a change to recheck.vm.Inst can break recheck.vm.Inst.ReadKind, while a change to recheck.vm.Inst.ReadKind can't break recheck.vm.Inst.
- Position
- Below the diagonal: recheck.vm.Inst.ReadKind uses a module listed above it, which is the healthy direction.
35→5 recheck.vm.Interpreter uses resyntax.ast✕
- Connections
- 3 pairs of types, where a type in recheck.vm.Interpreter uses a type in resyntax.ast.
- The types involved
codes.quine.labs.recheck.vm.Interpreter.Diff→codes.quine.labs.resyntax.ast.SourceLocationcodes.quine.labs.recheck.vm.Interpreter.Junction→codes.quine.labs.resyntax.ast.SourceLocationcodes.quine.labs.recheck.vm.Interpreter.Result→codes.quine.labs.resyntax.ast.SourceLocation
- Direction
- recheck.vm.Interpreter uses resyntax.ast, so a change to resyntax.ast can break recheck.vm.Interpreter, while a change to recheck.vm.Interpreter can't break resyntax.ast.
- Position
- Below the diagonal: recheck.vm.Interpreter uses a module listed above it, which is the healthy direction.
35→6 recheck.vm.Interpreter uses resyntax.charset✕
- Connections
- 2 pairs of types, where a type in recheck.vm.Interpreter uses a type in resyntax.charset.
- The types involved
codes.quine.labs.recheck.vm.Interpreter.FailedPoint→codes.quine.labs.resyntax.charset.UStringcodes.quine.labs.recheck.vm.Interpreter.Frame→codes.quine.labs.resyntax.charset.UString
- Direction
- recheck.vm.Interpreter uses resyntax.charset, so a change to resyntax.charset can break recheck.vm.Interpreter, while a change to recheck.vm.Interpreter can't break resyntax.charset.
- Position
- Below the diagonal: recheck.vm.Interpreter uses a module listed above it, which is the healthy direction.
35→25 recheck.vm.Interpreter uses recheck.vm.Inst✕
- Connections
- 3 pairs of types, where a type in recheck.vm.Interpreter uses a type in recheck.vm.Inst.
- The types involved
codes.quine.labs.recheck.vm.Interpreter.FailedPoint→codes.quine.labs.recheck.vm.Inst.ReadKindcodes.quine.labs.recheck.vm.Interpreter.Frame→codes.quine.labs.recheck.vm.Inst.Barriercodes.quine.labs.recheck.vm.Interpreter.Frame→codes.quine.labs.recheck.vm.Inst.VerbKind
- Direction
- recheck.vm.Interpreter uses recheck.vm.Inst, so a change to recheck.vm.Inst can break recheck.vm.Interpreter, while a change to recheck.vm.Interpreter can't break recheck.vm.Inst.
- Position
- Below the diagonal: recheck.vm.Interpreter uses a module listed above it, which is the healthy direction.
35→37 recheck.vm.Interpreter uses recheck.vm part of a loop✕
- Connections
- 1 pair of types, where a type in recheck.vm.Interpreter uses a type in recheck.vm.
- The types involved
codes.quine.labs.recheck.vm.Interpreter.Frame→codes.quine.labs.recheck.vm.Label
- Direction
- recheck.vm.Interpreter uses recheck.vm, so a change to recheck.vm can break recheck.vm.Interpreter, while a change to recheck.vm.Interpreter can't break recheck.vm.
- 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.
36→5 resyntax.ir.build uses resyntax.ast✕
- Connections
- 22 pairs of types, where a type in resyntax.ir.build uses a type in resyntax.ast.
- The types involved
codes.quine.labs.resyntax.ir.build.BuildingContext→codes.quine.labs.resyntax.ast.FlagSetcodes.quine.labs.resyntax.ir.build.BuildingContext→codes.quine.labs.resyntax.ast.FlagSetDiffcodes.quine.labs.resyntax.ir.build.CaptureAnalyzer→codes.quine.labs.resyntax.ast.CommandKindcodes.quine.labs.resyntax.ir.build.CaptureAnalyzer→codes.quine.labs.resyntax.ast.GroupKindcodes.quine.labs.resyntax.ir.build.CaptureAnalyzer→codes.quine.labs.resyntax.ast.Nodecodes.quine.labs.resyntax.ir.build.CaptureTable→codes.quine.labs.resyntax.ast.Nodecodes.quine.labs.resyntax.ir.build.IRBuilder→codes.quine.labs.resyntax.ast.FlagSetcodes.quine.labs.resyntax.ir.build.IRBuilder→codes.quine.labs.resyntax.ast.Nodecodes.quine.labs.resyntax.ir.build.IRBuildingException→codes.quine.labs.resyntax.ast.SourceLocationcodes.quine.labs.resyntax.ir.build.IRCharResolver→codes.quine.labs.resyntax.ast.ClassItemcodes.quine.labs.resyntax.ir.build.IRCharResolver→codes.quine.labs.resyntax.ast.EscapeClassKindcodes.quine.labs.resyntax.ir.build.IRCharResolver→codes.quine.labs.resyntax.ast.Nodecodes.quine.labs.resyntax.ir.build.IRCharResolver→codes.quine.labs.resyntax.ast.SourceLocationcodes.quine.labs.resyntax.ir.build.LookBehindAnalyzer→codes.quine.labs.resyntax.ast.GroupKindcodes.quine.labs.resyntax.ir.build.LookBehindAnalyzer→codes.quine.labs.resyntax.ast.Nodecodes.quine.labs.resyntax.ir.build.LookBehindAnalyzer→codes.quine.labs.resyntax.ast.Quantifiercodes.quine.labs.resyntax.ir.build.LookBehindAnalyzer→codes.quine.labs.resyntax.ast.Referencecodes.quine.labs.resyntax.ir.build.NodeKey→codes.quine.labs.resyntax.ast.Nodecodes.quine.labs.resyntax.ir.build.ReferenceResolver→codes.quine.labs.resyntax.ast.Referencecodes.quine.labs.resyntax.ir.build.ReferenceResolver→codes.quine.labs.resyntax.ast.SourceLocationcodes.quine.labs.resyntax.ir.build.SemanticAnalyzer→codes.quine.labs.resyntax.ast.ConditionalTestcodes.quine.labs.resyntax.ir.build.SemanticAnalyzer→codes.quine.labs.resyntax.ast.Node
- Direction
- resyntax.ir.build uses resyntax.ast, so a change to resyntax.ast can break resyntax.ir.build, while a change to resyntax.ir.build can't break resyntax.ast.
- Position
- Below the diagonal: resyntax.ir.build uses a module listed above it, which is the healthy direction.
36→6 resyntax.ir.build uses resyntax.charset✕
- Connections
- 10 pairs of types, where a type in resyntax.ir.build uses a type in resyntax.charset.
- The types involved
codes.quine.labs.resyntax.ir.build.IRBuilder→codes.quine.labs.resyntax.charset.UnitModecodes.quine.labs.resyntax.ir.build.IRCharResolver→codes.quine.labs.resyntax.charset.CharSetcodes.quine.labs.resyntax.ir.build.IRCharResolver→codes.quine.labs.resyntax.charset.ClassSetcodes.quine.labs.resyntax.ir.build.IRCharResolver→codes.quine.labs.resyntax.charset.UStringcodes.quine.labs.resyntax.ir.build.IRClassLookup→codes.quine.labs.resyntax.charset.CharSetcodes.quine.labs.resyntax.ir.build.IRPropertyLookup→codes.quine.labs.resyntax.charset.BinaryPropertycodes.quine.labs.resyntax.ir.build.IRPropertyLookup→codes.quine.labs.resyntax.charset.CharSetcodes.quine.labs.resyntax.ir.build.IRPropertyLookup→codes.quine.labs.resyntax.charset.EnumeratedPropertycodes.quine.labs.resyntax.ir.build.IRPropertyLookup→codes.quine.labs.resyntax.charset.PropertyValuecodes.quine.labs.resyntax.ir.build.IRPropertyLookup→codes.quine.labs.resyntax.charset.UnitMode
- Direction
- resyntax.ir.build uses resyntax.charset, so a change to resyntax.charset can break resyntax.ir.build, while a change to resyntax.ir.build can't break resyntax.charset.
- Position
- Below the diagonal: resyntax.ir.build uses a module listed above it, which is the healthy direction.
36→7 resyntax.ir.build uses resyntax.ir.build.LookBehindAnalyzer✕
- Connections
- 3 pairs of types, where a type in resyntax.ir.build uses a type in resyntax.ir.build.LookBehindAnalyzer.
- The types involved
codes.quine.labs.resyntax.ir.build.LookBehindAnalyzer→codes.quine.labs.resyntax.ir.build.LookBehindAnalyzer.JavaInfocodes.quine.labs.resyntax.ir.build.LookBehindAnalyzer→codes.quine.labs.resyntax.ir.build.LookBehindAnalyzer.RubyWidthcodes.quine.labs.resyntax.ir.build.LookBehindAnalyzer→codes.quine.labs.resyntax.ir.build.LookBehindAnalyzer.Width
- Direction
- resyntax.ir.build uses resyntax.ir.build.LookBehindAnalyzer, so a change to resyntax.ir.build.LookBehindAnalyzer can break resyntax.ir.build, while a change to resyntax.ir.build can't break resyntax.ir.build.LookBehindAnalyzer.
- Position
- Below the diagonal: resyntax.ir.build uses a module listed above it, which is the healthy direction.
36→12 resyntax.ir.build uses resyntax.dialect✕
- Connections
- 3 pairs of types, where a type in resyntax.ir.build uses a type in resyntax.dialect.
- The types involved
codes.quine.labs.resyntax.ir.build.BuildingContext→codes.quine.labs.resyntax.dialect.LineTerminatorSetcodes.quine.labs.resyntax.ir.build.IRBuilder→codes.quine.labs.resyntax.dialect.Dialectcodes.quine.labs.resyntax.ir.build.IRFeatureSet→codes.quine.labs.resyntax.dialect.LineTerminatorSet
- Direction
- resyntax.ir.build uses resyntax.dialect, so a change to resyntax.dialect can break resyntax.ir.build, while a change to resyntax.ir.build can't break resyntax.dialect.
- Position
- Below the diagonal: resyntax.ir.build uses a module listed above it, which is the healthy direction.
36→20 resyntax.ir.build uses resyntax.ir✕
- Connections
- 17 pairs of types, where a type in resyntax.ir.build uses a type in resyntax.ir.
- The types involved
codes.quine.labs.resyntax.ir.build.BuildingContext→codes.quine.labs.resyntax.ir.IRCharFlagSetcodes.quine.labs.resyntax.ir.build.BuildingContext→codes.quine.labs.resyntax.ir.IRCharsetcodes.quine.labs.resyntax.ir.build.CaptureTable→codes.quine.labs.resyntax.ir.IRCharFlagSetcodes.quine.labs.resyntax.ir.build.IRBuilder→codes.quine.labs.resyntax.ir.IRCharFlagSetcodes.quine.labs.resyntax.ir.build.IRBuilder→codes.quine.labs.resyntax.ir.IRNotEmptycodes.quine.labs.resyntax.ir.build.IRBuilder→codes.quine.labs.resyntax.ir.IRPatterncodes.quine.labs.resyntax.ir.build.IRCharResolver→codes.quine.labs.resyntax.ir.IRCaseEquivalencecodes.quine.labs.resyntax.ir.build.IRCharResolver→codes.quine.labs.resyntax.ir.IRCharFlagSetcodes.quine.labs.resyntax.ir.build.IRCharResolver→codes.quine.labs.resyntax.ir.IRNodecodes.quine.labs.resyntax.ir.build.IRCharResolver→codes.quine.labs.resyntax.ir.IRNodeDatacodes.quine.labs.resyntax.ir.build.IRCharResolver→codes.quine.labs.resyntax.ir.IRWordMarkSetcodes.quine.labs.resyntax.ir.build.IRClassLookup→codes.quine.labs.resyntax.ir.IRCharFlagSetcodes.quine.labs.resyntax.ir.build.IRFeatureSet→codes.quine.labs.resyntax.ir.IRBackReferenceChoicecodes.quine.labs.resyntax.ir.build.IRFeatureSet→codes.quine.labs.resyntax.ir.IREmptyIterationcodes.quine.labs.resyntax.ir.build.IRFeatureSet→codes.quine.labs.resyntax.ir.IRLineBeginAtEndcodes.quine.labs.resyntax.ir.build.IRPropertyLookup→codes.quine.labs.resyntax.ir.IRCharFlagSetcodes.quine.labs.resyntax.ir.build.LookBehindAnalyzer→codes.quine.labs.resyntax.ir.IRLookBehindMatch
- Direction
- resyntax.ir.build uses resyntax.ir, so a change to resyntax.ir can break resyntax.ir.build, while a change to resyntax.ir.build can't break resyntax.ir.
- Position
- Below the diagonal: resyntax.ir.build uses a module listed above it, which is the healthy direction.
36→31 resyntax.ir.build uses resyntax.ir.build.IRCharResolver✕
- Connections
- 2 pairs of types, where a type in resyntax.ir.build uses a type in resyntax.ir.build.IRCharResolver.
- The types involved
codes.quine.labs.resyntax.ir.build.IRCharResolver→codes.quine.labs.resyntax.ir.build.IRCharResolver.Litcodes.quine.labs.resyntax.ir.build.IRCharResolver→codes.quine.labs.resyntax.ir.build.IRCharResolver.RubyClassToken
- Direction
- resyntax.ir.build uses resyntax.ir.build.IRCharResolver, so a change to resyntax.ir.build.IRCharResolver can break resyntax.ir.build, while a change to resyntax.ir.build can't break resyntax.ir.build.IRCharResolver.
- Position
- Below the diagonal: resyntax.ir.build uses a module listed above it, which is the healthy direction.
37→2 recheck.vm uses recheck.common✕
- Connections
- 2 pairs of types, where a type in recheck.vm uses a type in recheck.common.
- The types involved
codes.quine.labs.recheck.vm.Interpreter→codes.quine.labs.recheck.common.Contextcodes.quine.labs.recheck.vm.ProgramBuilder→codes.quine.labs.recheck.common.Context
- Direction
- recheck.vm uses recheck.common, so a change to recheck.common can break recheck.vm, while a change to recheck.vm can't break recheck.common.
- Position
- Below the diagonal: recheck.vm uses a module listed above it, which is the healthy direction.
37→6 recheck.vm uses resyntax.charset✕
- Connections
- 1 pair of types, where a type in recheck.vm uses a type in resyntax.charset.
- The types involved
codes.quine.labs.recheck.vm.Interpreter→codes.quine.labs.resyntax.charset.UString
- Direction
- recheck.vm uses resyntax.charset, so a change to resyntax.charset can break recheck.vm, while a change to recheck.vm can't break resyntax.charset.
- Position
- Below the diagonal: recheck.vm uses a module listed above it, which is the healthy direction.
37→11 recheck.vm uses recheck.vm.Program✕
- Connections
- 1 pair of types, where a type in recheck.vm uses a type in recheck.vm.Program.
- The types involved
codes.quine.labs.recheck.vm.Program→codes.quine.labs.recheck.vm.Program.Meta
- Direction
- recheck.vm uses recheck.vm.Program, so a change to recheck.vm.Program can break recheck.vm, while a change to recheck.vm can't break recheck.vm.Program.
- Position
- Below the diagonal: recheck.vm uses a module listed above it, which is the healthy direction.
37→20 recheck.vm uses resyntax.ir✕
- Connections
- 1 pair of types, where a type in recheck.vm uses a type in resyntax.ir.
- The types involved
codes.quine.labs.recheck.vm.ProgramBuilder→codes.quine.labs.resyntax.ir.IRPattern
- Direction
- recheck.vm uses resyntax.ir, so a change to resyntax.ir can break recheck.vm, while a change to recheck.vm can't break resyntax.ir.
- Position
- Below the diagonal: recheck.vm uses a module listed above it, which is the healthy direction.
37→35 recheck.vm uses recheck.vm.Interpreter✕
- Connections
- 2 pairs of types, where a type in recheck.vm uses a type in recheck.vm.Interpreter.
- The types involved
codes.quine.labs.recheck.vm.Interpreter→codes.quine.labs.recheck.vm.Interpreter.Optionscodes.quine.labs.recheck.vm.Interpreter→codes.quine.labs.recheck.vm.Interpreter.Result
- Direction
- recheck.vm uses recheck.vm.Interpreter, so a change to recheck.vm.Interpreter can break recheck.vm, while a change to recheck.vm can't break recheck.vm.Interpreter.
- Position
- Below the diagonal: recheck.vm uses a module listed above it, which is the healthy direction.
38→6 resyntax.ir.build.IRClassLookup uses resyntax.charset✕
- Connections
- 10 pairs of types, where a type in resyntax.ir.build.IRClassLookup uses a type in resyntax.charset.
- The types involved
codes.quine.labs.resyntax.ir.build.IRClassLookup.DotNet→codes.quine.labs.resyntax.charset.CharSetcodes.quine.labs.resyntax.ir.build.IRClassLookup.Java→codes.quine.labs.resyntax.charset.CharSetcodes.quine.labs.resyntax.ir.build.IRClassLookup.JavaScript→codes.quine.labs.resyntax.charset.CharSetcodes.quine.labs.resyntax.ir.build.IRClassLookup.JavaScript→codes.quine.labs.resyntax.charset.UnitModecodes.quine.labs.resyntax.ir.build.IRClassLookup.PCRE→codes.quine.labs.resyntax.charset.CharSetcodes.quine.labs.resyntax.ir.build.IRClassLookup.Perl→codes.quine.labs.resyntax.charset.CharSetcodes.quine.labs.resyntax.ir.build.IRClassLookup.Python→codes.quine.labs.resyntax.charset.CharSetcodes.quine.labs.resyntax.ir.build.IRClassLookup.Python→codes.quine.labs.resyntax.charset.UnitModecodes.quine.labs.resyntax.ir.build.IRClassLookup.Ruby→codes.quine.labs.resyntax.charset.CharSetcodes.quine.labs.resyntax.ir.build.IRClassLookup.Ruby→codes.quine.labs.resyntax.charset.UnitMode
- Direction
- resyntax.ir.build.IRClassLookup uses resyntax.charset, so a change to resyntax.charset can break resyntax.ir.build.IRClassLookup, while a change to resyntax.ir.build.IRClassLookup can't break resyntax.charset.
- Position
- Below the diagonal: resyntax.ir.build.IRClassLookup uses a module listed above it, which is the healthy direction.
38→20 resyntax.ir.build.IRClassLookup uses resyntax.ir✕
- Connections
- 8 pairs of types, where a type in resyntax.ir.build.IRClassLookup uses a type in resyntax.ir.
- The types involved
codes.quine.labs.resyntax.ir.build.IRClassLookup.DotNet→codes.quine.labs.resyntax.ir.IRCharFlagSetcodes.quine.labs.resyntax.ir.build.IRClassLookup.Java→codes.quine.labs.resyntax.ir.IRCharFlagSetcodes.quine.labs.resyntax.ir.build.IRClassLookup.JavaScript→codes.quine.labs.resyntax.ir.IRCharFlagSetcodes.quine.labs.resyntax.ir.build.IRClassLookup.PCRE→codes.quine.labs.resyntax.ir.IRCharFlagSetcodes.quine.labs.resyntax.ir.build.IRClassLookup.PCRE→codes.quine.labs.resyntax.ir.IRCharsetcodes.quine.labs.resyntax.ir.build.IRClassLookup.Perl→codes.quine.labs.resyntax.ir.IRCharFlagSetcodes.quine.labs.resyntax.ir.build.IRClassLookup.Python→codes.quine.labs.resyntax.ir.IRCharFlagSetcodes.quine.labs.resyntax.ir.build.IRClassLookup.Ruby→codes.quine.labs.resyntax.ir.IRCharFlagSet
- Direction
- resyntax.ir.build.IRClassLookup uses resyntax.ir, so a change to resyntax.ir can break resyntax.ir.build.IRClassLookup, while a change to resyntax.ir.build.IRClassLookup can't break resyntax.ir.
- Position
- Below the diagonal: resyntax.ir.build.IRClassLookup uses a module listed above it, which is the healthy direction.
38→36 resyntax.ir.build.IRClassLookup uses resyntax.ir.build✕
- Connections
- 7 pairs of types, where a type in resyntax.ir.build.IRClassLookup uses a type in resyntax.ir.build.
- The types involved
codes.quine.labs.resyntax.ir.build.IRClassLookup.DotNet→codes.quine.labs.resyntax.ir.build.IRClassLookupcodes.quine.labs.resyntax.ir.build.IRClassLookup.Java→codes.quine.labs.resyntax.ir.build.IRClassLookupcodes.quine.labs.resyntax.ir.build.IRClassLookup.JavaScript→codes.quine.labs.resyntax.ir.build.IRClassLookupcodes.quine.labs.resyntax.ir.build.IRClassLookup.PCRE→codes.quine.labs.resyntax.ir.build.IRClassLookupcodes.quine.labs.resyntax.ir.build.IRClassLookup.Perl→codes.quine.labs.resyntax.ir.build.IRClassLookupcodes.quine.labs.resyntax.ir.build.IRClassLookup.Python→codes.quine.labs.resyntax.ir.build.IRClassLookupcodes.quine.labs.resyntax.ir.build.IRClassLookup.Ruby→codes.quine.labs.resyntax.ir.build.IRClassLookup
- Direction
- resyntax.ir.build.IRClassLookup uses resyntax.ir.build, so a change to resyntax.ir.build can break resyntax.ir.build.IRClassLookup, while a change to resyntax.ir.build.IRClassLookup can't break resyntax.ir.build.
- Position
- Below the diagonal: resyntax.ir.build.IRClassLookup uses a module listed above it, which is the healthy direction.
39→6 recheck.vm.Inst.AssertKind uses resyntax.charset✕
- Connections
- 4 pairs of types, where a type in recheck.vm.Inst.AssertKind uses a type in resyntax.charset.
- The types involved
codes.quine.labs.recheck.vm.Inst.AssertKind.MarkWordBoundary→codes.quine.labs.resyntax.charset.CharSetcodes.quine.labs.recheck.vm.Inst.AssertKind.MarkWordBoundaryNot→codes.quine.labs.resyntax.charset.CharSetcodes.quine.labs.recheck.vm.Inst.AssertKind.WordBoundary→codes.quine.labs.resyntax.charset.CharSetcodes.quine.labs.recheck.vm.Inst.AssertKind.WordBoundaryNot→codes.quine.labs.resyntax.charset.CharSet
- Direction
- recheck.vm.Inst.AssertKind uses resyntax.charset, so a change to resyntax.charset can break recheck.vm.Inst.AssertKind, while a change to recheck.vm.Inst.AssertKind can't break resyntax.charset.
- Position
- Below the diagonal: recheck.vm.Inst.AssertKind uses a module listed above it, which is the healthy direction.
39→12 recheck.vm.Inst.AssertKind uses resyntax.dialect✕
- Connections
- 3 pairs of types, where a type in recheck.vm.Inst.AssertKind uses a type in resyntax.dialect.
- The types involved
codes.quine.labs.recheck.vm.Inst.AssertKind.ChompInputEnd→codes.quine.labs.resyntax.dialect.LineTerminatorSetcodes.quine.labs.recheck.vm.Inst.AssertKind.LineBegin→codes.quine.labs.resyntax.dialect.LineTerminatorSetcodes.quine.labs.recheck.vm.Inst.AssertKind.LineEnd→codes.quine.labs.resyntax.dialect.LineTerminatorSet
- Direction
- recheck.vm.Inst.AssertKind uses resyntax.dialect, so a change to resyntax.dialect can break recheck.vm.Inst.AssertKind, while a change to recheck.vm.Inst.AssertKind can't break resyntax.dialect.
- Position
- Below the diagonal: recheck.vm.Inst.AssertKind uses a module listed above it, which is the healthy direction.
39→20 recheck.vm.Inst.AssertKind uses resyntax.ir✕
- Connections
- 3 pairs of types, where a type in recheck.vm.Inst.AssertKind uses a type in resyntax.ir.
- The types involved
codes.quine.labs.recheck.vm.Inst.AssertKind.LineBegin→codes.quine.labs.resyntax.ir.IRLineBeginAtEndcodes.quine.labs.recheck.vm.Inst.AssertKind.MarkWordBoundary→codes.quine.labs.resyntax.ir.IRWordMarkSetcodes.quine.labs.recheck.vm.Inst.AssertKind.MarkWordBoundaryNot→codes.quine.labs.resyntax.ir.IRWordMarkSet
- Direction
- recheck.vm.Inst.AssertKind uses resyntax.ir, so a change to resyntax.ir can break recheck.vm.Inst.AssertKind, while a change to recheck.vm.Inst.AssertKind can't break resyntax.ir.
- Position
- Below the diagonal: recheck.vm.Inst.AssertKind uses a module listed above it, which is the healthy direction.
39→25 recheck.vm.Inst.AssertKind uses recheck.vm.Inst✕
- Connections
- 11 pairs of types, where a type in recheck.vm.Inst.AssertKind uses a type in recheck.vm.Inst.
- The types involved
codes.quine.labs.recheck.vm.Inst.AssertKind.ChompInputEnd→codes.quine.labs.recheck.vm.Inst.AssertKindcodes.quine.labs.recheck.vm.Inst.AssertKind.InputBegin→codes.quine.labs.recheck.vm.Inst.AssertKindcodes.quine.labs.recheck.vm.Inst.AssertKind.InputEnd→codes.quine.labs.recheck.vm.Inst.AssertKindcodes.quine.labs.recheck.vm.Inst.AssertKind.LineBegin→codes.quine.labs.recheck.vm.Inst.AssertKindcodes.quine.labs.recheck.vm.Inst.AssertKind.LineEnd→codes.quine.labs.recheck.vm.Inst.AssertKindcodes.quine.labs.recheck.vm.Inst.AssertKind.LookBehindEnd→codes.quine.labs.recheck.vm.Inst.AssertKindcodes.quine.labs.recheck.vm.Inst.AssertKind.MarkWordBoundary→codes.quine.labs.recheck.vm.Inst.AssertKindcodes.quine.labs.recheck.vm.Inst.AssertKind.MarkWordBoundaryNot→codes.quine.labs.recheck.vm.Inst.AssertKindcodes.quine.labs.recheck.vm.Inst.AssertKind.NotBetweenCRLF→codes.quine.labs.recheck.vm.Inst.AssertKindcodes.quine.labs.recheck.vm.Inst.AssertKind.WordBoundary→codes.quine.labs.recheck.vm.Inst.AssertKindcodes.quine.labs.recheck.vm.Inst.AssertKind.WordBoundaryNot→codes.quine.labs.recheck.vm.Inst.AssertKind
- Direction
- recheck.vm.Inst.AssertKind uses recheck.vm.Inst, so a change to recheck.vm.Inst can break recheck.vm.Inst.AssertKind, while a change to recheck.vm.Inst.AssertKind can't break recheck.vm.Inst.
- Position
- Below the diagonal: recheck.vm.Inst.AssertKind uses a module listed above it, which is the healthy direction.
39→37 recheck.vm.Inst.AssertKind uses recheck.vm✕
- Connections
- 1 pair of types, where a type in recheck.vm.Inst.AssertKind uses a type in recheck.vm.
- The types involved
codes.quine.labs.recheck.vm.Inst.AssertKind.LookBehindEnd→codes.quine.labs.recheck.vm.CounterReg
- Direction
- recheck.vm.Inst.AssertKind uses recheck.vm, so a change to recheck.vm can break recheck.vm.Inst.AssertKind, while a change to recheck.vm.Inst.AssertKind can't break recheck.vm.
- Position
- Below the diagonal: recheck.vm.Inst.AssertKind uses a module listed above it, which is the healthy direction.
40→35 recheck.vm.Interpreter.Rollback uses recheck.vm.Interpreter✕
- Connections
- 4 pairs of types, where a type in recheck.vm.Interpreter.Rollback uses a type in recheck.vm.Interpreter.
- The types involved
codes.quine.labs.recheck.vm.Interpreter.Rollback.Fallback→codes.quine.labs.recheck.vm.Interpreter.Framecodes.quine.labs.recheck.vm.Interpreter.Rollback.Fallback→codes.quine.labs.recheck.vm.Interpreter.Rollbackcodes.quine.labs.recheck.vm.Interpreter.Rollback.HasSuccessor→codes.quine.labs.recheck.vm.Interpreter.Framecodes.quine.labs.recheck.vm.Interpreter.Rollback.HasSuccessor→codes.quine.labs.recheck.vm.Interpreter.Rollback
- Direction
- recheck.vm.Interpreter.Rollback uses recheck.vm.Interpreter, so a change to recheck.vm.Interpreter can break recheck.vm.Interpreter.Rollback, while a change to recheck.vm.Interpreter.Rollback can't break recheck.vm.Interpreter.
- Position
- Below the diagonal: recheck.vm.Interpreter.Rollback uses a module listed above it, which is the healthy direction.
40→37 recheck.vm.Interpreter.Rollback uses recheck.vm✕
- Connections
- 1 pair of types, where a type in recheck.vm.Interpreter.Rollback uses a type in recheck.vm.
- The types involved
codes.quine.labs.recheck.vm.Interpreter.Rollback.HasSuccessor→codes.quine.labs.recheck.vm.Label
- Direction
- recheck.vm.Interpreter.Rollback uses recheck.vm, so a change to recheck.vm can break recheck.vm.Interpreter.Rollback, while a change to recheck.vm.Interpreter.Rollback can't break recheck.vm.
- Position
- Below the diagonal: recheck.vm.Interpreter.Rollback uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 57 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 54 | High / Critical |
| A07:2025 — Authentication Failures | 17 | High / Critical |
Roadmap
Top priorities: Resolve the 16 High secret finding(s) in Secrets (history) — start with REDACTED (16); Resolve the 8 Documentation finding(s) in Documentation Quality — start with README.md (8); Resolve the 1 No ADRs found finding(s) in ADR Quality.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 8 Documentation finding(s) in Documentation Quality — start with README.md (8). | +5.3 pts | Low | Documentation Quality |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +5.3 pts | Low | ADR Quality |
| Resolve the 5 REDACTED finding(s) charged to Static Analysis (SAST) — the other 47 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. | +3.2 pts | Low | Static Analysis (SAST) |
| Resolve the 16 High secret finding(s) in Secrets (history) — start with REDACTED (16). | +5.8 pts | Medium | Secrets (history) |
| 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. | +5.0 pts | Medium | Architecture documentation |
| Resolve the 27 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (27). | +4.1 pts | Medium | Dependency Vulnerabilities |
| Expand the README with getting-started, architecture overview and a project map. | +3.8 pts | Medium | Documentation (README) |
| Resolve the 1 redundant comment finding(s) in Comment Value — start with markdown.ts. | +1.7 pts | Low | Comment Value |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Secrets (history): High secret: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/Parser.scala | 7.0 | Mixed | Cyclomatic Complexity: Parser.parseFlagSet (cyclomatic 52) |
| modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRCharResolver.scala | 7.0 | Mixed | Cyclomatic Complexity: IRCharResolver.escapeClassSet (cyclomatic 29) |
| modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/automaton/EpsNFABuilder.scala | 7.0 | Mixed | Cognitive Complexity: EpsNFABuilder.rejectEmpty (cognitive 23) |
| modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/vm/Interpreter.scala | 7.0 | Mixed | Cyclomatic Complexity: Interpreter.runLoop (cyclomatic 60) |
| modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRPropertyLookup.scala | 7.0 | Mixed | Cyclomatic Complexity: IRPropertyLookup.javaForProperty (cyclomatic 41) |
| modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/LookBehindAnalyzer.scala | 7.0 | Mixed | Cyclomatic Complexity: LookBehindAnalyzer.width (cyclomatic 40) |
| modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/PerlLiteralRewriter.scala | 7.1 | Mixed | Cyclomatic Complexity: PerlLiteralRewriter.scanChunk (cyclomatic 23) |
| modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/fuzz/StaticSeeder.scala | 7.2 | Mixed | Cyclomatic Complexity: StaticSeeder.simplify (cyclomatic 26) |
| modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRBuilder.scala | 7.2 | Mixed | Cyclomatic Complexity: IRBuilder.buildConditional (cyclomatic 21) |
| packages/eslint-plugin-redos/src/utils/checker.ts | 7.3 | Mixed | Explicit Debt: TodoComment |
| modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/vm/ProgramBuilder.scala | 7.4 | Mixed | God Classes: TooManyMethods: ProgramBuilder |
| modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/FeatureSet.scala | 7.8 | Mixed | Cyclomatic Complexity: FeatureSet.from (cyclomatic 175) |
| modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRFeatureSet.scala | 7.8 | Mixed | Cyclomatic Complexity: IRFeatureSet.from (cyclomatic 69) |
| modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ast/FlagSet.scala | 7.8 | Mixed | Cyclomatic Complexity: FlagSet.parse (cyclomatic 59) |
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 70 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 70 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, 277 of 290 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
- D10 Test Quality — 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. The 107 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 99 test source file(s) (.scala) that it cannot: it reads JavaScript/TypeScript test declarations off disk, so a JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
- 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 reliability not scored — the JavaScript/TypeScript suite (jest via `pnpm install --frozen-lockfile --ignore-scripts` in packages/eslint-plugin-redos/ (0 tests); jest via `pnpm install --frozen-lockfile --ignore-scripts` in packages/recheck/ (0 tests); jest via `pnpm install --frozen-lockfile --ignore-scripts` in packages/recheck-parameters/ (0 tests); jest via `pnpm install --frozen-lockfile --ignore-scripts` in website/ (0 tests)) ran but surfaced no test cases to the runner, so flakiness couldn't be exercised.
- 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/ibm/icu/icu4j/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.
- D16 Bus Factor — 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. Single-maintainer repository — bus factor is not applicable (6 contributor(s) across 3811 commit(s) sampled, automation and bot accounts excluded). One of them holds 92% of the history; the other 5 hold 1.6% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- 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 (packages/recheck/package.json), 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. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
- D24 Comment Value — 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. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `modules/recheck-cli/src/main/scala/codes/quine/labs/recheck/cli/AgentCommand.scala`, `modules/recheck-cli/src/main/scala/codes/quine/labs/recheck/cli/Main.scala`, `modules/recheck-cli/src/main/scala/codes/quine/labs/recheck/cli/RPC.scala`, `modules/recheck-codec/shared/src/main/scala/codes/quine/labs/recheck/codec/package.scala`, `modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/ReDoS.scala`, … (+51 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (start). the dev server (`npm run start`) exited before it served a page. Likely cause (the repository): package.json has no "start" script, so `npm run start` could not start the app. Last output: "npm error Missing script: "start" / npm error / npm error Did you mean one of these? / npm error npm star # Mark your favorite packages / npm error npm stars # View packages marked as favorites / npm error / npm error To see a list of scripts, run: / npm error npm run / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- M4 Documentation accuracy — 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. A badge or prose version claim scored 9/17 in its adjudication (docs/plans/deterministic-engine/adjudication/M4-v3.md: badges 9/9, prose 0/8, where prose versions are minimums or history), short of the 95 % precision gate, so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them. The .NET and Node.js version checks are a different kind and still publish.
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.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- 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.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- 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.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
33 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was FeatureSet.from at 175. A further 8 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 Parser.parseBackslashKind at 44 — they are counted neither in the figure above nor in this dimension's score. 3 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/vm/ProgramBuilder.scala (ProgramBuilder.build at 23), modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/automaton/EpsNFABuilder.scala (EpsNFABuilder.buildNode at 18), modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/IRNode.scala (IRNode.canMatchEmpty 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 60 down to 60 or less in Cyclomatic Complexity — start with FeatureSet.from (cyclomatic 175), IRFeatureSet.from (cyclomatic 69). — 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 5.4 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
- 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
50 method(s) exceeded the cognitive complexity threshold of 15; the worst was FeatureSet.from at 170.
What to do
- Bring the 4 bodies over 60 down to 60 or less in Cognitive Complexity — start with FeatureSet.from (cognitive 170), Interpreter.runLoop (cognitive 130), Parser.scanRemovedComments (cognitive 110). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cognitive Complexity from 4.1 to about 5.8/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
- 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 5 FileTooLong finding(s) in God Classes — start with Parser.scala, IRCharResolver.scala, Interpreter.scala. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 4 TooManyMethods finding(s) in God Classes — start with Parser.scala, ProgramBuilder.scala, IRCharResolver.scala. — One of this dimension's main actionable groups (4 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
4 duplicated block group(s) detected.
What to do
- Resolve the 3 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with NFA.scala, Interpreter.scala, IRCharResolver.scala. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 Duplicated block (8–9 lines × 2) finding(s) in Code Duplication — start with ProgramBuilder.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
18 production modules (npm+sbt), 0 dependency cycle(s), 1 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, with abstractness counted on 11 of the 18 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 1 Unstable project recheck finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
- 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 21 classes have LCOM4 above 3.
D9 · Test Distribution
568 test methods: 561 unit, 0 integration, 0 BDD, 7 e2e. The JavaScript/TypeScript suite contributes 107 `it`/`test` case(s) across 22 test file(s) declaring at least one; its tier split is read from package names and paths only. The Scala suite contributes 461 test case(s) across 85 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.
D10 · Test Quality
1 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 107 tests. Measured on the JavaScript/TypeScript suite only — at least 99 test source file(s) (.scala) went unread, so its test quality is unmeasured and is not in these counts.
What to do
- Resolve the 1 Skipped test finding(s) in Test Quality — start with main.test.ts. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D15 · Churn × Complexity Hotspots
Top hotspots: modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/FeatureSet.scala (67×175=11725); modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/Parser.scala (89×52=4628); modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/vm/Interpreter.scala (41×60=2460)
What to do
- Resolve the 17 Hotspot finding(s) in Churn × Complexity Hotspots — start with FeatureSet.scala, Parser.scala, Interpreter.scala. — One of this dimension's main actionable groups (17 warning-level).
D17 · Explicit Debt
5 deducted task-comment markers across 20769 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 5 TodoComment finding(s) in Explicit Debt — start with checker.ts (2), no-vulnerable.test.ts, no-vulnerable.ts. — One of this dimension's main actionable groups (5 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
0 of 1 documentation facets pass in full; short on: F2 example. 30 document(s) read across 11 unit(s).
What to do
- Resolve the 8 Documentation finding(s) in Documentation Quality — start with README.md (8). — One of this dimension's main actionable groups (8 recommendation-level).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D24 · Comment Value
1 of 50 judged comments only repeat the code they sit on (2.0 %).
What to do
- Resolve the 1 redundant comment finding(s) in Comment Value — start with markdown.ts. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 6 build units (npm, sbt) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
16 finding(s): 0 critical, 16 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 16 High secret finding(s) in Secrets (history) — start with REDACTED (16). — One of this dimension's main actionable groups (16 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
57 finding(s): 0 critical, 57 high, 0 medium, 0 low. 47 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 51 file(s) — `modules/recheck-cli/src/main/scala/codes/quine/labs/recheck/cli/AgentCommand.scala`, `modules/recheck-cli/src/main/scala/codes/quine/labs/recheck/cli/Main.scala`, `modules/recheck-cli/src/main/scala/codes/quine/labs/recheck/cli/RPC.scala`, `modules/recheck-codec/shared/src/main/scala/codes/quine/labs/recheck/codec/package.scala`, `modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/ReDoS.scala`, … (+46 more) — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 5 REDACTED finding(s) charged to Static Analysis (SAST) — the other 47 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. — One of this dimension's main actionable groups (52 issue-level, 5 of them charged here).
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 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).
D30 · Dependency Vulnerabilities
49 finding(s): 4 critical, 28 high, 13 medium, 4 low.
What to do
- Resolve the 27 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (27). — One of this dimension's main actionable groups (27 issue-level).
- Resolve the 4 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 1 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 77 of the 178 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: Main.scala↔arguments.scala 55%; EpsNFABuilder.scala↔FuzzProgram.scala 50%
What to do
- Resolve the 2 Change coupling finding(s) in Change Coupling — start with Main.scala, EpsNFABuilder.scala. — One of this dimension's main actionable groups (2 warning-level).
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — 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.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- A bare `// scalastyle:off`, `// scalafix:off` or `@nowarn` (or Wartremover's `warts.All`) switches every rule or warning off — hidden debt. Suppress the specific rule on the specific line, with a justification, instead. — modules/recheck-cli/src/main/scala/codes/quine/labs/recheck/cli/AgentCommand.scala:96
What to do
- Clear the softer debt: re-enable or delete `ignore`d and `pending` tests, decide whether each empty method or UnsupportedOperationException is deliberate (and say so in a comment), and replace a bare `// scalastyle:off` or `@nowarn` with targeted, justified suppressions.
M1 · Documentation (README)
- The root README is 22 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, in the README and in the repository documents it links, it found no a build/run or getting-started section, no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers. — README.md:1
What to do
- Expand the README with getting-started, architecture overview and a project map.
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 3 of 11 project(s) that lack one — worth up to 0.5 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
What to do
- Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
P3 · Security & performance tooling
What to do
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
P6 · Release Hygiene
PF3 · Async & latency hygiene
R1 · Type Safety
What to do
- Migrate the remaining .js/.jsx files to TypeScript.
R10 · Code Duplication
- packages/recheck/src/lib/agent.ts:189 · packages/recheck/src/lib/worker-pool.ts:81 — the two spans are one implementation copied and then locally edited — 76 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/recheck/src/lib/agent.ts:189
- packages/eslint-plugin-redos/scripts/build.mts:7 · packages/recheck/scripts/build.mts:11 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/eslint-plugin-redos/scripts/build.mts:7
- packages/eslint-plugin-redos/src/rules/no-vulnerable.ts:141 · packages/eslint-plugin-redos/src/rules/no-vulnerable.ts:151 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/eslint-plugin-redos/src/rules/no-vulnerable.ts:141
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R2 · Cyclomatic Complexity
- selectBackend has cyclomatic complexity 17 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/recheck/src/main.ts:54
- check has cyclomatic complexity 11 and cognitive complexity 9; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/eslint-plugin-redos/src/rules/no-vulnerable.ts:67
R3 · Large Files
R4 · Test Coverage
- No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×8) — packages/recheck-parameters/scripts/build.mts:1, packages/recheck/scripts/build.mts:1, packages/recheck/src/inject/main.ts:1, …
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R6 · Tooling
R7 · Dead Code
- 36 file(s) (~2219 LoC) were excluded from dead-code analysis. This package's entry point(s) resolved, but the walk stopped one hop in: packages/recheck/index.d.ts imports './parameters', which is not in the scanned tree. That is usually a generated or build-output module, so reachability cannot see past it and no dead-code claim is made about this package. Nothing is necessarily wrong here. — packages/recheck
- 8 file(s) (~343 LoC) were excluded from dead-code analysis. This package's entry point(s) resolved, but the walk stopped one hop in: packages/recheck-parameters/index.d.ts imports './lib/parameters.js', which is not in the scanned tree. That is usually a generated or build-output module, so reachability cannot see past it and no dead-code claim is made about this package. Nothing is necessarily wrong here. — packages/recheck-parameters
R8 · Dependency Hygiene
R9 · Circular Imports
- packages/recheck/src/main.ts → packages/recheck/src/synckit-worker.ts → packages/recheck/src/main.ts — packages/recheck/src/main.ts:141
What to do
- Break each cycle by extracting the shared piece into a module both sides can import.
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
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×2) — packages/eslint-plugin-redos/src/utils/cache.ts:40, packages/eslint-plugin-redos/src/utils/checker.ts:53
What to do
- Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
- No build over this repository's 143 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 | 65% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 92% | Exemplary | Solid. |
| Maturity | 44% | Weak — gated by M1, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 56% | Adequate — gated by P2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 36% | Weak — gated by D28, D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 2 check(s) recorded observations but carry no score
- P12 CI test-gate honesty — 3 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- X10 Duplicated predicate — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 59 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 JavaScript 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; 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; this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Scala code is a Play controller, a Cask routes object, a Scalatra servlet, a Finatra controller, an Akka/Pekko HTTP routes holder or a JSR-330/Spring singleton, so no instance is shared between request threads. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- 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
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the dev server (`npm run start`) exited before it served a page. Likely cause (the repository): package.json has no "start" script, so `npm run start` could not start the app. Last output: "npm error Missing script: "start" / npm error / npm error Did you mean one of these? / npm error npm star # Mark your favorite packages / npm error npm stars # View packages marked as favorites / npm error / npm error To see a list of scripts, run: / npm error npm run / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, a MongoDB or Cassandra driver, JDBC) imported either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database or data-store client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, JDBC, MongoDB, Cassandra, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database or data-store client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, JDBC, MongoDB, Cassandra, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D11 Test Reliability — No tests discovered
- D12 Dependency Hygiene — Dependency currency not established — repo1.maven.org did not answer
- D14 License Compliance — Not scored — this repository's 7 pinned sbt dependency coordinate(s) were read from its 7 sbt build file(s), but Maven Central could not be asked for the licence of 6 of them (HTTP 429 Too Many Requests from http://172.31.7.1:8790/maven/com/ibm/icu/icu4j/79.1/icu4j-79.1.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.
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; JavaScript, 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"]`.
- 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) — 56 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the jest suite in packages/eslint-plugin-redos/ ran and not one test passed (FAIL src/rules/no-vulnerable.test.ts), so the coverage would describe the failed run, not the code. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan. Alternatively, commit the lcov/Cobertura report your CI produces and it is read without a re-run.
- 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): 359 value object(s); 3 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- M4 Documentation accuracy — Not applicable: the 30 current-state document(s) make no claim of a kind M4 checks. 40 claim(s) of kinds M4 does not check were not checked (install 6, environment variable 34); M4 checks only links and versions and artefact counts.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM, JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — 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 applicable: allocation awareness is rated where code engineers for it — at least 400 production lines that ship benchmarks or already use allocation-aware idioms (8 or more). This repository's Scala code has 21,186 production line(s), 0 such use(s) and no benchmarks, so there is no allocation work to rate. The card is reward-only: its absence costs nothing.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- R5 Dependency Freshness — uses a pnpm lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
- S1 Web-Security Posture — No web surface: 143 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.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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 — 106 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
- 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
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Import cycle (2 files) packages/recheck/src/main.ts:141
Serious — 159 finding(s)
- Hotspot: modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/FeatureSet.scala modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/FeatureSet.scala:435
- Hotspot: modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/Parser.scala modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/Parser.scala:1346
- Hotspot: modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/vm/Interpreter.scala modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/vm/Interpreter.scala:319
- Hotspot: modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRCharResolver.scala modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRCharResolver.scala:401
- Hotspot: modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRBuilder.scala modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRBuilder.scala:332
- Hotspot: modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/LookBehindAnalyzer.scala modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/LookBehindAnalyzer.scala:98
- Hotspot: modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRPropertyLookup.scala modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRPropertyLookup.scala:229
- Hotspot: modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRFeatureSet.scala modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRFeatureSet.scala:298
- Hotspot: modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ast/FlagSet.scala modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ast/FlagSet.scala:79
- Hotspot: modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/vm/ProgramBuilder.scala modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/vm/ProgramBuilder.scala:304
- Hotspot: modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/automaton/EpsNFA.scala modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/automaton/EpsNFA.scala:73
- Hotspot: modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/fuzz/StaticSeeder.scala modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/fuzz/StaticSeeder.scala:45
- Hotspot: modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/automaton/EpsNFABuilder.scala modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/automaton/EpsNFABuilder.scala:184
- Hotspot: website/src/components/Demo/index.tsx website/src/components/Demo/index.tsx:15
- Hotspot: modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/SemanticAnalyzer.scala modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/SemanticAnalyzer.scala:33
- Hotspot: website/src/components/Demo/DemoResult.tsx website/src/components/Demo/DemoResult.tsx:70
- Hotspot: packages/recheck/src/main.ts packages/recheck/src/main.ts:54
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No test reaches this file packages/recheck-parameters/scripts/build.mts:1
- No test reaches this file packages/recheck/scripts/build.mts:1
- No test reaches this file packages/recheck/src/inject/main.ts:1
- No test reaches this file packages/eslint-plugin-redos/scripts/build.mts:1
- No test reaches this file packages/eslint-plugin-redos/src/main.ts:1
- No test reaches this file packages/recheck/src/inject/worker-node.ts:1
- No test reaches this file packages/recheck/src/inject/worker-browser.ts:1
- No test reaches this file packages/recheck/scripts/parameters.mts:1
- TodoComment packages/eslint-plugin-redos/src/utils/checker.ts:67
- TodoComment packages/eslint-plugin-redos/src/utils/checker.ts:87
- TodoComment packages/eslint-plugin-redos/src/rules/no-vulnerable.test.ts:77
- TodoComment packages/eslint-plugin-redos/src/rules/no-vulnerable.ts:121
- TodoComment modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/fuzz/FuzzChecker.scala:391
- FileTooLong: parser/Parser.scala modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/Parser.scala
- FileTooLong: build/IRCharResolver.scala modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRCharResolver.scala
- FileTooLong: vm/Interpreter.scala modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/vm/Interpreter.scala
- FileTooLong: vm/ProgramBuilder.scala modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/vm/ProgramBuilder.scala
- FileTooLong: build/IRPropertyLookup.scala modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRPropertyLookup.scala
- TooManyMethods: Parser modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/Parser.scala:140
- TooManyMethods: ProgramBuilder modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/vm/ProgramBuilder.scala:48
- TooManyMethods: IRCharResolver modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRCharResolver.scala:35
- TooManyMethods: IRPropertyLookup modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRPropertyLookup.scala:41
- Duplicated block (5 lines × 2) modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/automaton/NFA.scala:28
- Duplicated block (5 lines × 2) modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/vm/Interpreter.scala:798
- Duplicated block (5 lines × 2) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRCharResolver.scala:821
- Workspace package's tests never run by CI packages/eslint-plugin-redos/package.json:33
- Workspace package's tests never run by CI packages/recheck-parameters/package.json:21
- Workspace package's tests never run by CI packages/recheck/package.json:64
- Change coupling: Main.scala ↔ arguments.scala modules/recheck-cli/src/main/scala/codes/quine/labs/recheck/cli/Main.scala:1
- Change coupling: EpsNFABuilder.scala ↔ FuzzProgram.scala modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/automaton/EpsNFABuilder.scala:1
- Duplicated block (9 lines × 2 locations) packages/eslint-plugin-redos/scripts/build.mts:7
- Duplicated block (9 lines × 2 locations) packages/eslint-plugin-redos/src/rules/no-vulnerable.ts:141
- Swallowed exception (empty catch) packages/eslint-plugin-redos/src/utils/cache.ts:40
- Swallowed exception (empty catch) packages/eslint-plugin-redos/src/utils/checker.ts:53
- FeatureSet.from (cyclomatic 175) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/FeatureSet.scala:435
- IRFeatureSet.from (cyclomatic 69) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRFeatureSet.scala:298
- Interpreter.runLoop (cyclomatic 60) modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/vm/Interpreter.scala:319
- FlagSet.parse (cyclomatic 59) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ast/FlagSet.scala:79
- Parser.parseFlagSet (cyclomatic 52) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/Parser.scala:1346
- Parser.scanRemovedComments (cyclomatic 50) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/Parser.scala:915
- Interpreter.inst (cyclomatic 46) modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/vm/Interpreter.scala:574
- IRPropertyLookup.javaForProperty (cyclomatic 41) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRPropertyLookup.scala:229
- Parser.parseConditionalGroupTest (cyclomatic 41) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/Parser.scala:583
- LookBehindAnalyzer.width (cyclomatic 40) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/LookBehindAnalyzer.scala:98
- EpsNFA.toOrderedNFA (cyclomatic 29) modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/automaton/EpsNFA.scala:73
- IRCharResolver.escapeClassSet (cyclomatic 29) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRCharResolver.scala:401
- StaticSeeder.simplify (cyclomatic 26) modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/fuzz/StaticSeeder.scala:45
- Parser.parseExtendedGroup (cyclomatic 25) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/Parser.scala:442
- IRCharResolver.foldPart (cyclomatic 24) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRCharResolver.scala:208
- IRPropertyLookup.javaUnicodePredicate (cyclomatic 24) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRPropertyLookup.scala:281
- SemanticAnalyzer.walk (cyclomatic 23) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/SemanticAnalyzer.scala:33
- PerlLiteralRewriter.scanChunk (cyclomatic 23) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/PerlLiteralRewriter.scala:158
- IRBuilder.buildConditional (cyclomatic 21) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRBuilder.scala:364
- IRCharResolver.determineCaseEquivalence (cyclomatic 21) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRCharResolver.scala:865
- IRPropertyLookup.perl (cyclomatic 21) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRPropertyLookup.scala:774
- LookBehindAnalyzer.validateLookBehind (cyclomatic 21) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/LookBehindAnalyzer.scala:45
- LookBehindAnalyzer.rubyWidth (cyclomatic 20) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/LookBehindAnalyzer.scala:261
- IRBuilder.charWidth (cyclomatic 18) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRBuilder.scala:102
- PerlLiteralRewriter.caseModifier (cyclomatic 18) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/PerlLiteralRewriter.scala:94
- IRCharResolver.property (cyclomatic 17) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRCharResolver.scala:443
- Parser.parseBackslashBackReference (cyclomatic 17) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/Parser.scala:2211
- IRCharResolver.classItem (cyclomatic 16) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRCharResolver.scala:599
- Parser.determineUnitMode (cyclomatic 16) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/Parser.scala:112
- Parser.parseCurlyQuantifier (cyclomatic 16) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/Parser.scala:282
- Parser.parseClassItemAtom (cyclomatic 16) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/Parser.scala:2439
- Parser.parseClassItemNonRange (cyclomatic 16) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/Parser.scala:2534
- Parser.parseGroupNameBody (cyclomatic 16) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/Parser.scala:2767
- Skipped test: check: native (1) packages/recheck/src/main.test.ts:102
- FeatureSet.from (cognitive 170) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/FeatureSet.scala:435
- Interpreter.runLoop (cognitive 130) modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/vm/Interpreter.scala:319
- Parser.scanRemovedComments (cognitive 110) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/Parser.scala:915
- Parser.parseFlagSet (cognitive 77) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/Parser.scala:1346
- Parser.parseConditionalGroupTest (cognitive 56) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/Parser.scala:583
- EpsNFA.toOrderedNFA (cognitive 53) modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/automaton/EpsNFA.scala:73
- IRFeatureSet.from (cognitive 52) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRFeatureSet.scala:298
- FlagSet.parse (cognitive 50) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ast/FlagSet.scala:79
- IRCharResolver.foldPart (cognitive 50) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRCharResolver.scala:208
- GenerateRuntimeAttackScriptCommand.generate (cognitive 45) modules/recheck-cli/src/main/scala/codes/quine/labs/recheck/cli/GenerateRuntimeAttackScriptCommand.scala:16
- PerlLiteralRewriter.scanChunk (cognitive 43) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/PerlLiteralRewriter.scala:158
- LookBehindAnalyzer.validateLookBehind (cognitive 37) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/LookBehindAnalyzer.scala:45
- Interpreter.inst (cognitive 35) modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/vm/Interpreter.scala:574
- IRCharResolver.property (cognitive 33) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRCharResolver.scala:443
- LookBehindAnalyzer.width (cognitive 31) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/LookBehindAnalyzer.scala:98
- PerlLiteralRewriter.caseModifier (cognitive 31) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/PerlLiteralRewriter.scala:94
- IRPropertyLookup.perl (cognitive 30) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRPropertyLookup.scala:774
- AutomatonChecker.findEDA (cognitive 29) modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/automaton/AutomatonChecker.scala:99
- DynamicSeeder.seed (cognitive 28) modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/fuzz/DynamicSeeder.scala:25
- FString.admitsAnyRepeatCount (cognitive 28) modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/fuzz/FString.scala:86
- StaticSeeder.simplify (cognitive 28) modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/fuzz/StaticSeeder.scala:45
- StaticSeeder.findTinyEDA (cognitive 28) modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/fuzz/StaticSeeder.scala:154
- IRPropertyLookup.perlNumericValue (cognitive 25) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRPropertyLookup.scala:679
- EpsNFABuilder.rejectEmpty (cognitive 23) modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/automaton/EpsNFABuilder.scala:122
- Graph.scc (cognitive 23) modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/data/Graph.scala:40
- IRBuilder.charWidth (cognitive 23) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRBuilder.scala:102
- Parser.parseClassItem (cognitive 23) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/Parser.scala:2315
- Parser.parseClassItemAtom (cognitive 23) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/Parser.scala:2439
- SemanticAnalyzer.walk (cognitive 22) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/SemanticAnalyzer.scala:33
- Parser.parseSignedInlineFlagGroup (cognitive 22) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/Parser.scala:1083
- SourcePrescan.from (cognitive 22) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/SourcePrescan.scala:14
- StaticSeeder.findTinyIDA (cognitive 21) modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/fuzz/StaticSeeder.scala:166
- LookBehindAnalyzer.studyJavaRepeat (cognitive 21) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/LookBehindAnalyzer.scala:347
- Parser.parseGroupNameBody (cognitive 21) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/Parser.scala:2767
- IRCharResolver.determineCaseEquivalence (cognitive 20) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRCharResolver.scala:865
- LookBehindAnalyzer.rubyWidth (cognitive 20) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/LookBehindAnalyzer.scala:261
- main.selectBackend (cognitive 20) packages/recheck/src/main.ts:54
- RPC.run (cognitive 19) modules/recheck-cli/src/main/scala/codes/quine/labs/recheck/cli/RPC.scala:149
- Interpreter.compareFolded (cognitive 19) modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/vm/Interpreter.scala:732
- IRCharResolver.joinRubyByteRepeats (cognitive 19) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRCharResolver.scala:92
- Parser.determineUnitMode (cognitive 19) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/Parser.scala:112
- Parser.parseBackslashBackReference (cognitive 19) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/Parser.scala:2211
- Parser.parseBackslashLowerU (cognitive 17) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/Parser.scala:1922
- OrderedNFA.toNFAwLA (cognitive 16) modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/automaton/OrderedNFA.scala:95
- Alphabet.refine (cognitive 16) modules/resyntax-charset/shared/src/main/scala/codes/quine/labs/resyntax/charset/Alphabet.scala:57
- BuildingContext.charset (cognitive 16) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/BuildingContext.scala:91
- IRBuilder.buildSequence (cognitive 16) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRBuilder.scala:289
- IRCharResolver.literals (cognitive 16) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRCharResolver.scala:138
- Parser.skipLineComment (cognitive 16) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/Parser.scala:2976
- PerlLiteralRewriter.pop (cognitive 16) modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/parser/PerlLiteralRewriter.scala:128
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (8–9 lines × 2) modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/vm/ProgramBuilder.scala:677
- Unstable project recheck
- Off the main sequence: resyntaxCharset
- Coverage not measured — JavaScript/TypeScript suite
- No structured logging
- Duplicated block with local edits (13 matched lines × 2 locations) packages/recheck/src/lib/agent.ts:189
- Complex function selectBackend (cyclomatic 17, cognitive 22) packages/recheck/src/main.ts:54
- Complex function check (cyclomatic 11, cognitive 9) packages/eslint-plugin-redos/src/rules/no-vulnerable.ts:67
Minor — 25 finding(s)
- Documentation: no build, run or usage example packages/eslint-plugin-redos/README.md:1
- Documentation: no build, run or usage example packages/recheck/README.md:1
- Documentation: no build, run or usage example packages/recheck-jar/README.md:1
- Documentation: no build, run or usage example packages/recheck-linux-arm64/README.md:1
- Documentation: no build, run or usage example packages/recheck-linux-x64/README.md:1
- Documentation: no build, run or usage example packages/recheck-macos-arm64/README.md:1
- Documentation: no build, run or usage example packages/recheck-macos-x64/README.md:1
- Documentation: no build, run or usage example packages/recheck-windows-x64/README.md:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated predicate modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRFeatureSet.scala:350
- Duplicated predicate modules/resyntax/shared/src/main/scala/codes/quine/labs/resyntax/ir/build/IRCharResolver.scala:823
- No ADRs found
- redundant comment website/src/components/Parameters/markdown.ts:40
- Projects may be oversized for their cohesion
- REDACTED
- REDACTED
- REDACTED
- Blanket warning suppression modules/recheck-cli/src/main/scala/codes/quine/labs/recheck/cli/AgentCommand.scala:96
- Thin README README.md:1
- No ADRs
- No architecture diagram/doc
- 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-e65accabdbea495a8595a09ca28a40cd/history.json --exit-code 0 --source . | 2 | 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-e65accabdbea495a8595a09ca28a40cd/tree.json --exit-code 0 --source . | 1 | 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 . | 57 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 49 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 56 file(s) — `modules/recheck-cli/src/main/scala/codes/quine/labs/recheck/cli/AgentCommand.scala`, `modules/recheck-cli/src/main/scala/codes/quine/labs/recheck/cli/Main.scala`, `modules/recheck-cli/src/main/scala/codes/quine/labs/recheck/cli/RPC.scala`, `modules/recheck-codec/shared/src/main/scala/codes/quine/labs/recheck/codec/package.scala`, `modules/recheck-core/shared/src/main/scala/codes/quine/labs/recheck/ReDoS.scala`, … (+51 more) — so the PII/GDPR sweep did not cover them at all. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |