Executive summary
bytedance/appshark falls short of our standard for a preview release because we found no logging, tracing or health checks in the code and no automated security scanning of the code, its secrets or its dependencies. It scores 56.6 out of 100 and is rated Adequate, and both of its critical findings are security problems in the build pipeline.
Production Readiness, at 31.3, is the weakest lens and counts most in the score. The best first step for the work it takes is recording design decisions, worth about 4.9 points. Adding a diagnostic log would lift Production Readiness itself, worth about 9.6 points. Raising Production Readiness to 62 would lift the score to about 70.8.
Two pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Pinning each tool to an exact version would close this risk.
The product code is 16,371 lines, about €23,000 to rebuild.
If Production Readiness rose from 31.3 to 62, the lowest score rated Strong, the score would rise from 56.6 to about 70.8.
Rebuild cost: about €23,000 · Estimate
| Cost to rebuild | €7,500 to €38,000, for 126 to 399 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.8 at a score of 57. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 16,371 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: which parts of the code depend on which
| uses → | 1 net.bytedance.security.app.pointer | 2 net.bytedance.security.app.ui.TaintPathModeHtmlWriter.Companion | 3 net.bytedance.security.app.util.Profiler | 4 at.syntaxerror.json5.JSONException | 5 net.bytedance.security.app.android.JadxRunner | 6 net.bytedance.security.app.engineconfig | 7 net.bytedance.security.app.pathfinder.TaintPathFinder | 8 net.bytedance.security.app.pathfinder.TaintPathFinder.Companion | 9 net.bytedance.security.app.pointer.PointerFactory | 10 net.bytedance.security.app.preprocess.CallGraph | 11 net.bytedance.security.app.security | 12 net.bytedance.security.app.taintflow.AnalyzeContext | 13 net.bytedance.security.app.taintflow.TwoStagePointerAnalyze | 14 at.syntaxerror.json5 | 15 net.bytedance.security.app.AnalyzeStepByStep | 16 net.bytedance.security.app.engineconfig.VariableFlowConfig | 17 net.bytedance.security.app.preprocess | 18 net.bytedance.security.app.rules | 19 net.bytedance.security.app.security.ScanDeadline | 20 net.bytedance.security.app.security.ScanWorkspace | 21 at.syntaxerror.json5.Json5EscapeSequence | 22 net.bytedance.security.app.AnalyzeStepByStep.TYPE | 23 net.bytedance.security.app.taintflow | 24 net.bytedance.security.app | 25 net.bytedance.security.app.taintflow.MethodAnalyzeMode | 26 net.bytedance.security.app.ArgumentConfig | 27 net.bytedance.security.app.Fragment | 28 net.bytedance.security.app.android | 29 net.bytedance.security.app.pathfinder | 30 net.bytedance.security.app.ruleprocessor | 31 net.bytedance.security.app.sanitizer | 32 net.bytedance.security.app.taintflow.PruneMethodAnalyzeMode | 33 net.bytedance.security.app.pathfinder.TaintFlowEdgeFinder | 34 net.bytedance.security.app.result.model | 35 net.bytedance.security.app.ui.TaintPathModeHtmlWriter | 36 net.bytedance.security.app.result | 37 net.bytedance.security.app.result.VulnerabilityItem | 38 net.bytedance.security.app.ui | 39 net.bytedance.security.app.util | 40 net.bytedance.security.app.util.MethodSignatureParseState |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 net.bytedance.security.app.pointer | ||||||||||||||||||||||||||||||||||||||||
| 2 net.bytedance.security.app.ui.TaintPathModeHtmlWriter.Companion | ||||||||||||||||||||||||||||||||||||||||
| 3 net.bytedance.security.app.util.Profiler | ||||||||||||||||||||||||||||||||||||||||
| 4 at.syntaxerror.json5.JSONException | 1 | |||||||||||||||||||||||||||||||||||||||
| 5 net.bytedance.security.app.android.JadxRunner | 1 | |||||||||||||||||||||||||||||||||||||||
| 6 net.bytedance.security.app.engineconfig | 2 | |||||||||||||||||||||||||||||||||||||||
| 7 net.bytedance.security.app.pathfinder.TaintPathFinder | 1 | |||||||||||||||||||||||||||||||||||||||
| 8 net.bytedance.security.app.pathfinder.TaintPathFinder.Companion | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 net.bytedance.security.app.pointer.PointerFactory | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 net.bytedance.security.app.preprocess.CallGraph | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 net.bytedance.security.app.security | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 net.bytedance.security.app.taintflow.AnalyzeContext | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 net.bytedance.security.app.taintflow.TwoStagePointerAnalyze | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 at.syntaxerror.json5 | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 net.bytedance.security.app.AnalyzeStepByStep | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 net.bytedance.security.app.engineconfig.VariableFlowConfig | 2 | |||||||||||||||||||||||||||||||||||||||
| 17 net.bytedance.security.app.preprocess | 1 | 4 | ||||||||||||||||||||||||||||||||||||||
| 18 net.bytedance.security.app.rules | 5 | 20 | ||||||||||||||||||||||||||||||||||||||
| 19 net.bytedance.security.app.security.ScanDeadline | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 net.bytedance.security.app.security.ScanWorkspace | 2 | |||||||||||||||||||||||||||||||||||||||
| 21 at.syntaxerror.json5.Json5EscapeSequence | 10 | |||||||||||||||||||||||||||||||||||||||
| 22 net.bytedance.security.app.AnalyzeStepByStep.TYPE | 4 | |||||||||||||||||||||||||||||||||||||||
| 23 net.bytedance.security.app.taintflow | 16 | 2 | 2 | 2 | ||||||||||||||||||||||||||||||||||||
| 24 net.bytedance.security.app | 1 | 1 | 2 | 3 | 3 | 4 | ||||||||||||||||||||||||||||||||||
| 25 net.bytedance.security.app.taintflow.MethodAnalyzeMode | 3 | |||||||||||||||||||||||||||||||||||||||
| 26 net.bytedance.security.app.ArgumentConfig | 1 | |||||||||||||||||||||||||||||||||||||||
| 27 net.bytedance.security.app.Fragment | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 net.bytedance.security.app.android | 1 | 3 | 1 | |||||||||||||||||||||||||||||||||||||
| 29 net.bytedance.security.app.pathfinder | 3 | 2 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 30 net.bytedance.security.app.ruleprocessor | 1 | 3 | 15 | 7 | 14 | |||||||||||||||||||||||||||||||||||
| 31 net.bytedance.security.app.sanitizer | 4 | 3 | 1 | 3 | ||||||||||||||||||||||||||||||||||||
| 32 net.bytedance.security.app.taintflow.PruneMethodAnalyzeMode | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 33 net.bytedance.security.app.pathfinder.TaintFlowEdgeFinder | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 34 net.bytedance.security.app.result.model | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 35 net.bytedance.security.app.ui.TaintPathModeHtmlWriter | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 36 net.bytedance.security.app.result | 1 | 2 | 1 | 13 | ||||||||||||||||||||||||||||||||||||
| 37 net.bytedance.security.app.result.VulnerabilityItem | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 38 net.bytedance.security.app.ui | 1 | 1 | 4 | 1 | 1 | 1 | 1 | 8 | ||||||||||||||||||||||||||||||||
| 39 net.bytedance.security.app.util | 2 | 1 | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 40 net.bytedance.security.app.util.MethodSignatureParseState | 4 |
4→14 at.syntaxerror.json5.JSONException uses at.syntaxerror.json5 part of a loop✕
- Connections
- 1 pair of types, where a type in at.syntaxerror.json5.JSONException uses a type in at.syntaxerror.json5.
- The types involved
at.syntaxerror.json5.JSONException.SyntaxError→at.syntaxerror.json5.JSONException
- Direction
- at.syntaxerror.json5.JSONException uses at.syntaxerror.json5, so a change to at.syntaxerror.json5 can break at.syntaxerror.json5.JSONException, while a change to at.syntaxerror.json5.JSONException can't break at.syntaxerror.json5.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→28 net.bytedance.security.app.android.JadxRunner uses net.bytedance.security.app.android part of a loop✕
- Connections
- 1 pair of types, where a type in net.bytedance.security.app.android.JadxRunner uses a type in net.bytedance.security.app.android.
- The types involved
net.bytedance.security.app.android.JadxRunner.Companion→net.bytedance.security.app.android.JadxCacheMetadata
- Direction
- net.bytedance.security.app.android.JadxRunner uses net.bytedance.security.app.android, so a change to net.bytedance.security.app.android can break net.bytedance.security.app.android.JadxRunner, while a change to net.bytedance.security.app.android.JadxRunner can't break net.bytedance.security.app.android.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→24 net.bytedance.security.app.engineconfig uses net.bytedance.security.app part of a loop✕
- Connections
- 2 pairs of types, where a type in net.bytedance.security.app.engineconfig uses a type in net.bytedance.security.app.
- The types involved
net.bytedance.security.app.engineconfig.PointerPropagationConfig→net.bytedance.security.app.TaintTweakDatanet.bytedance.security.app.engineconfig.VariableFlowConfig→net.bytedance.security.app.TaintTweakData
- Direction
- net.bytedance.security.app.engineconfig uses net.bytedance.security.app, so a change to net.bytedance.security.app can break net.bytedance.security.app.engineconfig, while a change to net.bytedance.security.app.engineconfig can't break net.bytedance.security.app.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→1 net.bytedance.security.app.pathfinder.TaintPathFinder uses net.bytedance.security.app.pointer✕
- Connections
- 1 pair of types, where a type in net.bytedance.security.app.pathfinder.TaintPathFinder uses a type in net.bytedance.security.app.pointer.
- The types involved
net.bytedance.security.app.pathfinder.TaintPathFinder.Companion→net.bytedance.security.app.pointer.PLPointer
- Direction
- net.bytedance.security.app.pathfinder.TaintPathFinder uses net.bytedance.security.app.pointer, so a change to net.bytedance.security.app.pointer can break net.bytedance.security.app.pathfinder.TaintPathFinder, while a change to net.bytedance.security.app.pathfinder.TaintPathFinder can't break net.bytedance.security.app.pointer.
- Position
- Below the diagonal: net.bytedance.security.app.pathfinder.TaintPathFinder uses a module listed above it, which is the healthy direction.
8→1 net.bytedance.security.app.pathfinder.TaintPathFinder.Companion uses net.bytedance.security.app.pointer✕
- Connections
- 1 pair of types, where a type in net.bytedance.security.app.pathfinder.TaintPathFinder.Companion uses a type in net.bytedance.security.app.pointer.
- The types involved
net.bytedance.security.app.pathfinder.TaintPathFinder.Companion.PointerAndDepth→net.bytedance.security.app.pointer.PLPointer
- Direction
- net.bytedance.security.app.pathfinder.TaintPathFinder.Companion uses net.bytedance.security.app.pointer, so a change to net.bytedance.security.app.pointer can break net.bytedance.security.app.pathfinder.TaintPathFinder.Companion, while a change to net.bytedance.security.app.pathfinder.TaintPathFinder.Companion can't break net.bytedance.security.app.pointer.
- Position
- Below the diagonal: net.bytedance.security.app.pathfinder.TaintPathFinder.Companion uses a module listed above it, which is the healthy direction.
9→1 net.bytedance.security.app.pointer.PointerFactory uses net.bytedance.security.app.pointer✕
- Connections
- 1 pair of types, where a type in net.bytedance.security.app.pointer.PointerFactory uses a type in net.bytedance.security.app.pointer.
- The types involved
net.bytedance.security.app.pointer.PointerFactory.Companion→net.bytedance.security.app.pointer.PLObject
- Direction
- net.bytedance.security.app.pointer.PointerFactory uses net.bytedance.security.app.pointer, so a change to net.bytedance.security.app.pointer can break net.bytedance.security.app.pointer.PointerFactory, while a change to net.bytedance.security.app.pointer.PointerFactory can't break net.bytedance.security.app.pointer.
- Position
- Below the diagonal: net.bytedance.security.app.pointer.PointerFactory uses a module listed above it, which is the healthy direction.
10→17 net.bytedance.security.app.preprocess.CallGraph uses net.bytedance.security.app.preprocess part of a loop✕
- Connections
- 1 pair of types, where a type in net.bytedance.security.app.preprocess.CallGraph uses a type in net.bytedance.security.app.preprocess.
- The types involved
net.bytedance.security.app.preprocess.CallGraph.SourceAndSinkCross→net.bytedance.security.app.preprocess.CallGraph
- Direction
- net.bytedance.security.app.preprocess.CallGraph uses net.bytedance.security.app.preprocess, so a change to net.bytedance.security.app.preprocess can break net.bytedance.security.app.preprocess.CallGraph, while a change to net.bytedance.security.app.preprocess.CallGraph can't break net.bytedance.security.app.preprocess.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→24 net.bytedance.security.app.security uses net.bytedance.security.app part of a loop✕
- Connections
- 1 pair of types, where a type in net.bytedance.security.app.security uses a type in net.bytedance.security.app.
- The types involved
net.bytedance.security.app.security.RuleLoadContext→net.bytedance.security.app.RuleData
- Direction
- net.bytedance.security.app.security uses net.bytedance.security.app, so a change to net.bytedance.security.app can break net.bytedance.security.app.security, while a change to net.bytedance.security.app.security can't break net.bytedance.security.app.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→1 net.bytedance.security.app.taintflow.AnalyzeContext uses net.bytedance.security.app.pointer✕
- Connections
- 1 pair of types, where a type in net.bytedance.security.app.taintflow.AnalyzeContext uses a type in net.bytedance.security.app.pointer.
- The types involved
net.bytedance.security.app.taintflow.AnalyzeContext.Companion→net.bytedance.security.app.pointer.PLPointer
- Direction
- net.bytedance.security.app.taintflow.AnalyzeContext uses net.bytedance.security.app.pointer, so a change to net.bytedance.security.app.pointer can break net.bytedance.security.app.taintflow.AnalyzeContext, while a change to net.bytedance.security.app.taintflow.AnalyzeContext can't break net.bytedance.security.app.pointer.
- Position
- Below the diagonal: net.bytedance.security.app.taintflow.AnalyzeContext uses a module listed above it, which is the healthy direction.
13→1 net.bytedance.security.app.taintflow.TwoStagePointerAnalyze uses net.bytedance.security.app.pointer✕
- Connections
- 1 pair of types, where a type in net.bytedance.security.app.taintflow.TwoStagePointerAnalyze uses a type in net.bytedance.security.app.pointer.
- The types involved
net.bytedance.security.app.taintflow.TwoStagePointerAnalyze.Companion→net.bytedance.security.app.pointer.PLPointer
- Direction
- net.bytedance.security.app.taintflow.TwoStagePointerAnalyze uses net.bytedance.security.app.pointer, so a change to net.bytedance.security.app.pointer can break net.bytedance.security.app.taintflow.TwoStagePointerAnalyze, while a change to net.bytedance.security.app.taintflow.TwoStagePointerAnalyze can't break net.bytedance.security.app.pointer.
- Position
- Below the diagonal: net.bytedance.security.app.taintflow.TwoStagePointerAnalyze uses a module listed above it, which is the healthy direction.
14→4 at.syntaxerror.json5 uses at.syntaxerror.json5.JSONException✕
- Connections
- 1 pair of types, where a type in at.syntaxerror.json5 uses a type in at.syntaxerror.json5.JSONException.
- The types involved
at.syntaxerror.json5.JSONParser→at.syntaxerror.json5.JSONException.SyntaxError
- Direction
- at.syntaxerror.json5 uses at.syntaxerror.json5.JSONException, so a change to at.syntaxerror.json5.JSONException can break at.syntaxerror.json5, while a change to at.syntaxerror.json5 can't break at.syntaxerror.json5.JSONException.
- Position
- Below the diagonal: at.syntaxerror.json5 uses a module listed above it, which is the healthy direction.
15→11 net.bytedance.security.app.AnalyzeStepByStep uses net.bytedance.security.app.security✕
- Connections
- 1 pair of types, where a type in net.bytedance.security.app.AnalyzeStepByStep uses a type in net.bytedance.security.app.security.
- The types involved
net.bytedance.security.app.AnalyzeStepByStep.PreparedRules→net.bytedance.security.app.security.RuleLoadContext
- Direction
- net.bytedance.security.app.AnalyzeStepByStep uses net.bytedance.security.app.security, so a change to net.bytedance.security.app.security can break net.bytedance.security.app.AnalyzeStepByStep, while a change to net.bytedance.security.app.AnalyzeStepByStep can't break net.bytedance.security.app.security.
- Position
- Below the diagonal: net.bytedance.security.app.AnalyzeStepByStep uses a module listed above it, which is the healthy direction.
16→6 net.bytedance.security.app.engineconfig.VariableFlowConfig uses net.bytedance.security.app.engineconfig✕
- Connections
- 2 pairs of types, where a type in net.bytedance.security.app.engineconfig.VariableFlowConfig uses a type in net.bytedance.security.app.engineconfig.
- The types involved
net.bytedance.security.app.engineconfig.VariableFlowConfig.Companion→net.bytedance.security.app.engineconfig.IODatanet.bytedance.security.app.engineconfig.VariableFlowConfig.Companion→net.bytedance.security.app.engineconfig.Propagation
- Direction
- net.bytedance.security.app.engineconfig.VariableFlowConfig uses net.bytedance.security.app.engineconfig, so a change to net.bytedance.security.app.engineconfig can break net.bytedance.security.app.engineconfig.VariableFlowConfig, while a change to net.bytedance.security.app.engineconfig.VariableFlowConfig can't break net.bytedance.security.app.engineconfig.
- Position
- Below the diagonal: net.bytedance.security.app.engineconfig.VariableFlowConfig uses a module listed above it, which is the healthy direction.
17→10 net.bytedance.security.app.preprocess uses net.bytedance.security.app.preprocess.CallGraph✕
- Connections
- 1 pair of types, where a type in net.bytedance.security.app.preprocess uses a type in net.bytedance.security.app.preprocess.CallGraph.
- The types involved
net.bytedance.security.app.preprocess.CallGraph→net.bytedance.security.app.preprocess.CallGraph.CrossResult
- Direction
- net.bytedance.security.app.preprocess uses net.bytedance.security.app.preprocess.CallGraph, so a change to net.bytedance.security.app.preprocess.CallGraph can break net.bytedance.security.app.preprocess, while a change to net.bytedance.security.app.preprocess can't break net.bytedance.security.app.preprocess.CallGraph.
- Position
- Below the diagonal: net.bytedance.security.app.preprocess uses a module listed above it, which is the healthy direction.
17→24 net.bytedance.security.app.preprocess uses net.bytedance.security.app part of a loop✕
- Connections
- 4 pairs of types, where a type in net.bytedance.security.app.preprocess uses a type in net.bytedance.security.app.
- The types involved
net.bytedance.security.app.preprocess.AnalyzePreProcessor→net.bytedance.security.app.PreAnalyzeContextnet.bytedance.security.app.preprocess.ClassCounter→net.bytedance.security.app.PreAnalyzeContextnet.bytedance.security.app.preprocess.MethodCounter→net.bytedance.security.app.PreAnalyzeContextnet.bytedance.security.app.preprocess.MethodFieldConstCacheVisitor→net.bytedance.security.app.PreAnalyzeContext
- Direction
- net.bytedance.security.app.preprocess uses net.bytedance.security.app, so a change to net.bytedance.security.app can break net.bytedance.security.app.preprocess, while a change to net.bytedance.security.app.preprocess can't break net.bytedance.security.app.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→11 net.bytedance.security.app.rules uses net.bytedance.security.app.security✕
- Connections
- 5 pairs of types, where a type in net.bytedance.security.app.rules uses a type in net.bytedance.security.app.security.
- The types involved
net.bytedance.security.app.rules.DirectModeRule→net.bytedance.security.app.security.RuleLoadContextnet.bytedance.security.app.rules.IRuleFactory→net.bytedance.security.app.security.RuleLoadContextnet.bytedance.security.app.rules.RuleFactory→net.bytedance.security.app.security.RuleLoadContextnet.bytedance.security.app.rules.Rules→net.bytedance.security.app.security.RuleLoadContextnet.bytedance.security.app.rules.SliceModeRule→net.bytedance.security.app.security.RuleLoadContext
- Direction
- net.bytedance.security.app.rules uses net.bytedance.security.app.security, so a change to net.bytedance.security.app.security can break net.bytedance.security.app.rules, while a change to net.bytedance.security.app.rules can't break net.bytedance.security.app.security.
- Position
- Below the diagonal: net.bytedance.security.app.rules uses a module listed above it, which is the healthy direction.
18→24 net.bytedance.security.app.rules uses net.bytedance.security.app part of a loop✕
- Connections
- 20 pairs of types, where a type in net.bytedance.security.app.rules uses a type in net.bytedance.security.app.
- The types involved
net.bytedance.security.app.rules.AbstractRule→net.bytedance.security.app.RuleDatanet.bytedance.security.app.rules.AbstractRule→net.bytedance.security.app.RuleDescriptionnet.bytedance.security.app.rules.ApiModeRule→net.bytedance.security.app.RuleDatanet.bytedance.security.app.rules.ApiModeRule→net.bytedance.security.app.SinkBodynet.bytedance.security.app.rules.ConstNumberModeRule→net.bytedance.security.app.RuleDatanet.bytedance.security.app.rules.ConstStringModeRule→net.bytedance.security.app.RuleDatanet.bytedance.security.app.rules.DirectModeRule→net.bytedance.security.app.Entrynet.bytedance.security.app.rules.DirectModeRule→net.bytedance.security.app.RuleDatanet.bytedance.security.app.rules.DirectModeRule→net.bytedance.security.app.RuleObjBodynet.bytedance.security.app.rules.DirectModeRule→net.bytedance.security.app.SinkBodynet.bytedance.security.app.rules.DirectModeRule→net.bytedance.security.app.SourceBodynet.bytedance.security.app.rules.DirectModeRule→net.bytedance.security.app.ThroughAPInet.bytedance.security.app.rules.IRule→net.bytedance.security.app.RuleDescriptionnet.bytedance.security.app.rules.IRuleFactory→net.bytedance.security.app.RuleDatanet.bytedance.security.app.rules.RuleFactory→net.bytedance.security.app.RuleDatanet.bytedance.security.app.rules.SliceModeRule→net.bytedance.security.app.RuleDatanet.bytedance.security.app.rules.TaintFlowRule→net.bytedance.security.app.RuleDatanet.bytedance.security.app.rules.TaintFlowRule→net.bytedance.security.app.SinkBodynet.bytedance.security.app.rules.TaintFlowRule→net.bytedance.security.app.SourceBodynet.bytedance.security.app.rules.TaintFlowRule→net.bytedance.security.app.TaintTweakData
- Direction
- net.bytedance.security.app.rules uses net.bytedance.security.app, so a change to net.bytedance.security.app can break net.bytedance.security.app.rules, while a change to net.bytedance.security.app.rules can't break net.bytedance.security.app.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→11 net.bytedance.security.app.security.ScanDeadline uses net.bytedance.security.app.security✕
- Connections
- 1 pair of types, where a type in net.bytedance.security.app.security.ScanDeadline uses a type in net.bytedance.security.app.security.
- The types involved
net.bytedance.security.app.security.ScanDeadline.Companion→net.bytedance.security.app.security.ScanDeadline
- Direction
- net.bytedance.security.app.security.ScanDeadline uses net.bytedance.security.app.security, so a change to net.bytedance.security.app.security can break net.bytedance.security.app.security.ScanDeadline, while a change to net.bytedance.security.app.security.ScanDeadline can't break net.bytedance.security.app.security.
- Position
- Below the diagonal: net.bytedance.security.app.security.ScanDeadline uses a module listed above it, which is the healthy direction.
20→11 net.bytedance.security.app.security.ScanWorkspace uses net.bytedance.security.app.security✕
- Connections
- 2 pairs of types, where a type in net.bytedance.security.app.security.ScanWorkspace uses a type in net.bytedance.security.app.security.
- The types involved
net.bytedance.security.app.security.ScanWorkspace.Companion→net.bytedance.security.app.security.ScanWorkspacenet.bytedance.security.app.security.ScanWorkspace.Companion→net.bytedance.security.app.security.SecurityLimits
- Direction
- net.bytedance.security.app.security.ScanWorkspace uses net.bytedance.security.app.security, so a change to net.bytedance.security.app.security can break net.bytedance.security.app.security.ScanWorkspace, while a change to net.bytedance.security.app.security.ScanWorkspace can't break net.bytedance.security.app.security.
- Position
- Below the diagonal: net.bytedance.security.app.security.ScanWorkspace uses a module listed above it, which is the healthy direction.
21→14 at.syntaxerror.json5.Json5EscapeSequence uses at.syntaxerror.json5✕
- Connections
- 10 pairs of types, where a type in at.syntaxerror.json5.Json5EscapeSequence uses a type in at.syntaxerror.json5.
- The types involved
at.syntaxerror.json5.Json5EscapeSequence.Apostrophe→at.syntaxerror.json5.Json5EscapeSequenceat.syntaxerror.json5.Json5EscapeSequence.Backspace→at.syntaxerror.json5.Json5EscapeSequenceat.syntaxerror.json5.Json5EscapeSequence.CarriageReturn→at.syntaxerror.json5.Json5EscapeSequenceat.syntaxerror.json5.Json5EscapeSequence.FormFeed→at.syntaxerror.json5.Json5EscapeSequenceat.syntaxerror.json5.Json5EscapeSequence.HorizontalTab→at.syntaxerror.json5.Json5EscapeSequenceat.syntaxerror.json5.Json5EscapeSequence.LineFeed→at.syntaxerror.json5.Json5EscapeSequenceat.syntaxerror.json5.Json5EscapeSequence.Null→at.syntaxerror.json5.Json5EscapeSequenceat.syntaxerror.json5.Json5EscapeSequence.QuotationMark→at.syntaxerror.json5.Json5EscapeSequenceat.syntaxerror.json5.Json5EscapeSequence.ReverseSolidus→at.syntaxerror.json5.Json5EscapeSequenceat.syntaxerror.json5.Json5EscapeSequence.VerticalTab→at.syntaxerror.json5.Json5EscapeSequence
- Direction
- at.syntaxerror.json5.Json5EscapeSequence uses at.syntaxerror.json5, so a change to at.syntaxerror.json5 can break at.syntaxerror.json5.Json5EscapeSequence, while a change to at.syntaxerror.json5.Json5EscapeSequence can't break at.syntaxerror.json5.
- Position
- Below the diagonal: at.syntaxerror.json5.Json5EscapeSequence uses a module listed above it, which is the healthy direction.
22→15 net.bytedance.security.app.AnalyzeStepByStep.TYPE uses net.bytedance.security.app.AnalyzeStepByStep✕
- Connections
- 4 pairs of types, where a type in net.bytedance.security.app.AnalyzeStepByStep.TYPE uses a type in net.bytedance.security.app.AnalyzeStepByStep.
- The types involved
net.bytedance.security.app.AnalyzeStepByStep.TYPE.AAR→net.bytedance.security.app.AnalyzeStepByStep.TYPEnet.bytedance.security.app.AnalyzeStepByStep.TYPE.APK→net.bytedance.security.app.AnalyzeStepByStep.TYPEnet.bytedance.security.app.AnalyzeStepByStep.TYPE.CLASS→net.bytedance.security.app.AnalyzeStepByStep.TYPEnet.bytedance.security.app.AnalyzeStepByStep.TYPE.JIMPLE→net.bytedance.security.app.AnalyzeStepByStep.TYPE
- Direction
- net.bytedance.security.app.AnalyzeStepByStep.TYPE uses net.bytedance.security.app.AnalyzeStepByStep, so a change to net.bytedance.security.app.AnalyzeStepByStep can break net.bytedance.security.app.AnalyzeStepByStep.TYPE, while a change to net.bytedance.security.app.AnalyzeStepByStep.TYPE can't break net.bytedance.security.app.AnalyzeStepByStep.
- Position
- Below the diagonal: net.bytedance.security.app.AnalyzeStepByStep.TYPE uses a module listed above it, which is the healthy direction.
23→1 net.bytedance.security.app.taintflow uses net.bytedance.security.app.pointer✕
- Connections
- 16 pairs of types, where a type in net.bytedance.security.app.taintflow uses a type in net.bytedance.security.app.pointer.
- The types involved
net.bytedance.security.app.taintflow.AnalyzeContext→net.bytedance.security.app.pointer.PLObjectnet.bytedance.security.app.taintflow.AnalyzeContext→net.bytedance.security.app.pointer.PLPointernet.bytedance.security.app.taintflow.AnalyzeContext→net.bytedance.security.app.pointer.PointerFactorynet.bytedance.security.app.taintflow.ObscureRuleHandler→net.bytedance.security.app.pointer.PLPointernet.bytedance.security.app.taintflow.ObscureRuleHandler→net.bytedance.security.app.pointer.PointerFactorynet.bytedance.security.app.taintflow.PruneMethodAnalyzeMode→net.bytedance.security.app.pointer.PLLocalPointernet.bytedance.security.app.taintflow.StmtTransfer→net.bytedance.security.app.pointer.PLLocalPointernet.bytedance.security.app.taintflow.StmtTransfer→net.bytedance.security.app.pointer.PLPointernet.bytedance.security.app.taintflow.StmtTransfer→net.bytedance.security.app.pointer.PointerFactorynet.bytedance.security.app.taintflow.TaintAnalyzer→net.bytedance.security.app.pointer.PLLocalPointernet.bytedance.security.app.taintflow.TaintAnalyzerData→net.bytedance.security.app.pointer.PLLocalPointernet.bytedance.security.app.taintflow.TaintAnalyzerData→net.bytedance.security.app.pointer.PLPointernet.bytedance.security.app.taintflow.TwoStagePointerAnalyze→net.bytedance.security.app.pointer.PLLocalPointernet.bytedance.security.app.taintflow.TwoStagePointerAnalyze→net.bytedance.security.app.pointer.PLObjectnet.bytedance.security.app.taintflow.TwoStagePointerAnalyze→net.bytedance.security.app.pointer.PLPointernet.bytedance.security.app.taintflow.TwoStagePointerAnalyze→net.bytedance.security.app.pointer.PointerFactory
- Direction
- net.bytedance.security.app.taintflow uses net.bytedance.security.app.pointer, so a change to net.bytedance.security.app.pointer can break net.bytedance.security.app.taintflow, while a change to net.bytedance.security.app.taintflow can't break net.bytedance.security.app.pointer.
- Position
- Below the diagonal: net.bytedance.security.app.taintflow uses a module listed above it, which is the healthy direction.
23→6 net.bytedance.security.app.taintflow uses net.bytedance.security.app.engineconfig✕
- Connections
- 2 pairs of types, where a type in net.bytedance.security.app.taintflow uses a type in net.bytedance.security.app.engineconfig.
- The types involved
net.bytedance.security.app.taintflow.DefaultPointerPropagationRule→net.bytedance.security.app.engineconfig.PointerPropagationConfignet.bytedance.security.app.taintflow.DefaultVariableFlowRule→net.bytedance.security.app.engineconfig.VariableFlowConfig
- Direction
- net.bytedance.security.app.taintflow uses net.bytedance.security.app.engineconfig, so a change to net.bytedance.security.app.engineconfig can break net.bytedance.security.app.taintflow, while a change to net.bytedance.security.app.taintflow can't break net.bytedance.security.app.engineconfig.
- Position
- Below the diagonal: net.bytedance.security.app.taintflow uses a module listed above it, which is the healthy direction.
23→18 net.bytedance.security.app.taintflow uses net.bytedance.security.app.rules✕
- Connections
- 2 pairs of types, where a type in net.bytedance.security.app.taintflow uses a type in net.bytedance.security.app.rules.
- The types involved
net.bytedance.security.app.taintflow.FlowItem→net.bytedance.security.app.rules.TaintPositionnet.bytedance.security.app.taintflow.TaintAnalyzer→net.bytedance.security.app.rules.TaintFlowRule
- Direction
- net.bytedance.security.app.taintflow uses net.bytedance.security.app.rules, so a change to net.bytedance.security.app.rules can break net.bytedance.security.app.taintflow, while a change to net.bytedance.security.app.taintflow can't break net.bytedance.security.app.rules.
- Position
- Below the diagonal: net.bytedance.security.app.taintflow uses a module listed above it, which is the healthy direction.
23→24 net.bytedance.security.app.taintflow uses net.bytedance.security.app part of a loop✕
- Connections
- 2 pairs of types, where a type in net.bytedance.security.app.taintflow uses a type in net.bytedance.security.app.
- The types involved
net.bytedance.security.app.taintflow.PruneMethodAnalyzeMode→net.bytedance.security.app.PreAnalyzeContextnet.bytedance.security.app.taintflow.TaintTweakTaintFlowRule→net.bytedance.security.app.TaintTweakData
- Direction
- net.bytedance.security.app.taintflow uses net.bytedance.security.app, so a change to net.bytedance.security.app can break net.bytedance.security.app.taintflow, while a change to net.bytedance.security.app.taintflow can't break net.bytedance.security.app.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→6 net.bytedance.security.app uses net.bytedance.security.app.engineconfig✕
- Connections
- 1 pair of types, where a type in net.bytedance.security.app uses a type in net.bytedance.security.app.engineconfig.
- The types involved
net.bytedance.security.app.TaintTweakData→net.bytedance.security.app.engineconfig.IOData
- Direction
- net.bytedance.security.app uses net.bytedance.security.app.engineconfig, so a change to net.bytedance.security.app.engineconfig can break net.bytedance.security.app, while a change to net.bytedance.security.app can't break net.bytedance.security.app.engineconfig.
- Position
- Below the diagonal: net.bytedance.security.app uses a module listed above it, which is the healthy direction.
24→11 net.bytedance.security.app uses net.bytedance.security.app.security✕
- Connections
- 1 pair of types, where a type in net.bytedance.security.app uses a type in net.bytedance.security.app.security.
- The types involved
net.bytedance.security.app.ArgumentConfig→net.bytedance.security.app.security.SecurityLimits
- Direction
- net.bytedance.security.app uses net.bytedance.security.app.security, so a change to net.bytedance.security.app.security can break net.bytedance.security.app, while a change to net.bytedance.security.app can't break net.bytedance.security.app.security.
- Position
- Below the diagonal: net.bytedance.security.app uses a module listed above it, which is the healthy direction.
24→15 net.bytedance.security.app uses net.bytedance.security.app.AnalyzeStepByStep✕
- Connections
- 2 pairs of types, where a type in net.bytedance.security.app uses a type in net.bytedance.security.app.AnalyzeStepByStep.
- The types involved
net.bytedance.security.app.AnalyzeStepByStep→net.bytedance.security.app.AnalyzeStepByStep.PreparedRulesnet.bytedance.security.app.AnalyzeStepByStep→net.bytedance.security.app.AnalyzeStepByStep.TYPE
- Direction
- net.bytedance.security.app uses net.bytedance.security.app.AnalyzeStepByStep, so a change to net.bytedance.security.app.AnalyzeStepByStep can break net.bytedance.security.app, while a change to net.bytedance.security.app can't break net.bytedance.security.app.AnalyzeStepByStep.
- Position
- Below the diagonal: net.bytedance.security.app uses a module listed above it, which is the healthy direction.
24→17 net.bytedance.security.app uses net.bytedance.security.app.preprocess✕
- Connections
- 3 pairs of types, where a type in net.bytedance.security.app uses a type in net.bytedance.security.app.preprocess.
- The types involved
net.bytedance.security.app.PreAnalyzeContext→net.bytedance.security.app.preprocess.AnalyzePreProcessornet.bytedance.security.app.PreAnalyzeContext→net.bytedance.security.app.preprocess.CallGraphnet.bytedance.security.app.PreAnalyzeContext→net.bytedance.security.app.preprocess.CallSite
- Direction
- net.bytedance.security.app uses net.bytedance.security.app.preprocess, so a change to net.bytedance.security.app.preprocess can break net.bytedance.security.app, while a change to net.bytedance.security.app can't break net.bytedance.security.app.preprocess.
- Position
- Below the diagonal: net.bytedance.security.app uses a module listed above it, which is the healthy direction.
24→18 net.bytedance.security.app uses net.bytedance.security.app.rules✕
- Connections
- 3 pairs of types, where a type in net.bytedance.security.app uses a type in net.bytedance.security.app.rules.
- The types involved
net.bytedance.security.app.AnalyzeStepByStep→net.bytedance.security.app.rules.Rulesnet.bytedance.security.app.AnalyzersAndDepth→net.bytedance.security.app.rules.TaintFlowRulenet.bytedance.security.app.PreAnalyzeContext→net.bytedance.security.app.rules.IRulesForContext
- Direction
- net.bytedance.security.app uses net.bytedance.security.app.rules, so a change to net.bytedance.security.app.rules can break net.bytedance.security.app, while a change to net.bytedance.security.app can't break net.bytedance.security.app.rules.
- Position
- Below the diagonal: net.bytedance.security.app uses a module listed above it, which is the healthy direction.
24→23 net.bytedance.security.app uses net.bytedance.security.app.taintflow✕
- Connections
- 4 pairs of types, where a type in net.bytedance.security.app uses a type in net.bytedance.security.app.taintflow.
- The types involved
net.bytedance.security.app.AnalyzeStepByStep→net.bytedance.security.app.taintflow.TaintAnalyzernet.bytedance.security.app.AnalyzersAndDepth→net.bytedance.security.app.taintflow.TaintAnalyzernet.bytedance.security.app.SliceAnalyzeWrapper→net.bytedance.security.app.taintflow.TaintAnalyzernet.bytedance.security.app.WholeProcessAnalyzeWrapper→net.bytedance.security.app.taintflow.TaintAnalyzer
- Direction
- net.bytedance.security.app uses net.bytedance.security.app.taintflow, so a change to net.bytedance.security.app.taintflow can break net.bytedance.security.app, while a change to net.bytedance.security.app can't break net.bytedance.security.app.taintflow.
- Position
- Below the diagonal: net.bytedance.security.app uses a module listed above it, which is the healthy direction.
25→23 net.bytedance.security.app.taintflow.MethodAnalyzeMode uses net.bytedance.security.app.taintflow✕
- Connections
- 3 pairs of types, where a type in net.bytedance.security.app.taintflow.MethodAnalyzeMode uses a type in net.bytedance.security.app.taintflow.
- The types involved
net.bytedance.security.app.taintflow.MethodAnalyzeMode.Analyze→net.bytedance.security.app.taintflow.MethodAnalyzeModenet.bytedance.security.app.taintflow.MethodAnalyzeMode.Obscure→net.bytedance.security.app.taintflow.MethodAnalyzeModenet.bytedance.security.app.taintflow.MethodAnalyzeMode.Skip→net.bytedance.security.app.taintflow.MethodAnalyzeMode
- Direction
- net.bytedance.security.app.taintflow.MethodAnalyzeMode uses net.bytedance.security.app.taintflow, so a change to net.bytedance.security.app.taintflow can break net.bytedance.security.app.taintflow.MethodAnalyzeMode, while a change to net.bytedance.security.app.taintflow.MethodAnalyzeMode can't break net.bytedance.security.app.taintflow.
- Position
- Below the diagonal: net.bytedance.security.app.taintflow.MethodAnalyzeMode uses a module listed above it, which is the healthy direction.
26→24 net.bytedance.security.app.ArgumentConfig uses net.bytedance.security.app✕
- Connections
- 1 pair of types, where a type in net.bytedance.security.app.ArgumentConfig uses a type in net.bytedance.security.app.
- The types involved
net.bytedance.security.app.ArgumentConfig.Companion→net.bytedance.security.app.ArgumentConfig
- Direction
- net.bytedance.security.app.ArgumentConfig uses net.bytedance.security.app, so a change to net.bytedance.security.app can break net.bytedance.security.app.ArgumentConfig, while a change to net.bytedance.security.app.ArgumentConfig can't break net.bytedance.security.app.
- Position
- Below the diagonal: net.bytedance.security.app.ArgumentConfig uses a module listed above it, which is the healthy direction.
27→24 net.bytedance.security.app.Fragment uses net.bytedance.security.app✕
- Connections
- 1 pair of types, where a type in net.bytedance.security.app.Fragment uses a type in net.bytedance.security.app.
- The types involved
net.bytedance.security.app.Fragment.Companion→net.bytedance.security.app.PreAnalyzeContext
- Direction
- net.bytedance.security.app.Fragment uses net.bytedance.security.app, so a change to net.bytedance.security.app can break net.bytedance.security.app.Fragment, while a change to net.bytedance.security.app.Fragment can't break net.bytedance.security.app.
- Position
- Below the diagonal: net.bytedance.security.app.Fragment uses a module listed above it, which is the healthy direction.
28→5 net.bytedance.security.app.android uses net.bytedance.security.app.android.JadxRunner✕
- Connections
- 1 pair of types, where a type in net.bytedance.security.app.android uses a type in net.bytedance.security.app.android.JadxRunner.
- The types involved
net.bytedance.security.app.android.JadxRunner→net.bytedance.security.app.android.JadxRunner.OutputStats
- Direction
- net.bytedance.security.app.android uses net.bytedance.security.app.android.JadxRunner, so a change to net.bytedance.security.app.android.JadxRunner can break net.bytedance.security.app.android, while a change to net.bytedance.security.app.android can't break net.bytedance.security.app.android.JadxRunner.
- Position
- Below the diagonal: net.bytedance.security.app.android uses a module listed above it, which is the healthy direction.
28→11 net.bytedance.security.app.android uses net.bytedance.security.app.security✕
- Connections
- 3 pairs of types, where a type in net.bytedance.security.app.android uses a type in net.bytedance.security.app.security.
- The types involved
net.bytedance.security.app.android.AndroidUtils→net.bytedance.security.app.security.ScanWorkspacenet.bytedance.security.app.android.JadxRunner→net.bytedance.security.app.security.ScanWorkspacenet.bytedance.security.app.android.JadxRunner→net.bytedance.security.app.security.SecurityLimits
- Direction
- net.bytedance.security.app.android uses net.bytedance.security.app.security, so a change to net.bytedance.security.app.security can break net.bytedance.security.app.android, while a change to net.bytedance.security.app.android can't break net.bytedance.security.app.security.
- Position
- Below the diagonal: net.bytedance.security.app.android uses a module listed above it, which is the healthy direction.
28→24 net.bytedance.security.app.android uses net.bytedance.security.app✕
- Connections
- 1 pair of types, where a type in net.bytedance.security.app.android uses a type in net.bytedance.security.app.
- The types involved
net.bytedance.security.app.android.AndroidUtils→net.bytedance.security.app.PreAnalyzeContext
- Direction
- net.bytedance.security.app.android uses net.bytedance.security.app, so a change to net.bytedance.security.app can break net.bytedance.security.app.android, while a change to net.bytedance.security.app.android can't break net.bytedance.security.app.
- Position
- Below the diagonal: net.bytedance.security.app.android uses a module listed above it, which is the healthy direction.
29→1 net.bytedance.security.app.pathfinder uses net.bytedance.security.app.pointer✕
- Connections
- 3 pairs of types, where a type in net.bytedance.security.app.pathfinder uses a type in net.bytedance.security.app.pointer.
- The types involved
net.bytedance.security.app.pathfinder.PathResult→net.bytedance.security.app.pointer.PLPointernet.bytedance.security.app.pathfinder.TaintPathFinder→net.bytedance.security.app.pointer.PLLocalPointernet.bytedance.security.app.pathfinder.TaintPathFinder→net.bytedance.security.app.pointer.PLPointer
- Direction
- net.bytedance.security.app.pathfinder uses net.bytedance.security.app.pointer, so a change to net.bytedance.security.app.pointer can break net.bytedance.security.app.pathfinder, while a change to net.bytedance.security.app.pathfinder can't break net.bytedance.security.app.pointer.
- Position
- Below the diagonal: net.bytedance.security.app.pathfinder uses a module listed above it, which is the healthy direction.
29→18 net.bytedance.security.app.pathfinder uses net.bytedance.security.app.rules✕
- Connections
- 2 pairs of types, where a type in net.bytedance.security.app.pathfinder uses a type in net.bytedance.security.app.rules.
- The types involved
net.bytedance.security.app.pathfinder.TaintFlowEdgeFinder→net.bytedance.security.app.rules.TaintFlowRulenet.bytedance.security.app.pathfinder.TaintPathFinder→net.bytedance.security.app.rules.TaintFlowRule
- Direction
- net.bytedance.security.app.pathfinder uses net.bytedance.security.app.rules, so a change to net.bytedance.security.app.rules can break net.bytedance.security.app.pathfinder, while a change to net.bytedance.security.app.pathfinder can't break net.bytedance.security.app.rules.
- Position
- Below the diagonal: net.bytedance.security.app.pathfinder uses a module listed above it, which is the healthy direction.
29→23 net.bytedance.security.app.pathfinder uses net.bytedance.security.app.taintflow✕
- Connections
- 2 pairs of types, where a type in net.bytedance.security.app.pathfinder uses a type in net.bytedance.security.app.taintflow.
- The types involved
net.bytedance.security.app.pathfinder.TaintPathFinder→net.bytedance.security.app.taintflow.AnalyzeContextnet.bytedance.security.app.pathfinder.TaintPathFinder→net.bytedance.security.app.taintflow.TaintAnalyzer
- Direction
- net.bytedance.security.app.pathfinder uses net.bytedance.security.app.taintflow, so a change to net.bytedance.security.app.taintflow can break net.bytedance.security.app.pathfinder, while a change to net.bytedance.security.app.pathfinder can't break net.bytedance.security.app.taintflow.
- Position
- Below the diagonal: net.bytedance.security.app.pathfinder uses a module listed above it, which is the healthy direction.
29→24 net.bytedance.security.app.pathfinder uses net.bytedance.security.app✕
- Connections
- 1 pair of types, where a type in net.bytedance.security.app.pathfinder uses a type in net.bytedance.security.app.
- The types involved
net.bytedance.security.app.pathfinder.TaintPathFinder→net.bytedance.security.app.PreAnalyzeContext
- Direction
- net.bytedance.security.app.pathfinder uses net.bytedance.security.app, so a change to net.bytedance.security.app can break net.bytedance.security.app.pathfinder, while a change to net.bytedance.security.app.pathfinder can't break net.bytedance.security.app.
- Position
- Below the diagonal: net.bytedance.security.app.pathfinder uses a module listed above it, which is the healthy direction.
30→1 net.bytedance.security.app.ruleprocessor uses net.bytedance.security.app.pointer✕
- Connections
- 1 pair of types, where a type in net.bytedance.security.app.ruleprocessor uses a type in net.bytedance.security.app.pointer.
- The types involved
net.bytedance.security.app.ruleprocessor.TaintRuleSourceSinkCollector→net.bytedance.security.app.pointer.PLLocalPointer
- Direction
- net.bytedance.security.app.ruleprocessor uses net.bytedance.security.app.pointer, so a change to net.bytedance.security.app.pointer can break net.bytedance.security.app.ruleprocessor, while a change to net.bytedance.security.app.ruleprocessor can't break net.bytedance.security.app.pointer.
- Position
- Below the diagonal: net.bytedance.security.app.ruleprocessor uses a module listed above it, which is the healthy direction.
30→17 net.bytedance.security.app.ruleprocessor uses net.bytedance.security.app.preprocess✕
- Connections
- 3 pairs of types, where a type in net.bytedance.security.app.ruleprocessor uses a type in net.bytedance.security.app.preprocess.
- The types involved
net.bytedance.security.app.ruleprocessor.ApiModeProcessor→net.bytedance.security.app.preprocess.CallSitenet.bytedance.security.app.ruleprocessor.ConstModeProcessor→net.bytedance.security.app.preprocess.CallSitenet.bytedance.security.app.ruleprocessor.TaintRuleSourceSinkCollector→net.bytedance.security.app.preprocess.CallSite
- Direction
- net.bytedance.security.app.ruleprocessor uses net.bytedance.security.app.preprocess, so a change to net.bytedance.security.app.preprocess can break net.bytedance.security.app.ruleprocessor, while a change to net.bytedance.security.app.ruleprocessor can't break net.bytedance.security.app.preprocess.
- Position
- Below the diagonal: net.bytedance.security.app.ruleprocessor uses a module listed above it, which is the healthy direction.
30→18 net.bytedance.security.app.ruleprocessor uses net.bytedance.security.app.rules✕
- Connections
- 15 pairs of types, where a type in net.bytedance.security.app.ruleprocessor uses a type in net.bytedance.security.app.rules.
- The types involved
net.bytedance.security.app.ruleprocessor.ApiModeProcessor→net.bytedance.security.app.rules.IRulenet.bytedance.security.app.ruleprocessor.ConstModeProcessor→net.bytedance.security.app.rules.ConstNumberModeRulenet.bytedance.security.app.ruleprocessor.ConstModeProcessor→net.bytedance.security.app.rules.ConstStringModeRulenet.bytedance.security.app.ruleprocessor.ConstModeProcessor→net.bytedance.security.app.rules.TaintFlowRulenet.bytedance.security.app.ruleprocessor.ConstNumberModeProcessor→net.bytedance.security.app.rules.ConstNumberModeRulenet.bytedance.security.app.ruleprocessor.ConstNumberModeProcessor→net.bytedance.security.app.rules.IRulenet.bytedance.security.app.ruleprocessor.ConstStringModeProcessor→net.bytedance.security.app.rules.ConstStringModeRulenet.bytedance.security.app.ruleprocessor.ConstStringModeProcessor→net.bytedance.security.app.rules.IRulenet.bytedance.security.app.ruleprocessor.DirectModeProcessor→net.bytedance.security.app.rules.DirectModeRulenet.bytedance.security.app.ruleprocessor.DirectModeProcessor→net.bytedance.security.app.rules.IRulenet.bytedance.security.app.ruleprocessor.IRuleProcessor→net.bytedance.security.app.rules.IRulenet.bytedance.security.app.ruleprocessor.SliceModeProcessor→net.bytedance.security.app.rules.DirectModeRulenet.bytedance.security.app.ruleprocessor.SliceModeProcessor→net.bytedance.security.app.rules.SliceModeRulenet.bytedance.security.app.ruleprocessor.TaintFlowRuleProcessor→net.bytedance.security.app.rules.IRulenet.bytedance.security.app.ruleprocessor.TaintRuleSourceSinkCollector→net.bytedance.security.app.rules.DirectModeRule
- Direction
- net.bytedance.security.app.ruleprocessor uses net.bytedance.security.app.rules, so a change to net.bytedance.security.app.rules can break net.bytedance.security.app.ruleprocessor, while a change to net.bytedance.security.app.ruleprocessor can't break net.bytedance.security.app.rules.
- Position
- Below the diagonal: net.bytedance.security.app.ruleprocessor uses a module listed above it, which is the healthy direction.
30→23 net.bytedance.security.app.ruleprocessor uses net.bytedance.security.app.taintflow✕
- Connections
- 7 pairs of types, where a type in net.bytedance.security.app.ruleprocessor uses a type in net.bytedance.security.app.taintflow.
- The types involved
net.bytedance.security.app.ruleprocessor.ConstModeProcessor→net.bytedance.security.app.taintflow.TaintAnalyzernet.bytedance.security.app.ruleprocessor.ConstNumberModeProcessor→net.bytedance.security.app.taintflow.TaintAnalyzernet.bytedance.security.app.ruleprocessor.ConstStringModeProcessor→net.bytedance.security.app.taintflow.TaintAnalyzernet.bytedance.security.app.ruleprocessor.DirectModeProcessor→net.bytedance.security.app.taintflow.TaintAnalyzernet.bytedance.security.app.ruleprocessor.SliceModeProcessor→net.bytedance.security.app.taintflow.TaintAnalyzernet.bytedance.security.app.ruleprocessor.TaintFlowRuleProcessor→net.bytedance.security.app.taintflow.TaintAnalyzernet.bytedance.security.app.ruleprocessor.TaintRuleSourceSinkCollector→net.bytedance.security.app.taintflow.TaintAnalyzerData
- Direction
- net.bytedance.security.app.ruleprocessor uses net.bytedance.security.app.taintflow, so a change to net.bytedance.security.app.taintflow can break net.bytedance.security.app.ruleprocessor, while a change to net.bytedance.security.app.ruleprocessor can't break net.bytedance.security.app.taintflow.
- Position
- Below the diagonal: net.bytedance.security.app.ruleprocessor uses a module listed above it, which is the healthy direction.
30→24 net.bytedance.security.app.ruleprocessor uses net.bytedance.security.app✕
- Connections
- 14 pairs of types, where a type in net.bytedance.security.app.ruleprocessor uses a type in net.bytedance.security.app.
- The types involved
net.bytedance.security.app.ruleprocessor.ApiModeProcessor→net.bytedance.security.app.PreAnalyzeContextnet.bytedance.security.app.ruleprocessor.ConstModeProcessor→net.bytedance.security.app.PreAnalyzeContextnet.bytedance.security.app.ruleprocessor.ConstModeProcessor→net.bytedance.security.app.SinkBodynet.bytedance.security.app.ruleprocessor.ConstNumberModeProcessor→net.bytedance.security.app.PreAnalyzeContextnet.bytedance.security.app.ruleprocessor.ConstStringModeProcessor→net.bytedance.security.app.PreAnalyzeContextnet.bytedance.security.app.ruleprocessor.DirectModeProcessor→net.bytedance.security.app.Entrynet.bytedance.security.app.ruleprocessor.DirectModeProcessor→net.bytedance.security.app.PreAnalyzeContextnet.bytedance.security.app.ruleprocessor.RuleProcessorFactory→net.bytedance.security.app.PreAnalyzeContextnet.bytedance.security.app.ruleprocessor.SliceModeProcessor→net.bytedance.security.app.PreAnalyzeContextnet.bytedance.security.app.ruleprocessor.TaintFlowRuleProcessor→net.bytedance.security.app.PreAnalyzeContextnet.bytedance.security.app.ruleprocessor.TaintRuleSourceSinkCollector→net.bytedance.security.app.PreAnalyzeContextnet.bytedance.security.app.ruleprocessor.TaintRuleSourceSinkCollector→net.bytedance.security.app.SinkBodynet.bytedance.security.app.ruleprocessor.TaintRuleSourceSinkCollector→net.bytedance.security.app.SourceBodynet.bytedance.security.app.ruleprocessor.TaintRuleSourceSinkCollector→net.bytedance.security.app.SourceReturn
- Direction
- net.bytedance.security.app.ruleprocessor uses net.bytedance.security.app, so a change to net.bytedance.security.app can break net.bytedance.security.app.ruleprocessor, while a change to net.bytedance.security.app.ruleprocessor can't break net.bytedance.security.app.
- Position
- Below the diagonal: net.bytedance.security.app.ruleprocessor uses a module listed above it, which is the healthy direction.
31→1 net.bytedance.security.app.sanitizer uses net.bytedance.security.app.pointer✕
- Connections
- 4 pairs of types, where a type in net.bytedance.security.app.sanitizer uses a type in net.bytedance.security.app.pointer.
- The types involved
net.bytedance.security.app.sanitizer.ConstStringCheckSanitizer→net.bytedance.security.app.pointer.PLLocalPointernet.bytedance.security.app.sanitizer.SanitizeContext→net.bytedance.security.app.pointer.PLPointernet.bytedance.security.app.sanitizer.TaintCheckSanitizer→net.bytedance.security.app.pointer.PLLocalPointernet.bytedance.security.app.sanitizer.TaintCheckSanitizerParser→net.bytedance.security.app.pointer.PLLocalPointer
- Direction
- net.bytedance.security.app.sanitizer uses net.bytedance.security.app.pointer, so a change to net.bytedance.security.app.pointer can break net.bytedance.security.app.sanitizer, while a change to net.bytedance.security.app.sanitizer can't break net.bytedance.security.app.pointer.
- Position
- Below the diagonal: net.bytedance.security.app.sanitizer uses a module listed above it, which is the healthy direction.
31→18 net.bytedance.security.app.sanitizer uses net.bytedance.security.app.rules✕
- Connections
- 3 pairs of types, where a type in net.bytedance.security.app.sanitizer uses a type in net.bytedance.security.app.rules.
- The types involved
net.bytedance.security.app.sanitizer.SanitizerFactory→net.bytedance.security.app.rules.TaintFlowRulenet.bytedance.security.app.sanitizer.TaintCheckSanitizer→net.bytedance.security.app.rules.TaintFlowRulenet.bytedance.security.app.sanitizer.TaintCheckSanitizerParser→net.bytedance.security.app.rules.TaintFlowRule
- Direction
- net.bytedance.security.app.sanitizer uses net.bytedance.security.app.rules, so a change to net.bytedance.security.app.rules can break net.bytedance.security.app.sanitizer, while a change to net.bytedance.security.app.sanitizer can't break net.bytedance.security.app.rules.
- Position
- Below the diagonal: net.bytedance.security.app.sanitizer uses a module listed above it, which is the healthy direction.
31→23 net.bytedance.security.app.sanitizer uses net.bytedance.security.app.taintflow✕
- Connections
- 1 pair of types, where a type in net.bytedance.security.app.sanitizer uses a type in net.bytedance.security.app.taintflow.
- The types involved
net.bytedance.security.app.sanitizer.SanitizeContext→net.bytedance.security.app.taintflow.AnalyzeContext
- Direction
- net.bytedance.security.app.sanitizer uses net.bytedance.security.app.taintflow, so a change to net.bytedance.security.app.taintflow can break net.bytedance.security.app.sanitizer, while a change to net.bytedance.security.app.sanitizer can't break net.bytedance.security.app.taintflow.
- Position
- Below the diagonal: net.bytedance.security.app.sanitizer uses a module listed above it, which is the healthy direction.
31→24 net.bytedance.security.app.sanitizer uses net.bytedance.security.app✕
- Connections
- 3 pairs of types, where a type in net.bytedance.security.app.sanitizer uses a type in net.bytedance.security.app.
- The types involved
net.bytedance.security.app.sanitizer.SanitizerFactory→net.bytedance.security.app.PreAnalyzeContextnet.bytedance.security.app.sanitizer.TaintCheckSanitizerParser→net.bytedance.security.app.PreAnalyzeContextnet.bytedance.security.app.sanitizer.TaintCheckSanitizerParser→net.bytedance.security.app.SinkBody
- Direction
- net.bytedance.security.app.sanitizer uses net.bytedance.security.app, so a change to net.bytedance.security.app can break net.bytedance.security.app.sanitizer, while a change to net.bytedance.security.app.sanitizer can't break net.bytedance.security.app.
- Position
- Below the diagonal: net.bytedance.security.app.sanitizer uses a module listed above it, which is the healthy direction.
32→1 net.bytedance.security.app.taintflow.PruneMethodAnalyzeMode uses net.bytedance.security.app.pointer✕
- Connections
- 1 pair of types, where a type in net.bytedance.security.app.taintflow.PruneMethodAnalyzeMode uses a type in net.bytedance.security.app.pointer.
- The types involved
net.bytedance.security.app.taintflow.PruneMethodAnalyzeMode.Companion→net.bytedance.security.app.pointer.PLLocalPointer
- Direction
- net.bytedance.security.app.taintflow.PruneMethodAnalyzeMode uses net.bytedance.security.app.pointer, so a change to net.bytedance.security.app.pointer can break net.bytedance.security.app.taintflow.PruneMethodAnalyzeMode, while a change to net.bytedance.security.app.taintflow.PruneMethodAnalyzeMode can't break net.bytedance.security.app.pointer.
- Position
- Below the diagonal: net.bytedance.security.app.taintflow.PruneMethodAnalyzeMode uses a module listed above it, which is the healthy direction.
32→23 net.bytedance.security.app.taintflow.PruneMethodAnalyzeMode uses net.bytedance.security.app.taintflow✕
- Connections
- 2 pairs of types, where a type in net.bytedance.security.app.taintflow.PruneMethodAnalyzeMode uses a type in net.bytedance.security.app.taintflow.
- The types involved
net.bytedance.security.app.taintflow.PruneMethodAnalyzeMode.Companion→net.bytedance.security.app.taintflow.PruneMethodAnalyzeModenet.bytedance.security.app.taintflow.PruneMethodAnalyzeMode.Companion→net.bytedance.security.app.taintflow.TaintAnalyzer
- Direction
- net.bytedance.security.app.taintflow.PruneMethodAnalyzeMode uses net.bytedance.security.app.taintflow, so a change to net.bytedance.security.app.taintflow can break net.bytedance.security.app.taintflow.PruneMethodAnalyzeMode, while a change to net.bytedance.security.app.taintflow.PruneMethodAnalyzeMode can't break net.bytedance.security.app.taintflow.
- Position
- Below the diagonal: net.bytedance.security.app.taintflow.PruneMethodAnalyzeMode uses a module listed above it, which is the healthy direction.
32→24 net.bytedance.security.app.taintflow.PruneMethodAnalyzeMode uses net.bytedance.security.app✕
- Connections
- 1 pair of types, where a type in net.bytedance.security.app.taintflow.PruneMethodAnalyzeMode uses a type in net.bytedance.security.app.
- The types involved
net.bytedance.security.app.taintflow.PruneMethodAnalyzeMode.Companion→net.bytedance.security.app.PreAnalyzeContext
- Direction
- net.bytedance.security.app.taintflow.PruneMethodAnalyzeMode uses net.bytedance.security.app, so a change to net.bytedance.security.app can break net.bytedance.security.app.taintflow.PruneMethodAnalyzeMode, while a change to net.bytedance.security.app.taintflow.PruneMethodAnalyzeMode can't break net.bytedance.security.app.
- Position
- Below the diagonal: net.bytedance.security.app.taintflow.PruneMethodAnalyzeMode uses a module listed above it, which is the healthy direction.
33→1 net.bytedance.security.app.pathfinder.TaintFlowEdgeFinder uses net.bytedance.security.app.pointer✕
- Connections
- 3 pairs of types, where a type in net.bytedance.security.app.pathfinder.TaintFlowEdgeFinder uses a type in net.bytedance.security.app.pointer.
- The types involved
net.bytedance.security.app.pathfinder.TaintFlowEdgeFinder.Companion→net.bytedance.security.app.pointer.PLLocalPointernet.bytedance.security.app.pathfinder.TaintFlowEdgeFinder.Companion→net.bytedance.security.app.pointer.PLPointernet.bytedance.security.app.pathfinder.TaintFlowEdgeFinder.Companion→net.bytedance.security.app.pointer.PLPtrObjectField
- Direction
- net.bytedance.security.app.pathfinder.TaintFlowEdgeFinder uses net.bytedance.security.app.pointer, so a change to net.bytedance.security.app.pointer can break net.bytedance.security.app.pathfinder.TaintFlowEdgeFinder, while a change to net.bytedance.security.app.pathfinder.TaintFlowEdgeFinder can't break net.bytedance.security.app.pointer.
- Position
- Below the diagonal: net.bytedance.security.app.pathfinder.TaintFlowEdgeFinder uses a module listed above it, which is the healthy direction.
33→29 net.bytedance.security.app.pathfinder.TaintFlowEdgeFinder uses net.bytedance.security.app.pathfinder✕
- Connections
- 1 pair of types, where a type in net.bytedance.security.app.pathfinder.TaintFlowEdgeFinder uses a type in net.bytedance.security.app.pathfinder.
- The types involved
net.bytedance.security.app.pathfinder.TaintFlowEdgeFinder.Companion→net.bytedance.security.app.pathfinder.TaintEdge
- Direction
- net.bytedance.security.app.pathfinder.TaintFlowEdgeFinder uses net.bytedance.security.app.pathfinder, so a change to net.bytedance.security.app.pathfinder can break net.bytedance.security.app.pathfinder.TaintFlowEdgeFinder, while a change to net.bytedance.security.app.pathfinder.TaintFlowEdgeFinder can't break net.bytedance.security.app.pathfinder.
- Position
- Below the diagonal: net.bytedance.security.app.pathfinder.TaintFlowEdgeFinder uses a module listed above it, which is the healthy direction.
34→18 net.bytedance.security.app.result.model uses net.bytedance.security.app.rules✕
- Connections
- 1 pair of types, where a type in net.bytedance.security.app.result.model uses a type in net.bytedance.security.app.rules.
- The types involved
net.bytedance.security.app.result.model.SecurityVulnerabilityItem→net.bytedance.security.app.rules.IRule
- Direction
- net.bytedance.security.app.result.model uses net.bytedance.security.app.rules, so a change to net.bytedance.security.app.rules can break net.bytedance.security.app.result.model, while a change to net.bytedance.security.app.result.model can't break net.bytedance.security.app.rules.
- Position
- Below the diagonal: net.bytedance.security.app.result.model uses a module listed above it, which is the healthy direction.
34→28 net.bytedance.security.app.result.model uses net.bytedance.security.app.android✕
- Connections
- 1 pair of types, where a type in net.bytedance.security.app.result.model uses a type in net.bytedance.security.app.android.
- The types involved
net.bytedance.security.app.result.model.BasicInfo→net.bytedance.security.app.android.ComponentDescription
- Direction
- net.bytedance.security.app.result.model uses net.bytedance.security.app.android, so a change to net.bytedance.security.app.android can break net.bytedance.security.app.result.model, while a change to net.bytedance.security.app.result.model can't break net.bytedance.security.app.android.
- Position
- Below the diagonal: net.bytedance.security.app.result.model uses a module listed above it, which is the healthy direction.
35→1 net.bytedance.security.app.ui.TaintPathModeHtmlWriter uses net.bytedance.security.app.pointer✕
- Connections
- 1 pair of types, where a type in net.bytedance.security.app.ui.TaintPathModeHtmlWriter uses a type in net.bytedance.security.app.pointer.
- The types involved
net.bytedance.security.app.ui.TaintPathModeHtmlWriter.Companion→net.bytedance.security.app.pointer.PLPointer
- Direction
- net.bytedance.security.app.ui.TaintPathModeHtmlWriter uses net.bytedance.security.app.pointer, so a change to net.bytedance.security.app.pointer can break net.bytedance.security.app.ui.TaintPathModeHtmlWriter, while a change to net.bytedance.security.app.ui.TaintPathModeHtmlWriter can't break net.bytedance.security.app.pointer.
- Position
- Below the diagonal: net.bytedance.security.app.ui.TaintPathModeHtmlWriter uses a module listed above it, which is the healthy direction.
35→2 net.bytedance.security.app.ui.TaintPathModeHtmlWriter uses net.bytedance.security.app.ui.TaintPathModeHtmlWriter.Companion✕
- Connections
- 1 pair of types, where a type in net.bytedance.security.app.ui.TaintPathModeHtmlWriter uses a type in net.bytedance.security.app.ui.TaintPathModeHtmlWriter.Companion.
- The types involved
net.bytedance.security.app.ui.TaintPathModeHtmlWriter.Companion→net.bytedance.security.app.ui.TaintPathModeHtmlWriter.Companion.Range
- Direction
- net.bytedance.security.app.ui.TaintPathModeHtmlWriter uses net.bytedance.security.app.ui.TaintPathModeHtmlWriter.Companion, so a change to net.bytedance.security.app.ui.TaintPathModeHtmlWriter.Companion can break net.bytedance.security.app.ui.TaintPathModeHtmlWriter, while a change to net.bytedance.security.app.ui.TaintPathModeHtmlWriter can't break net.bytedance.security.app.ui.TaintPathModeHtmlWriter.Companion.
- Position
- Below the diagonal: net.bytedance.security.app.ui.TaintPathModeHtmlWriter uses a module listed above it, which is the healthy direction.
35→29 net.bytedance.security.app.ui.TaintPathModeHtmlWriter uses net.bytedance.security.app.pathfinder✕
- Connections
- 1 pair of types, where a type in net.bytedance.security.app.ui.TaintPathModeHtmlWriter uses a type in net.bytedance.security.app.pathfinder.
- The types involved
net.bytedance.security.app.ui.TaintPathModeHtmlWriter.Companion→net.bytedance.security.app.pathfinder.TaintEdge
- Direction
- net.bytedance.security.app.ui.TaintPathModeHtmlWriter uses net.bytedance.security.app.pathfinder, so a change to net.bytedance.security.app.pathfinder can break net.bytedance.security.app.ui.TaintPathModeHtmlWriter, while a change to net.bytedance.security.app.ui.TaintPathModeHtmlWriter can't break net.bytedance.security.app.pathfinder.
- Position
- Below the diagonal: net.bytedance.security.app.ui.TaintPathModeHtmlWriter uses a module listed above it, which is the healthy direction.
36→18 net.bytedance.security.app.result uses net.bytedance.security.app.rules✕
- Connections
- 1 pair of types, where a type in net.bytedance.security.app.result uses a type in net.bytedance.security.app.rules.
- The types involved
net.bytedance.security.app.result.VulnerabilityItem→net.bytedance.security.app.rules.IRule
- Direction
- net.bytedance.security.app.result uses net.bytedance.security.app.rules, so a change to net.bytedance.security.app.rules can break net.bytedance.security.app.result, while a change to net.bytedance.security.app.result can't break net.bytedance.security.app.rules.
- Position
- Below the diagonal: net.bytedance.security.app.result uses a module listed above it, which is the healthy direction.
36→24 net.bytedance.security.app.result uses net.bytedance.security.app✕
- Connections
- 2 pairs of types, where a type in net.bytedance.security.app.result uses a type in net.bytedance.security.app.
- The types involved
net.bytedance.security.app.result.OutputSecResults→net.bytedance.security.app.PreAnalyzeContextnet.bytedance.security.app.result.TraceTask→net.bytedance.security.app.PreAnalyzeContext
- Direction
- net.bytedance.security.app.result uses net.bytedance.security.app, so a change to net.bytedance.security.app can break net.bytedance.security.app.result, while a change to net.bytedance.security.app.result can't break net.bytedance.security.app.
- Position
- Below the diagonal: net.bytedance.security.app.result uses a module listed above it, which is the healthy direction.
36→28 net.bytedance.security.app.result uses net.bytedance.security.app.android✕
- Connections
- 1 pair of types, where a type in net.bytedance.security.app.result uses a type in net.bytedance.security.app.android.
- The types involved
net.bytedance.security.app.result.TraceTask→net.bytedance.security.app.android.ComponentDescription
- Direction
- net.bytedance.security.app.result uses net.bytedance.security.app.android, so a change to net.bytedance.security.app.android can break net.bytedance.security.app.result, while a change to net.bytedance.security.app.result can't break net.bytedance.security.app.android.
- Position
- Below the diagonal: net.bytedance.security.app.result uses a module listed above it, which is the healthy direction.
36→34 net.bytedance.security.app.result uses net.bytedance.security.app.result.model✕
- Connections
- 13 pairs of types, where a type in net.bytedance.security.app.result uses a type in net.bytedance.security.app.result.model.
- The types involved
net.bytedance.security.app.result.OutputSecResults→net.bytedance.security.app.result.model.AppInfonet.bytedance.security.app.result.OutputSecResults→net.bytedance.security.app.result.model.BasicInfonet.bytedance.security.app.result.OutputSecResults→net.bytedance.security.app.result.model.HttpAPInet.bytedance.security.app.result.OutputSecResults→net.bytedance.security.app.result.model.JsBridgeAPInet.bytedance.security.app.result.OutputSecResults→net.bytedance.security.app.result.model.ManifestRisknet.bytedance.security.app.result.OutputSecResults→net.bytedance.security.app.result.model.SecurityVulnerabilityItemnet.bytedance.security.app.result.Results→net.bytedance.security.app.result.model.AppInfonet.bytedance.security.app.result.Results→net.bytedance.security.app.result.model.BasicInfonet.bytedance.security.app.result.Results→net.bytedance.security.app.result.model.HttpAPInet.bytedance.security.app.result.Results→net.bytedance.security.app.result.model.JsBridgeAPInet.bytedance.security.app.result.Results→net.bytedance.security.app.result.model.ManifestRisknet.bytedance.security.app.result.Results→net.bytedance.security.app.result.model.SecurityRiskItemnet.bytedance.security.app.result.VulnerabilityItem→net.bytedance.security.app.result.model.SecurityVulnerabilityItem
- Direction
- net.bytedance.security.app.result uses net.bytedance.security.app.result.model, so a change to net.bytedance.security.app.result.model can break net.bytedance.security.app.result, while a change to net.bytedance.security.app.result can't break net.bytedance.security.app.result.model.
- Position
- Below the diagonal: net.bytedance.security.app.result uses a module listed above it, which is the healthy direction.
37→18 net.bytedance.security.app.result.VulnerabilityItem uses net.bytedance.security.app.rules✕
- Connections
- 1 pair of types, where a type in net.bytedance.security.app.result.VulnerabilityItem uses a type in net.bytedance.security.app.rules.
- The types involved
net.bytedance.security.app.result.VulnerabilityItem.Companion→net.bytedance.security.app.rules.IRule
- Direction
- net.bytedance.security.app.result.VulnerabilityItem uses net.bytedance.security.app.rules, so a change to net.bytedance.security.app.rules can break net.bytedance.security.app.result.VulnerabilityItem, while a change to net.bytedance.security.app.result.VulnerabilityItem can't break net.bytedance.security.app.rules.
- Position
- Below the diagonal: net.bytedance.security.app.result.VulnerabilityItem uses a module listed above it, which is the healthy direction.
37→34 net.bytedance.security.app.result.VulnerabilityItem uses net.bytedance.security.app.result.model✕
- Connections
- 1 pair of types, where a type in net.bytedance.security.app.result.VulnerabilityItem uses a type in net.bytedance.security.app.result.model.
- The types involved
net.bytedance.security.app.result.VulnerabilityItem.Companion→net.bytedance.security.app.result.model.SecurityVulnerabilityItem
- Direction
- net.bytedance.security.app.result.VulnerabilityItem uses net.bytedance.security.app.result.model, so a change to net.bytedance.security.app.result.model can break net.bytedance.security.app.result.VulnerabilityItem, while a change to net.bytedance.security.app.result.VulnerabilityItem can't break net.bytedance.security.app.result.model.
- Position
- Below the diagonal: net.bytedance.security.app.result.VulnerabilityItem uses a module listed above it, which is the healthy direction.
38→1 net.bytedance.security.app.ui uses net.bytedance.security.app.pointer✕
- Connections
- 1 pair of types, where a type in net.bytedance.security.app.ui uses a type in net.bytedance.security.app.pointer.
- The types involved
net.bytedance.security.app.ui.TaintPathModeHtmlWriter→net.bytedance.security.app.pointer.PLPointer
- Direction
- net.bytedance.security.app.ui uses net.bytedance.security.app.pointer, so a change to net.bytedance.security.app.pointer can break net.bytedance.security.app.ui, while a change to net.bytedance.security.app.ui can't break net.bytedance.security.app.pointer.
- Position
- Below the diagonal: net.bytedance.security.app.ui uses a module listed above it, which is the healthy direction.
38→17 net.bytedance.security.app.ui uses net.bytedance.security.app.preprocess✕
- Connections
- 1 pair of types, where a type in net.bytedance.security.app.ui uses a type in net.bytedance.security.app.preprocess.
- The types involved
net.bytedance.security.app.ui.FindClassModeHtmlWriter→net.bytedance.security.app.preprocess.CallSite
- Direction
- net.bytedance.security.app.ui uses net.bytedance.security.app.preprocess, so a change to net.bytedance.security.app.preprocess can break net.bytedance.security.app.ui, while a change to net.bytedance.security.app.ui can't break net.bytedance.security.app.preprocess.
- Position
- Below the diagonal: net.bytedance.security.app.ui uses a module listed above it, which is the healthy direction.
38→18 net.bytedance.security.app.ui uses net.bytedance.security.app.rules✕
- Connections
- 4 pairs of types, where a type in net.bytedance.security.app.ui uses a type in net.bytedance.security.app.rules.
- The types involved
net.bytedance.security.app.ui.APIModeHtmlWriter→net.bytedance.security.app.rules.IRulenet.bytedance.security.app.ui.ConstExtractModeHtmlWriter→net.bytedance.security.app.rules.IRulenet.bytedance.security.app.ui.FindClassModeHtmlWriter→net.bytedance.security.app.rules.IRulenet.bytedance.security.app.ui.TaintPathModeHtmlWriter→net.bytedance.security.app.rules.TaintFlowRule
- Direction
- net.bytedance.security.app.ui uses net.bytedance.security.app.rules, so a change to net.bytedance.security.app.rules can break net.bytedance.security.app.ui, while a change to net.bytedance.security.app.ui can't break net.bytedance.security.app.rules.
- Position
- Below the diagonal: net.bytedance.security.app.ui uses a module listed above it, which is the healthy direction.
38→23 net.bytedance.security.app.ui uses net.bytedance.security.app.taintflow✕
- Connections
- 1 pair of types, where a type in net.bytedance.security.app.ui uses a type in net.bytedance.security.app.taintflow.
- The types involved
net.bytedance.security.app.ui.TaintPathModeHtmlWriter→net.bytedance.security.app.taintflow.TaintAnalyzer
- Direction
- net.bytedance.security.app.ui uses net.bytedance.security.app.taintflow, so a change to net.bytedance.security.app.taintflow can break net.bytedance.security.app.ui, while a change to net.bytedance.security.app.ui can't break net.bytedance.security.app.taintflow.
- Position
- Below the diagonal: net.bytedance.security.app.ui uses a module listed above it, which is the healthy direction.
38→24 net.bytedance.security.app.ui uses net.bytedance.security.app✕
- Connections
- 1 pair of types, where a type in net.bytedance.security.app.ui uses a type in net.bytedance.security.app.
- The types involved
net.bytedance.security.app.ui.HtmlWriter→net.bytedance.security.app.RuleDescription
- Direction
- net.bytedance.security.app.ui uses net.bytedance.security.app, so a change to net.bytedance.security.app can break net.bytedance.security.app.ui, while a change to net.bytedance.security.app.ui can't break net.bytedance.security.app.
- Position
- Below the diagonal: net.bytedance.security.app.ui uses a module listed above it, which is the healthy direction.
38→28 net.bytedance.security.app.ui uses net.bytedance.security.app.android✕
- Connections
- 1 pair of types, where a type in net.bytedance.security.app.ui uses a type in net.bytedance.security.app.android.
- The types involved
net.bytedance.security.app.ui.TaintPathModeVulnerability→net.bytedance.security.app.android.ComponentDescription
- Direction
- net.bytedance.security.app.ui uses net.bytedance.security.app.android, so a change to net.bytedance.security.app.android can break net.bytedance.security.app.ui, while a change to net.bytedance.security.app.ui can't break net.bytedance.security.app.android.
- Position
- Below the diagonal: net.bytedance.security.app.ui uses a module listed above it, which is the healthy direction.
38→29 net.bytedance.security.app.ui uses net.bytedance.security.app.pathfinder✕
- Connections
- 1 pair of types, where a type in net.bytedance.security.app.ui uses a type in net.bytedance.security.app.pathfinder.
- The types involved
net.bytedance.security.app.ui.TaintPathModeHtmlWriter→net.bytedance.security.app.pathfinder.PathResult
- Direction
- net.bytedance.security.app.ui uses net.bytedance.security.app.pathfinder, so a change to net.bytedance.security.app.pathfinder can break net.bytedance.security.app.ui, while a change to net.bytedance.security.app.ui can't break net.bytedance.security.app.pathfinder.
- Position
- Below the diagonal: net.bytedance.security.app.ui uses a module listed above it, which is the healthy direction.
38→36 net.bytedance.security.app.ui uses net.bytedance.security.app.result✕
- Connections
- 8 pairs of types, where a type in net.bytedance.security.app.ui uses a type in net.bytedance.security.app.result.
- The types involved
net.bytedance.security.app.ui.APIModeHtmlWriter→net.bytedance.security.app.result.OutputSecResultsnet.bytedance.security.app.ui.ApiModeVulnerability→net.bytedance.security.app.result.IVulnerabilitynet.bytedance.security.app.ui.ConstExtractModeHtmlWriter→net.bytedance.security.app.result.OutputSecResultsnet.bytedance.security.app.ui.ConstExtractModeVulnerability→net.bytedance.security.app.result.IVulnerabilitynet.bytedance.security.app.ui.FindClassModeHtmlWriter→net.bytedance.security.app.result.OutputSecResultsnet.bytedance.security.app.ui.FindClassModeVulnerability→net.bytedance.security.app.result.IVulnerabilitynet.bytedance.security.app.ui.TaintPathModeHtmlWriter→net.bytedance.security.app.result.OutputSecResultsnet.bytedance.security.app.ui.TaintPathModeVulnerability→net.bytedance.security.app.result.IVulnerability
- Direction
- net.bytedance.security.app.ui uses net.bytedance.security.app.result, so a change to net.bytedance.security.app.result can break net.bytedance.security.app.ui, while a change to net.bytedance.security.app.ui can't break net.bytedance.security.app.result.
- Position
- Below the diagonal: net.bytedance.security.app.ui uses a module listed above it, which is the healthy direction.
39→3 net.bytedance.security.app.util uses net.bytedance.security.app.util.Profiler✕
- Connections
- 2 pairs of types, where a type in net.bytedance.security.app.util uses a type in net.bytedance.security.app.util.Profiler.
- The types involved
net.bytedance.security.app.util.Profiler→net.bytedance.security.app.util.Profiler.AnalyzeContextDatanet.bytedance.security.app.util.Profiler→net.bytedance.security.app.util.Profiler.TaintAnalyzerItem
- Direction
- net.bytedance.security.app.util uses net.bytedance.security.app.util.Profiler, so a change to net.bytedance.security.app.util.Profiler can break net.bytedance.security.app.util, while a change to net.bytedance.security.app.util can't break net.bytedance.security.app.util.Profiler.
- Position
- Below the diagonal: net.bytedance.security.app.util uses a module listed above it, which is the healthy direction.
39→14 net.bytedance.security.app.util uses at.syntaxerror.json5✕
- Connections
- 1 pair of types, where a type in net.bytedance.security.app.util uses a type in at.syntaxerror.json5.
- The types involved
net.bytedance.security.app.util.Json→at.syntaxerror.json5.Json5Module
- Direction
- net.bytedance.security.app.util uses at.syntaxerror.json5, so a change to at.syntaxerror.json5 can break net.bytedance.security.app.util, while a change to net.bytedance.security.app.util can't break at.syntaxerror.json5.
- Position
- Below the diagonal: net.bytedance.security.app.util uses a module listed above it, which is the healthy direction.
39→23 net.bytedance.security.app.util uses net.bytedance.security.app.taintflow✕
- Connections
- 2 pairs of types, where a type in net.bytedance.security.app.util uses a type in net.bytedance.security.app.taintflow.
- The types involved
net.bytedance.security.app.util.Profiler→net.bytedance.security.app.taintflow.AnalyzeContextnet.bytedance.security.app.util.Profiler→net.bytedance.security.app.taintflow.TaintAnalyzer
- Direction
- net.bytedance.security.app.util uses net.bytedance.security.app.taintflow, so a change to net.bytedance.security.app.taintflow can break net.bytedance.security.app.util, while a change to net.bytedance.security.app.util can't break net.bytedance.security.app.taintflow.
- Position
- Below the diagonal: net.bytedance.security.app.util uses a module listed above it, which is the healthy direction.
39→24 net.bytedance.security.app.util uses net.bytedance.security.app✕
- Connections
- 1 pair of types, where a type in net.bytedance.security.app.util uses a type in net.bytedance.security.app.
- The types involved
net.bytedance.security.app.util.Profiler→net.bytedance.security.app.PreAnalyzeContext
- Direction
- net.bytedance.security.app.util uses net.bytedance.security.app, so a change to net.bytedance.security.app can break net.bytedance.security.app.util, while a change to net.bytedance.security.app.util can't break net.bytedance.security.app.
- Position
- Below the diagonal: net.bytedance.security.app.util uses a module listed above it, which is the healthy direction.
39→34 net.bytedance.security.app.util uses net.bytedance.security.app.result.model✕
- Connections
- 1 pair of types, where a type in net.bytedance.security.app.util uses a type in net.bytedance.security.app.result.model.
- The types involved
net.bytedance.security.app.util.Profiler→net.bytedance.security.app.result.model.AppInfo
- Direction
- net.bytedance.security.app.util uses net.bytedance.security.app.result.model, so a change to net.bytedance.security.app.result.model can break net.bytedance.security.app.util, while a change to net.bytedance.security.app.util can't break net.bytedance.security.app.result.model.
- Position
- Below the diagonal: net.bytedance.security.app.util uses a module listed above it, which is the healthy direction.
39→36 net.bytedance.security.app.util uses net.bytedance.security.app.result✕
- Connections
- 1 pair of types, where a type in net.bytedance.security.app.util uses a type in net.bytedance.security.app.result.
- The types involved
net.bytedance.security.app.util.Profiler→net.bytedance.security.app.result.Results
- Direction
- net.bytedance.security.app.util uses net.bytedance.security.app.result, so a change to net.bytedance.security.app.result can break net.bytedance.security.app.util, while a change to net.bytedance.security.app.util can't break net.bytedance.security.app.result.
- Position
- Below the diagonal: net.bytedance.security.app.util uses a module listed above it, which is the healthy direction.
40→39 net.bytedance.security.app.util.MethodSignatureParseState uses net.bytedance.security.app.util✕
- Connections
- 4 pairs of types, where a type in net.bytedance.security.app.util.MethodSignatureParseState uses a type in net.bytedance.security.app.util.
- The types involved
net.bytedance.security.app.util.MethodSignatureParseState.Argument→net.bytedance.security.app.util.MethodSignatureParseStatenet.bytedance.security.app.util.MethodSignatureParseState.Class→net.bytedance.security.app.util.MethodSignatureParseStatenet.bytedance.security.app.util.MethodSignatureParseState.FunctionName→net.bytedance.security.app.util.MethodSignatureParseStatenet.bytedance.security.app.util.MethodSignatureParseState.ReturnType→net.bytedance.security.app.util.MethodSignatureParseState
- Direction
- net.bytedance.security.app.util.MethodSignatureParseState uses net.bytedance.security.app.util, so a change to net.bytedance.security.app.util can break net.bytedance.security.app.util.MethodSignatureParseState, while a change to net.bytedance.security.app.util.MethodSignatureParseState can't break net.bytedance.security.app.util.
- Position
- Below the diagonal: net.bytedance.security.app.util.MethodSignatureParseState 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 | 4 | High / Critical |
Roadmap
Top priorities: 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; Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing; Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle.kts.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle.kts. | +4.9 pts | Low | ADR Quality |
| 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. | +9.6 pts | Medium | Observability |
| Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +9.6 pts | Medium | Security & performance tooling |
| 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. | +4.2 pts | Medium | Architecture documentation |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +3.9 pts | Medium | Release Hygiene |
| Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite. | +2.1 pts | Medium | Documentation (README) |
| Kotlin: call the suspend function directly instead of wrapping it in runBlocking, use delay() instead of Thread.sleep, and move unavoidable blocking I/O into withContext(Dispatchers.IO). | +1.0 pts | Medium | Async & latency hygiene |
| Run the test suite in CI via an explicit runner step (`gradle test` for the toolchain this pipeline already uses) and gate merges on it. | +1.0 pts | Medium | CI/CD gates |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| src/main/kotlin/net/bytedance/security/app/ui/TaintPathModeHtmlWriter.kt | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/main/kotlin/net/bytedance/security/app/pathfinder/TaintPathFinder.kt | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/main/kotlin/net/bytedance/security/app/taintflow/StmtTransfer.kt | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/main/kotlin/net/bytedance/security/app/preprocess/Reflection.kt | 7.0 | Near-clean | Cognitive Complexity: Reflection.calcGetMethod (cognitive 35) |
| src/main/kotlin/net/bytedance/security/app/taintflow/TwoStagePointerAnalyze.kt | 7.0 | Near-clean | Cyclomatic Complexity: TwoStagePointerAnalyze.analyzeStmtInterProcedure (cyclomatic 30) |
| src/main/kotlin/net/bytedance/security/app/pathfinder/TaintFlowEdgeFinder.kt | 7.1 | Near-clean | Cognitive Complexity: TaintFlowEdgeFinder.localToParam (cognitive 22) |
| src/main/kotlin/net/bytedance/security/app/PLUtils.kt | 7.1 | Near-clean | Cyclomatic Complexity: PLUtils.entryMethod (cyclomatic 17) |
| src/main/kotlin/net/bytedance/security/app/ruleprocessor/TaintRuleSourceSinkCollector.kt | 7.2 | Near-clean | Cyclomatic Complexity: TaintRuleSourceSinkCollector.calcSinkPointers (cyclomatic 19) |
| src/main/kotlin/net/bytedance/security/app/taintflow/ObscureRuleHandler.kt | 7.2 | Near-clean | Cyclomatic Complexity: ObscureRuleHandler.addEdgeByRule (cyclomatic 19) |
| src/main/kotlin/net/bytedance/security/app/preprocess/MethodFieldConstCacheVisitor.kt | 7.2 | Near-clean | Cyclomatic Complexity: MethodFieldConstCacheVisitor.visitEachStmt (cyclomatic 16) |
| src/main/kotlin/net/bytedance/security/app/android/AndroidUtils.kt | 7.4 | Near-clean | Cognitive Complexity: AndroidUtils.loadDynamicRegisterReceiver (cognitive 60) |
| src/main/kotlin/net/bytedance/security/app/ruleprocessor/ConstModeProcessor.kt | 7.4 | Near-clean | Cognitive Complexity: ConstModeProcessor.calcAllConstPointers (cognitive 33) |
| src/main/kotlin/net/bytedance/security/app/preprocess/MethodPatch.kt | 7.8 | Near-clean | Cyclomatic Complexity: MethodPatch.calcCallbackPatchUnits (cyclomatic 24) |
| src/main/kotlin/net/bytedance/security/app/MethodFinder.kt | 7.8 | Near-clean | Cyclomatic Complexity: MethodFinder.checkAndParseMethodSigInternal (cyclomatic 17) |
| src/main/kotlin/net/bytedance/security/app/rules/DirectModeRule.kt | 7.8 | Near-clean | Cognitive Complexity: DirectModeRule.constStringPatterns (cognitive 62) |
| src/main/kotlin/net/bytedance/security/app/Fragment.kt | 7.8 | Near-clean | Cognitive Complexity: Fragment.findOneStepFragment (cognitive 23) |
| src/main/kotlin/net/bytedance/security/app/engineconfig/PointerPropagationConfig.kt | 7.8 | Near-clean | Code Duplication: Edited copy of a member (21 corresponding lines) |
| src/main/kotlin/net/bytedance/security/app/preprocess/CallGraph.kt | 7.8 | Near-clean | Code Duplication: Edited copy of a member (20 corresponding lines) |
| src/main/kotlin/net/bytedance/security/app/ruleprocessor/DirectModeProcessor.kt | 8.5 | Near-clean | Cognitive Complexity: DirectModeProcessor.parseDirectEntry (cognitive 28) |
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 40 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 40 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, 100 of 104 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.kt, .java) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.kt, .java) and this repository declares a JVM test suite (repository root, Gradle), but it was not re-run: the analyzer environment could not run it. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — a Gradle build resolved 101 artifact(s) across its subprojects (69 behind a shipped release, reported), but the currency signal was not established over the whole graph, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- 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 (8 contributor(s) across 148 commit(s) sampled, automation and bot accounts excluded). One of them holds 84% of the history; the other 7 hold 2.3% 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D26 Project Cohesion — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `(repository root)` (15471 LoC, 268 module-visible types across 18 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
- 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. `src/main/kotlin/at/syntaxerror/json5/JSONParser.kt` 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.
- AXB1 Runtime evidence locked — no reproducible boot — 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. Subject: 2 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
- 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.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java source only, and this repository's Kotlin is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby, Scala and Rust source only, and this repository's Kotlin is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- P1 CI/CD gates — 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. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — 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 web-security 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 web-security controls.
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.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- 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.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
9 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was TwoStagePointerAnalyze.analyzeStmtInterProcedure at 30.
What to do
- Bring the 9 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with TwoStagePointerAnalyze.analyzeStmtInterProcedure (cyclomatic 30), TaintPathModeHtmlWriter.genCodeDetail (cyclomatic 25), MethodPatch.calcCallbackPatchUnits (cyclomatic 24). — 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 9 together lifts Cyclomatic Complexity from 8.6 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
41 method(s) exceeded the cognitive complexity threshold of 15; the worst was TaintPathModeHtmlWriter.genCodeDetail at 82.
What to do
- Bring the 2 bodies over 60 down to 60 or less in Cognitive Complexity — start with TaintPathModeHtmlWriter.genCodeDetail (cognitive 82), DirectModeRule.constStringPatterns (cognitive 62). — 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 Cognitive Complexity from 3.5 to about 4.3/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
D3 · God Classes
2 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 1 MethodTooLong finding(s) in God Classes — start with TwoStagePointerAnalyze.kt. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 FileTooLong finding(s) in God Classes — start with TwoStagePointerAnalyze.kt. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
15 duplicated block group(s) detected. 4.7 % of the production lines (770 of 16,371) are in a reported copy. A further 15 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 3 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with PLUtils.kt, ObscureRuleHandler.kt, ConstNumberModeProcessor.kt. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Edited copy of a member (12 corresponding lines) finding(s) in Code Duplication — start with PLUtils.kt, Reflection.kt. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Edited copy of a member (9 corresponding lines) finding(s) in Code Duplication — start with ObscureRuleHandler.kt, DefaultPointerPropagationRule.kt. — One of this dimension's main actionable groups (2 warning-level).
D6 · Cohesion (LCOM4)
3 of 40 classes have LCOM4 above 3.
What to do
- Resolve the 3 Low cohesion finding(s) in Cohesion (LCOM4) — start with Profiler.kt, MethodStmtFieldCache.kt, PreAnalyzeContext.kt. — One of this dimension's main actionable groups (3 warning-level).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 6 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 1 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. A further 1 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window. Repeated repair below the complexity floor: src/main/kotlin/net/bytedance/security/app/AnalyzeStepByStep.kt (3 of 5 changes were fixes)
What to do
- Resolve the 1 Repeated repair finding(s) in Churn × Complexity Hotspots — start with AnalyzeStepByStep.kt. — One of this dimension's main actionable groups (1 warning-level).
D17 · Explicit Debt
3 deducted task-comment markers across 16371 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 3 TodoComment finding(s) in Explicit Debt — start with TaintPathModeHtmlWriter.kt, StmtTransfer.kt, TaintPathFinder.kt. — One of this dimension's main actionable groups (3 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 20 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle.kts. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
40 % of calls cross a namespace and 4 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
4 finding(s): 0 critical, 2 high, 2 medium, 0 low. 2 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `gradlew` (line 177) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
- No action in Static Analysis (SAST) — all 2 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (2 issue-level, 0 of them charged here).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 64 of the 125 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 8 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
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
What to do
- Run the test suite in CI via an explicit runner step (`gradle test` for the toolchain this pipeline already uses) and gate merges on it.
P2 · Observability
- No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
What to do
- Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 1 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:13
- `build.gradle.kts` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — build.gradle.kts:31
What to do
- Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF3 · Async & latency hygiene
- `runInMilliSeconds` is async and calls runBlocking — a blocking call inside async code stalls the coroutine's thread, and every coroutine dispatched to it for as long as it runs. — src/main/kotlin/net/bytedance/security/app/util/TaskQueue.kt:87
What to do
- Kotlin: call the suspend function directly instead of wrapping it in runBlocking, use delay() instead of Thread.sleep, and move unavoidable blocking I/O into withContext(Dispatchers.IO).
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X16 · Unfloored truncation loop
X18 · Disposal-pattern correctness
X21 · Side-effecting pattern guard
X27 · Collection changed while being enumerated
X3 · Exception handling
- `catch (ex: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — src/main/kotlin/net/bytedance/security/app/util/dataClassToString.kt:33
- `catch (_: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — src/main/kotlin/net/bytedance/security/app/android/JadxRunner.kt:180
What to do
- Swallowed exception (caught, then discarded)
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 83.2 | Adequate — gated by D2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 98.5 | Exemplary | Strongest area. |
| Maturity | 68.9 | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 31.3 | Weak — gated by P2, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 96.7 | Exemplary | Solid. |
| Performance | 85.0 | Exemplary | Solid. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 73 check(s) not relevant to this codebase
- AC1 Text alternatives — Frontend below the scale floor (24 DOM element(s) < 25) — too little surface to assess accessibility.
- AC2 Forms & labels — Frontend below the scale floor (24 DOM element(s) < 25) — too little surface to assess accessibility.
- AC3 Page structure — Frontend below the scale floor (24 DOM element(s) < 25) — too little surface to assess accessibility.
- AC4 Keyboard semantics — Frontend below the scale floor (24 DOM element(s) < 25) — too little surface to assess accessibility.
- AC5 ARIA correctness — Frontend below the scale floor (24 DOM element(s) < 25) — too little surface to assess accessibility.
- AC6 Visual & motion safety — Frontend below the scale floor (24 DOM element(s) < 25) — too little surface to assess accessibility.
- AX1 Captive dependencies — Not applicable: this repository's Java 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 Kotlin 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 Java code is a Spring, JSR-330 or CDI singleton bean. No class in this Kotlin code is a Spring, JSR-330 or CDI singleton bean.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no data at rest for these controls to protect.
- 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 Room, JPA or MongoDB entity, an Exposed or Ktorm table, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) 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 Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) 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 Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~5879 lines of test source are present (.kt, .java) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .kt suite was found but not re-run
- D12 Dependency Hygiene — Not scored — a Gradle build resolved 101 artifact(s) across its subprojects (69 behind a shipped release, reported), but the currency signal was not established over the whole graph, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- 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 — D21 withholds its case and prefix conventions rows: 1 candidate(s) found and not reported.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .java, .kt, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D26 Project Cohesion — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet).
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D36 Supply-chain Provenance & Signing — The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet).
- D5 Coupling — Not applicable — this Gradle build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (52 value object(s))
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- S1 Web-Security Posture — Not assessed: these web-security 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 web-security 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.
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no C# was loaded; this repository's Java and Kotlin were read, and no request in it can be cancelled by a caller (Ktor, OkHttp's newCall or a URL stream, from a suspend function) — a Java request off Android takes no token: it is cancelled through the handle it returns (Future.cancel, Call.cancel, a Disposable), ambiently (io.grpc.Context) or by interrupting its thread, not through a parameter; a Kotlin request outside a suspend function has no caller's cancellation to honour
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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 Kotlin was read, and it logs through none that an assembled message defeats: Android's `Log` and Timber, java.util.logging and log4j-api-kotlin take one finished message (as log4net does in C#), or it makes no call through a named logger at all. Calls made through SLF4J, log4j 2 or kotlin-logging (`LoggerFactory.getLogger`, `KotlinLogging.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 — 2 finding(s)
- REDACTED
- REDACTED
Serious — 95 finding(s)
- TodoComment src/main/kotlin/net/bytedance/security/app/ui/TaintPathModeHtmlWriter.kt:283
- TodoComment src/main/kotlin/net/bytedance/security/app/taintflow/StmtTransfer.kt:287
- TodoComment src/main/kotlin/net/bytedance/security/app/pathfinder/TaintPathFinder.kt:56
- Duplicated block (8 lines × 2) src/main/kotlin/net/bytedance/security/app/PLUtils.kt:82
- Duplicated block (8 lines × 2) src/main/kotlin/net/bytedance/security/app/taintflow/ObscureRuleHandler.kt:194
- Duplicated block (8 lines × 2) src/main/kotlin/net/bytedance/security/app/ruleprocessor/ConstNumberModeProcessor.kt:35
- Low cohesion: Profiler (LCOM4 8) src/main/kotlin/net/bytedance/security/app/util/Profiler.kt:119
- Low cohesion: MethodStmtFieldCache (LCOM4 6) src/main/kotlin/net/bytedance/security/app/preprocess/MethodStmtFieldCache.kt:40
- Low cohesion: PreAnalyzeContext (LCOM4 5) src/main/kotlin/net/bytedance/security/app/PreAnalyzeContext.kt:40
- REDACTED
- REDACTED
- Edited copy of a member (12 corresponding lines) src/main/kotlin/net/bytedance/security/app/PLUtils.kt:81
- Edited copy of a member (12 corresponding lines) src/main/kotlin/net/bytedance/security/app/preprocess/Reflection.kt:68
- Edited copy of a member (9 corresponding lines) src/main/kotlin/net/bytedance/security/app/taintflow/ObscureRuleHandler.kt:193
- Edited copy of a member (9 corresponding lines) src/main/kotlin/net/bytedance/security/app/taintflow/DefaultPointerPropagationRule.kt:34
- Swallowed exception (caught, then discarded) src/main/kotlin/net/bytedance/security/app/util/dataClassToString.kt:33
- Swallowed exception (caught, then discarded) src/main/kotlin/net/bytedance/security/app/android/JadxRunner.kt:180
- TwoStagePointerAnalyze.analyzeStmtInterProcedure (cyclomatic 30) src/main/kotlin/net/bytedance/security/app/taintflow/TwoStagePointerAnalyze.kt:144
- TaintPathModeHtmlWriter.genCodeDetail (cyclomatic 25) src/main/kotlin/net/bytedance/security/app/ui/TaintPathModeHtmlWriter.kt:123
- MethodPatch.calcCallbackPatchUnits (cyclomatic 24) src/main/kotlin/net/bytedance/security/app/preprocess/MethodPatch.kt:94
- TaintRuleSourceSinkCollector.calcSinkPointers (cyclomatic 19) src/main/kotlin/net/bytedance/security/app/ruleprocessor/TaintRuleSourceSinkCollector.kt:111
- ObscureRuleHandler.addEdgeByRule (cyclomatic 19) src/main/kotlin/net/bytedance/security/app/taintflow/ObscureRuleHandler.kt:44
- MethodFinder.checkAndParseMethodSigInternal (cyclomatic 17) src/main/kotlin/net/bytedance/security/app/MethodFinder.kt:105
- PLUtils.entryMethod (cyclomatic 17) src/main/kotlin/net/bytedance/security/app/PLUtils.kt:205
- TwoStagePointerAnalyze.instanceInvoke (cyclomatic 17) src/main/kotlin/net/bytedance/security/app/taintflow/TwoStagePointerAnalyze.kt:353
- MethodFieldConstCacheVisitor.visitEachStmt (cyclomatic 16) src/main/kotlin/net/bytedance/security/app/preprocess/MethodFieldConstCacheVisitor.kt:125
- Repeated repair: src/main/kotlin/net/bytedance/security/app/AnalyzeStepByStep.kt src/main/kotlin/net/bytedance/security/app/AnalyzeStepByStep.kt:159
- TaintPathModeHtmlWriter.genCodeDetail (cognitive 82) src/main/kotlin/net/bytedance/security/app/ui/TaintPathModeHtmlWriter.kt:123
- DirectModeRule.constStringPatterns (cognitive 62) src/main/kotlin/net/bytedance/security/app/rules/DirectModeRule.kt:53
- AndroidUtils.loadDynamicRegisterReceiver (cognitive 60) src/main/kotlin/net/bytedance/security/app/android/AndroidUtils.kt:391
- TaintRuleSourceSinkCollector.calcSinkPointers (cognitive 50) src/main/kotlin/net/bytedance/security/app/ruleprocessor/TaintRuleSourceSinkCollector.kt:111
- MethodPatch.calcCallbackPatchUnits (cognitive 49) src/main/kotlin/net/bytedance/security/app/preprocess/MethodPatch.kt:94
- MethodFieldConstCacheVisitor.visitEachStmt (cognitive 42) src/main/kotlin/net/bytedance/security/app/preprocess/MethodFieldConstCacheVisitor.kt:125
- MethodFinder.checkAndParseMethodSigInternal (cognitive 41) src/main/kotlin/net/bytedance/security/app/MethodFinder.kt:105
- TwoStagePointerAnalyze.instanceInvoke (cognitive 41) src/main/kotlin/net/bytedance/security/app/taintflow/TwoStagePointerAnalyze.kt:353
- TwoStagePointerAnalyze.handleInstanceInvoke (cognitive 36) src/main/kotlin/net/bytedance/security/app/taintflow/TwoStagePointerAnalyze.kt:621
- Reflection.calcGetMethod (cognitive 35) src/main/kotlin/net/bytedance/security/app/preprocess/Reflection.kt:178
- PLUtils.entryMethod (cognitive 34) src/main/kotlin/net/bytedance/security/app/PLUtils.kt:205
- Reflection.getReflectionClass (cognitive 34) src/main/kotlin/net/bytedance/security/app/preprocess/Reflection.kt:541
- TaintRuleSourceSinkCollector.processSourceReturn (cognitive 34) src/main/kotlin/net/bytedance/security/app/ruleprocessor/TaintRuleSourceSinkCollector.kt:313
- ObscureRuleHandler.addEdgeByRule (cognitive 34) src/main/kotlin/net/bytedance/security/app/taintflow/ObscureRuleHandler.kt:44
- TwoStagePointerAnalyze.staticInvoke (cognitive 34) src/main/kotlin/net/bytedance/security/app/taintflow/TwoStagePointerAnalyze.kt:297
- ConstModeProcessor.calcAllConstPointers (cognitive 33) src/main/kotlin/net/bytedance/security/app/ruleprocessor/ConstModeProcessor.kt:118
- Reflection.injectInvokeStmt (cognitive 28) src/main/kotlin/net/bytedance/security/app/preprocess/Reflection.kt:116
- DirectModeProcessor.parseDirectEntry (cognitive 28) src/main/kotlin/net/bytedance/security/app/ruleprocessor/DirectModeProcessor.kt:86
- TwoStagePointerAnalyze.analyzeStmtInterProcedure (cognitive 28) src/main/kotlin/net/bytedance/security/app/taintflow/TwoStagePointerAnalyze.kt:144
- TaintPathFinder.runConstAnalyze (cognitive 27) src/main/kotlin/net/bytedance/security/app/pathfinder/TaintPathFinder.kt:83
- TraceTask.addManifest (cognitive 26) src/main/kotlin/net/bytedance/security/app/result/TraceTask.kt:56
- HelperKt.newFunctionSignature (cognitive 26) src/main/kotlin/net/bytedance/security/app/util/helper.kt:52
- MethodFieldConstCacheVisitor.collectOthers (cognitive 25) src/main/kotlin/net/bytedance/security/app/preprocess/MethodFieldConstCacheVisitor.kt:90
- TaintPathFinder.isConstStringRuleMatch (cognitive 24) src/main/kotlin/net/bytedance/security/app/pathfinder/TaintPathFinder.kt:161
- ConstModeProcessor.constStrArgMatch (cognitive 24) src/main/kotlin/net/bytedance/security/app/ruleprocessor/ConstModeProcessor.kt:171
- TaintRuleSourceSinkCollector.processSourceMethodParameter (cognitive 24) src/main/kotlin/net/bytedance/security/app/ruleprocessor/TaintRuleSourceSinkCollector.kt:274
- Fragment.findOneStepFragment (cognitive 23) src/main/kotlin/net/bytedance/security/app/Fragment.kt:184
- AndroidUtils.getDefinedPermissions (cognitive 23) src/main/kotlin/net/bytedance/security/app/android/AndroidUtils.kt:340
- TaintCheckSanitizerParser.calcSanitizePtrSet (cognitive 23) src/main/kotlin/net/bytedance/security/app/sanitizer/TaintCheckSanitizerParser.kt:106
- TaintFlowEdgeFinder.localToParam (cognitive 22) src/main/kotlin/net/bytedance/security/app/pathfinder/TaintFlowEdgeFinder.kt:108
- TaintFlowEdgeFinder.localToLocalThroughReturn (cognitive 22) src/main/kotlin/net/bytedance/security/app/pathfinder/TaintFlowEdgeFinder.kt:186
- TaintCheckSanitizer.matched (cognitive 22) src/main/kotlin/net/bytedance/security/app/sanitizer/TaintCheckSanitizer.kt:41
- AndroidUtils.parseComponent (cognitive 21) src/main/kotlin/net/bytedance/security/app/android/AndroidUtils.kt:539
- MethodFieldConstCacheVisitor.getAllSubClasses (cognitive 21) src/main/kotlin/net/bytedance/security/app/preprocess/MethodFieldConstCacheVisitor.kt:251
- PLUtils.getAllSubCLass (cognitive 20) src/main/kotlin/net/bytedance/security/app/PLUtils.kt:114
- CallbackConfig.getOneItem (cognitive 20) src/main/kotlin/net/bytedance/security/app/engineconfig/CallbackConfig.kt:63
- Reflection.insertClassInstantStmt (cognitive 18) src/main/kotlin/net/bytedance/security/app/preprocess/Reflection.kt:393
- Fragment.queryLayoutIdRecursive (cognitive 17) src/main/kotlin/net/bytedance/security/app/Fragment.kt:255
- UtilKt.formatJavaCode (cognitive 17) src/main/kotlin/net/bytedance/security/app/ui/util.kt:58
- JadxRunner.run (cognitive 16) src/main/kotlin/net/bytedance/security/app/android/JadxRunner.kt:56
- ConstModeProcessor.calcConstValueEntries (cognitive 16) src/main/kotlin/net/bytedance/security/app/ruleprocessor/ConstModeProcessor.kt:39
- MethodTooLong: TwoStagePointerAnalyze.handleInstanceInvoke src/main/kotlin/net/bytedance/security/app/taintflow/TwoStagePointerAnalyze.kt:621
- FileTooLong: taintflow/TwoStagePointerAnalyze.kt src/main/kotlin/net/bytedance/security/app/taintflow/TwoStagePointerAnalyze.kt
- Members sharing a duplicated core (4 members, 50+ identical tokens) src/main/kotlin/net/bytedance/security/app/preprocess/Reflection.kt:287
- Edited copy of a member (37 corresponding lines) src/main/kotlin/net/bytedance/security/app/taintflow/TwoStagePointerAnalyze.kt:305
- Edited copy of a member (33 corresponding lines) src/main/kotlin/net/bytedance/security/app/taintflow/StmtTransfer.kt:154
- Edited copy of a member (31 corresponding lines) src/main/kotlin/net/bytedance/security/app/pathfinder/TaintPathFinder.kt:161
- Edited copy of a member (25 corresponding lines) src/main/kotlin/net/bytedance/security/app/pathfinder/TaintFlowEdgeFinder.kt:77
- Edited copy of a member (21 corresponding lines) src/main/kotlin/net/bytedance/security/app/engineconfig/PointerPropagationConfig.kt:45
- Edited copy of a member (20 corresponding lines) src/main/kotlin/net/bytedance/security/app/preprocess/CallGraph.kt:202
- Edited copy of a member (18 corresponding lines) src/main/kotlin/net/bytedance/security/app/taintflow/AnalyzeContext.kt:138
- Edited copies of one member (3 members, 15+ corresponding lines) src/main/kotlin/net/bytedance/security/app/preprocess/Reflection.kt:575
- Edited copy of a member (13 corresponding lines) src/main/kotlin/net/bytedance/security/app/preprocess/CallGraph.kt:181
- Edited copy of a member (14 corresponding lines) src/main/kotlin/net/bytedance/security/app/rules/Rules.kt:90
- Duplicated block (21 lines × 2) src/main/kotlin/net/bytedance/security/app/pathfinder/TaintFlowEdgeFinder.kt:229
- Duplicated block (20 lines × 2) src/main/kotlin/net/bytedance/security/app/pathfinder/TaintFlowEdgeFinder.kt:82
- Duplicated block (12–15 lines × 3) src/main/kotlin/net/bytedance/security/app/preprocess/Reflection.kt:316
- Duplicated block (14 lines × 2) src/main/kotlin/net/bytedance/security/app/engineconfig/PointerPropagationConfig.kt:52
- Duplicated block (8–13 lines × 2) src/main/kotlin/net/bytedance/security/app/taintflow/StmtTransfer.kt:134
- Duplicated block (9–12 lines × 2) src/main/kotlin/net/bytedance/security/app/util/SecureFileIO.kt:160
- Duplicated block (10 lines × 3) src/main/kotlin/net/bytedance/security/app/pathfinder/TaintFlowEdgeFinder.kt:81
- Duplicated block (10 lines × 2) src/main/kotlin/net/bytedance/security/app/pointer/PointerFactory.kt:42
- Duplicated block (9 lines × 3) src/main/kotlin/net/bytedance/security/app/preprocess/Reflection.kt:312
- Duplicated block (6–9 lines × 3) src/main/kotlin/net/bytedance/security/app/taintflow/StmtTransfer.kt:134
- Duplicated block (7 lines × 2) src/main/kotlin/net/bytedance/security/app/rules/DirectModeRule.kt:145
- Duplicated block (13 lines × 2) src/main/kotlin/net/bytedance/security/app/preprocess/Reflection.kt:299
- No structured logging
- Sync-over-async blocking src/main/kotlin/net/bytedance/security/app/util/TaskQueue.kt:87
Minor — 7 finding(s)
- No ADRs found build.gradle.kts:13
- REDACTED
- No ADRs
- No SAST REDACTED:13
- No dependency-update automation build.gradle.kts:31
- No changelog
- Duplicated predicate src/main/kotlin/net/bytedance/security/app/PLUtils.kt:83
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-d00dfdbf11994d9b871aba26d1a57efa/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-d00dfdbf11994d9b871aba26d1a57efa/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 4 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet). | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 1 file(s) — `src/main/kotlin/at/syntaxerror/json5/JSONParser.kt` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet). | 0 | — |