Executive summary
square/leakcanary falls short of our standard for production 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 57 out of 100 and is rated Adequate, and 22 of its 23 critical findings are security problems in the build pipeline.
Production Readiness, at 41, is the weakest lens and counts most in the score. The best first step for the work it takes is fixing the package under a licence on your banned list, worth about 5 points. Adding a diagnostic log would lift Production Readiness itself, worth about 7 points. Raising Production Readiness to 70 would lift the score to about 68.
Twenty-two pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One package carries licence risk. Pinning each tool to an exact version and replacing or clearing the banned-licence packages would close both risks.
The product code is 68,138 lines, about €100,000 to rebuild.
If Production Readiness rose from 41 to 70, the lowest score rated Strong, the score would rise from 57 to about 68.
New since the last survey: 1 finding
- License Compliance · Banned license: org.neo4j:neo4j
Fixed since the last survey: 1 finding
- Documentation (README) · README may be stale
Rebuild cost: about €100,000 · Estimate
| Cost to rebuild | €35,000 to €170,000, for 576 to 1,826 hours of work, about 0.7 person-years for 1 to 2 engineers |
|---|---|
| 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 | Medium: 68,138 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 leakcanary.EventListener | 2 leakcanary.HeapAnalysisJob | 3 shark.LeakTraceObject | 4 shark.SharkLog | 5 shark.internal.hppc | 6 leakcanary.HeapAnalysisInterceptor | 7 leakcanary.ProcessInfo | 8 shark.FilteringLeakingObjectFinder | 9 shark.GcRoot | 10 shark.HprofRecord | 11 shark.HprofRecord.HeapDumpRecord.ObjectRecord.ClassDumpRecord | 12 shark.LeakTrace | 13 shark.OnAnalysisProgressListener | 14 shark.dive.HeapBitmaps | 15 leakcanary.EventListener.Event | 16 shark.HprofRecord.HeapDumpRecord | 17 shark.HprofRecord.HeapDumpRecord.ObjectRecord | 18 shark.internal | 19 shark.internal.IndexedObject | 20 shark.internal.ReferencePathNode | 21 shark.HeapObject | 22 shark.RealLeakTracerFactory | 23 shark.ChainingInstanceReferenceReader | 24 shark | 25 leakcanary.HeapAnalysisJob.Result | 26 leakcanary.LeakCanary.Config | 27 leakcanary.internal.activity.db | 28 leakcanary.internal.activity.screen | 29 org.leakcanary.data | 30 shark.AndroidReferenceReaders | 31 shark.PrioritizingShortestPathFinder | 32 shark.dive | 33 shark.internal.HprofInMemoryIndex | 34 leakcanary.LeakCanary | 35 org.leakcanary.screens | 36 shark.dive.agent | 37 leakcanary.internal | 38 shark.dive.app | 39 shark.dive.eval | 40 leakcanary |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 leakcanary.EventListener | ||||||||||||||||||||||||||||||||||||||||
| 2 leakcanary.HeapAnalysisJob | ||||||||||||||||||||||||||||||||||||||||
| 3 shark.LeakTraceObject | ||||||||||||||||||||||||||||||||||||||||
| 4 shark.SharkLog | ||||||||||||||||||||||||||||||||||||||||
| 5 shark.internal.hppc | ||||||||||||||||||||||||||||||||||||||||
| 6 leakcanary.HeapAnalysisInterceptor | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 7 leakcanary.ProcessInfo | 1 | |||||||||||||||||||||||||||||||||||||||
| 8 shark.FilteringLeakingObjectFinder | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 shark.GcRoot | 16 | |||||||||||||||||||||||||||||||||||||||
| 10 shark.HprofRecord | 7 | |||||||||||||||||||||||||||||||||||||||
| 11 shark.HprofRecord.HeapDumpRecord.ObjectRecord.ClassDumpRecord | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 shark.LeakTrace | 2 | |||||||||||||||||||||||||||||||||||||||
| 13 shark.OnAnalysisProgressListener | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 shark.dive.HeapBitmaps | 2 | |||||||||||||||||||||||||||||||||||||||
| 15 leakcanary.EventListener.Event | 5 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 16 shark.HprofRecord.HeapDumpRecord | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 17 shark.HprofRecord.HeapDumpRecord.ObjectRecord | 2 | 4 | ||||||||||||||||||||||||||||||||||||||
| 18 shark.internal | 8 | 2 | 2 | 3 | 2 | 5 | 5 | 4 | 14 | |||||||||||||||||||||||||||||||
| 19 shark.internal.IndexedObject | 4 | 1 | ||||||||||||||||||||||||||||||||||||||
| 20 shark.internal.ReferencePathNode | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 shark.HeapObject | 2 | 4 | 4 | 17 | ||||||||||||||||||||||||||||||||||||
| 22 shark.RealLeakTracerFactory | 1 | 1 | 2 | 5 | ||||||||||||||||||||||||||||||||||||
| 23 shark.ChainingInstanceReferenceReader | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 24 shark | 4 | 1 | 2 | 1 | 18 | 6 | 3 | 1 | 1 | 3 | 9 | 13 | 4 | 1 | 31 | 2 | 3 | |||||||||||||||||||||||
| 25 leakcanary.HeapAnalysisJob.Result | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 26 leakcanary.LeakCanary.Config | 4 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 27 leakcanary.internal.activity.db | 2 | |||||||||||||||||||||||||||||||||||||||
| 28 leakcanary.internal.activity.screen | 4 | 6 | ||||||||||||||||||||||||||||||||||||||
| 29 org.leakcanary.data | 1 | |||||||||||||||||||||||||||||||||||||||
| 30 shark.AndroidReferenceReaders | 1 | 5 | 10 | |||||||||||||||||||||||||||||||||||||
| 31 shark.PrioritizingShortestPathFinder | 3 | 3 | 6 | |||||||||||||||||||||||||||||||||||||
| 32 shark.dive | 1 | 5 | 1 | 7 | 1 | 58 | ||||||||||||||||||||||||||||||||||
| 33 shark.internal.HprofInMemoryIndex | 3 | 1 | 2 | 4 | 12 | |||||||||||||||||||||||||||||||||||
| 34 leakcanary.LeakCanary | 4 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 35 org.leakcanary.screens | 7 | 4 | ||||||||||||||||||||||||||||||||||||||
| 36 shark.dive.agent | 36 | |||||||||||||||||||||||||||||||||||||||
| 37 leakcanary.internal | 1 | 1 | 1 | 1 | 3 | 16 | 2 | 1 | 11 | |||||||||||||||||||||||||||||||
| 38 shark.dive.app | 2 | 1 | 146 | 10 | ||||||||||||||||||||||||||||||||||||
| 39 shark.dive.eval | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 40 leakcanary | 9 | 11 | 1 | 8 | 1 | 18 | 1 | 1 |
6→2 leakcanary.HeapAnalysisInterceptor uses leakcanary.HeapAnalysisJob✕
- Connections
- 1 pair of types, where a type in leakcanary.HeapAnalysisInterceptor uses a type in leakcanary.HeapAnalysisJob.
- The types involved
leakcanary.HeapAnalysisInterceptor.Chain→leakcanary.HeapAnalysisJob.Result
- Direction
- leakcanary.HeapAnalysisInterceptor uses leakcanary.HeapAnalysisJob, so a change to leakcanary.HeapAnalysisJob can break leakcanary.HeapAnalysisInterceptor, while a change to leakcanary.HeapAnalysisInterceptor can't break leakcanary.HeapAnalysisJob.
- Position
- Below the diagonal: leakcanary.HeapAnalysisInterceptor uses a module listed above it, which is the healthy direction.
6→40 leakcanary.HeapAnalysisInterceptor uses leakcanary part of a loop✕
- Connections
- 1 pair of types, where a type in leakcanary.HeapAnalysisInterceptor uses a type in leakcanary.
- The types involved
leakcanary.HeapAnalysisInterceptor.Chain→leakcanary.HeapAnalysisJob
- Direction
- leakcanary.HeapAnalysisInterceptor uses leakcanary, so a change to leakcanary can break leakcanary.HeapAnalysisInterceptor, while a change to leakcanary.HeapAnalysisInterceptor can't break leakcanary.
- 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→40 leakcanary.ProcessInfo uses leakcanary part of a loop✕
- Connections
- 1 pair of types, where a type in leakcanary.ProcessInfo uses a type in leakcanary.
- The types involved
leakcanary.ProcessInfo.Real→leakcanary.ProcessInfo
- Direction
- leakcanary.ProcessInfo uses leakcanary, so a change to leakcanary can break leakcanary.ProcessInfo, while a change to leakcanary.ProcessInfo can't break leakcanary.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→24 shark.FilteringLeakingObjectFinder uses shark part of a loop✕
- Connections
- 1 pair of types, where a type in shark.FilteringLeakingObjectFinder uses a type in shark.
- The types involved
shark.FilteringLeakingObjectFinder.LeakingObjectFilter→shark.HeapObject
- Direction
- shark.FilteringLeakingObjectFinder uses shark, so a change to shark can break shark.FilteringLeakingObjectFinder, while a change to shark.FilteringLeakingObjectFinder can't break shark.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→24 shark.GcRoot uses shark part of a loop✕
- Connections
- 16 pairs of types, where a type in shark.GcRoot uses a type in shark.
- The types involved
shark.GcRoot.Debugger→shark.GcRootshark.GcRoot.Finalizing→shark.GcRootshark.GcRoot.InternedString→shark.GcRootshark.GcRoot.JavaFrame→shark.GcRootshark.GcRoot.JniGlobal→shark.GcRootshark.GcRoot.JniLocal→shark.GcRootshark.GcRoot.JniMonitor→shark.GcRootshark.GcRoot.MonitorUsed→shark.GcRootshark.GcRoot.NativeStack→shark.GcRootshark.GcRoot.ReferenceCleanup→shark.GcRootshark.GcRoot.StickyClass→shark.GcRootshark.GcRoot.ThreadBlock→shark.GcRootshark.GcRoot.ThreadObject→shark.GcRootshark.GcRoot.Unknown→shark.GcRootshark.GcRoot.Unreachable→shark.GcRootshark.GcRoot.VmInternal→shark.GcRoot
- Direction
- shark.GcRoot uses shark, so a change to shark can break shark.GcRoot, while a change to shark.GcRoot can't break shark.
- 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.
10→24 shark.HprofRecord uses shark part of a loop✕
- Connections
- 7 pairs of types, where a type in shark.HprofRecord uses a type in shark.
- The types involved
shark.HprofRecord.HeapDumpEndRecord→shark.HprofRecordshark.HprofRecord.HeapDumpRecord→shark.HprofRecordshark.HprofRecord.LoadClassRecord→shark.HprofRecordshark.HprofRecord.StackFrameRecord→shark.HprofRecordshark.HprofRecord.StackTraceRecord→shark.HprofRecordshark.HprofRecord.StringRecord→shark.HprofRecordshark.HprofRecord.UnloadClassRecord→shark.HprofRecord
- Direction
- shark.HprofRecord uses shark, so a change to shark can break shark.HprofRecord, while a change to shark.HprofRecord can't break shark.
- 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 shark.HprofRecord.HeapDumpRecord.ObjectRecord.ClassDumpRecord uses shark part of a loop✕
- Connections
- 1 pair of types, where a type in shark.HprofRecord.HeapDumpRecord.ObjectRecord.ClassDumpRecord uses a type in shark.
- The types involved
shark.HprofRecord.HeapDumpRecord.ObjectRecord.ClassDumpRecord.StaticFieldRecord→shark.ValueHolder
- Direction
- shark.HprofRecord.HeapDumpRecord.ObjectRecord.ClassDumpRecord uses shark, so a change to shark can break shark.HprofRecord.HeapDumpRecord.ObjectRecord.ClassDumpRecord, while a change to shark.HprofRecord.HeapDumpRecord.ObjectRecord.ClassDumpRecord can't break shark.
- 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→24 shark.LeakTrace uses shark part of a loop✕
- Connections
- 2 pairs of types, where a type in shark.LeakTrace uses a type in shark.
- The types involved
shark.LeakTrace.Companion→shark.LeakTraceshark.LeakTrace.Companion→shark.LeakTraceReference
- Direction
- shark.LeakTrace uses shark, so a change to shark can break shark.LeakTrace, while a change to shark.LeakTrace can't break shark.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→24 shark.OnAnalysisProgressListener uses shark part of a loop✕
- Connections
- 1 pair of types, where a type in shark.OnAnalysisProgressListener uses a type in shark.
- The types involved
shark.OnAnalysisProgressListener.Companion→shark.OnAnalysisProgressListener
- Direction
- shark.OnAnalysisProgressListener uses shark, so a change to shark can break shark.OnAnalysisProgressListener, while a change to shark.OnAnalysisProgressListener can't break shark.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→32 shark.dive.HeapBitmaps uses shark.dive part of a loop✕
- Connections
- 2 pairs of types, where a type in shark.dive.HeapBitmaps uses a type in shark.dive.
- The types involved
shark.dive.HeapBitmaps.PointerImages→shark.dive.EncodedImageFormatshark.dive.HeapBitmaps.PointerImages→shark.dive.PixelSize
- Direction
- shark.dive.HeapBitmaps uses shark.dive, so a change to shark.dive can break shark.dive.HeapBitmaps, while a change to shark.dive.HeapBitmaps can't break shark.dive.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→1 leakcanary.EventListener.Event uses leakcanary.EventListener✕
- Connections
- 5 pairs of types, where a type in leakcanary.EventListener.Event uses a type in leakcanary.EventListener.
- The types involved
leakcanary.EventListener.Event.DumpingHeap→leakcanary.EventListener.Eventleakcanary.EventListener.Event.HeapAnalysisDone→leakcanary.EventListener.Eventleakcanary.EventListener.Event.HeapAnalysisProgress→leakcanary.EventListener.Eventleakcanary.EventListener.Event.HeapDump→leakcanary.EventListener.Eventleakcanary.EventListener.Event.HeapDumpFailed→leakcanary.EventListener.Event
- Direction
- leakcanary.EventListener.Event uses leakcanary.EventListener, so a change to leakcanary.EventListener can break leakcanary.EventListener.Event, while a change to leakcanary.EventListener.Event can't break leakcanary.EventListener.
- Position
- Below the diagonal: leakcanary.EventListener.Event uses a module listed above it, which is the healthy direction.
15→13 leakcanary.EventListener.Event uses shark.OnAnalysisProgressListener✕
- Connections
- 1 pair of types, where a type in leakcanary.EventListener.Event uses a type in shark.OnAnalysisProgressListener.
- The types involved
leakcanary.EventListener.Event.HeapAnalysisProgress→shark.OnAnalysisProgressListener.Step
- Direction
- leakcanary.EventListener.Event uses shark.OnAnalysisProgressListener, so a change to shark.OnAnalysisProgressListener can break leakcanary.EventListener.Event, while a change to leakcanary.EventListener.Event can't break shark.OnAnalysisProgressListener.
- Position
- Below the diagonal: leakcanary.EventListener.Event uses a module listed above it, which is the healthy direction.
15→37 leakcanary.EventListener.Event uses leakcanary.internal part of a loop✕
- Connections
- 1 pair of types, where a type in leakcanary.EventListener.Event uses a type in leakcanary.internal.
- The types involved
leakcanary.EventListener.Event.HeapAnalysisDone→leakcanary.internal.SerializableIntent
- Direction
- leakcanary.EventListener.Event uses leakcanary.internal, so a change to leakcanary.internal can break leakcanary.EventListener.Event, while a change to leakcanary.EventListener.Event can't break leakcanary.internal.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→10 shark.HprofRecord.HeapDumpRecord uses shark.HprofRecord✕
- Connections
- 3 pairs of types, where a type in shark.HprofRecord.HeapDumpRecord uses a type in shark.HprofRecord.
- The types involved
shark.HprofRecord.HeapDumpRecord.GcRootRecord→shark.HprofRecord.HeapDumpRecordshark.HprofRecord.HeapDumpRecord.HeapDumpInfoRecord→shark.HprofRecord.HeapDumpRecordshark.HprofRecord.HeapDumpRecord.ObjectRecord→shark.HprofRecord.HeapDumpRecord
- Direction
- shark.HprofRecord.HeapDumpRecord uses shark.HprofRecord, so a change to shark.HprofRecord can break shark.HprofRecord.HeapDumpRecord, while a change to shark.HprofRecord.HeapDumpRecord can't break shark.HprofRecord.
- Position
- Below the diagonal: shark.HprofRecord.HeapDumpRecord uses a module listed above it, which is the healthy direction.
16→24 shark.HprofRecord.HeapDumpRecord uses shark part of a loop✕
- Connections
- 1 pair of types, where a type in shark.HprofRecord.HeapDumpRecord uses a type in shark.
- The types involved
shark.HprofRecord.HeapDumpRecord.GcRootRecord→shark.GcRoot
- Direction
- shark.HprofRecord.HeapDumpRecord uses shark, so a change to shark can break shark.HprofRecord.HeapDumpRecord, while a change to shark.HprofRecord.HeapDumpRecord can't break shark.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→11 shark.HprofRecord.HeapDumpRecord.ObjectRecord uses shark.HprofRecord.HeapDumpRecord.ObjectRecord.ClassDumpRecord✕
- Connections
- 2 pairs of types, where a type in shark.HprofRecord.HeapDumpRecord.ObjectRecord uses a type in shark.HprofRecord.HeapDumpRecord.ObjectRecord.ClassDumpRecord.
- The types involved
shark.HprofRecord.HeapDumpRecord.ObjectRecord.ClassDumpRecord→shark.HprofRecord.HeapDumpRecord.ObjectRecord.ClassDumpRecord.FieldRecordshark.HprofRecord.HeapDumpRecord.ObjectRecord.ClassDumpRecord→shark.HprofRecord.HeapDumpRecord.ObjectRecord.ClassDumpRecord.StaticFieldRecord
- Direction
- shark.HprofRecord.HeapDumpRecord.ObjectRecord uses shark.HprofRecord.HeapDumpRecord.ObjectRecord.ClassDumpRecord, so a change to shark.HprofRecord.HeapDumpRecord.ObjectRecord.ClassDumpRecord can break shark.HprofRecord.HeapDumpRecord.ObjectRecord, while a change to shark.HprofRecord.HeapDumpRecord.ObjectRecord can't break shark.HprofRecord.HeapDumpRecord.ObjectRecord.ClassDumpRecord.
- Position
- Below the diagonal: shark.HprofRecord.HeapDumpRecord.ObjectRecord uses a module listed above it, which is the healthy direction.
17→16 shark.HprofRecord.HeapDumpRecord.ObjectRecord uses shark.HprofRecord.HeapDumpRecord✕
- Connections
- 4 pairs of types, where a type in shark.HprofRecord.HeapDumpRecord.ObjectRecord uses a type in shark.HprofRecord.HeapDumpRecord.
- The types involved
shark.HprofRecord.HeapDumpRecord.ObjectRecord.ClassDumpRecord→shark.HprofRecord.HeapDumpRecord.ObjectRecordshark.HprofRecord.HeapDumpRecord.ObjectRecord.InstanceDumpRecord→shark.HprofRecord.HeapDumpRecord.ObjectRecordshark.HprofRecord.HeapDumpRecord.ObjectRecord.ObjectArrayDumpRecord→shark.HprofRecord.HeapDumpRecord.ObjectRecordshark.HprofRecord.HeapDumpRecord.ObjectRecord.PrimitiveArrayDumpRecord→shark.HprofRecord.HeapDumpRecord.ObjectRecord
- Direction
- shark.HprofRecord.HeapDumpRecord.ObjectRecord uses shark.HprofRecord.HeapDumpRecord, so a change to shark.HprofRecord.HeapDumpRecord can break shark.HprofRecord.HeapDumpRecord.ObjectRecord, while a change to shark.HprofRecord.HeapDumpRecord.ObjectRecord can't break shark.HprofRecord.HeapDumpRecord.
- Position
- Below the diagonal: shark.HprofRecord.HeapDumpRecord.ObjectRecord uses a module listed above it, which is the healthy direction.
18→5 shark.internal uses shark.internal.hppc✕
- Connections
- 8 pairs of types, where a type in shark.internal uses a type in shark.internal.hppc.
- The types involved
shark.internal.ArraySortedBytesMap→shark.internal.hppc.LongObjectPairshark.internal.HprofInMemoryIndex→shark.internal.hppc.IntObjectPairshark.internal.HprofInMemoryIndex→shark.internal.hppc.LongLongScatterMapshark.internal.HprofInMemoryIndex→shark.internal.hppc.LongObjectPairshark.internal.HprofInMemoryIndex→shark.internal.hppc.LongObjectScatterMapshark.internal.HprofInMemoryIndex→shark.internal.hppc.LongScatterSetshark.internal.PagedSortedBytesMap→shark.internal.hppc.LongObjectPairshark.internal.SortedBytesMap→shark.internal.hppc.LongObjectPair
- Direction
- shark.internal uses shark.internal.hppc, so a change to shark.internal.hppc can break shark.internal, while a change to shark.internal can't break shark.internal.hppc.
- Position
- Below the diagonal: shark.internal uses a module listed above it, which is the healthy direction.
18→9 shark.internal uses shark.GcRoot✕
- Connections
- 2 pairs of types, where a type in shark.internal uses a type in shark.GcRoot.
- The types involved
shark.internal.HprofInMemoryIndex→shark.GcRoot.ThreadObjectshark.internal.ThreadObjects→shark.GcRoot.ThreadObject
- Direction
- shark.internal uses shark.GcRoot, so a change to shark.GcRoot can break shark.internal, while a change to shark.internal can't break shark.GcRoot.
- Position
- Below the diagonal: shark.internal uses a module listed above it, which is the healthy direction.
18→10 shark.internal uses shark.HprofRecord✕
- Connections
- 2 pairs of types, where a type in shark.internal uses a type in shark.HprofRecord.
- The types involved
shark.internal.HprofInMemoryIndex→shark.HprofRecord.StackFrameRecordshark.internal.HprofInMemoryIndex→shark.HprofRecord.StackTraceRecord
- Direction
- shark.internal uses shark.HprofRecord, so a change to shark.HprofRecord can break shark.internal, while a change to shark.internal can't break shark.HprofRecord.
- Position
- Below the diagonal: shark.internal uses a module listed above it, which is the healthy direction.
18→11 shark.internal uses shark.HprofRecord.HeapDumpRecord.ObjectRecord.ClassDumpRecord✕
- Connections
- 3 pairs of types, where a type in shark.internal uses a type in shark.HprofRecord.HeapDumpRecord.ObjectRecord.ClassDumpRecord.
- The types involved
shark.internal.ClassFieldsReader→shark.HprofRecord.HeapDumpRecord.ObjectRecord.ClassDumpRecord.FieldRecordshark.internal.ClassFieldsReader→shark.HprofRecord.HeapDumpRecord.ObjectRecord.ClassDumpRecord.StaticFieldRecordshark.internal.FieldValuesReader→shark.HprofRecord.HeapDumpRecord.ObjectRecord.ClassDumpRecord.FieldRecord
- Direction
- shark.internal uses shark.HprofRecord.HeapDumpRecord.ObjectRecord.ClassDumpRecord, so a change to shark.HprofRecord.HeapDumpRecord.ObjectRecord.ClassDumpRecord can break shark.internal, while a change to shark.internal can't break shark.HprofRecord.HeapDumpRecord.ObjectRecord.ClassDumpRecord.
- Position
- Below the diagonal: shark.internal uses a module listed above it, which is the healthy direction.
18→17 shark.internal uses shark.HprofRecord.HeapDumpRecord.ObjectRecord✕
- Connections
- 2 pairs of types, where a type in shark.internal uses a type in shark.HprofRecord.HeapDumpRecord.ObjectRecord.
- The types involved
shark.internal.FieldIdReader→shark.HprofRecord.HeapDumpRecord.ObjectRecord.InstanceDumpRecordshark.internal.FieldValuesReader→shark.HprofRecord.HeapDumpRecord.ObjectRecord.InstanceDumpRecord
- Direction
- shark.internal uses shark.HprofRecord.HeapDumpRecord.ObjectRecord, so a change to shark.HprofRecord.HeapDumpRecord.ObjectRecord can break shark.internal, while a change to shark.internal can't break shark.HprofRecord.HeapDumpRecord.ObjectRecord.
- Position
- Below the diagonal: shark.internal uses a module listed above it, which is the healthy direction.
18→19 shark.internal uses shark.internal.IndexedObject part of a loop✕
- Connections
- 5 pairs of types, where a type in shark.internal uses a type in shark.internal.IndexedObject.
- The types involved
shark.internal.ClassFieldsReader→shark.internal.IndexedObject.IndexedClassshark.internal.HprofInMemoryIndex→shark.internal.IndexedObject.IndexedClassshark.internal.HprofInMemoryIndex→shark.internal.IndexedObject.IndexedInstanceshark.internal.HprofInMemoryIndex→shark.internal.IndexedObject.IndexedObjectArrayshark.internal.HprofInMemoryIndex→shark.internal.IndexedObject.IndexedPrimitiveArray
- Direction
- shark.internal uses shark.internal.IndexedObject, so a change to shark.internal.IndexedObject can break shark.internal, while a change to shark.internal can't break shark.internal.IndexedObject.
- 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→21 shark.internal uses shark.HeapObject part of a loop✕
- Connections
- 5 pairs of types, where a type in shark.internal uses a type in shark.HeapObject.
- The types involved
shark.internal.InternalSharedArrayListReferenceReader→shark.HeapObject.HeapInstanceshark.internal.InternalSharedHashMapReferenceReader→shark.HeapObject.HeapInstanceshark.internal.InternalSharedLinkedListReferenceReader→shark.HeapObject.HeapInstanceshark.internal.InternalSharedWeakHashMapReferenceReader→shark.HeapObject.HeapInstanceshark.internal.InternalSharkCollectionsHelper→shark.HeapObject.HeapInstance
- Direction
- shark.internal uses shark.HeapObject, so a change to shark.HeapObject can break shark.internal, while a change to shark.internal can't break shark.HeapObject.
- 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→23 shark.internal uses shark.ChainingInstanceReferenceReader part of a loop✕
- Connections
- 4 pairs of types, where a type in shark.internal uses a type in shark.ChainingInstanceReferenceReader.
- The types involved
shark.internal.InternalSharedArrayListReferenceReader→shark.ChainingInstanceReferenceReader.VirtualInstanceReferenceReadershark.internal.InternalSharedHashMapReferenceReader→shark.ChainingInstanceReferenceReader.VirtualInstanceReferenceReadershark.internal.InternalSharedLinkedListReferenceReader→shark.ChainingInstanceReferenceReader.VirtualInstanceReferenceReadershark.internal.InternalSharedWeakHashMapReferenceReader→shark.ChainingInstanceReferenceReader.VirtualInstanceReferenceReader
- Direction
- shark.internal uses shark.ChainingInstanceReferenceReader, so a change to shark.ChainingInstanceReferenceReader can break shark.internal, while a change to shark.internal can't break shark.ChainingInstanceReferenceReader.
- 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→24 shark.internal uses shark part of a loop✕
- Connections
- 14 pairs of types, where a type in shark.internal uses a type in shark.
- The types involved
shark.internal.FieldValuesReader→shark.ValueHoldershark.internal.HeapObjectIdSet→shark.HeapGraphshark.internal.HprofInMemoryIndex→shark.GcRootshark.internal.HprofInMemoryIndex→shark.ProguardMappingshark.internal.InternalSharedArrayListReferenceReader→shark.Referenceshark.internal.InternalSharedHashMapReferenceReader→shark.HeapMapEntryshark.internal.InternalSharedHashMapReferenceReader→shark.Referenceshark.internal.InternalSharedLinkedListReferenceReader→shark.Referenceshark.internal.InternalSharedWeakHashMapReferenceReader→shark.Referenceshark.internal.InternalSharkCollectionsHelper→shark.HeapObjectshark.internal.ShallowSizeCalculator→shark.HeapGraphshark.internal.ThreadObjects→shark.HeapGraphshark.internal.ThreadStackRoots→shark.GcRootshark.internal.ThreadStackRoots→shark.HeapGraph
- Direction
- shark.internal uses shark, so a change to shark can break shark.internal, while a change to shark.internal can't break shark.
- 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→18 shark.internal.IndexedObject uses shark.internal✕
- Connections
- 4 pairs of types, where a type in shark.internal.IndexedObject uses a type in shark.internal.
- The types involved
shark.internal.IndexedObject.IndexedClass→shark.internal.IndexedObjectshark.internal.IndexedObject.IndexedInstance→shark.internal.IndexedObjectshark.internal.IndexedObject.IndexedObjectArray→shark.internal.IndexedObjectshark.internal.IndexedObject.IndexedPrimitiveArray→shark.internal.IndexedObject
- Direction
- shark.internal.IndexedObject uses shark.internal, so a change to shark.internal can break shark.internal.IndexedObject, while a change to shark.internal.IndexedObject can't break shark.internal.
- Position
- Below the diagonal: shark.internal.IndexedObject uses a module listed above it, which is the healthy direction.
19→24 shark.internal.IndexedObject uses shark part of a loop✕
- Connections
- 1 pair of types, where a type in shark.internal.IndexedObject uses a type in shark.
- The types involved
shark.internal.IndexedObject.IndexedPrimitiveArray→shark.PrimitiveType
- Direction
- shark.internal.IndexedObject uses shark, so a change to shark can break shark.internal.IndexedObject, while a change to shark.internal.IndexedObject can't break shark.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→18 shark.internal.ReferencePathNode uses shark.internal✕
- Connections
- 2 pairs of types, where a type in shark.internal.ReferencePathNode uses a type in shark.internal.
- The types involved
shark.internal.ReferencePathNode.ChildNode→shark.internal.ReferencePathNodeshark.internal.ReferencePathNode.RootNode→shark.internal.ReferencePathNode
- Direction
- shark.internal.ReferencePathNode uses shark.internal, so a change to shark.internal can break shark.internal.ReferencePathNode, while a change to shark.internal.ReferencePathNode can't break shark.internal.
- Position
- Below the diagonal: shark.internal.ReferencePathNode uses a module listed above it, which is the healthy direction.
20→24 shark.internal.ReferencePathNode uses shark part of a loop✕
- Connections
- 1 pair of types, where a type in shark.internal.ReferencePathNode uses a type in shark.
- The types involved
shark.internal.ReferencePathNode.RootNode→shark.GcRoot
- Direction
- shark.internal.ReferencePathNode uses shark, so a change to shark can break shark.internal.ReferencePathNode, while a change to shark.internal.ReferencePathNode can't break shark.
- 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.
21→11 shark.HeapObject uses shark.HprofRecord.HeapDumpRecord.ObjectRecord.ClassDumpRecord✕
- Connections
- 2 pairs of types, where a type in shark.HeapObject uses a type in shark.HprofRecord.HeapDumpRecord.ObjectRecord.ClassDumpRecord.
- The types involved
shark.HeapObject.HeapClass→shark.HprofRecord.HeapDumpRecord.ObjectRecord.ClassDumpRecord.FieldRecordshark.HeapObject.HeapClass→shark.HprofRecord.HeapDumpRecord.ObjectRecord.ClassDumpRecord.StaticFieldRecord
- Direction
- shark.HeapObject uses shark.HprofRecord.HeapDumpRecord.ObjectRecord.ClassDumpRecord, so a change to shark.HprofRecord.HeapDumpRecord.ObjectRecord.ClassDumpRecord can break shark.HeapObject, while a change to shark.HeapObject can't break shark.HprofRecord.HeapDumpRecord.ObjectRecord.ClassDumpRecord.
- Position
- Below the diagonal: shark.HeapObject uses a module listed above it, which is the healthy direction.
21→17 shark.HeapObject uses shark.HprofRecord.HeapDumpRecord.ObjectRecord✕
- Connections
- 4 pairs of types, where a type in shark.HeapObject uses a type in shark.HprofRecord.HeapDumpRecord.ObjectRecord.
- The types involved
shark.HeapObject.HeapClass→shark.HprofRecord.HeapDumpRecord.ObjectRecord.ClassDumpRecordshark.HeapObject.HeapInstance→shark.HprofRecord.HeapDumpRecord.ObjectRecord.InstanceDumpRecordshark.HeapObject.HeapObjectArray→shark.HprofRecord.HeapDumpRecord.ObjectRecord.ObjectArrayDumpRecordshark.HeapObject.HeapPrimitiveArray→shark.HprofRecord.HeapDumpRecord.ObjectRecord.PrimitiveArrayDumpRecord
- Direction
- shark.HeapObject uses shark.HprofRecord.HeapDumpRecord.ObjectRecord, so a change to shark.HprofRecord.HeapDumpRecord.ObjectRecord can break shark.HeapObject, while a change to shark.HeapObject can't break shark.HprofRecord.HeapDumpRecord.ObjectRecord.
- Position
- Below the diagonal: shark.HeapObject uses a module listed above it, which is the healthy direction.
21→19 shark.HeapObject uses shark.internal.IndexedObject✕
- Connections
- 4 pairs of types, where a type in shark.HeapObject uses a type in shark.internal.IndexedObject.
- The types involved
shark.HeapObject.HeapClass→shark.internal.IndexedObject.IndexedClassshark.HeapObject.HeapInstance→shark.internal.IndexedObject.IndexedInstanceshark.HeapObject.HeapObjectArray→shark.internal.IndexedObject.IndexedObjectArrayshark.HeapObject.HeapPrimitiveArray→shark.internal.IndexedObject.IndexedPrimitiveArray
- Direction
- shark.HeapObject uses shark.internal.IndexedObject, so a change to shark.internal.IndexedObject can break shark.HeapObject, while a change to shark.HeapObject can't break shark.internal.IndexedObject.
- Position
- Below the diagonal: shark.HeapObject uses a module listed above it, which is the healthy direction.
21→24 shark.HeapObject uses shark part of a loop✕
- Connections
- 17 pairs of types, where a type in shark.HeapObject uses a type in shark.
- The types involved
shark.HeapObject.Companion→shark.PrimitiveTypeshark.HeapObject.HeapClass→shark.HeapFieldshark.HeapObject.HeapClass→shark.HeapGraphshark.HeapObject.HeapClass→shark.HeapObjectshark.HeapObject.HeapClass→shark.HprofHeapGraphshark.HeapObject.HeapInstance→shark.HeapFieldshark.HeapObject.HeapInstance→shark.HeapGraphshark.HeapObject.HeapInstance→shark.HeapObjectshark.HeapObject.HeapInstance→shark.HprofHeapGraphshark.HeapObject.HeapObjectArray→shark.HeapGraphshark.HeapObject.HeapObjectArray→shark.HeapObjectshark.HeapObject.HeapObjectArray→shark.HeapValueshark.HeapObject.HeapObjectArray→shark.HprofHeapGraphshark.HeapObject.HeapPrimitiveArray→shark.HeapGraphshark.HeapObject.HeapPrimitiveArray→shark.HeapObjectshark.HeapObject.HeapPrimitiveArray→shark.HprofHeapGraphshark.HeapObject.HeapPrimitiveArray→shark.PrimitiveType
- Direction
- shark.HeapObject uses shark, so a change to shark can break shark.HeapObject, while a change to shark.HeapObject can't break shark.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→3 shark.RealLeakTracerFactory uses shark.LeakTraceObject✕
- Connections
- 1 pair of types, where a type in shark.RealLeakTracerFactory uses a type in shark.LeakTraceObject.
- The types involved
shark.RealLeakTracerFactory.InspectedObject→shark.LeakTraceObject.Verdict
- Direction
- shark.RealLeakTracerFactory uses shark.LeakTraceObject, so a change to shark.LeakTraceObject can break shark.RealLeakTracerFactory, while a change to shark.RealLeakTracerFactory can't break shark.LeakTraceObject.
- Position
- Below the diagonal: shark.RealLeakTracerFactory uses a module listed above it, which is the healthy direction.
22→18 shark.RealLeakTracerFactory uses shark.internal✕
- Connections
- 1 pair of types, where a type in shark.RealLeakTracerFactory uses a type in shark.internal.
- The types involved
shark.RealLeakTracerFactory.ShortestPath→shark.internal.ReferencePathNode
- Direction
- shark.RealLeakTracerFactory uses shark.internal, so a change to shark.internal can break shark.RealLeakTracerFactory, while a change to shark.RealLeakTracerFactory can't break shark.internal.
- Position
- Below the diagonal: shark.RealLeakTracerFactory uses a module listed above it, which is the healthy direction.
22→20 shark.RealLeakTracerFactory uses shark.internal.ReferencePathNode✕
- Connections
- 2 pairs of types, where a type in shark.RealLeakTracerFactory uses a type in shark.internal.ReferencePathNode.
- The types involved
shark.RealLeakTracerFactory.ShortestPath→shark.internal.ReferencePathNode.ChildNodeshark.RealLeakTracerFactory.ShortestPath→shark.internal.ReferencePathNode.RootNode
- Direction
- shark.RealLeakTracerFactory uses shark.internal.ReferencePathNode, so a change to shark.internal.ReferencePathNode can break shark.RealLeakTracerFactory, while a change to shark.RealLeakTracerFactory can't break shark.internal.ReferencePathNode.
- Position
- Below the diagonal: shark.RealLeakTracerFactory uses a module listed above it, which is the healthy direction.
22→24 shark.RealLeakTracerFactory uses shark part of a loop✕
- Connections
- 5 pairs of types, where a type in shark.RealLeakTracerFactory uses a type in shark.
- The types involved
shark.RealLeakTracerFactory.FindLeakInput→shark.HeapGraphshark.RealLeakTracerFactory.FindLeakInput→shark.ObjectInspectorshark.RealLeakTracerFactory.FindLeakInput→shark.ShortestPathFindershark.RealLeakTracerFactory.InspectedObject→shark.HeapObjectshark.RealLeakTracerFactory.ShortestPath→shark.LibraryLeakReferenceMatcher
- Direction
- shark.RealLeakTracerFactory uses shark, so a change to shark can break shark.RealLeakTracerFactory, while a change to shark.RealLeakTracerFactory can't break shark.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→21 shark.ChainingInstanceReferenceReader uses shark.HeapObject✕
- Connections
- 1 pair of types, where a type in shark.ChainingInstanceReferenceReader uses a type in shark.HeapObject.
- The types involved
shark.ChainingInstanceReferenceReader.VirtualInstanceReferenceReader→shark.HeapObject.HeapInstance
- Direction
- shark.ChainingInstanceReferenceReader uses shark.HeapObject, so a change to shark.HeapObject can break shark.ChainingInstanceReferenceReader, while a change to shark.ChainingInstanceReferenceReader can't break shark.HeapObject.
- Position
- Below the diagonal: shark.ChainingInstanceReferenceReader uses a module listed above it, which is the healthy direction.
23→24 shark.ChainingInstanceReferenceReader uses shark part of a loop✕
- Connections
- 1 pair of types, where a type in shark.ChainingInstanceReferenceReader uses a type in shark.
- The types involved
shark.ChainingInstanceReferenceReader.VirtualInstanceReferenceReader→shark.ReferenceReader
- Direction
- shark.ChainingInstanceReferenceReader uses shark, so a change to shark can break shark.ChainingInstanceReferenceReader, while a change to shark.ChainingInstanceReferenceReader can't break shark.
- 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→3 shark uses shark.LeakTraceObject✕
- Connections
- 4 pairs of types, where a type in shark uses a type in shark.LeakTraceObject.
- The types involved
shark.LeakTraceObject→shark.LeakTraceObject.ObjectTypeshark.LeakTraceObject→shark.LeakTraceObject.Verdictshark.RealLeakTracerFactory→shark.LeakTraceObject.ObjectTypeshark.RealLeakTracerFactory→shark.LeakTraceObject.Verdict
- Direction
- shark uses shark.LeakTraceObject, so a change to shark.LeakTraceObject can break shark, while a change to shark can't break shark.LeakTraceObject.
- Position
- Below the diagonal: shark uses a module listed above it, which is the healthy direction.
24→4 shark uses shark.SharkLog✕
- Connections
- 1 pair of types, where a type in shark uses a type in shark.SharkLog.
- The types involved
shark.SharkLog→shark.SharkLog.Logger
- Direction
- shark uses shark.SharkLog, so a change to shark.SharkLog can break shark, while a change to shark can't break shark.SharkLog.
- Position
- Below the diagonal: shark uses a module listed above it, which is the healthy direction.
24→5 shark uses shark.internal.hppc✕
- Connections
- 2 pairs of types, where a type in shark uses a type in shark.internal.hppc.
- The types involved
shark.FlatteningPartitionedInstanceReferenceReader→shark.internal.hppc.LongScatterSetshark.PrioritizingShortestPathFinder→shark.internal.hppc.LongScatterSet
- Direction
- shark uses shark.internal.hppc, so a change to shark.internal.hppc can break shark, while a change to shark can't break shark.internal.hppc.
- Position
- Below the diagonal: shark uses a module listed above it, which is the healthy direction.
24→8 shark uses shark.FilteringLeakingObjectFinder✕
- Connections
- 1 pair of types, where a type in shark uses a type in shark.FilteringLeakingObjectFinder.
- The types involved
shark.FilteringLeakingObjectFinder→shark.FilteringLeakingObjectFinder.LeakingObjectFilter
- Direction
- shark uses shark.FilteringLeakingObjectFinder, so a change to shark.FilteringLeakingObjectFinder can break shark, while a change to shark can't break shark.FilteringLeakingObjectFinder.
- Position
- Below the diagonal: shark uses a module listed above it, which is the healthy direction.
24→9 shark uses shark.GcRoot✕
- Connections
- 18 pairs of types, where a type in shark uses a type in shark.GcRoot.
- The types involved
shark.HeapThread→shark.GcRoot.ThreadObjectshark.HprofHeapGraph→shark.GcRoot.ThreadObjectshark.HprofRecordReader→shark.GcRoot.Debuggershark.HprofRecordReader→shark.GcRoot.Finalizingshark.HprofRecordReader→shark.GcRoot.InternedStringshark.HprofRecordReader→shark.GcRoot.JavaFrameshark.HprofRecordReader→shark.GcRoot.JniGlobalshark.HprofRecordReader→shark.GcRoot.JniLocalshark.HprofRecordReader→shark.GcRoot.JniMonitorshark.HprofRecordReader→shark.GcRoot.MonitorUsedshark.HprofRecordReader→shark.GcRoot.NativeStackshark.HprofRecordReader→shark.GcRoot.ReferenceCleanupshark.HprofRecordReader→shark.GcRoot.StickyClassshark.HprofRecordReader→shark.GcRoot.ThreadBlockshark.HprofRecordReader→shark.GcRoot.ThreadObjectshark.HprofRecordReader→shark.GcRoot.Unknownshark.HprofRecordReader→shark.GcRoot.Unreachableshark.HprofRecordReader→shark.GcRoot.VmInternal
- Direction
- shark uses shark.GcRoot, so a change to shark.GcRoot can break shark, while a change to shark can't break shark.GcRoot.
- Position
- Below the diagonal: shark uses a module listed above it, which is the healthy direction.
24→10 shark uses shark.HprofRecord✕
- Connections
- 6 pairs of types, where a type in shark uses a type in shark.HprofRecord.
- The types involved
shark.HprofDeobfuscator→shark.HprofRecord.StringRecordshark.HprofRecordReader→shark.HprofRecord.LoadClassRecordshark.HprofRecordReader→shark.HprofRecord.StackFrameRecordshark.HprofRecordReader→shark.HprofRecord.StackTraceRecordshark.HprofRecordReader→shark.HprofRecord.StringRecordshark.HprofRecordReader→shark.HprofRecord.UnloadClassRecord
- Direction
- shark uses shark.HprofRecord, so a change to shark.HprofRecord can break shark, while a change to shark can't break shark.HprofRecord.
- Position
- Below the diagonal: shark uses a module listed above it, which is the healthy direction.
24→11 shark uses shark.HprofRecord.HeapDumpRecord.ObjectRecord.ClassDumpRecord✕
- Connections
- 3 pairs of types, where a type in shark uses a type in shark.HprofRecord.HeapDumpRecord.ObjectRecord.ClassDumpRecord.
- The types involved
shark.FieldInstanceReferenceReader→shark.HprofRecord.HeapDumpRecord.ObjectRecord.ClassDumpRecord.FieldRecordshark.HprofHeapGraph→shark.HprofRecord.HeapDumpRecord.ObjectRecord.ClassDumpRecord.FieldRecordshark.HprofHeapGraph→shark.HprofRecord.HeapDumpRecord.ObjectRecord.ClassDumpRecord.StaticFieldRecord
- Direction
- shark uses shark.HprofRecord.HeapDumpRecord.ObjectRecord.ClassDumpRecord, so a change to shark.HprofRecord.HeapDumpRecord.ObjectRecord.ClassDumpRecord can break shark, while a change to shark can't break shark.HprofRecord.HeapDumpRecord.ObjectRecord.ClassDumpRecord.
- Position
- Below the diagonal: shark uses a module listed above it, which is the healthy direction.
24→12 shark uses shark.LeakTrace✕
- Connections
- 1 pair of types, where a type in shark uses a type in shark.LeakTrace.
- The types involved
shark.LeakTrace→shark.LeakTrace.GcRootType
- Direction
- shark uses shark.LeakTrace, so a change to shark.LeakTrace can break shark, while a change to shark can't break shark.LeakTrace.
- Position
- Below the diagonal: shark uses a module listed above it, which is the healthy direction.
24→13 shark uses shark.OnAnalysisProgressListener✕
- Connections
- 1 pair of types, where a type in shark uses a type in shark.OnAnalysisProgressListener.
- The types involved
shark.OnAnalysisProgressListener→shark.OnAnalysisProgressListener.Step
- Direction
- shark uses shark.OnAnalysisProgressListener, so a change to shark.OnAnalysisProgressListener can break shark, while a change to shark can't break shark.OnAnalysisProgressListener.
- Position
- Below the diagonal: shark uses a module listed above it, which is the healthy direction.
24→16 shark uses shark.HprofRecord.HeapDumpRecord✕
- Connections
- 3 pairs of types, where a type in shark uses a type in shark.HprofRecord.HeapDumpRecord.
- The types involved
shark.HeapObject→shark.HprofRecord.HeapDumpRecord.ObjectRecordshark.HprofHeapGraph→shark.HprofRecord.HeapDumpRecord.ObjectRecordshark.HprofRecordReader→shark.HprofRecord.HeapDumpRecord.HeapDumpInfoRecord
- Direction
- shark uses shark.HprofRecord.HeapDumpRecord, so a change to shark.HprofRecord.HeapDumpRecord can break shark, while a change to shark can't break shark.HprofRecord.HeapDumpRecord.
- Position
- Below the diagonal: shark uses a module listed above it, which is the healthy direction.
24→17 shark uses shark.HprofRecord.HeapDumpRecord.ObjectRecord✕
- Connections
- 9 pairs of types, where a type in shark uses a type in shark.HprofRecord.HeapDumpRecord.ObjectRecord.
- The types involved
shark.HprofDeobfuscator→shark.HprofRecord.HeapDumpRecord.ObjectRecord.ClassDumpRecordshark.HprofHeapGraph→shark.HprofRecord.HeapDumpRecord.ObjectRecord.ClassDumpRecordshark.HprofHeapGraph→shark.HprofRecord.HeapDumpRecord.ObjectRecord.InstanceDumpRecordshark.HprofHeapGraph→shark.HprofRecord.HeapDumpRecord.ObjectRecord.ObjectArrayDumpRecordshark.HprofHeapGraph→shark.HprofRecord.HeapDumpRecord.ObjectRecord.PrimitiveArrayDumpRecordshark.HprofRecordReader→shark.HprofRecord.HeapDumpRecord.ObjectRecord.ClassDumpRecordshark.HprofRecordReader→shark.HprofRecord.HeapDumpRecord.ObjectRecord.InstanceDumpRecordshark.HprofRecordReader→shark.HprofRecord.HeapDumpRecord.ObjectRecord.ObjectArrayDumpRecordshark.HprofRecordReader→shark.HprofRecord.HeapDumpRecord.ObjectRecord.PrimitiveArrayDumpRecord
- Direction
- shark uses shark.HprofRecord.HeapDumpRecord.ObjectRecord, so a change to shark.HprofRecord.HeapDumpRecord.ObjectRecord can break shark, while a change to shark can't break shark.HprofRecord.HeapDumpRecord.ObjectRecord.
- Position
- Below the diagonal: shark uses a module listed above it, which is the healthy direction.
24→18 shark uses shark.internal✕
- Connections
- 13 pairs of types, where a type in shark uses a type in shark.internal.
- The types involved
shark.AndroidObjectSizeCalculator→shark.internal.ShallowSizeCalculatorshark.HprofHeapGraph→shark.internal.FieldValuesReadershark.HprofHeapGraph→shark.internal.HprofInMemoryIndexshark.HprofHeapGraph→shark.internal.IndexedObjectshark.HprofHeapGraph→shark.internal.LruCacheshark.HprofIndex→shark.internal.HprofInMemoryIndexshark.KeyedWeakReferenceFinder→shark.internal.KeyedWeakReferenceMirrorshark.LeakShareCalculator→shark.internal.HeapObjectIdSetshark.MapEntryReader→shark.internal.InternalSharedHashMapReferenceReadershark.PathFindingResults→shark.internal.ReferencePathNodeshark.PrioritizingShortestPathFinder→shark.internal.QueuedNodeshark.PrioritizingShortestPathFinder→shark.internal.ReferencePathNodeshark.RealLeakTracerFactory→shark.internal.ReferencePathNode
- Direction
- shark uses shark.internal, so a change to shark.internal can break shark, while a change to shark can't break shark.internal.
- Position
- Below the diagonal: shark uses a module listed above it, which is the healthy direction.
24→19 shark uses shark.internal.IndexedObject✕
- Connections
- 4 pairs of types, where a type in shark uses a type in shark.internal.IndexedObject.
- The types involved
shark.HprofHeapGraph→shark.internal.IndexedObject.IndexedClassshark.HprofHeapGraph→shark.internal.IndexedObject.IndexedInstanceshark.HprofHeapGraph→shark.internal.IndexedObject.IndexedObjectArrayshark.HprofHeapGraph→shark.internal.IndexedObject.IndexedPrimitiveArray
- Direction
- shark uses shark.internal.IndexedObject, so a change to shark.internal.IndexedObject can break shark, while a change to shark can't break shark.internal.IndexedObject.
- Position
- Below the diagonal: shark uses a module listed above it, which is the healthy direction.
24→20 shark uses shark.internal.ReferencePathNode✕
- Connections
- 1 pair of types, where a type in shark uses a type in shark.internal.ReferencePathNode.
- The types involved
shark.PrioritizingShortestPathFinder→shark.internal.ReferencePathNode.RootNode
- Direction
- shark uses shark.internal.ReferencePathNode, so a change to shark.internal.ReferencePathNode can break shark, while a change to shark can't break shark.internal.ReferencePathNode.
- Position
- Below the diagonal: shark uses a module listed above it, which is the healthy direction.
24→21 shark uses shark.HeapObject✕
- Connections
- 31 pairs of types, where a type in shark uses a type in shark.HeapObject. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
shark.AndroidObjectInspectorsKt→shark.HeapObject.HeapInstanceshark.ChainingInstanceReferenceReader→shark.HeapObject.HeapInstanceshark.ClassReferenceReader→shark.HeapObject.HeapClassshark.DelegatingObjectReferenceReader→shark.HeapObject.HeapClassshark.DelegatingObjectReferenceReader→shark.HeapObject.HeapInstanceshark.DelegatingObjectReferenceReader→shark.HeapObject.HeapObjectArrayshark.FieldInstanceReferenceReader→shark.HeapObject.HeapClassshark.FieldInstanceReferenceReader→shark.HeapObject.HeapInstanceshark.FlatteningPartitionedInstanceReferenceReader→shark.HeapObject.HeapInstanceshark.HeapField→shark.HeapObject.HeapClassshark.HeapField→shark.HeapObject.HeapInstanceshark.HeapField→shark.HeapObject.HeapObjectArrayshark.HeapField→shark.HeapObject.HeapPrimitiveArrayshark.HeapGraph→shark.HeapObject.HeapClassshark.HeapGraph→shark.HeapObject.HeapInstanceshark.HeapGraph→shark.HeapObject.HeapObjectArrayshark.HeapGraph→shark.HeapObject.HeapPrimitiveArrayshark.HeapMapEntry→shark.HeapObject.HeapInstanceshark.HeapObject→shark.HeapObject.HeapClassshark.HeapObject→shark.HeapObject.HeapInstanceshark.HeapObject→shark.HeapObject.HeapObjectArrayshark.HeapObject→shark.HeapObject.HeapPrimitiveArrayshark.HeapThread→shark.HeapObject.HeapInstanceshark.HprofHeapGraph→shark.HeapObject.HeapClassshark.HprofHeapGraph→shark.HeapObject.HeapInstance
- Direction
- shark uses shark.HeapObject, so a change to shark.HeapObject can break shark, while a change to shark can't break shark.HeapObject.
- Position
- Below the diagonal: shark uses a module listed above it, which is the healthy direction.
24→22 shark uses shark.RealLeakTracerFactory✕
- Connections
- 2 pairs of types, where a type in shark uses a type in shark.RealLeakTracerFactory.
- The types involved
shark.RealLeakTracerFactory→shark.RealLeakTracerFactory.InspectedObjectshark.RealLeakTracerFactory→shark.RealLeakTracerFactory.ShortestPath
- Direction
- shark uses shark.RealLeakTracerFactory, so a change to shark.RealLeakTracerFactory can break shark, while a change to shark can't break shark.RealLeakTracerFactory.
- Position
- Below the diagonal: shark uses a module listed above it, which is the healthy direction.
24→23 shark uses shark.ChainingInstanceReferenceReader✕
- Connections
- 3 pairs of types, where a type in shark uses a type in shark.ChainingInstanceReferenceReader.
- The types involved
shark.ChainingInstanceReferenceReader→shark.ChainingInstanceReferenceReader.VirtualInstanceReferenceReadershark.FlatteningPartitionedInstanceReferenceReader→shark.ChainingInstanceReferenceReader.VirtualInstanceReferenceReadershark.JavaLocalReferenceReader→shark.ChainingInstanceReferenceReader.VirtualInstanceReferenceReader
- Direction
- shark uses shark.ChainingInstanceReferenceReader, so a change to shark.ChainingInstanceReferenceReader can break shark, while a change to shark can't break shark.ChainingInstanceReferenceReader.
- Position
- Below the diagonal: shark uses a module listed above it, which is the healthy direction.
25→2 leakcanary.HeapAnalysisJob.Result uses leakcanary.HeapAnalysisJob✕
- Connections
- 2 pairs of types, where a type in leakcanary.HeapAnalysisJob.Result uses a type in leakcanary.HeapAnalysisJob.
- The types involved
leakcanary.HeapAnalysisJob.Result.Canceled→leakcanary.HeapAnalysisJob.Resultleakcanary.HeapAnalysisJob.Result.Done→leakcanary.HeapAnalysisJob.Result
- Direction
- leakcanary.HeapAnalysisJob.Result uses leakcanary.HeapAnalysisJob, so a change to leakcanary.HeapAnalysisJob can break leakcanary.HeapAnalysisJob.Result, while a change to leakcanary.HeapAnalysisJob.Result can't break leakcanary.HeapAnalysisJob.
- Position
- Below the diagonal: leakcanary.HeapAnalysisJob.Result uses a module listed above it, which is the healthy direction.
25→24 leakcanary.HeapAnalysisJob.Result uses shark✕
- Connections
- 1 pair of types, where a type in leakcanary.HeapAnalysisJob.Result uses a type in shark.
- The types involved
leakcanary.HeapAnalysisJob.Result.Done→shark.HeapAnalysis
- Direction
- leakcanary.HeapAnalysisJob.Result uses shark, so a change to shark can break leakcanary.HeapAnalysisJob.Result, while a change to leakcanary.HeapAnalysisJob.Result can't break shark.
- Position
- Below the diagonal: leakcanary.HeapAnalysisJob.Result uses a module listed above it, which is the healthy direction.
26→24 leakcanary.LeakCanary.Config uses shark✕
- Connections
- 4 pairs of types, where a type in leakcanary.LeakCanary.Config uses a type in shark.
- The types involved
leakcanary.LeakCanary.Config.Builder→shark.LeakingObjectFinderleakcanary.LeakCanary.Config.Builder→shark.MetadataExtractorleakcanary.LeakCanary.Config.Builder→shark.ObjectInspectorleakcanary.LeakCanary.Config.Builder→shark.ReferenceMatcher
- Direction
- leakcanary.LeakCanary.Config uses shark, so a change to shark can break leakcanary.LeakCanary.Config, while a change to leakcanary.LeakCanary.Config can't break shark.
- Position
- Below the diagonal: leakcanary.LeakCanary.Config uses a module listed above it, which is the healthy direction.
26→34 leakcanary.LeakCanary.Config uses leakcanary.LeakCanary part of a loop✕
- Connections
- 1 pair of types, where a type in leakcanary.LeakCanary.Config uses a type in leakcanary.LeakCanary.
- The types involved
leakcanary.LeakCanary.Config.Builder→leakcanary.LeakCanary.Config
- Direction
- leakcanary.LeakCanary.Config uses leakcanary.LeakCanary, so a change to leakcanary.LeakCanary can break leakcanary.LeakCanary.Config, while a change to leakcanary.LeakCanary.Config can't break leakcanary.LeakCanary.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→40 leakcanary.LeakCanary.Config uses leakcanary part of a loop✕
- Connections
- 2 pairs of types, where a type in leakcanary.LeakCanary.Config uses a type in leakcanary.
- The types involved
leakcanary.LeakCanary.Config.Builder→leakcanary.EventListenerleakcanary.LeakCanary.Config.Builder→leakcanary.HeapDumper
- Direction
- leakcanary.LeakCanary.Config uses leakcanary, so a change to leakcanary can break leakcanary.LeakCanary.Config, while a change to leakcanary.LeakCanary.Config can't break leakcanary.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
27→24 leakcanary.internal.activity.db uses shark✕
- Connections
- 2 pairs of types, where a type in leakcanary.internal.activity.db uses a type in shark.
- The types involved
leakcanary.internal.activity.db.HeapAnalysisTable→shark.HeapAnalysisleakcanary.internal.activity.db.LeakTable→shark.Leak
- Direction
- leakcanary.internal.activity.db uses shark, so a change to shark can break leakcanary.internal.activity.db, while a change to leakcanary.internal.activity.db can't break shark.
- Position
- Below the diagonal: leakcanary.internal.activity.db uses a module listed above it, which is the healthy direction.
28→21 leakcanary.internal.activity.screen uses shark.HeapObject✕
- Connections
- 4 pairs of types, where a type in leakcanary.internal.activity.screen uses a type in shark.HeapObject.
- The types involved
leakcanary.internal.activity.screen.HprofExplorerScreen→shark.HeapObject.HeapClassleakcanary.internal.activity.screen.HprofExplorerScreen→shark.HeapObject.HeapInstanceleakcanary.internal.activity.screen.HprofExplorerScreen→shark.HeapObject.HeapObjectArrayleakcanary.internal.activity.screen.HprofExplorerScreen→shark.HeapObject.HeapPrimitiveArray
- Direction
- leakcanary.internal.activity.screen uses shark.HeapObject, so a change to shark.HeapObject can break leakcanary.internal.activity.screen, while a change to leakcanary.internal.activity.screen can't break shark.HeapObject.
- Position
- Below the diagonal: leakcanary.internal.activity.screen uses a module listed above it, which is the healthy direction.
28→24 leakcanary.internal.activity.screen uses shark✕
- Connections
- 6 pairs of types, where a type in leakcanary.internal.activity.screen uses a type in shark.
- The types involved
leakcanary.internal.activity.screen.HeapAnalysisFailureScreen→shark.HeapAnalysisFailureleakcanary.internal.activity.screen.HeapDumpScreen→shark.HeapAnalysisSuccessleakcanary.internal.activity.screen.HprofExplorerScreen→shark.HeapFieldleakcanary.internal.activity.screen.HprofExplorerScreen→shark.HeapValueleakcanary.internal.activity.screen.LeakScreen→shark.HeapAnalysisSuccessleakcanary.internal.activity.screen.LeakScreen→shark.LeakTrace
- Direction
- leakcanary.internal.activity.screen uses shark, so a change to shark can break leakcanary.internal.activity.screen, while a change to leakcanary.internal.activity.screen can't break shark.
- Position
- Below the diagonal: leakcanary.internal.activity.screen uses a module listed above it, which is the healthy direction.
29→24 org.leakcanary.data uses shark✕
- Connections
- 1 pair of types, where a type in org.leakcanary.data uses a type in shark.
- The types involved
org.leakcanary.data.HeapRepository→shark.HeapAnalysis
- Direction
- org.leakcanary.data uses shark, so a change to shark can break org.leakcanary.data, while a change to org.leakcanary.data can't break shark.
- Position
- Below the diagonal: org.leakcanary.data uses a module listed above it, which is the healthy direction.
30→21 shark.AndroidReferenceReaders uses shark.HeapObject✕
- Connections
- 1 pair of types, where a type in shark.AndroidReferenceReaders uses a type in shark.HeapObject.
- The types involved
shark.AndroidReferenceReaders.Companion→shark.HeapObject.HeapInstance
- Direction
- shark.AndroidReferenceReaders uses shark.HeapObject, so a change to shark.HeapObject can break shark.AndroidReferenceReaders, while a change to shark.AndroidReferenceReaders can't break shark.HeapObject.
- Position
- Below the diagonal: shark.AndroidReferenceReaders uses a module listed above it, which is the healthy direction.
30→23 shark.AndroidReferenceReaders uses shark.ChainingInstanceReferenceReader✕
- Connections
- 5 pairs of types, where a type in shark.AndroidReferenceReaders uses a type in shark.ChainingInstanceReferenceReader.
- The types involved
shark.AndroidReferenceReaders.ACTIVITY_THREAD__NEW_ACTIVITIES→shark.ChainingInstanceReferenceReader.VirtualInstanceReferenceReadershark.AndroidReferenceReaders.ANIMATOR_WEAK_REF_SUCKS→shark.ChainingInstanceReferenceReader.VirtualInstanceReferenceReadershark.AndroidReferenceReaders.ARRAY_SET→shark.ChainingInstanceReferenceReader.VirtualInstanceReferenceReadershark.AndroidReferenceReaders.MESSAGE_QUEUE→shark.ChainingInstanceReferenceReader.VirtualInstanceReferenceReadershark.AndroidReferenceReaders.SAFE_ITERABLE_MAP→shark.ChainingInstanceReferenceReader.VirtualInstanceReferenceReader
- Direction
- shark.AndroidReferenceReaders uses shark.ChainingInstanceReferenceReader, so a change to shark.ChainingInstanceReferenceReader can break shark.AndroidReferenceReaders, while a change to shark.AndroidReferenceReaders can't break shark.ChainingInstanceReferenceReader.
- Position
- Below the diagonal: shark.AndroidReferenceReaders uses a module listed above it, which is the healthy direction.
30→24 shark.AndroidReferenceReaders uses shark✕
- Connections
- 10 pairs of types, where a type in shark.AndroidReferenceReaders uses a type in shark.
- The types involved
shark.AndroidReferenceReaders.ACTIVITY_THREAD__NEW_ACTIVITIES→shark.AndroidReferenceReadersshark.AndroidReferenceReaders.ACTIVITY_THREAD__NEW_ACTIVITIES→shark.HeapGraphshark.AndroidReferenceReaders.ANIMATOR_WEAK_REF_SUCKS→shark.AndroidReferenceReadersshark.AndroidReferenceReaders.ANIMATOR_WEAK_REF_SUCKS→shark.HeapGraphshark.AndroidReferenceReaders.ARRAY_SET→shark.AndroidReferenceReadersshark.AndroidReferenceReaders.ARRAY_SET→shark.HeapGraphshark.AndroidReferenceReaders.MESSAGE_QUEUE→shark.AndroidReferenceReadersshark.AndroidReferenceReaders.MESSAGE_QUEUE→shark.HeapGraphshark.AndroidReferenceReaders.SAFE_ITERABLE_MAP→shark.AndroidReferenceReadersshark.AndroidReferenceReaders.SAFE_ITERABLE_MAP→shark.HeapGraph
- Direction
- shark.AndroidReferenceReaders uses shark, so a change to shark can break shark.AndroidReferenceReaders, while a change to shark.AndroidReferenceReaders can't break shark.
- Position
- Below the diagonal: shark.AndroidReferenceReaders uses a module listed above it, which is the healthy direction.
31→5 shark.PrioritizingShortestPathFinder uses shark.internal.hppc✕
- Connections
- 3 pairs of types, where a type in shark.PrioritizingShortestPathFinder uses a type in shark.internal.hppc.
- The types involved
shark.PrioritizingShortestPathFinder.Phase2→shark.internal.hppc.LongDequeshark.PrioritizingShortestPathFinder.Phase2→shark.internal.hppc.LongScatterSetshark.PrioritizingShortestPathFinder.State→shark.internal.hppc.LongScatterSet
- Direction
- shark.PrioritizingShortestPathFinder uses shark.internal.hppc, so a change to shark.internal.hppc can break shark.PrioritizingShortestPathFinder, while a change to shark.PrioritizingShortestPathFinder can't break shark.internal.hppc.
- Position
- Below the diagonal: shark.PrioritizingShortestPathFinder uses a module listed above it, which is the healthy direction.
31→18 shark.PrioritizingShortestPathFinder uses shark.internal✕
- Connections
- 3 pairs of types, where a type in shark.PrioritizingShortestPathFinder uses a type in shark.internal.
- The types involved
shark.PrioritizingShortestPathFinder.Phase2→shark.internal.HeapObjectIdSetshark.PrioritizingShortestPathFinder.State→shark.internal.HeapObjectIdSetshark.PrioritizingShortestPathFinder.State→shark.internal.QueuedNode
- Direction
- shark.PrioritizingShortestPathFinder uses shark.internal, so a change to shark.internal can break shark.PrioritizingShortestPathFinder, while a change to shark.PrioritizingShortestPathFinder can't break shark.internal.
- Position
- Below the diagonal: shark.PrioritizingShortestPathFinder uses a module listed above it, which is the healthy direction.
31→24 shark.PrioritizingShortestPathFinder uses shark✕
- Connections
- 6 pairs of types, where a type in shark.PrioritizingShortestPathFinder uses a type in shark.
- The types involved
shark.PrioritizingShortestPathFinder.Factory→shark.GcRootProvidershark.PrioritizingShortestPathFinder.Factory→shark.HeapGraphshark.PrioritizingShortestPathFinder.Factory→shark.HeapObjectshark.PrioritizingShortestPathFinder.Factory→shark.ShortestPathFindershark.PrioritizingShortestPathFinder.Phase2→shark.Retainedshark.PrioritizingShortestPathFinder.State→shark.HeapGraph
- Direction
- shark.PrioritizingShortestPathFinder uses shark, so a change to shark can break shark.PrioritizingShortestPathFinder, while a change to shark.PrioritizingShortestPathFinder can't break shark.
- Position
- Below the diagonal: shark.PrioritizingShortestPathFinder uses a module listed above it, which is the healthy direction.
32→4 shark.dive uses shark.SharkLog✕
- Connections
- 1 pair of types, where a type in shark.dive uses a type in shark.SharkLog.
- The types involved
shark.dive.SessionLog→shark.SharkLog.Logger
- Direction
- shark.dive uses shark.SharkLog, so a change to shark.SharkLog can break shark.dive, while a change to shark.dive can't break shark.SharkLog.
- Position
- Below the diagonal: shark.dive uses a module listed above it, which is the healthy direction.
32→12 shark.dive uses shark.LeakTrace✕
- Connections
- 5 pairs of types, where a type in shark.dive uses a type in shark.LeakTrace.
- The types involved
shark.dive.GcRootReferrer→shark.LeakTrace.GcRootTypeshark.dive.IndependentPath→shark.LeakTrace.GcRootTypeshark.dive.LeakFingerprintKt→shark.LeakTrace.GcRootTypeshark.dive.RootPath→shark.LeakTrace.GcRootTypeshark.dive.RootPathWay→shark.LeakTrace.GcRootType
- Direction
- shark.dive uses shark.LeakTrace, so a change to shark.LeakTrace can break shark.dive, while a change to shark.dive can't break shark.LeakTrace.
- Position
- Below the diagonal: shark.dive uses a module listed above it, which is the healthy direction.
32→14 shark.dive uses shark.dive.HeapBitmaps✕
- Connections
- 1 pair of types, where a type in shark.dive uses a type in shark.dive.HeapBitmaps.
- The types involved
shark.dive.HeapBitmaps→shark.dive.HeapBitmaps.PointerImages
- Direction
- shark.dive uses shark.dive.HeapBitmaps, so a change to shark.dive.HeapBitmaps can break shark.dive, while a change to shark.dive can't break shark.dive.HeapBitmaps.
- Position
- Below the diagonal: shark.dive uses a module listed above it, which is the healthy direction.
32→21 shark.dive uses shark.HeapObject✕
- Connections
- 7 pairs of types, where a type in shark.dive uses a type in shark.HeapObject.
- The types involved
shark.dive.CachedMapValues→shark.HeapObject.HeapInstanceshark.dive.HeapBitmaps→shark.HeapObject.HeapClassshark.dive.OwnerReferences→shark.HeapObject.HeapClassshark.dive.ReferenceStrengthReader→shark.HeapObject.HeapClassshark.dive.ReferenceStrengthReader→shark.HeapObject.HeapInstanceshark.dive.RunningActivityReferenceReader→shark.HeapObject.HeapInstanceshark.dive.SlotTableReferenceReader→shark.HeapObject.HeapInstance
- Direction
- shark.dive uses shark.HeapObject, so a change to shark.HeapObject can break shark.dive, while a change to shark.dive can't break shark.HeapObject.
- Position
- Below the diagonal: shark.dive uses a module listed above it, which is the healthy direction.
32→23 shark.dive uses shark.ChainingInstanceReferenceReader✕
- Connections
- 1 pair of types, where a type in shark.dive uses a type in shark.ChainingInstanceReferenceReader.
- The types involved
shark.dive.DataStructureReferenceReader→shark.ChainingInstanceReferenceReader.VirtualInstanceReferenceReader
- Direction
- shark.dive uses shark.ChainingInstanceReferenceReader, so a change to shark.ChainingInstanceReferenceReader can break shark.dive, while a change to shark.dive can't break shark.ChainingInstanceReferenceReader.
- Position
- Below the diagonal: shark.dive uses a module listed above it, which is the healthy direction.
32→24 shark.dive uses shark✕
- Connections
- 58 pairs of types, where a type in shark.dive uses a type in shark. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
shark.dive.CachedMapValues→shark.HeapGraphshark.dive.CachedMapValues→shark.HeapObjectshark.dive.CachedMapValues→shark.MapEntryReadershark.dive.DataStructureReferenceReader→shark.HeapGraphshark.dive.DataStructureReferenceReader→shark.HeapObjectshark.dive.DataStructureReferenceReader→shark.Referenceshark.dive.EveryReferenceReader→shark.HeapObjectshark.dive.EveryReferenceReader→shark.Referenceshark.dive.EveryReferenceReader→shark.ReferenceReadershark.dive.HeapBitmaps→shark.HeapGraphshark.dive.HeapBitmaps→shark.HeapObjectshark.dive.HeapDive→shark.CloseableHeapGraphshark.dive.HeapDominatorTreemap→shark.GcRootshark.dive.HeapDominatorTreemap→shark.HeapDominatorTreeshark.dive.HeapDominatorTreemap→shark.HeapGraphshark.dive.HeapDominatorTreemap→shark.HeapObjectshark.dive.HeapDominatorTreemap→shark.HeapValueshark.dive.HeapDominatorTreemap→shark.ObjectReportershark.dive.HeapDominatorTreemap→shark.ReferenceReadershark.dive.HeapReachability→shark.HeapGraphshark.dive.HeapReachability→shark.HeapObjectshark.dive.LayoutNodeChildReferenceReader→shark.HeapGraphshark.dive.LayoutNodeChildReferenceReader→shark.HeapObjectshark.dive.LayoutNodeChildReferenceReader→shark.Referenceshark.dive.LeakFingerprintKt→shark.LeakTrace
- Direction
- shark.dive uses shark, so a change to shark can break shark.dive, while a change to shark.dive can't break shark.
- Position
- Below the diagonal: shark.dive uses a module listed above it, which is the healthy direction.
33→5 shark.internal.HprofInMemoryIndex uses shark.internal.hppc✕
- Connections
- 3 pairs of types, where a type in shark.internal.HprofInMemoryIndex uses a type in shark.internal.hppc.
- The types involved
shark.internal.HprofInMemoryIndex.Builder→shark.internal.hppc.LongLongScatterMapshark.internal.HprofInMemoryIndex.Builder→shark.internal.hppc.LongObjectScatterMapshark.internal.HprofInMemoryIndex.Builder→shark.internal.hppc.LongScatterSet
- Direction
- shark.internal.HprofInMemoryIndex uses shark.internal.hppc, so a change to shark.internal.hppc can break shark.internal.HprofInMemoryIndex, while a change to shark.internal.HprofInMemoryIndex can't break shark.internal.hppc.
- Position
- Below the diagonal: shark.internal.HprofInMemoryIndex uses a module listed above it, which is the healthy direction.
33→9 shark.internal.HprofInMemoryIndex uses shark.GcRoot✕
- Connections
- 1 pair of types, where a type in shark.internal.HprofInMemoryIndex uses a type in shark.GcRoot.
- The types involved
shark.internal.HprofInMemoryIndex.Builder→shark.GcRoot.ThreadObject
- Direction
- shark.internal.HprofInMemoryIndex uses shark.GcRoot, so a change to shark.GcRoot can break shark.internal.HprofInMemoryIndex, while a change to shark.internal.HprofInMemoryIndex can't break shark.GcRoot.
- Position
- Below the diagonal: shark.internal.HprofInMemoryIndex uses a module listed above it, which is the healthy direction.
33→10 shark.internal.HprofInMemoryIndex uses shark.HprofRecord✕
- Connections
- 2 pairs of types, where a type in shark.internal.HprofInMemoryIndex uses a type in shark.HprofRecord.
- The types involved
shark.internal.HprofInMemoryIndex.Builder→shark.HprofRecord.StackFrameRecordshark.internal.HprofInMemoryIndex.Builder→shark.HprofRecord.StackTraceRecord
- Direction
- shark.internal.HprofInMemoryIndex uses shark.HprofRecord, so a change to shark.HprofRecord can break shark.internal.HprofInMemoryIndex, while a change to shark.internal.HprofInMemoryIndex can't break shark.HprofRecord.
- Position
- Below the diagonal: shark.internal.HprofInMemoryIndex uses a module listed above it, which is the healthy direction.
33→18 shark.internal.HprofInMemoryIndex uses shark.internal✕
- Connections
- 4 pairs of types, where a type in shark.internal.HprofInMemoryIndex uses a type in shark.internal.
- The types involved
shark.internal.HprofInMemoryIndex.Builder→shark.internal.HprofInMemoryIndexshark.internal.HprofInMemoryIndex.Builder→shark.internal.ObjectIdEncodingshark.internal.HprofInMemoryIndex.Builder→shark.internal.SortedBytesMapBuildershark.internal.HprofInMemoryIndex.Companion→shark.internal.HprofInMemoryIndex
- Direction
- shark.internal.HprofInMemoryIndex uses shark.internal, so a change to shark.internal can break shark.internal.HprofInMemoryIndex, while a change to shark.internal.HprofInMemoryIndex can't break shark.internal.
- Position
- Below the diagonal: shark.internal.HprofInMemoryIndex uses a module listed above it, which is the healthy direction.
33→24 shark.internal.HprofInMemoryIndex uses shark✕
- Connections
- 12 pairs of types, where a type in shark.internal.HprofInMemoryIndex uses a type in shark.
- The types involved
shark.internal.HprofInMemoryIndex.Builder→shark.CancelSignalshark.internal.HprofInMemoryIndex.Builder→shark.GcRootshark.internal.HprofInMemoryIndex.Builder→shark.HprofHeadershark.internal.HprofInMemoryIndex.Builder→shark.HprofRecordReadershark.internal.HprofInMemoryIndex.Builder→shark.HprofRecordTagshark.internal.HprofInMemoryIndex.Builder→shark.OnHprofRecordTagListenershark.internal.HprofInMemoryIndex.Builder→shark.ProguardMappingshark.internal.HprofInMemoryIndex.Companion→shark.CancelSignalshark.internal.HprofInMemoryIndex.Companion→shark.HprofHeadershark.internal.HprofInMemoryIndex.Companion→shark.HprofRecordTagshark.internal.HprofInMemoryIndex.Companion→shark.ProguardMappingshark.internal.HprofInMemoryIndex.Companion→shark.StreamingHprofReader
- Direction
- shark.internal.HprofInMemoryIndex uses shark, so a change to shark can break shark.internal.HprofInMemoryIndex, while a change to shark.internal.HprofInMemoryIndex can't break shark.
- Position
- Below the diagonal: shark.internal.HprofInMemoryIndex uses a module listed above it, which is the healthy direction.
34→24 leakcanary.LeakCanary uses shark✕
- Connections
- 4 pairs of types, where a type in leakcanary.LeakCanary uses a type in shark.
- The types involved
leakcanary.LeakCanary.Config→shark.LeakingObjectFinderleakcanary.LeakCanary.Config→shark.MetadataExtractorleakcanary.LeakCanary.Config→shark.ObjectInspectorleakcanary.LeakCanary.Config→shark.ReferenceMatcher
- Direction
- leakcanary.LeakCanary uses shark, so a change to shark can break leakcanary.LeakCanary, while a change to leakcanary.LeakCanary can't break shark.
- Position
- Below the diagonal: leakcanary.LeakCanary uses a module listed above it, which is the healthy direction.
34→26 leakcanary.LeakCanary uses leakcanary.LeakCanary.Config✕
- Connections
- 1 pair of types, where a type in leakcanary.LeakCanary uses a type in leakcanary.LeakCanary.Config.
- The types involved
leakcanary.LeakCanary.Config→leakcanary.LeakCanary.Config.Builder
- Direction
- leakcanary.LeakCanary uses leakcanary.LeakCanary.Config, so a change to leakcanary.LeakCanary.Config can break leakcanary.LeakCanary, while a change to leakcanary.LeakCanary can't break leakcanary.LeakCanary.Config.
- Position
- Below the diagonal: leakcanary.LeakCanary uses a module listed above it, which is the healthy direction.
34→40 leakcanary.LeakCanary uses leakcanary part of a loop✕
- Connections
- 2 pairs of types, where a type in leakcanary.LeakCanary uses a type in leakcanary.
- The types involved
leakcanary.LeakCanary.Config→leakcanary.EventListenerleakcanary.LeakCanary.Config→leakcanary.HeapDumper
- Direction
- leakcanary.LeakCanary uses leakcanary, so a change to leakcanary can break leakcanary.LeakCanary, while a change to leakcanary.LeakCanary can't break leakcanary.
- 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.
35→24 org.leakcanary.screens uses shark✕
- Connections
- 7 pairs of types, where a type in org.leakcanary.screens uses a type in shark.
- The types involved
org.leakcanary.screens.AnalysisDetails→shark.HeapAnalysisSuccessorg.leakcanary.screens.ClientAppAnalysisScreenKt→shark.Leakorg.leakcanary.screens.ClientAppAnalysisViewModel→shark.HeapAnalysisSuccessorg.leakcanary.screens.ClientAppAnalysisViewModel→shark.Leakorg.leakcanary.screens.LeakData→shark.HeapAnalysisSuccessorg.leakcanary.screens.LeakData→shark.Leakorg.leakcanary.screens.LeakScreenKt→shark.LeakTraceObject
- Direction
- org.leakcanary.screens uses shark, so a change to shark can break org.leakcanary.screens, while a change to org.leakcanary.screens can't break shark.
- Position
- Below the diagonal: org.leakcanary.screens uses a module listed above it, which is the healthy direction.
35→29 org.leakcanary.screens uses org.leakcanary.data✕
- Connections
- 4 pairs of types, where a type in org.leakcanary.screens uses a type in org.leakcanary.data.
- The types involved
org.leakcanary.screens.ClientAppAnalysesViewModel→org.leakcanary.data.HeapRepositoryorg.leakcanary.screens.ClientAppAnalysisViewModel→org.leakcanary.data.HeapRepositoryorg.leakcanary.screens.ClientAppsViewModel→org.leakcanary.data.HeapRepositoryorg.leakcanary.screens.LeakViewModel→org.leakcanary.data.HeapRepository
- Direction
- org.leakcanary.screens uses org.leakcanary.data, so a change to org.leakcanary.data can break org.leakcanary.screens, while a change to org.leakcanary.screens can't break org.leakcanary.data.
- Position
- Below the diagonal: org.leakcanary.screens uses a module listed above it, which is the healthy direction.
36→32 shark.dive.agent uses shark.dive✕
- Connections
- 36 pairs of types, where a type in shark.dive.agent uses a type in shark.dive. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
shark.dive.agent.AgentHeapDump→shark.dive.HeapDiveshark.dive.agent.AgentHeapDump→shark.dive.HeapSizesshark.dive.agent.AgentHeapDump→shark.dive.Placeshark.dive.agent.AgentHeapDump→shark.dive.VerdictOverrideshark.dive.agent.AgentHeapDump→shark.dive.VerdictOverridesshark.dive.agent.AgentHeapDumps→shark.dive.AndroidDeviceshark.dive.agent.AgentHeapDumps→shark.dive.DeviceProcessshark.dive.agent.AgentJson→shark.dive.AndroidDeviceshark.dive.agent.AgentJson→shark.dive.DeviceProcessshark.dive.agent.AgentJson→shark.dive.DominatorOutlineshark.dive.agent.AgentJson→shark.dive.HeapLeaksshark.dive.agent.AgentJson→shark.dive.HeapObjectSummaryshark.dive.agent.AgentJson→shark.dive.HeapSizesshark.dive.agent.AgentJson→shark.dive.IndependentPathsshark.dive.agent.AgentJson→shark.dive.ObjectContentshark.dive.agent.AgentJson→shark.dive.ObjectDominatorshark.dive.agent.AgentJson→shark.dive.ObjectListshark.dive.agent.AgentJson→shark.dive.ObjectListEntryshark.dive.agent.AgentJson→shark.dive.ObjectReferrersshark.dive.agent.AgentJson→shark.dive.PathReferenceshark.dive.agent.AgentJson→shark.dive.PathStepshark.dive.agent.AgentJson→shark.dive.RootPathshark.dive.agent.AgentJson→shark.dive.RootPathStepshark.dive.agent.AgentJson→shark.dive.VerdictOverridesshark.dive.agent.AgentPlaceKt→shark.dive.Place
- Direction
- shark.dive.agent uses shark.dive, so a change to shark.dive can break shark.dive.agent, while a change to shark.dive.agent can't break shark.dive.
- Position
- Below the diagonal: shark.dive.agent uses a module listed above it, which is the healthy direction.
37→1 leakcanary.internal uses leakcanary.EventListener✕
- Connections
- 1 pair of types, where a type in leakcanary.internal uses a type in leakcanary.EventListener.
- The types involved
leakcanary.internal.InternalLeakCanary→leakcanary.EventListener.Event
- Direction
- leakcanary.internal uses leakcanary.EventListener, so a change to leakcanary.EventListener can break leakcanary.internal, while a change to leakcanary.internal can't break leakcanary.EventListener.
- Position
- Below the diagonal: leakcanary.internal uses a module listed above it, which is the healthy direction.
37→2 leakcanary.internal uses leakcanary.HeapAnalysisJob✕
- Connections
- 1 pair of types, where a type in leakcanary.internal uses a type in leakcanary.HeapAnalysisJob.
- The types involved
leakcanary.internal.RealHeapAnalysisJob→leakcanary.HeapAnalysisJob.Result
- Direction
- leakcanary.internal uses leakcanary.HeapAnalysisJob, so a change to leakcanary.HeapAnalysisJob can break leakcanary.internal, while a change to leakcanary.internal can't break leakcanary.HeapAnalysisJob.
- Position
- Below the diagonal: leakcanary.internal uses a module listed above it, which is the healthy direction.
37→6 leakcanary.internal uses leakcanary.HeapAnalysisInterceptor✕
- Connections
- 1 pair of types, where a type in leakcanary.internal uses a type in leakcanary.HeapAnalysisInterceptor.
- The types involved
leakcanary.internal.RealHeapAnalysisJob→leakcanary.HeapAnalysisInterceptor.Chain
- Direction
- leakcanary.internal uses leakcanary.HeapAnalysisInterceptor, so a change to leakcanary.HeapAnalysisInterceptor can break leakcanary.internal, while a change to leakcanary.internal can't break leakcanary.HeapAnalysisInterceptor.
- Position
- Below the diagonal: leakcanary.internal uses a module listed above it, which is the healthy direction.
37→13 leakcanary.internal uses shark.OnAnalysisProgressListener✕
- Connections
- 1 pair of types, where a type in leakcanary.internal uses a type in shark.OnAnalysisProgressListener.
- The types involved
leakcanary.internal.RealHeapAnalysisJob→shark.OnAnalysisProgressListener.Step
- Direction
- leakcanary.internal uses shark.OnAnalysisProgressListener, so a change to shark.OnAnalysisProgressListener can break leakcanary.internal, while a change to leakcanary.internal can't break shark.OnAnalysisProgressListener.
- Position
- Below the diagonal: leakcanary.internal uses a module listed above it, which is the healthy direction.
37→15 leakcanary.internal uses leakcanary.EventListener.Event✕
- Connections
- 3 pairs of types, where a type in leakcanary.internal uses a type in leakcanary.EventListener.Event.
- The types involved
leakcanary.internal.AndroidDebugHeapAnalyzer→leakcanary.EventListener.Event.HeapAnalysisDoneleakcanary.internal.AndroidDebugHeapAnalyzer→leakcanary.EventListener.Event.HeapAnalysisProgressleakcanary.internal.AndroidDebugHeapAnalyzer→leakcanary.EventListener.Event.HeapDump
- Direction
- leakcanary.internal uses leakcanary.EventListener.Event, so a change to leakcanary.EventListener.Event can break leakcanary.internal, while a change to leakcanary.internal can't break leakcanary.EventListener.Event.
- Position
- Below the diagonal: leakcanary.internal uses a module listed above it, which is the healthy direction.
37→24 leakcanary.internal uses shark✕
- Connections
- 16 pairs of types, where a type in leakcanary.internal uses a type in shark.
- The types involved
leakcanary.internal.AndroidDebugHeapAnalyzer→shark.CancelSignalleakcanary.internal.AndroidDebugHeapAnalyzer→shark.HeapAnalysisleakcanary.internal.AndroidDebugHeapAnalyzer→shark.HeapAnalysisFailureleakcanary.internal.AndroidDebugHeapAnalyzer→shark.OnAnalysisProgressListenerleakcanary.internal.DisplayLeakAdapter→shark.LeakTraceleakcanary.internal.InstrumentationHeapAnalyzer→shark.HeapAnalysisleakcanary.internal.InstrumentationHeapAnalyzer→shark.LeakingObjectFinderleakcanary.internal.InstrumentationHeapAnalyzer→shark.MetadataExtractorleakcanary.internal.InstrumentationHeapAnalyzer→shark.ObjectInspectorleakcanary.internal.InstrumentationHeapAnalyzer→shark.ProguardMappingleakcanary.internal.InstrumentationHeapAnalyzer→shark.ReferenceMatcherleakcanary.internal.OutOfMemoryGuidanceKt→shark.HeapAnalysisFailureleakcanary.internal.RealHeapAnalysisJob→shark.CancelSignalleakcanary.internal.RealHeapAnalysisJob→shark.CloseableHeapGraphleakcanary.internal.RealHeapAnalysisJob→shark.HeapAnalysisleakcanary.internal.RetryingHeapAnalyzer→shark.HeapAnalysis
- Direction
- leakcanary.internal uses shark, so a change to shark can break leakcanary.internal, while a change to leakcanary.internal can't break shark.
- Position
- Below the diagonal: leakcanary.internal uses a module listed above it, which is the healthy direction.
37→25 leakcanary.internal uses leakcanary.HeapAnalysisJob.Result✕
- Connections
- 2 pairs of types, where a type in leakcanary.internal uses a type in leakcanary.HeapAnalysisJob.Result.
- The types involved
leakcanary.internal.RealHeapAnalysisJob→leakcanary.HeapAnalysisJob.Result.Canceledleakcanary.internal.RealHeapAnalysisJob→leakcanary.HeapAnalysisJob.Result.Done
- Direction
- leakcanary.internal uses leakcanary.HeapAnalysisJob.Result, so a change to leakcanary.HeapAnalysisJob.Result can break leakcanary.internal, while a change to leakcanary.internal can't break leakcanary.HeapAnalysisJob.Result.
- Position
- Below the diagonal: leakcanary.internal uses a module listed above it, which is the healthy direction.
37→34 leakcanary.internal uses leakcanary.LeakCanary✕
- Connections
- 1 pair of types, where a type in leakcanary.internal uses a type in leakcanary.LeakCanary.
- The types involved
leakcanary.internal.HeapDumpTrigger→leakcanary.LeakCanary.Config
- Direction
- leakcanary.internal uses leakcanary.LeakCanary, so a change to leakcanary.LeakCanary can break leakcanary.internal, while a change to leakcanary.internal can't break leakcanary.LeakCanary.
- Position
- Below the diagonal: leakcanary.internal uses a module listed above it, which is the healthy direction.
37→40 leakcanary.internal uses leakcanary part of a loop✕
- Connections
- 11 pairs of types, where a type in leakcanary.internal uses a type in leakcanary.
- The types involved
leakcanary.internal.AndroidOFragmentDestroyWatcher→leakcanary.DeletableObjectReporterleakcanary.internal.AndroidXFragmentDestroyWatcher→leakcanary.DeletableObjectReporterleakcanary.internal.BackgroundListener→leakcanary.ProcessInfoleakcanary.internal.HeapDumpTrigger→leakcanary.GcTriggerleakcanary.internal.HeapDumpTrigger→leakcanary.RetainedObjectTrackerleakcanary.internal.InternalLeakCanary→leakcanary.OnObjectRetainedListenerleakcanary.internal.RealHeapAnalysisJob→leakcanary.HeapAnalysisConfigleakcanary.internal.RealHeapAnalysisJob→leakcanary.HeapAnalysisInterceptorleakcanary.internal.RealHeapAnalysisJob→leakcanary.HeapAnalysisJobleakcanary.internal.RealHeapAnalysisJob→leakcanary.JobContextleakcanary.internal.ViewModelClearedWatcher→leakcanary.DeletableObjectReporter
- Direction
- leakcanary.internal uses leakcanary, so a change to leakcanary can break leakcanary.internal, while a change to leakcanary.internal can't break leakcanary.
- 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.
38→4 shark.dive.app uses shark.SharkLog✕
- Connections
- 2 pairs of types, where a type in shark.dive.app uses a type in shark.SharkLog.
- The types involved
shark.dive.app.Loggers→shark.SharkLog.Loggershark.dive.app.StreamLogger→shark.SharkLog.Logger
- Direction
- shark.dive.app uses shark.SharkLog, so a change to shark.SharkLog can break shark.dive.app, while a change to shark.dive.app can't break shark.SharkLog.
- Position
- Below the diagonal: shark.dive.app uses a module listed above it, which is the healthy direction.
38→24 shark.dive.app uses shark✕
- Connections
- 1 pair of types, where a type in shark.dive.app uses a type in shark.
- The types involved
shark.dive.app.ReadInFlight→shark.CancelSignal
- Direction
- shark.dive.app uses shark, so a change to shark can break shark.dive.app, while a change to shark.dive.app can't break shark.
- Position
- Below the diagonal: shark.dive.app uses a module listed above it, which is the healthy direction.
38→32 shark.dive.app uses shark.dive✕
- Connections
- 146 pairs of types, where a type in shark.dive.app uses a type in shark.dive. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
shark.dive.app.AgentLogsScreenKt→shark.dive.Placeshark.dive.app.BitmapsFromDeviceDialogKt→shark.dive.AndroidDeviceshark.dive.app.BitmapsFromDeviceDialogKt→shark.dive.BitmapCountsshark.dive.app.BitmapsFromDeviceDialogKt→shark.dive.DeviceHeapDumpsshark.dive.app.BitmapsFromDeviceDialogKt→shark.dive.DeviceProcessshark.dive.app.BitmapsFromDeviceDialogKt→shark.dive.HeapDumpOriginshark.dive.app.BitmapsFromDeviceDialogKt→shark.dive.NativeBitmapPixelsshark.dive.app.CellColoring→shark.dive.ReachabilityStrengthshark.dive.app.CellColors→shark.dive.PresentedCellshark.dive.app.CellColors→shark.dive.ReachabilityStrengthshark.dive.app.CellColorsKt→shark.dive.ReachabilityStrengthshark.dive.app.CellViewKt→shark.dive.CellContentshark.dive.app.DeepLinkPeers→shark.dive.DeepLinkshark.dive.app.DetailsPanelKt→shark.dive.HeapObjectSummaryshark.dive.app.DetailsPanelKt→shark.dive.ObjectGroupSummaryshark.dive.app.DetailsPanelKt→shark.dive.ReachabilityStrengthshark.dive.app.DetailsPanelKt→shark.dive.Topicshark.dive.app.DeviceCandidate→shark.dive.AndroidDeviceshark.dive.app.DeviceCandidate→shark.dive.DeviceMatchshark.dive.app.DeviceCandidate→shark.dive.DeviceProcessshark.dive.app.DiveAgentsKt→shark.dive.DeviceHeapDumpsshark.dive.app.DiveArguments→shark.dive.DeepLinkshark.dive.app.DiveHeapDumpPathsKt→shark.dive.HeapDumpPathsshark.dive.app.DiveLoggingKt→shark.dive.SessionLogshark.dive.app.DiveWindow→shark.dive.NativeBitmapPixels
- Direction
- shark.dive.app uses shark.dive, so a change to shark.dive can break shark.dive.app, while a change to shark.dive.app can't break shark.dive.
- Position
- Below the diagonal: shark.dive.app uses a module listed above it, which is the healthy direction.
38→36 shark.dive.app uses shark.dive.agent✕
- Connections
- 10 pairs of types, where a type in shark.dive.app uses a type in shark.dive.agent.
- The types involved
shark.dive.app.AgentLogsScreenKt→shark.dive.agent.AgentSessionshark.dive.app.AgentLogsScreenKt→shark.dive.agent.AgentSessionCallshark.dive.app.DiveAgentsKt→shark.dive.agent.AgentHeapDumpshark.dive.app.DiveAgentsKt→shark.dive.agent.AgentSessionshark.dive.app.HeapDumpDiveKt→shark.dive.agent.AgentSessionshark.dive.app.HeapDumpSessions→shark.dive.agent.AgentSessionshark.dive.app.MainKt→shark.dive.agent.AgentSessionshark.dive.app.OpenAgentHeapDump→shark.dive.agent.AgentHeapDumpshark.dive.app.WindowAgentHeapDumps→shark.dive.agent.AgentHeapDumpshark.dive.app.WindowAgentHeapDumps→shark.dive.agent.AgentHeapDumps
- Direction
- shark.dive.app uses shark.dive.agent, so a change to shark.dive.agent can break shark.dive.app, while a change to shark.dive.app can't break shark.dive.agent.
- Position
- Below the diagonal: shark.dive.app uses a module listed above it, which is the healthy direction.
39→32 shark.dive.eval uses shark.dive✕
- Connections
- 1 pair of types, where a type in shark.dive.eval uses a type in shark.dive.
- The types involved
shark.dive.eval.EvalScenario→shark.dive.Verdict
- Direction
- shark.dive.eval uses shark.dive, so a change to shark.dive can break shark.dive.eval, while a change to shark.dive.eval can't break shark.dive.
- Position
- Below the diagonal: shark.dive.eval uses a module listed above it, which is the healthy direction.
39→36 shark.dive.eval uses shark.dive.agent✕
- Connections
- 1 pair of types, where a type in shark.dive.eval uses a type in shark.dive.agent.
- The types involved
shark.dive.eval.EvalMainKt→shark.dive.agent.AgentSession
- Direction
- shark.dive.eval uses shark.dive.agent, so a change to shark.dive.agent can break shark.dive.eval, while a change to shark.dive.eval can't break shark.dive.agent.
- Position
- Below the diagonal: shark.dive.eval uses a module listed above it, which is the healthy direction.
40→1 leakcanary uses leakcanary.EventListener✕
- Connections
- 9 pairs of types, where a type in leakcanary uses a type in leakcanary.EventListener.
- The types involved
leakcanary.BackgroundThreadHeapAnalyzer→leakcanary.EventListener.Eventleakcanary.EventListener→leakcanary.EventListener.Eventleakcanary.LazyForwardingEventListener→leakcanary.EventListener.Eventleakcanary.LogcatEventListener→leakcanary.EventListener.Eventleakcanary.NotificationEventListener→leakcanary.EventListener.Eventleakcanary.RemoteWorkManagerHeapAnalyzer→leakcanary.EventListener.Eventleakcanary.ToastEventListener→leakcanary.EventListener.Eventleakcanary.TvEventListener→leakcanary.EventListener.Eventleakcanary.WorkManagerHeapAnalyzer→leakcanary.EventListener.Event
- Direction
- leakcanary uses leakcanary.EventListener, so a change to leakcanary.EventListener can break leakcanary, while a change to leakcanary can't break leakcanary.EventListener.
- Position
- Below the diagonal: leakcanary uses a module listed above it, which is the healthy direction.
40→2 leakcanary uses leakcanary.HeapAnalysisJob✕
- Connections
- 11 pairs of types, where a type in leakcanary uses a type in leakcanary.HeapAnalysisJob.
- The types involved
leakcanary.BackgroundTrigger→leakcanary.HeapAnalysisJob.Resultleakcanary.ConditionalInterceptor→leakcanary.HeapAnalysisJob.Resultleakcanary.GoodAndroidVersionInterceptor→leakcanary.HeapAnalysisJob.Resultleakcanary.HeapAnalysisInterceptor→leakcanary.HeapAnalysisJob.Resultleakcanary.HeapAnalysisJob→leakcanary.HeapAnalysisJob.Resultleakcanary.MinimumDiskSpaceInterceptor→leakcanary.HeapAnalysisJob.Resultleakcanary.MinimumElapsedSinceStartInterceptor→leakcanary.HeapAnalysisJob.Resultleakcanary.MinimumMemoryInterceptor→leakcanary.HeapAnalysisJob.Resultleakcanary.OncePerPeriodInterceptor→leakcanary.HeapAnalysisJob.Resultleakcanary.SaveResourceIdsInterceptor→leakcanary.HeapAnalysisJob.Resultleakcanary.ScreenOffTrigger→leakcanary.HeapAnalysisJob.Result
- Direction
- leakcanary uses leakcanary.HeapAnalysisJob, so a change to leakcanary.HeapAnalysisJob can break leakcanary, while a change to leakcanary can't break leakcanary.HeapAnalysisJob.
- Position
- Below the diagonal: leakcanary uses a module listed above it, which is the healthy direction.
40→4 leakcanary uses shark.SharkLog✕
- Connections
- 1 pair of types, where a type in leakcanary uses a type in shark.SharkLog.
- The types involved
leakcanary.LogcatSharkLog→shark.SharkLog.Logger
- Direction
- leakcanary uses shark.SharkLog, so a change to shark.SharkLog can break leakcanary, while a change to leakcanary can't break shark.SharkLog.
- Position
- Below the diagonal: leakcanary uses a module listed above it, which is the healthy direction.
40→6 leakcanary uses leakcanary.HeapAnalysisInterceptor✕
- Connections
- 8 pairs of types, where a type in leakcanary uses a type in leakcanary.HeapAnalysisInterceptor.
- The types involved
leakcanary.ConditionalInterceptor→leakcanary.HeapAnalysisInterceptor.Chainleakcanary.GoodAndroidVersionInterceptor→leakcanary.HeapAnalysisInterceptor.Chainleakcanary.HeapAnalysisInterceptor→leakcanary.HeapAnalysisInterceptor.Chainleakcanary.MinimumDiskSpaceInterceptor→leakcanary.HeapAnalysisInterceptor.Chainleakcanary.MinimumElapsedSinceStartInterceptor→leakcanary.HeapAnalysisInterceptor.Chainleakcanary.MinimumMemoryInterceptor→leakcanary.HeapAnalysisInterceptor.Chainleakcanary.OncePerPeriodInterceptor→leakcanary.HeapAnalysisInterceptor.Chainleakcanary.SaveResourceIdsInterceptor→leakcanary.HeapAnalysisInterceptor.Chain
- Direction
- leakcanary uses leakcanary.HeapAnalysisInterceptor, so a change to leakcanary.HeapAnalysisInterceptor can break leakcanary, while a change to leakcanary can't break leakcanary.HeapAnalysisInterceptor.
- Position
- Below the diagonal: leakcanary uses a module listed above it, which is the healthy direction.
40→7 leakcanary uses leakcanary.ProcessInfo✕
- Connections
- 1 pair of types, where a type in leakcanary uses a type in leakcanary.ProcessInfo.
- The types involved
leakcanary.ProcessInfo→leakcanary.ProcessInfo.AvailableRam
- Direction
- leakcanary uses leakcanary.ProcessInfo, so a change to leakcanary.ProcessInfo can break leakcanary, while a change to leakcanary can't break leakcanary.ProcessInfo.
- Position
- Below the diagonal: leakcanary uses a module listed above it, which is the healthy direction.
40→24 leakcanary uses shark✕
- Connections
- 18 pairs of types, where a type in leakcanary uses a type in shark.
- The types involved
leakcanary.DumpingRepeatingScenarioObjectGrowthDetector→shark.HeapDiffleakcanary.DumpingRepeatingScenarioObjectGrowthDetector→shark.HeapTraversalInputleakcanary.DumpingRepeatingScenarioObjectGrowthDetector→shark.HeapTraversalOutputleakcanary.DumpingRepeatingScenarioObjectGrowthDetector→shark.ObjectGrowthDetectorleakcanary.DumpingRepeatingScenarioObjectGrowthDetector→shark.RepeatingScenarioObjectGrowthDetectorleakcanary.HeapAnalysisConfig→shark.LeakingObjectFinderleakcanary.HeapAnalysisConfig→shark.MetadataExtractorleakcanary.HeapAnalysisConfig→shark.ObjectInspectorleakcanary.HeapAnalysisConfig→shark.ProguardMappingleakcanary.HeapAnalysisConfig→shark.ReferenceMatcherleakcanary.HeapAnalysisReporter→shark.HeapAnalysisleakcanary.HeapDumpStorageStrategy→shark.HeapDiffleakcanary.NoLeakAssertionFailedError→shark.HeapAnalysisSuccessleakcanary.ObjectGrowthWarmupHeapDumper→shark.ObjectGrowthDetectorleakcanary.ObjectGrowthWarmupHeapDumperKt→shark.ObjectGrowthDetectorleakcanary.RepeatingUiAutomatorScenarioKt→shark.ObjectGrowthDetectorleakcanary.RepeatingUiAutomatorScenarioKt→shark.RepeatingScenarioObjectGrowthDetectorleakcanary.TvEventListener→shark.HeapAnalysis
- Direction
- leakcanary uses shark, so a change to shark can break leakcanary, while a change to leakcanary can't break shark.
- Position
- Below the diagonal: leakcanary uses a module listed above it, which is the healthy direction.
40→34 leakcanary uses leakcanary.LeakCanary✕
- Connections
- 1 pair of types, where a type in leakcanary uses a type in leakcanary.LeakCanary.
- The types involved
leakcanary.LeakCanary→leakcanary.LeakCanary.Config
- Direction
- leakcanary uses leakcanary.LeakCanary, so a change to leakcanary.LeakCanary can break leakcanary, while a change to leakcanary can't break leakcanary.LeakCanary.
- Position
- Below the diagonal: leakcanary uses a module listed above it, which is the healthy direction.
40→37 leakcanary uses leakcanary.internal✕
- Connections
- 1 pair of types, where a type in leakcanary uses a type in leakcanary.internal.
- The types involved
leakcanary.BackgroundTrigger→leakcanary.internal.BackgroundListener
- Direction
- leakcanary uses leakcanary.internal, so a change to leakcanary.internal can break leakcanary, while a change to leakcanary can't break leakcanary.internal.
- Position
- Below the diagonal: leakcanary 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 | 23 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 4 | Medium |
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 Banned license finding(s) in License Compliance.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 Banned license finding(s) in License Compliance. | +4.6 pts | Low | License Compliance |
| 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. | +7.5 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. | +7.5 pts | Medium | Security & performance tooling |
| Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. | +2.7 pts | Low | Bus Factor |
| Resolve the 1 Off-boarding risk finding(s) in Bus Factor. | +2.7 pts | Low | Bus Factor |
| Expand the README with getting-started, architecture overview and a project map. | +3.8 pts | Medium | Documentation (README) |
| Swallowed exception (caught, then discarded) | +0.9 pts | Medium | Exception handling |
| Bring the 14 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with StreamingHprofReader.readRecords (cyclomatic 60), HeapDumpDiveKt.HeapDumpDive (cyclomatic 49), Builder.onHprofRecord (cyclomatic 45). | +0.5 pts | High | Cyclomatic Complexity |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| shark/shark-dive/shark-dive-app/src/main/java/shark/dive/app/HeapDumpDive.kt | 5.9 | Mixed | Cyclomatic Complexity: HeapDumpDiveKt.HeapDumpDive (cyclomatic 49) |
| shark/shark-graph/src/main/java/shark/internal/HprofInMemoryIndex.kt | 6.0 | Mixed | Explicit Debt: TodoComment |
| shark/shark-cli/src/main/java/shark/Neo4JCommand.kt | 6.0 | Mixed | Explicit Debt: TodoComment |
| shark/shark/src/main/java/shark/RealLeakTracerFactory.kt | 6.0 | Mixed | Explicit Debt: TodoComment |
| leakcanary/leakcanary-app/src/main/java/org/leakcanary/screens/LeakScreen.kt | 6.0 | Mixed | Explicit Debt: TodoComment |
| samples/leakcanary-android-sample/src/debug/java/com/example/leakcanary/ExampleSetup.kt | 6.4 | Mixed | Explicit Debt: TodoComment |
| leakcanary/leakcanary-app/src/main/java/org/leakcanary/screens/ClientAppAnalysisScreen.kt | 6.4 | Mixed | Explicit Debt: TodoComment |
| leakcanary/leakcanary-app/src/main/java/org/leakcanary/service/LeakUiAppService.kt | 6.6 | Mixed | Explicit Debt: TodoComment |
| shark/shark/src/main/java/shark/HeapAnalyzer.kt | 6.7 | Mixed | Explicit Debt: TodoComment |
| samples/leakcanary-android-sample/src/debug/java/com/example/leakcanary/DebugExampleApplication.kt | 6.9 | Mixed | Explicit Debt: TodoComment |
| leakcanary/leakcanary-app-service/src/main/java/org/leakcanary/internal/LeakUiAppClient.kt | 6.9 | Mixed | Explicit Debt: TodoComment |
| leakcanary/leakcanary-app/src/main/java/org/leakcanary/screens/ClientAppAnalysesScreen.kt | 6.9 | Mixed | Explicit Debt: TodoComment |
| shark/shark-graph/src/main/java/shark/internal/hppc/LongLongScatterMap.kt | 7.0 | Mixed | Code Duplication: Duplicated block (30 lines × 2) |
| shark/shark-android/src/main/java/shark/AndroidObjectInspectors.kt | 7.1 | Mixed | Cyclomatic Complexity: AndroidObjectInspectorsKt.unwrapComponentContext (cyclomatic 20) |
| leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/activity/screen/LeakTraceWrapper.kt | 7.2 | Mixed | Cognitive Complexity: LeakTraceWrapper.wrapLine (cognitive 24) |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
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 50 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 50 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, 234 of 631 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) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (JaCoCo XML — the Gradle `jacocoTestReport` task) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (JaCoCo XML — the Gradle `jacocoTestReport` task) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D12 Dependency Hygiene — 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. Currency was graded against Maven Central, but whether an artifact is DEPRECATED is not: Maven Central publishes no deprecation marker, exactly as rubygems.org does not. Whether one is UNMAINTAINED is not graded either — no registry publishes a maintenance status, and release age does not stand in for one. Two of this dimension's four signals are therefore unread on a Gradle tree, and its score reflects currency alone.
- D14 License Compliance — 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. This repository declares a Python pyproject.toml/requirements.txt (pip/uv/Poetry), but the licence verdict published here was taken over its JVM dependencies. Nothing was read about its Python dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D19 Documentation Quality — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- 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.
- 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. `leakcanary/leakcanary-android-core/src/main/java/leakcanary/EventListener.kt`, `leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/InternalLeakCanary.kt`, `leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/OnRetainInstanceListener.kt`, `leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/activity/db/Io.kt`, `leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/navigation/Views.kt`, … (+54 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- 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 and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Java, Kotlin 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 and Scala 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.
- 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.
- X2 Cancellation propagation — 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, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, 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.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- 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.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D20 ADR Quality: ADR quality 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.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
14 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was StreamingHprofReader.readRecords at 60. A further 6 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being HprofWriter.write at 37 — they are counted neither in the figure above nor in this dimension's score. 4 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: shark/shark-hprof/src/main/java/shark/HprofWriter.kt (HprofWriter.write at 37), shark/shark-dive/shark-dive-core/src/main/java/shark/dive/GcRootStrength.kt (GcRootStrengthKt.reachabilityStrength at 17), shark/shark-dive/shark-dive-core/src/main/java/shark/dive/HeapDominatorTreemap.kt (HeapDominatorTreemap.gcRootLabel at 17), shark/shark/src/main/java/shark/LeakTrace.kt (GcRootType.fromGcRoot at 17). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 14 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with StreamingHprofReader.readRecords (cyclomatic 60), HeapDumpDiveKt.HeapDumpDive (cyclomatic 49), Builder.onHprofRecord (cyclomatic 45). — 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 14 together lifts Cyclomatic Complexity from 7.4 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
33 method(s) exceeded the cognitive complexity threshold of 15; the worst was StreamingHprofReader.readRecords at 161.
What to do
- Bring the 1 body over 60 down to 60 or less in Cognitive Complexity — start with StreamingHprofReader.readRecords (cognitive 161). — Refactoring it lifts Cognitive Complexity from 5.5 to about 6.5/10.
D3 · God Classes
21 god class(es) detected.
What to do
- Resolve the 7 FileTooLong finding(s) in God Classes — start with AndroidReferenceMatchers.kt, HeapDumpDive.kt, HeapDominatorTreemap.kt. — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 7 MethodTooLong finding(s) in God Classes — start with HprofInMemoryIndex.kt (2), HprofWriter.kt, Neo4JCommand.kt. — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 5 ClassTooLong finding(s) in God Classes — start with HeapDominatorTreemap.kt, HprofInMemoryIndex.kt, AgentTools.kt. — One of this dimension's main actionable groups (5 warning-level).
D4 · Code Duplication
26 duplicated block group(s) detected. 1 of the 26 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
What to do
- Resolve the 3 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with InteractiveCommand.kt, UnsortedByteEntries.kt, PagedUnsortedByteEntries.kt. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with ByteSubArray.kt, AgentServer.kt, HeapDumpScreen.kt. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Duplicated block (30 lines × 2) finding(s) in Code Duplication — start with LeakTraceWrapper.kt, LongLongScatterMap.kt. — One of this dimension's main actionable groups (2 warning-level).
D5 · Coupling
40 production modules (Gradle), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 4 module(s) off the main sequence, with abstractness counted on 36 of the 40 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 4 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (4 warning-level).
D6 · Cohesion (LCOM4)
0 of 155 classes have LCOM4 above 3.
D7 · Architectural Integrity
No mechanizable ADR was identified, so enforcement is not measured. Dependency cycles not checked (no project-reference graph; where this repository's language has an import-cycle lens, cycles are reported there).
D11 · Test Reliability
0 flaky across 1 measured tier(s). Java/Kotlin (repository root, Gradle): measured (0 flaky).
D12 · Dependency Hygiene
This repository's Gradle dependency graph was RESOLVED BY A BUILD, across every subproject rather than the root alone: 674 artifact(s) resolved, 477 of them gradable against Maven Central, and 383 behind a shipped release. Where a version was requested and a different one won conflict resolution, the RESOLVED version is what is graded — grading the request would recommend an upgrade already applied. Known CVEs in the same graph are a separate question again, reported under D30.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
1 of 34 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 43 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 27 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. ★ COVERAGE OF THIS VERDICT: it grades this repository's JVM dependencies and nothing else. The repository also declares a Python pyproject.toml/requirements.txt (pip/uv/Poetry), and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
What to do
- Resolve the 1 Banned license finding(s) in License Compliance. — One of this dimension's main actionable groups (1 issue-level).
D15 · Churn × Complexity Hotspots
Top hotspots: shark/shark-dive/shark-dive-app/src/main/java/shark/dive/app/HeapDumpDive.kt (65×49=3185); shark/shark-dive/shark-dive-agent/src/main/java/shark/dive/agent/AgentSessionFile.kt (24×26=624); shark/shark-graph/src/main/java/shark/internal/HprofInMemoryIndex.kt (8×45=360)
What to do
- Resolve the 7 Hotspot finding(s) in Churn × Complexity Hotspots — start with HeapDumpDive.kt, AgentSessionFile.kt, HprofInMemoryIndex.kt. — One of this dimension's main actionable groups (7 warning-level).
D16 · Bus Factor
165 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is shark/shark-dive/shark-dive-core/src/main/java/shark/dive/HeapDominatorTreemap.kt. Counted over 263 of the 517 production source files in this repository: 250 are under the ~2,400-byte size floor this dimension measures over, and the remaining 4 have no attributable history left to measure.
What to do
- Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D17 · Explicit Debt
65 deducted task-comment markers across 68138 LoC (0.1/KLoC) → score 9.8. 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 64 TodoComment finding(s) in Explicit Debt — start with ExampleSetup.kt (9), ClientAppAnalysisScreen.kt (7), RealLeakTracerFactory.kt (5). — One of this dimension's main actionable groups (64 warning-level).
- Resolve the 1 HackComment finding(s) in Explicit Debt — start with RealHeapAnalysisJob.kt. — One of this dimension's main actionable groups (1 warning-level).
D20 · ADR Quality
0 of 1 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question, a date that is no calendar day). How well each record argues its case is not measured.
D26 · Project Cohesion
4 of 31 build units (Gradle) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
23 finding(s): 0 critical, 22 high, 1 medium, 0 low. 22 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 5 file(s) — `config/hooks/pre-push` (line 14), `docs/theme/main.html` (lines 1–4, lines 4–31), `gradlew` (line 74, line 178), `plumber/plumber-android-core/src/main/java/leakcanary/AndroidLeakFixes.kt`, `shark/shark-dive/shark-dive-agent/harness/eval/run-eval.sh` (line 115) — 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. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- No action in Static Analysis (SAST) — all 22 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 (22 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in any ecosystem this repository declares.
D34 · Knowledge Freshness
2 of 267 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/SquigglySpanRenderer.kt. Counted over 267 of the 517 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: HeapDumpDive.kt↔TreemapView.kt 100%; HeapDumpDive.kt↔LeaksScreen.kt 55%; HeapDumpDive.kt↔Main.kt 51%
What to do
- Resolve the 3 Change coupling finding(s) in Change Coupling — start with Main.kt, HeapAnalyzer.kt, LeaksScreen.kt. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with HeapDumpDive.kt. — One of this dimension's main actionable groups (1 warning-level).
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 12 platform declaration(s) and 61 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX2 · Stateful singletons
AX3 · Project dependency cycles
AX4 · Dependency direction
M1 · Documentation (README)
- The root README is 110 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, in the README and in the repository documents it links, it found no a build/run or getting-started section, no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers. — README.md:1
What to do
- Expand the README with getting-started, architecture overview and a project map.
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Describe the projects a newcomer cannot place from the root README: 41 of 41 have no README of their own, in their folder or in their family's project (`leakcanary/leakcanary-android`, `leakcanary/leakcanary-android-core`, `leakcanary/leakcanary-android-instrumentation`, `leakcanary/leakcanary-android-process`, `leakcanary/leakcanary-android-release` and 36 more).
M2 · Architecture documentation
M3 · Folder & project structure
P1 · CI/CD gates
P10 · Library API & versioning
- 1 public type in `leakcanary.internal.DisplayLeakAdapter` is marked as implementation by its own namespace, folder or name: `Companion` (leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/DisplayLeakAdapter.kt:284, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/DisplayLeakAdapter.kt:284
- 2 public types in `leakcanary.internal.DisplayLeakConnectorView` are marked as implementation by their own namespace, folder or name: `Type` (leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/DisplayLeakConnectorView.kt:58, `internal`), `Companion` (leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/DisplayLeakConnectorView.kt:235, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/DisplayLeakConnectorView.kt:58
- 10 public types in `leakcanary.internal.DisplayLeakConnectorView.Type` are marked as implementation by their own namespace, folder or name: `GC_ROOT` (leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/DisplayLeakConnectorView.kt:59, `internal`), `START` (leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/DisplayLeakConnectorView.kt:60, `internal`), `START_LAST_REACHABLE` (leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/DisplayLeakConnectorView.kt:61, `internal`), `NODE_UNKNOWN` (leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/DisplayLeakConnectorView.kt:62, `internal`), `NODE_FIRST_UNREACHABLE` (leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/DisplayLeakConnectorView.kt:63, `internal`), `NODE_UNREACHABLE` (leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/DisplayLeakConnectorView.kt:64, `internal`), `NODE_REACHABLE` (leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/DisplayLeakConnectorView.kt:65, `internal`), `NODE_LAST_REACHABLE` (leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/DisplayLeakConnectorView.kt:66, `internal`), and 2 more. While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/DisplayLeakConnectorView.kt:59
- 1 public type in `leakcanary.internal.HeapAnalysisDoneDispatchWorker` is marked as implementation by its own namespace, folder or name: `Companion` (leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/HeapAnalysisDoneDispatchWorker.kt:53, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/HeapAnalysisDoneDispatchWorker.kt:53
- 1 public type in `leakcanary.internal.HeapAnalyzerWorker` is marked as implementation by its own namespace, folder or name: `Companion` (leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/HeapAnalyzerWorker.kt:33, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/HeapAnalyzerWorker.kt:33
- 1 public type in `leakcanary.internal.HeapDumpControl` is marked as implementation by its own namespace, folder or name: `ICanHazHeap` (leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/HeapDumpControl.kt:16, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/HeapDumpControl.kt:16
- 4 public types in `leakcanary.internal.HeapDumpControl.ICanHazHeap` are marked as implementation by their own namespace, folder or name: `Yup` (leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/HeapDumpControl.kt:17, `internal`), `Nope` (leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/HeapDumpControl.kt:18, `internal`), `SilentNope` (leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/HeapDumpControl.kt:19, `internal`), `NotifyingNope` (leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/HeapDumpControl.kt:24, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/HeapDumpControl.kt:17
- 1 public type in `leakcanary.internal.HeapDumpTrigger` is marked as implementation by its own namespace, folder or name: `Companion` (leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/HeapDumpTrigger.kt:417, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/HeapDumpTrigger.kt:417
- 12 public types in `leakcanary.internal` are marked as implementation by their own namespace, folder or name: `HexObjectIdsKt` (leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/HexObjectIds.kt:1, `internal`), `NotificationTypeKt` (leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/NotificationType.kt:1, `internal`), `OutOfMemoryGuidanceKt` (leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/OutOfMemoryGuidance.kt:1, `internal`), `SerializablesKt` (leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/Serializables.kt:1, `internal`), `VisibilityTrackerKt` (leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/VisibilityTracker.kt:1, `internal`), `RemoteLeakCanaryWorkerService` (leakcanary/leakcanary-android-process/src/main/java/leakcanary/internal/RemoteLeakCanaryWorkerService.kt:14, `internal`), `AndroidTestHeapLimitKt` (leakcanary/leakcanary-android-test/src/main/java/leakcanary/internal/AndroidTestHeapLimit.kt:1, `internal`), `HandlersKt` (leakcanary/leakcanary-android-utils/src/main/java/leakcanary/internal/Handlers.kt:1, `internal`), and 4 more. While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/HexObjectIds.kt:1
- 3 public types in `leakcanary.internal.InternalLeakCanary.FormFactor` are marked as implementation by their own namespace, folder or name: `MOBILE` (leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/InternalLeakCanary.kt:75, `internal`), `TV` (leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/InternalLeakCanary.kt:76, `internal`), `WATCH` (leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/InternalLeakCanary.kt:77, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/InternalLeakCanary.kt:75
What to do
- Hide `leakcanary.internal.DisplayLeakAdapter` (`Companion`) (Java: package-private (no modifier), or leave its package out of `module-info` exports; Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `leakcanary.internal.DisplayLeakConnectorView` (`Type`, `Companion`) (Java: package-private (no modifier), or leave its package out of `module-info` exports; Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `leakcanary.internal.DisplayLeakConnectorView.Type` (`GC_ROOT`, `START`, `START_LAST_REACHABLE`, `NODE_UNKNOWN`, `NODE_FIRST_UNREACHABLE`, `NODE_UNREACHABLE`, `NODE_REACHABLE`, `NODE_LAST_REACHABLE`, and 2 more) (Java: package-private (no modifier), or leave its package out of `module-info` exports; Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `leakcanary.internal.HeapAnalysisDoneDispatchWorker` (`Companion`) (Java: package-private (no modifier), or leave its package out of `module-info` exports; Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `leakcanary.internal.HeapAnalyzerWorker` (`Companion`) (Java: package-private (no modifier), or leave its package out of `module-info` exports; Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `leakcanary.internal.HeapDumpControl` (`ICanHazHeap`) (Java: package-private (no modifier), or leave its package out of `module-info` exports; Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `leakcanary.internal.HeapDumpControl.ICanHazHeap` (`Yup`, `Nope`, `SilentNope`, `NotifyingNope`) (Java: package-private (no modifier), or leave its package out of `module-info` exports; Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `leakcanary.internal.HeapDumpTrigger` (`Companion`) (Java: package-private (no modifier), or leave its package out of `module-info` exports; Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `leakcanary.internal` (`HexObjectIdsKt`, `NotificationTypeKt`, `OutOfMemoryGuidanceKt`, `SerializablesKt`, `VisibilityTrackerKt`, `RemoteLeakCanaryWorkerService`, `AndroidTestHeapLimitKt`, `HandlersKt`, and 4 more) (Java: package-private (no modifier), or leave its package out of `module-info` exports; Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `leakcanary.internal.InternalLeakCanary.FormFactor` (`MOBILE`, `TV`, `WATCH`) (Java: package-private (no modifier), or leave its package out of `module-info` exports; Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
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 5 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:4
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.
P4 · Deployment & Rollback
P6 · Release Hygiene
PF3 · Async & latency hygiene
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X16 · Unfloored truncation loop
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X21 · Side-effecting pattern guard
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X3 · Exception handling
- `catch (notJson: 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. — shark/shark-dive/shark-dive-agent/src/main/java/shark/dive/agent/AgentWire.kt:76
- `catch (e: 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. (×5) — shark/shark/src/main/java/shark/HeapAnalysis.kt:280, shark/shark/src/main/java/shark/HeapAnalysis.kt:290, shark/shark/src/main/java/shark/HeapAnalysis.kt:301, …
- `catch (ignored: Throwable)` 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. (×7) — plumber/plumber-android-core/src/main/java/leakcanary/internal/FragmentExtensions.kt:12, object-watcher/object-watcher-android-core/src/main/java/leakcanary/internal/LeakCanaryDelegate.kt:14, object-watcher/object-watcher-android-androidx/src/main/java/leakcanary/internal/AndroidXFragmentDestroyWatcher.kt:113, …
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. — leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/activity/db/Cursors.kt:23
What to do
- Swallowed exception (caught, then discarded)
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 80% | Strong | Solid. |
| Architecture | 95% | Exemplary | Solid. |
| Maturity | 57% | Adequate — gated by D16 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 41% | Weak — gated by P2, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 80% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 2 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 10 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 67 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: Dagger rejects, at compile time, a component that holds a binding with a narrower scope than its own.
- 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
- AX6 Interface segregation — no public interfaces
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility (rendered) — 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 — ~32661 lines of test source are present (.kt) 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.
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D19 Documentation Quality — D19 reads .NET projects and npm packages as units; 40 folder(s) declared by build.gradle.kts were not judged for an overview, an example or the map.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Java, Kotlin not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Kotlin surface was not measured.
- 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 — None of 0 binding record(s) states a rule in checkable form (a backticked element with a prohibition, or an `adr-rules` block), so conformance cannot be read from the code. Write the rule as an `adr-rules` block (`forbid:` a symbol, a package or a dependency) to make it checkable.
- D27 Navigability — symbol resolution incomplete — navigability not assessed
- 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) — 59 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- D9 Test Distribution — Test source is present (.kt) 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 its unit/integration/BDD/E2E split couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 198 value object(s); 8 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, 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
- M4 Documentation accuracy — Not applicable: the 34 current-state document(s) make no claim of a kind M4 checks. 19 claim(s) of kinds M4 does not check were not checked (path 4, environment variable 15); M4 checks only links and versions and artefact counts.
- 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 — no coverage report found on disk — produce a coverage report in a standard format (JaCoCo XML — the Gradle `jacocoTestReport` task) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- 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
- X2 Cancellation propagation — 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
- 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
- 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
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's 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.
- 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 — 23 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Banned license: org.neo4j:neo4j
Serious — 191 finding(s)
- TodoComment shark/shark-graph/src/main/java/shark/HprofHeapGraph.kt:417
- TodoComment shark/shark-graph/src/main/java/shark/internal/HprofInMemoryIndex.kt:546
- TodoComment shark/shark-cli/src/main/java/shark/Neo4JCommand.kt:162
- TodoComment shark/shark-cli/src/main/java/shark/Neo4JCommand.kt:173
- TodoComment shark/shark-cli/src/main/java/shark/Neo4JCommand.kt:438
- TodoComment shark/shark-cli/src/main/java/shark/Neo4JCommand.kt:739
- TodoComment shark/shark/src/main/java/shark/AndroidReferenceReaderFactory.kt:3
- TodoComment shark/shark/src/main/java/shark/VirtualizingMatchingReferenceReaderFactory.kt:5
- TodoComment shark/shark/src/main/java/shark/AndroidReferenceReaderFactory.kt:4
- TodoComment shark/shark/src/main/java/shark/GcRootReference.kt:3
- TodoComment shark/shark/src/main/java/shark/HeapAnalyzer.kt:101
- TodoComment shark/shark/src/main/java/shark/LeakTracer.kt:5
- TodoComment shark/shark/src/main/java/shark/LeaksAndUnreachableObjects.kt:3
- TodoComment shark/shark/src/main/java/shark/PathFindingResults.kt:6
- TodoComment shark/shark/src/main/java/shark/PrioritizingShortestPathFinder.kt:122
- TodoComment shark/shark/src/main/java/shark/RealLeakTracerFactory.kt:55
- TodoComment shark/shark/src/main/java/shark/RealLeakTracerFactory.kt:45
- TodoComment shark/shark/src/main/java/shark/RealLeakTracerFactory.kt:46
- TodoComment shark/shark/src/main/java/shark/RealLeakTracerFactory.kt:47
- TodoComment shark/shark/src/main/java/shark/RealLeakTracerFactory.kt:72
- TodoComment shark/shark/src/main/java/shark/Reference.kt:57
- TodoComment shark/shark/src/main/java/shark/ReferenceReader.kt:3
- TodoComment shark/shark/src/main/java/shark/ShortestPathFinder.kt:3
- TodoComment samples/leakcanary-android-sample/src/debug/java/com/example/leakcanary/DebugExampleApplication.kt:13
- TodoComment samples/leakcanary-android-sample/src/debug/java/com/example/leakcanary/DebugExampleApplication.kt:18
- Swallowed exception (caught, then discarded) shark/shark-dive/shark-dive-agent/src/main/java/shark/dive/agent/AgentWire.kt:76
- Swallowed exception (caught, then discarded) shark/shark/src/main/java/shark/HeapAnalysis.kt:280
- Swallowed exception (caught, then discarded) shark/shark/src/main/java/shark/HeapAnalysis.kt:290
- Swallowed exception (caught, then discarded) shark/shark/src/main/java/shark/HeapAnalysis.kt:301
- Swallowed exception (caught, then discarded) plumber/plumber-android-core/src/main/java/leakcanary/internal/FragmentExtensions.kt:12
- Swallowed exception (caught, then discarded) object-watcher/object-watcher-android-core/src/main/java/leakcanary/internal/LeakCanaryDelegate.kt:14
- Swallowed exception (caught, then discarded) object-watcher/object-watcher-android-androidx/src/main/java/leakcanary/internal/AndroidXFragmentDestroyWatcher.kt:113
- Swallowed exception (caught, then discarded) leakcanary/leakcanary-core/src/main/java/leakcanary/HeapGrowthOutOfMemoryGuidance.kt:148
- Swallowed exception (caught, then discarded) leakcanary/leakcanary-android-core/src/main/java/leakcanary/RemoteWorkManagerHeapAnalyzer.kt:29
- Swallowed exception (caught, then discarded) leakcanary/leakcanary-android-core/src/main/java/leakcanary/WorkManagerHeapAnalyzer.kt:29
- Swallowed exception (caught, then discarded) leakcanary/leakcanary-android-core/src/main/java/leakcanary/WorkManagerHeapAnalyzer.kt:39
- Swallowed exception (caught, then discarded) leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/HeapDumpControl.kt:41
- Swallowed exception (caught, then discarded) leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/HeapDumpControl.kt:58
- Hotspot: shark/shark-dive/shark-dive-app/src/main/java/shark/dive/app/HeapDumpDive.kt shark/shark-dive/shark-dive-app/src/main/java/shark/dive/app/HeapDumpDive.kt:121
- Hotspot: shark/shark-dive/shark-dive-agent/src/main/java/shark/dive/agent/AgentSessionFile.kt shark/shark-dive/shark-dive-agent/src/main/java/shark/dive/agent/AgentSessionFile.kt:674
- Hotspot: shark/shark-graph/src/main/java/shark/internal/HprofInMemoryIndex.kt shark/shark-graph/src/main/java/shark/internal/HprofInMemoryIndex.kt:639
- Hotspot: shark/shark-hprof/src/main/java/shark/HprofPrimitiveArrayStripper.kt shark/shark-hprof/src/main/java/shark/HprofPrimitiveArrayStripper.kt:123
- Hotspot: shark/shark/src/main/java/shark/ObjectGrowthDetector.kt shark/shark/src/main/java/shark/ObjectGrowthDetector.kt:76
- Hotspot: shark/shark-dive/shark-dive-core/src/main/java/shark/dive/TreemapLayout.kt shark/shark-dive/shark-dive-core/src/main/java/shark/dive/TreemapLayout.kt:151
- Hotspot: shark/shark/src/main/java/shark/internal/ReferencePathNode.kt shark/shark/src/main/java/shark/internal/ReferencePathNode.kt:56
- FileTooLong: shark/AndroidReferenceMatchers.kt shark/shark-android/src/main/java/shark/AndroidReferenceMatchers.kt
- FileTooLong: app/HeapDumpDive.kt shark/shark-dive/shark-dive-app/src/main/java/shark/dive/app/HeapDumpDive.kt
- FileTooLong: dive/HeapDominatorTreemap.kt shark/shark-dive/shark-dive-core/src/main/java/shark/dive/HeapDominatorTreemap.kt
- FileTooLong: agent/AgentTools.kt shark/shark-dive/shark-dive-agent/src/main/java/shark/dive/agent/AgentTools.kt
- FileTooLong: internal/HprofInMemoryIndex.kt shark/shark-graph/src/main/java/shark/internal/HprofInMemoryIndex.kt
- FileTooLong: shark/AndroidObjectInspectors.kt shark/shark-android/src/main/java/shark/AndroidObjectInspectors.kt
- FileTooLong: shark/Neo4JCommand.kt shark/shark-cli/src/main/java/shark/Neo4JCommand.kt
- MethodTooLong: HprofWriter.write shark/shark-hprof/src/main/java/shark/HprofWriter.kt:147
- MethodTooLong: Companion.dumpEdges shark/shark-cli/src/main/java/shark/Neo4JCommand.kt:307
- MethodTooLong: Builder.onHprofRecord shark/shark-graph/src/main/java/shark/internal/HprofInMemoryIndex.kt:639
- MethodTooLong: ObjectGrowthDetector.traverseHeapDiffingShortestPaths shark/shark/src/main/java/shark/ObjectGrowthDetector.kt:76
- MethodTooLong: Companion.indexHprof shark/shark-graph/src/main/java/shark/internal/HprofInMemoryIndex.kt:949
- MethodTooLong: StreamingRecordReaderAdapter.readRecords shark/shark-hprof/src/main/java/shark/StreamingRecordReaderAdapter.kt:59
- MethodTooLong: HeapGrowthCommand.run shark/shark-cli/src/main/java/shark/HeapGrowthCommand.kt:37
- ClassTooLong: HeapDominatorTreemap shark/shark-dive/shark-dive-core/src/main/java/shark/dive/HeapDominatorTreemap.kt:79
- ClassTooLong: HprofInMemoryIndex shark/shark-graph/src/main/java/shark/internal/HprofInMemoryIndex.kt:75
- ClassTooLong: AgentTools shark/shark-dive/shark-dive-agent/src/main/java/shark/dive/agent/AgentTools.kt:63
- ClassTooLong: Neo4JCommand shark/shark-cli/src/main/java/shark/Neo4JCommand.kt:79
- ClassTooLong: InteractiveCommand shark/shark-cli/src/main/java/shark/InteractiveCommand.kt:46
- Off the main sequence: :shark:shark-android
- Off the main sequence: :leakcanary:leakcanary-gc
- Off the main sequence: :shark:shark
- Off the main sequence: :leakcanary:leakcanary-android-utils
- Change coupling: Main.kt ↔ TreemapView.kt shark/shark-dive/shark-dive-app/src/main/java/shark/dive/app/Main.kt:1
- Change coupling: HeapAnalyzer.kt ↔ ObjectDominators.kt shark/shark/src/main/java/shark/HeapAnalyzer.kt:1
- Change coupling: LeaksScreen.kt ↔ Verdict.kt shark/shark-dive/shark-dive-app/src/main/java/shark/dive/app/LeaksScreen.kt:1
- Duplicated block (7 lines × 2) shark/shark-cli/src/main/java/shark/InteractiveCommand.kt:509
- Duplicated block (7 lines × 2) shark/shark-graph/src/main/java/shark/internal/UnsortedByteEntries.kt:100
- Duplicated block (7 lines × 2) shark/shark-graph/src/main/java/shark/internal/PagedUnsortedByteEntries.kt:92
- Duplicated block (5 lines × 2) shark/shark-graph/src/main/java/shark/internal/ByteSubArray.kt:120
- Duplicated block (5 lines × 2) shark/shark-dive/shark-dive-agent/src/main/java/shark/dive/agent/AgentServer.kt:345
- Duplicated block (5 lines × 2) leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/activity/screen/HeapDumpScreen.kt:108
- LeakTraceWrapper.wrapLine (cognitive 24) leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/activity/screen/LeakTraceWrapper.kt:60
- LeakTraceWrapper.wrapLine (cognitive 24) leakcanary/leakcanary-app/src/main/java/org/leakcanary/util/LeakTraceWrapper.kt:60
- LeakTraceWrapper.wrap (cognitive 16) leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/activity/screen/LeakTraceWrapper.kt:24
- LeakTraceWrapper.wrap (cognitive 16) leakcanary/leakcanary-app/src/main/java/org/leakcanary/util/LeakTraceWrapper.kt:24
- TooManyMethods: HeapDominatorTreemap shark/shark-dive/shark-dive-core/src/main/java/shark/dive/HeapDominatorTreemap.kt:79
- TooManyMethods: HprofRecordReader shark/shark-hprof/src/main/java/shark/HprofRecordReader.kt:71
- Duplicated block (30 lines × 2) leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/activity/screen/LeakTraceWrapper.kt:29
- Duplicated block (30 lines × 2) shark/shark-graph/src/main/java/shark/internal/hppc/LongLongScatterMap.kt:374
- Duplicated block (29 lines × 2) shark/shark-graph/src/main/java/shark/internal/hppc/LongLongScatterMap.kt:81
- Duplicated block (29 lines × 2) shark/shark-hprof-test/src/main/kotlin/shark/HprofWriterHelper.kt:137
- Duplicated block (17–19 lines × 3) shark/shark-dive/shark-dive-core/src/main/java/shark/dive/RadialLayout.kt:144
- Duplicated block (17–19 lines × 3) shark/shark-graph/src/main/java/shark/internal/hppc/LongLongScatterMap.kt:233
- Duplicated block (15 lines × 2) shark/shark-graph/src/main/java/shark/internal/hppc/LongLongScatterMap.kt:120
- Duplicated block (15 lines × 2) shark/shark-graph/src/main/java/shark/internal/hppc/LongLongScatterMap.kt:353
- StreamingHprofReader.readRecords (cyclomatic 60) shark/shark-hprof/src/main/java/shark/StreamingHprofReader.kt:55
- HeapDumpDiveKt.HeapDumpDive (cyclomatic 49) shark/shark-dive/shark-dive-app/src/main/java/shark/dive/app/HeapDumpDive.kt:121
- Builder.onHprofRecord (cyclomatic 45) shark/shark-graph/src/main/java/shark/internal/HprofInMemoryIndex.kt:639
- HprofPrimitiveArrayStripper.stripPrimitiveArrays (cyclomatic 44) shark/shark-hprof/src/main/java/shark/HprofPrimitiveArrayStripper.kt:123
- ObjectGrowthDetector.traverseHeapDiffingShortestPaths (cyclomatic 32) shark/shark/src/main/java/shark/ObjectGrowthDetector.kt:76
- AgentSessionFileKt.verbOfTool (cyclomatic 26) shark/shark-dive/shark-dive-agent/src/main/java/shark/dive/agent/AgentSessionFile.kt:674
- Neo4JCommand.dumpEdges (cyclomatic 23) shark/shark-cli/src/main/java/shark/Neo4JCommand.kt:307
- AndroidObjectInspectorsKt.unwrapComponentContext (cyclomatic 20) shark/shark-android/src/main/java/shark/AndroidObjectInspectors.kt:1059
- RealLeakTracerFactory.computeVerdicts (cyclomatic 20) shark/shark/src/main/java/shark/RealLeakTracerFactory.kt:372
- HeapGrowthCommand.run (cyclomatic 19) shark/shark-cli/src/main/java/shark/HeapGrowthCommand.kt:37
- StreamingRecordReaderAdapter.asHprofTags (cyclomatic 19) shark/shark-hprof/src/main/java/shark/StreamingRecordReaderAdapter.kt:227
- MatchingGcRootProvider.provideGcRoots (cyclomatic 19) shark/shark/src/main/java/shark/MatchingGcRootProvider.kt:39
- HprofExplorerScreen.heapValueAsString (cyclomatic 16) leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/activity/screen/HprofExplorerScreen.kt:278
- ReferencePathNodeKt.invalidObjectIdErrorMessage (cyclomatic 16) shark/shark/src/main/java/shark/internal/ReferencePathNode.kt:56
- HackComment leakcanary/leakcanary-android-release/src/main/java/leakcanary/internal/RealHeapAnalysisJob.kt:215
- StreamingHprofReader.readRecords (cognitive 161) shark/shark-hprof/src/main/java/shark/StreamingHprofReader.kt:55
- ObjectGrowthDetector.traverseHeapDiffingShortestPaths (cognitive 60) shark/shark/src/main/java/shark/ObjectGrowthDetector.kt:76
- HprofPrimitiveArrayStripper.stripPrimitiveArrays (cognitive 50) shark/shark-hprof/src/main/java/shark/HprofPrimitiveArrayStripper.kt:123
- HeapDumpDiveKt.HeapDumpDive (cognitive 49) shark/shark-dive/shark-dive-app/src/main/java/shark/dive/app/HeapDumpDive.kt:121
- Builder.onHprofRecord (cognitive 43) shark/shark-graph/src/main/java/shark/internal/HprofInMemoryIndex.kt:639
- HeapGrowthCommand.run (cognitive 41) shark/shark-cli/src/main/java/shark/HeapGrowthCommand.kt:37
- AndroidObjectInspectorsKt.unwrapComponentContext (cognitive 39) shark/shark-android/src/main/java/shark/AndroidObjectInspectors.kt:1059
- DisplayLeakAdapter.getConnectorType (cognitive 36) leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/DisplayLeakAdapter.kt:212
- HeapDumpTrigger.checkRetainedCount (cognitive 35) leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/HeapDumpTrigger.kt:276
- StreamingRecordReaderAdapter.asHprofTags (cognitive 30) shark/shark-hprof/src/main/java/shark/StreamingRecordReaderAdapter.kt:227
- SquarifyKt.squarify (cognitive 30) shark/shark-dive/shark-dive-core/src/main/java/shark/dive/Squarify.kt:22
- ReferrerIndex.compact (cognitive 29) shark/shark-dive/shark-dive-core/src/main/java/shark/dive/ReferrerIndex.kt:252
- RealLeakTracerFactory.computeVerdicts (cognitive 27) shark/shark/src/main/java/shark/RealLeakTracerFactory.kt:372
- SlotTableReferenceReader.readGroups (cognitive 26) shark/shark-dive/shark-dive-core/src/main/java/shark/dive/SlotTableReferenceReader.kt:247
- VIEW.inspect (cognitive 25) shark/shark-android/src/main/java/shark/AndroidObjectInspectors.kt:109
- StackLayout.layout (cognitive 25) shark/shark-dive/shark-dive-core/src/main/java/shark/dive/StackLayout.kt:94
- Neo4JCommand.dumpEdges (cognitive 24) shark/shark-cli/src/main/java/shark/Neo4JCommand.kt:307
- FieldInstanceReferenceReader.read (cognitive 24) shark/shark/src/main/java/shark/FieldInstanceReferenceReader.kt:55
- TreemapLayout.layout (cognitive 24) shark/shark-dive/shark-dive-core/src/main/java/shark/dive/TreemapLayout.kt:151
- CellColors.of (cognitive 23) shark/shark-dive/shark-dive-app/src/main/java/shark/dive/app/CellColors.kt:213
- CONTEXT_WRAPPER.inspect (cognitive 22) shark/shark-android/src/main/java/shark/AndroidObjectInspectors.kt:279
- DisplayLeakAdapter.bindConnectorRow (cognitive 21) leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/DisplayLeakAdapter.kt:98
- LeakCanaryAndroidInternalUtils.addLeakActivityDynamicShortcut (cognitive 20) leakcanary/leakcanary-android-core/src/main/java/leakcanary/LeakCanaryAndroidInternalUtils.kt:20
- LeakScreenKt.LeakScreen (cognitive 20) leakcanary/leakcanary-app/src/main/java/org/leakcanary/screens/LeakScreen.kt:146
- RadialLayout.layout (cognitive 19) shark/shark-dive/shark-dive-core/src/main/java/shark/dive/RadialLayout.kt:104
- ACTIVITY_THREAD__NEW_ACTIVITIES.create (cognitive 18) shark/shark/src/main/java/shark/AndroidReferenceReaders.kt:53
- InteractiveCommand.analyze (cognitive 17) shark/shark-cli/src/main/java/shark/InteractiveCommand.kt:560
- AgentSessionFileKt.verbOfTool (cognitive 17) shark/shark-dive/shark-dive-agent/src/main/java/shark/dive/agent/AgentSessionFile.kt:674
- ANONYMOUS_CLASS.inspect (cognitive 16) shark/shark/src/main/java/shark/ObjectInspectors.kt:85
- REDACTED
- Change-coupling hub: HeapDumpDive.kt → LeaksScreen.kt, Main.kt, TreemapView.kt shark/shark-dive/shark-dive-app/src/main/java/shark/dive/app/HeapDumpDive.kt
- REDACTED
- Duplicated block (100 lines × 2) leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/activity/screen/LeakTraceWrapper.kt:66
- Duplicated block (28 lines × 2) leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/activity/ui/TimeFormatter.kt:21
- Duplicated block (21 lines × 2) shark/shark-graph/src/main/java/shark/internal/hppc/LongLongScatterMap.kt:288
- Duplicated block (14–16 lines × 2) shark/shark-graph/src/main/java/shark/internal/ClassFieldsReader.kt:33
- Duplicated block (16 lines × 2) shark/shark-graph/src/main/java/shark/internal/hppc/LongLongScatterMap.kt:323
- Duplicated block (13–14 lines × 2) leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/HeapDumpTrigger.kt:247
- Duplicated block (13 lines × 2) shark/shark-graph/src/main/java/shark/internal/ClassFieldsReader.kt:105
- Duplicated block (9 lines × 3) shark/shark-graph/src/main/java/shark/internal/ClassFieldsReader.kt:106
- Duplicated block (8 lines × 2) shark/shark-dive/shark-dive-app/src/main/java/shark/dive/app/RootPathPanel.kt:255
- Duplicated block (17 lines × 2) leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/Serializables.kt:10
- Duplicated block (10 lines × 2) shark/shark-graph/src/main/java/shark/internal/hppc/LongLongScatterMap.kt:265
- Duplicated block (6 lines × 2) leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/utils/Size.kt:11
- No structured logging
- Swallowed exception (empty catch) leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/activity/db/Cursors.kt:23
Minor — 34 finding(s)
- Implementation type on the public API leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/DisplayLeakAdapter.kt:284
- Implementation type on the public API leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/DisplayLeakConnectorView.kt:58
- Implementation type on the public API leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/DisplayLeakConnectorView.kt:59
- Implementation type on the public API leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/HeapAnalysisDoneDispatchWorker.kt:53
- Implementation type on the public API leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/HeapAnalyzerWorker.kt:33
- Implementation type on the public API leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/HeapDumpControl.kt:16
- Implementation type on the public API leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/HeapDumpControl.kt:17
- Implementation type on the public API leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/HeapDumpTrigger.kt:417
- Implementation type on the public API leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/HexObjectIds.kt:1
- Implementation type on the public API leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/InternalLeakCanary.kt:75
- Duplicated predicate shark/shark/src/main/java/shark/ObjectGrowthDetector.kt:372
- Duplicated predicate shark/shark-graph/src/main/java/shark/internal/PagedUnsortedByteEntries.kt:94
- Duplicated predicate shark/shark-graph/src/main/java/shark/internal/PagedUnsortedByteEntries.kt:122
- Duplicated predicate shark/shark-graph/src/main/java/shark/internal/PagedUnsortedByteEntries.kt:107
- Duplicated predicate shark/shark/src/main/java/shark/ApacheHarmonyInstanceRefReaders.kt:113
- Duplicated predicate shark/shark/src/main/java/shark/ApacheHarmonyInstanceRefReaders.kt:165
- Duplicated predicate shark/shark-dive/shark-dive-core/src/main/java/shark/dive/StarredFile.kt:39
- Duplicated predicate leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/activity/screen/LeakTraceWrapper.kt:106
- Duplicated predicate leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/activity/screen/LeakTraceWrapper.kt:130
- Duplicated predicate shark/shark/src/main/java/shark/ObjectGrowthDetector.kt:72
- Silent fallback default in catch shark/shark/src/main/java/shark/HeapAnalysis.kt:280
- Silent fallback default in catch shark/shark/src/main/java/shark/HeapAnalysis.kt:290
- Silent fallback default in catch shark/shark/src/main/java/shark/HeapAnalysis.kt:301
- Orphaned file leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/SquigglySpanRenderer.kt:1
- Orphaned file shark/shark-hprof/src/main/java/shark/ProguardMappingReader.kt:1
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- Projects may be oversized for their cohesion
- Orphaned files with no living knowledge
- REDACTED
- REDACTED
- REDACTED
- Thin README README.md:1
- No SAST REDACTED:4
Minor — 383 finding(s)
- Outdated (compile): com.google.guava:guava
- Outdated (compile): com.google.guava:failureaccess
- Outdated (compile): org.checkerframework:checker-qual
- Outdated (compile): com.google.errorprone:error_prone_annotations
- Outdated (compile): com.google.j2objc:j2objc-annotations
- Outdated (compile): net.java.dev.jna:jna-platform
- Outdated (compile): net.java.dev.jna:jna
- Outdated (compile): org.jetbrains.kotlin:kotlin-stdlib-jdk8
- Outdated (compile): org.jetbrains.kotlin:kotlin-stdlib
- Outdated (compile): org.jetbrains:annotations
- Outdated (compile): org.jetbrains.kotlin:kotlin-stdlib-jdk7
- Outdated (compile): com.google.protobuf:protobuf-java
- Outdated (compile): com.google.code.gson:gson
- Outdated (compile): com.google.jimfs:jimfs
- Outdated (compile): org.apache.commons:commons-compress
- Outdated (compile): commons-codec:commons-codec
- Outdated (compile): commons-io:commons-io
- Outdated (compile): org.apache.commons:commons-lang3
- Outdated (compile): org.glassfish.jaxb:jaxb-runtime
- Outdated (compile): jakarta.xml.bind:jakarta.xml.bind-api
- Outdated (compile): jakarta.activation:jakarta.activation-api
- Outdated (compile): org.glassfish.jaxb:txw2
- Outdated (compile): com.sun.istack:istack-commons-runtime
- Outdated (compile): org.jvnet.staxex:stax-ex
- Outdated (compile): com.sun.xml.fastinfoset:FastInfoset
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-8e8a4815be334b849fd4e14244cf20f4/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-8e8a4815be334b849fd4e14244cf20f4/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 . | 23 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 59 file(s) — `leakcanary/leakcanary-android-core/src/main/java/leakcanary/EventListener.kt`, `leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/InternalLeakCanary.kt`, `leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/OnRetainInstanceListener.kt`, `leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/activity/db/Io.kt`, `leakcanary/leakcanary-android-core/src/main/java/leakcanary/internal/navigation/Views.kt`, … (+54 more) — 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 | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |