Executive summary
airbnb/Showkase falls short of our standard for production, in part because we found no automated security scanning of the code, its secrets or its dependencies. It scores 57.5 out of 100 and is rated Adequate, and all 17 of its critical findings are security problems in the build pipeline.
Production Readiness, at 46.3, is the weakest lens and counts most in the score. The best first step is having someone learn and document the 31 files no active contributor knows, worth about 9.5 points. Adding tests for untested code would lift Production Readiness itself, worth about 5.4 points. Raising Production Readiness to 70 would lift the score to about 64.2.
Seventeen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Pinning each tool to an exact version would close this risk.
The product code is 7,621 lines, about €12,000 to rebuild.
If Production Readiness rose from 46.3 to 70, the lowest score rated Strong, the score would rise from 57.5 to about 64.2.
Rebuild cost: about €12,000 · Estimate
| Cost to rebuild | €4,000 to €20,000, for 66 to 210 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 58. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 7,621 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 airbnb.android.showkase.annotation | 2 airbnb.android.showkase.exceptions | 3 airbnb.android.showkase.processor.ShowkaseProcessor | 4 airbnb.android.showkase.processor.Timer | 5 airbnb.android.showkase.processor.exceptions | 6 airbnb.android.showkase.processor.logging.ShowkaseValidator | 7 airbnb.android.showkase.processor.utils | 8 airbnb.android.showkase.processor.writer.PaparazziShowkaseScreenshotTestWriter | 9 airbnb.android.showkase.processor.writer.ShowkaseBrowserWriter | 10 airbnb.android.showkase.processor.writer.ShowkaseExtensionFunctionsWriter | 11 airbnb.android.showkase.processor.writer.ShowkaseScreenshotTestWriter | 12 airbnb.android.showkase.ui.ShowkaseBrowserActivity | 13 airbnb.android.submodule.showkasesample | 14 airbnb.android.submodule.showkasesample.payments | 15 vinaygaba.showkase_browser_testing_submodule | 16 vinaygaba.showkase_browser_testing_submodule.two | 17 airbnb.android.showkase.annotation.ScreenshotCaptureType | 18 airbnb.android.showkase.annotation.ScreenshotConfig | 19 airbnb.android.showkase.models | 20 airbnb.android.showkase.processor.models.ShowkaseMetadata | 21 airbnb.android.showkase_browser_testing | 22 airbnb.android.showkase.models.ShowkaseCategory | 23 airbnb.android.showkase.models.ShowkaseCurrentScreen | 24 airbnb.android.showkase.processor.models | 25 airbnb.android.showkase.screenshot.testing | 26 airbnb.android.showkase.screenshot.testing.paparazzi | 27 airbnb.android.showkase.ui | 28 airbnb.android.showkase.processor.models.ShowkaseFunctionType | 29 airbnb.android.showkase.processor.models.ShowkaseMetadataType | 30 airbnb.android.showkase.processor.writer | 31 airbnb.android.showkase.screenshot.testing.ShowkaseScreenshotType | 32 airbnb.android.showkase.screenshot.testing.paparazzi.PaparazziShowkaseScreenshotTest | 33 airbnb.android.showkase.screenshot.testing.paparazzi.PaparazziShowkaseUIMode | 34 airbnb.android.showkase.screenshot.testing.shot | 35 airbnb.android.showkase.ui.ShowkaseComponentCardType | 36 airbnb.android.showkase.processor.logging | 37 airbnb.android.showkase.processor | 38 airbnb.android.showkase.processor.ScreenshotTestType | 39 airbnb.android.showkase.processor.ShowkaseGeneratedMetadataType |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 airbnb.android.showkase.annotation | |||||||||||||||||||||||||||||||||||||||
| 2 airbnb.android.showkase.exceptions | |||||||||||||||||||||||||||||||||||||||
| 3 airbnb.android.showkase.processor.ShowkaseProcessor | |||||||||||||||||||||||||||||||||||||||
| 4 airbnb.android.showkase.processor.Timer | |||||||||||||||||||||||||||||||||||||||
| 5 airbnb.android.showkase.processor.exceptions | |||||||||||||||||||||||||||||||||||||||
| 6 airbnb.android.showkase.processor.logging.ShowkaseValidator | |||||||||||||||||||||||||||||||||||||||
| 7 airbnb.android.showkase.processor.utils | |||||||||||||||||||||||||||||||||||||||
| 8 airbnb.android.showkase.processor.writer.PaparazziShowkaseScreenshotTestWriter | |||||||||||||||||||||||||||||||||||||||
| 9 airbnb.android.showkase.processor.writer.ShowkaseBrowserWriter | |||||||||||||||||||||||||||||||||||||||
| 10 airbnb.android.showkase.processor.writer.ShowkaseExtensionFunctionsWriter | |||||||||||||||||||||||||||||||||||||||
| 11 airbnb.android.showkase.processor.writer.ShowkaseScreenshotTestWriter | |||||||||||||||||||||||||||||||||||||||
| 12 airbnb.android.showkase.ui.ShowkaseBrowserActivity | |||||||||||||||||||||||||||||||||||||||
| 13 airbnb.android.submodule.showkasesample | |||||||||||||||||||||||||||||||||||||||
| 14 airbnb.android.submodule.showkasesample.payments | |||||||||||||||||||||||||||||||||||||||
| 15 vinaygaba.showkase_browser_testing_submodule | |||||||||||||||||||||||||||||||||||||||
| 16 vinaygaba.showkase_browser_testing_submodule.two | |||||||||||||||||||||||||||||||||||||||
| 17 airbnb.android.showkase.annotation.ScreenshotCaptureType | 3 | ||||||||||||||||||||||||||||||||||||||
| 18 airbnb.android.showkase.annotation.ScreenshotConfig | 3 | ||||||||||||||||||||||||||||||||||||||
| 19 airbnb.android.showkase.models | 1 | ||||||||||||||||||||||||||||||||||||||
| 20 airbnb.android.showkase.processor.models.ShowkaseMetadata | 1 | 3 | |||||||||||||||||||||||||||||||||||||
| 21 airbnb.android.showkase_browser_testing | 1 | ||||||||||||||||||||||||||||||||||||||
| 22 airbnb.android.showkase.models.ShowkaseCategory | 3 | ||||||||||||||||||||||||||||||||||||||
| 23 airbnb.android.showkase.models.ShowkaseCurrentScreen | 9 | ||||||||||||||||||||||||||||||||||||||
| 24 airbnb.android.showkase.processor.models | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 25 airbnb.android.showkase.screenshot.testing | 3 | ||||||||||||||||||||||||||||||||||||||
| 26 airbnb.android.showkase.screenshot.testing.paparazzi | 3 | 3 | |||||||||||||||||||||||||||||||||||||
| 27 airbnb.android.showkase.ui | 30 | ||||||||||||||||||||||||||||||||||||||
| 28 airbnb.android.showkase.processor.models.ShowkaseFunctionType | 4 | ||||||||||||||||||||||||||||||||||||||
| 29 airbnb.android.showkase.processor.models.ShowkaseMetadataType | 3 | ||||||||||||||||||||||||||||||||||||||
| 30 airbnb.android.showkase.processor.writer | 1 | 2 | 3 | 2 | |||||||||||||||||||||||||||||||||||
| 31 airbnb.android.showkase.screenshot.testing.ShowkaseScreenshotType | 3 | ||||||||||||||||||||||||||||||||||||||
| 32 airbnb.android.showkase.screenshot.testing.paparazzi.PaparazziShowkaseScreenshotTest | 2 | ||||||||||||||||||||||||||||||||||||||
| 33 airbnb.android.showkase.screenshot.testing.paparazzi.PaparazziShowkaseUIMode | 2 | ||||||||||||||||||||||||||||||||||||||
| 34 airbnb.android.showkase.screenshot.testing.shot | 2 | ||||||||||||||||||||||||||||||||||||||
| 35 airbnb.android.showkase.ui.ShowkaseComponentCardType | 5 | ||||||||||||||||||||||||||||||||||||||
| 36 airbnb.android.showkase.processor.logging | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 37 airbnb.android.showkase.processor | 1 | 1 | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||
| 38 airbnb.android.showkase.processor.ScreenshotTestType | 2 | ||||||||||||||||||||||||||||||||||||||
| 39 airbnb.android.showkase.processor.ShowkaseGeneratedMetadataType | 4 |
17→1 airbnb.android.showkase.annotation.ScreenshotCaptureType uses airbnb.android.showkase.annotation✕
- Connections
- 3 pairs of types, where a type in airbnb.android.showkase.annotation.ScreenshotCaptureType uses a type in airbnb.android.showkase.annotation.
- The types involved
com.airbnb.android.showkase.annotation.ScreenshotCaptureType.MultipleImagesAtOffsets→com.airbnb.android.showkase.annotation.ScreenshotCaptureTypecom.airbnb.android.showkase.annotation.ScreenshotCaptureType.SingleAnimatedImage→com.airbnb.android.showkase.annotation.ScreenshotCaptureTypecom.airbnb.android.showkase.annotation.ScreenshotCaptureType.SingleStaticImage→com.airbnb.android.showkase.annotation.ScreenshotCaptureType
- Direction
- airbnb.android.showkase.annotation.ScreenshotCaptureType uses airbnb.android.showkase.annotation, so a change to airbnb.android.showkase.annotation can break airbnb.android.showkase.annotation.ScreenshotCaptureType, while a change to airbnb.android.showkase.annotation.ScreenshotCaptureType can't break airbnb.android.showkase.annotation.
- Position
- Below the diagonal: airbnb.android.showkase.annotation.ScreenshotCaptureType uses a module listed above it, which is the healthy direction.
18→1 airbnb.android.showkase.annotation.ScreenshotConfig uses airbnb.android.showkase.annotation✕
- Connections
- 3 pairs of types, where a type in airbnb.android.showkase.annotation.ScreenshotConfig uses a type in airbnb.android.showkase.annotation.
- The types involved
com.airbnb.android.showkase.annotation.ScreenshotConfig.MultipleImagesAtOffsets→com.airbnb.android.showkase.annotation.ScreenshotConfigcom.airbnb.android.showkase.annotation.ScreenshotConfig.SingleAnimatedImage→com.airbnb.android.showkase.annotation.ScreenshotConfigcom.airbnb.android.showkase.annotation.ScreenshotConfig.SingleStaticImage→com.airbnb.android.showkase.annotation.ScreenshotConfig
- Direction
- airbnb.android.showkase.annotation.ScreenshotConfig uses airbnb.android.showkase.annotation, so a change to airbnb.android.showkase.annotation can break airbnb.android.showkase.annotation.ScreenshotConfig, while a change to airbnb.android.showkase.annotation.ScreenshotConfig can't break airbnb.android.showkase.annotation.
- Position
- Below the diagonal: airbnb.android.showkase.annotation.ScreenshotConfig uses a module listed above it, which is the healthy direction.
19→1 airbnb.android.showkase.models uses airbnb.android.showkase.annotation✕
- Connections
- 1 pair of types, where a type in airbnb.android.showkase.models uses a type in airbnb.android.showkase.annotation.
- The types involved
com.airbnb.android.showkase.models.ShowkaseBrowserComponent→com.airbnb.android.showkase.annotation.ScreenshotConfig
- Direction
- airbnb.android.showkase.models uses airbnb.android.showkase.annotation, so a change to airbnb.android.showkase.annotation can break airbnb.android.showkase.models, while a change to airbnb.android.showkase.models can't break airbnb.android.showkase.annotation.
- Position
- Below the diagonal: airbnb.android.showkase.models uses a module listed above it, which is the healthy direction.
20→1 airbnb.android.showkase.processor.models.ShowkaseMetadata uses airbnb.android.showkase.annotation✕
- Connections
- 1 pair of types, where a type in airbnb.android.showkase.processor.models.ShowkaseMetadata uses a type in airbnb.android.showkase.annotation.
- The types involved
com.airbnb.android.showkase.processor.models.ShowkaseMetadata.Component→com.airbnb.android.showkase.annotation.ScreenshotConfig
- Direction
- airbnb.android.showkase.processor.models.ShowkaseMetadata uses airbnb.android.showkase.annotation, so a change to airbnb.android.showkase.annotation can break airbnb.android.showkase.processor.models.ShowkaseMetadata, while a change to airbnb.android.showkase.processor.models.ShowkaseMetadata can't break airbnb.android.showkase.annotation.
- Position
- Below the diagonal: airbnb.android.showkase.processor.models.ShowkaseMetadata uses a module listed above it, which is the healthy direction.
20→24 airbnb.android.showkase.processor.models.ShowkaseMetadata uses airbnb.android.showkase.processor.models part of a loop✕
- Connections
- 3 pairs of types, where a type in airbnb.android.showkase.processor.models.ShowkaseMetadata uses a type in airbnb.android.showkase.processor.models.
- The types involved
com.airbnb.android.showkase.processor.models.ShowkaseMetadata.Color→com.airbnb.android.showkase.processor.models.ShowkaseMetadatacom.airbnb.android.showkase.processor.models.ShowkaseMetadata.Component→com.airbnb.android.showkase.processor.models.ShowkaseMetadatacom.airbnb.android.showkase.processor.models.ShowkaseMetadata.Typography→com.airbnb.android.showkase.processor.models.ShowkaseMetadata
- Direction
- airbnb.android.showkase.processor.models.ShowkaseMetadata uses airbnb.android.showkase.processor.models, so a change to airbnb.android.showkase.processor.models can break airbnb.android.showkase.processor.models.ShowkaseMetadata, while a change to airbnb.android.showkase.processor.models.ShowkaseMetadata can't break airbnb.android.showkase.processor.models.
- 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→1 airbnb.android.showkase_browser_testing uses airbnb.android.showkase.annotation✕
- Connections
- 1 pair of types, where a type in airbnb.android.showkase_browser_testing uses a type in airbnb.android.showkase.annotation.
- The types involved
com.airbnb.android.showkase_browser_testing.MyRootModule→com.airbnb.android.showkase.annotation.ShowkaseRootModule
- Direction
- airbnb.android.showkase_browser_testing uses airbnb.android.showkase.annotation, so a change to airbnb.android.showkase.annotation can break airbnb.android.showkase_browser_testing, while a change to airbnb.android.showkase_browser_testing can't break airbnb.android.showkase.annotation.
- Position
- Below the diagonal: airbnb.android.showkase_browser_testing uses a module listed above it, which is the healthy direction.
22→19 airbnb.android.showkase.models.ShowkaseCategory uses airbnb.android.showkase.models✕
- Connections
- 3 pairs of types, where a type in airbnb.android.showkase.models.ShowkaseCategory uses a type in airbnb.android.showkase.models.
- The types involved
com.airbnb.android.showkase.models.ShowkaseCategory.COLORS→com.airbnb.android.showkase.models.ShowkaseCategorycom.airbnb.android.showkase.models.ShowkaseCategory.COMPONENTS→com.airbnb.android.showkase.models.ShowkaseCategorycom.airbnb.android.showkase.models.ShowkaseCategory.TYPOGRAPHY→com.airbnb.android.showkase.models.ShowkaseCategory
- Direction
- airbnb.android.showkase.models.ShowkaseCategory uses airbnb.android.showkase.models, so a change to airbnb.android.showkase.models can break airbnb.android.showkase.models.ShowkaseCategory, while a change to airbnb.android.showkase.models.ShowkaseCategory can't break airbnb.android.showkase.models.
- Position
- Below the diagonal: airbnb.android.showkase.models.ShowkaseCategory uses a module listed above it, which is the healthy direction.
23→19 airbnb.android.showkase.models.ShowkaseCurrentScreen uses airbnb.android.showkase.models✕
- Connections
- 9 pairs of types, where a type in airbnb.android.showkase.models.ShowkaseCurrentScreen uses a type in airbnb.android.showkase.models.
- The types involved
com.airbnb.android.showkase.models.ShowkaseCurrentScreen.COLORS_IN_A_GROUP→com.airbnb.android.showkase.models.ShowkaseCurrentScreencom.airbnb.android.showkase.models.ShowkaseCurrentScreen.COLOR_GROUPS→com.airbnb.android.showkase.models.ShowkaseCurrentScreencom.airbnb.android.showkase.models.ShowkaseCurrentScreen.COMPONENTS_IN_A_GROUP→com.airbnb.android.showkase.models.ShowkaseCurrentScreencom.airbnb.android.showkase.models.ShowkaseCurrentScreen.COMPONENT_DETAIL→com.airbnb.android.showkase.models.ShowkaseCurrentScreencom.airbnb.android.showkase.models.ShowkaseCurrentScreen.COMPONENT_GROUPS→com.airbnb.android.showkase.models.ShowkaseCurrentScreencom.airbnb.android.showkase.models.ShowkaseCurrentScreen.COMPONENT_STYLES→com.airbnb.android.showkase.models.ShowkaseCurrentScreencom.airbnb.android.showkase.models.ShowkaseCurrentScreen.SHOWKASE_CATEGORIES→com.airbnb.android.showkase.models.ShowkaseCurrentScreencom.airbnb.android.showkase.models.ShowkaseCurrentScreen.TYPOGRAPHY_GROUPS→com.airbnb.android.showkase.models.ShowkaseCurrentScreencom.airbnb.android.showkase.models.ShowkaseCurrentScreen.TYPOGRAPHY_IN_A_GROUP→com.airbnb.android.showkase.models.ShowkaseCurrentScreen
- Direction
- airbnb.android.showkase.models.ShowkaseCurrentScreen uses airbnb.android.showkase.models, so a change to airbnb.android.showkase.models can break airbnb.android.showkase.models.ShowkaseCurrentScreen, while a change to airbnb.android.showkase.models.ShowkaseCurrentScreen can't break airbnb.android.showkase.models.
- Position
- Below the diagonal: airbnb.android.showkase.models.ShowkaseCurrentScreen uses a module listed above it, which is the healthy direction.
24→1 airbnb.android.showkase.processor.models uses airbnb.android.showkase.annotation✕
- Connections
- 2 pairs of types, where a type in airbnb.android.showkase.processor.models uses a type in airbnb.android.showkase.annotation.
- The types involved
com.airbnb.android.showkase.processor.models.ShowkaseMetadataKt→com.airbnb.android.showkase.annotation.ScreenshotConfigcom.airbnb.android.showkase.processor.models.ShowkaseMetadataKt→com.airbnb.android.showkase.annotation.ShowkaseMultiPreviewCodegenMetadata
- Direction
- airbnb.android.showkase.processor.models uses airbnb.android.showkase.annotation, so a change to airbnb.android.showkase.annotation can break airbnb.android.showkase.processor.models, while a change to airbnb.android.showkase.processor.models can't break airbnb.android.showkase.annotation.
- Position
- Below the diagonal: airbnb.android.showkase.processor.models uses a module listed above it, which is the healthy direction.
24→20 airbnb.android.showkase.processor.models uses airbnb.android.showkase.processor.models.ShowkaseMetadata✕
- Connections
- 1 pair of types, where a type in airbnb.android.showkase.processor.models uses a type in airbnb.android.showkase.processor.models.ShowkaseMetadata.
- The types involved
com.airbnb.android.showkase.processor.models.ShowkaseMetadataKt→com.airbnb.android.showkase.processor.models.ShowkaseMetadata.Component
- Direction
- airbnb.android.showkase.processor.models uses airbnb.android.showkase.processor.models.ShowkaseMetadata, so a change to airbnb.android.showkase.processor.models.ShowkaseMetadata can break airbnb.android.showkase.processor.models, while a change to airbnb.android.showkase.processor.models can't break airbnb.android.showkase.processor.models.ShowkaseMetadata.
- Position
- Below the diagonal: airbnb.android.showkase.processor.models uses a module listed above it, which is the healthy direction.
24→36 airbnb.android.showkase.processor.models uses airbnb.android.showkase.processor.logging part of a loop✕
- Connections
- 1 pair of types, where a type in airbnb.android.showkase.processor.models uses a type in airbnb.android.showkase.processor.logging.
- The types involved
com.airbnb.android.showkase.processor.models.ShowkaseMetadataKt→com.airbnb.android.showkase.processor.logging.ShowkaseValidator
- Direction
- airbnb.android.showkase.processor.models uses airbnb.android.showkase.processor.logging, so a change to airbnb.android.showkase.processor.logging can break airbnb.android.showkase.processor.models, while a change to airbnb.android.showkase.processor.models can't break airbnb.android.showkase.processor.logging.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→19 airbnb.android.showkase.screenshot.testing uses airbnb.android.showkase.models✕
- Connections
- 3 pairs of types, where a type in airbnb.android.showkase.screenshot.testing uses a type in airbnb.android.showkase.models.
- The types involved
com.airbnb.android.showkase.screenshot.testing.ShowkaseScreenshotTest→com.airbnb.android.showkase.models.ShowkaseBrowserColorcom.airbnb.android.showkase.screenshot.testing.ShowkaseScreenshotTest→com.airbnb.android.showkase.models.ShowkaseBrowserComponentcom.airbnb.android.showkase.screenshot.testing.ShowkaseScreenshotTest→com.airbnb.android.showkase.models.ShowkaseBrowserTypography
- Direction
- airbnb.android.showkase.screenshot.testing uses airbnb.android.showkase.models, so a change to airbnb.android.showkase.models can break airbnb.android.showkase.screenshot.testing, while a change to airbnb.android.showkase.screenshot.testing can't break airbnb.android.showkase.models.
- Position
- Below the diagonal: airbnb.android.showkase.screenshot.testing uses a module listed above it, which is the healthy direction.
26→1 airbnb.android.showkase.screenshot.testing.paparazzi uses airbnb.android.showkase.annotation✕
- Connections
- 3 pairs of types, where a type in airbnb.android.showkase.screenshot.testing.paparazzi uses a type in airbnb.android.showkase.annotation.
- The types involved
com.airbnb.android.showkase.screenshot.testing.paparazzi.ComponentPaparazziShowkaseTestPreview→com.airbnb.android.showkase.annotation.ScreenshotConfigcom.airbnb.android.showkase.screenshot.testing.paparazzi.PaparazziShowkaseScreenshotTest→com.airbnb.android.showkase.annotation.ScreenshotConfigcom.airbnb.android.showkase.screenshot.testing.paparazzi.PaparazziShowkaseTestPreview→com.airbnb.android.showkase.annotation.ScreenshotConfig
- Direction
- airbnb.android.showkase.screenshot.testing.paparazzi uses airbnb.android.showkase.annotation, so a change to airbnb.android.showkase.annotation can break airbnb.android.showkase.screenshot.testing.paparazzi, while a change to airbnb.android.showkase.screenshot.testing.paparazzi can't break airbnb.android.showkase.annotation.
- Position
- Below the diagonal: airbnb.android.showkase.screenshot.testing.paparazzi uses a module listed above it, which is the healthy direction.
26→19 airbnb.android.showkase.screenshot.testing.paparazzi uses airbnb.android.showkase.models✕
- Connections
- 3 pairs of types, where a type in airbnb.android.showkase.screenshot.testing.paparazzi uses a type in airbnb.android.showkase.models.
- The types involved
com.airbnb.android.showkase.screenshot.testing.paparazzi.ColorPaparazziShowkaseTestPreview→com.airbnb.android.showkase.models.ShowkaseBrowserColorcom.airbnb.android.showkase.screenshot.testing.paparazzi.ComponentPaparazziShowkaseTestPreview→com.airbnb.android.showkase.models.ShowkaseBrowserComponentcom.airbnb.android.showkase.screenshot.testing.paparazzi.TypographyPaparazziShowkaseTestPreview→com.airbnb.android.showkase.models.ShowkaseBrowserTypography
- Direction
- airbnb.android.showkase.screenshot.testing.paparazzi uses airbnb.android.showkase.models, so a change to airbnb.android.showkase.models can break airbnb.android.showkase.screenshot.testing.paparazzi, while a change to airbnb.android.showkase.screenshot.testing.paparazzi can't break airbnb.android.showkase.models.
- Position
- Below the diagonal: airbnb.android.showkase.screenshot.testing.paparazzi uses a module listed above it, which is the healthy direction.
27→19 airbnb.android.showkase.ui uses airbnb.android.showkase.models✕
- Connections
- 30 pairs of types, where a type in airbnb.android.showkase.ui uses a type in airbnb.android.showkase.models. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.airbnb.android.showkase.ui.CommonComponentsKt→com.airbnb.android.showkase.models.ShowkaseBrowserComponentcom.airbnb.android.showkase.ui.ShowkaseBrowserActivity→com.airbnb.android.showkase.models.ShowkaseElementsMetadatacom.airbnb.android.showkase.ui.ShowkaseBrowserAppKt→com.airbnb.android.showkase.models.ShowkaseBrowserColorcom.airbnb.android.showkase.ui.ShowkaseBrowserAppKt→com.airbnb.android.showkase.models.ShowkaseBrowserComponentcom.airbnb.android.showkase.ui.ShowkaseBrowserAppKt→com.airbnb.android.showkase.models.ShowkaseBrowserScreenMetadatacom.airbnb.android.showkase.ui.ShowkaseBrowserAppKt→com.airbnb.android.showkase.models.ShowkaseBrowserTypographycom.airbnb.android.showkase.ui.ShowkaseBrowserAppKt→com.airbnb.android.showkase.models.ShowkaseCategorycom.airbnb.android.showkase.ui.ShowkaseBrowserAppKt→com.airbnb.android.showkase.models.ShowkaseCurrentScreencom.airbnb.android.showkase.ui.ShowkaseCategoriesScreenKt→com.airbnb.android.showkase.models.ShowkaseBrowserScreenMetadatacom.airbnb.android.showkase.ui.ShowkaseCategoriesScreenKt→com.airbnb.android.showkase.models.ShowkaseCategorycom.airbnb.android.showkase.ui.ShowkaseColorsInAGroupScreenKt→com.airbnb.android.showkase.models.ShowkaseBrowserColorcom.airbnb.android.showkase.ui.ShowkaseColorsInAGroupScreenKt→com.airbnb.android.showkase.models.ShowkaseBrowserScreenMetadatacom.airbnb.android.showkase.ui.ShowkaseColorsInAGroupScreenKt→com.airbnb.android.showkase.models.ShowkaseCurrentScreencom.airbnb.android.showkase.ui.ShowkaseComponentDetailScreenKt→com.airbnb.android.showkase.models.ShowkaseBrowserComponentcom.airbnb.android.showkase.ui.ShowkaseComponentDetailScreenKt→com.airbnb.android.showkase.models.ShowkaseBrowserScreenMetadatacom.airbnb.android.showkase.ui.ShowkaseComponentDetailScreenKt→com.airbnb.android.showkase.models.ShowkaseCurrentScreencom.airbnb.android.showkase.ui.ShowkaseComponentStylesScreenKt→com.airbnb.android.showkase.models.ShowkaseBrowserComponentcom.airbnb.android.showkase.ui.ShowkaseComponentStylesScreenKt→com.airbnb.android.showkase.models.ShowkaseBrowserScreenMetadatacom.airbnb.android.showkase.ui.ShowkaseComponentStylesScreenKt→com.airbnb.android.showkase.models.ShowkaseCurrentScreencom.airbnb.android.showkase.ui.ShowkaseComponentsInAGroupScreenKt→com.airbnb.android.showkase.models.ShowkaseBrowserComponentcom.airbnb.android.showkase.ui.ShowkaseComponentsInAGroupScreenKt→com.airbnb.android.showkase.models.ShowkaseBrowserScreenMetadatacom.airbnb.android.showkase.ui.ShowkaseComponentsInAGroupScreenKt→com.airbnb.android.showkase.models.ShowkaseCurrentScreencom.airbnb.android.showkase.ui.ShowkaseGroupsScreenKt→com.airbnb.android.showkase.models.ShowkaseBrowserColorcom.airbnb.android.showkase.ui.ShowkaseGroupsScreenKt→com.airbnb.android.showkase.models.ShowkaseBrowserComponentcom.airbnb.android.showkase.ui.ShowkaseGroupsScreenKt→com.airbnb.android.showkase.models.ShowkaseBrowserScreenMetadata
- Direction
- airbnb.android.showkase.ui uses airbnb.android.showkase.models, so a change to airbnb.android.showkase.models can break airbnb.android.showkase.ui, while a change to airbnb.android.showkase.ui can't break airbnb.android.showkase.models.
- Position
- Below the diagonal: airbnb.android.showkase.ui uses a module listed above it, which is the healthy direction.
28→24 airbnb.android.showkase.processor.models.ShowkaseFunctionType uses airbnb.android.showkase.processor.models✕
- Connections
- 4 pairs of types, where a type in airbnb.android.showkase.processor.models.ShowkaseFunctionType uses a type in airbnb.android.showkase.processor.models.
- The types involved
com.airbnb.android.showkase.processor.models.ShowkaseFunctionType.INSIDE_CLASS→com.airbnb.android.showkase.processor.models.ShowkaseFunctionTypecom.airbnb.android.showkase.processor.models.ShowkaseFunctionType.INSIDE_COMPANION_OBJECT→com.airbnb.android.showkase.processor.models.ShowkaseFunctionTypecom.airbnb.android.showkase.processor.models.ShowkaseFunctionType.INSIDE_OBJECT→com.airbnb.android.showkase.processor.models.ShowkaseFunctionTypecom.airbnb.android.showkase.processor.models.ShowkaseFunctionType.TOP_LEVEL→com.airbnb.android.showkase.processor.models.ShowkaseFunctionType
- Direction
- airbnb.android.showkase.processor.models.ShowkaseFunctionType uses airbnb.android.showkase.processor.models, so a change to airbnb.android.showkase.processor.models can break airbnb.android.showkase.processor.models.ShowkaseFunctionType, while a change to airbnb.android.showkase.processor.models.ShowkaseFunctionType can't break airbnb.android.showkase.processor.models.
- Position
- Below the diagonal: airbnb.android.showkase.processor.models.ShowkaseFunctionType uses a module listed above it, which is the healthy direction.
29→24 airbnb.android.showkase.processor.models.ShowkaseMetadataType uses airbnb.android.showkase.processor.models✕
- Connections
- 3 pairs of types, where a type in airbnb.android.showkase.processor.models.ShowkaseMetadataType uses a type in airbnb.android.showkase.processor.models.
- The types involved
com.airbnb.android.showkase.processor.models.ShowkaseMetadataType.COLOR→com.airbnb.android.showkase.processor.models.ShowkaseMetadataTypecom.airbnb.android.showkase.processor.models.ShowkaseMetadataType.COMPONENT→com.airbnb.android.showkase.processor.models.ShowkaseMetadataTypecom.airbnb.android.showkase.processor.models.ShowkaseMetadataType.TYPOGRAPHY→com.airbnb.android.showkase.processor.models.ShowkaseMetadataType
- Direction
- airbnb.android.showkase.processor.models.ShowkaseMetadataType uses airbnb.android.showkase.processor.models, so a change to airbnb.android.showkase.processor.models can break airbnb.android.showkase.processor.models.ShowkaseMetadataType, while a change to airbnb.android.showkase.processor.models.ShowkaseMetadataType can't break airbnb.android.showkase.processor.models.
- Position
- Below the diagonal: airbnb.android.showkase.processor.models.ShowkaseMetadataType uses a module listed above it, which is the healthy direction.
30→1 airbnb.android.showkase.processor.writer uses airbnb.android.showkase.annotation✕
- Connections
- 1 pair of types, where a type in airbnb.android.showkase.processor.writer uses a type in airbnb.android.showkase.annotation.
- The types involved
com.airbnb.android.showkase.processor.writer.WriterUtilsKt→com.airbnb.android.showkase.annotation.ScreenshotConfig
- Direction
- airbnb.android.showkase.processor.writer uses airbnb.android.showkase.annotation, so a change to airbnb.android.showkase.annotation can break airbnb.android.showkase.processor.writer, while a change to airbnb.android.showkase.processor.writer can't break airbnb.android.showkase.annotation.
- Position
- Below the diagonal: airbnb.android.showkase.processor.writer uses a module listed above it, which is the healthy direction.
30→20 airbnb.android.showkase.processor.writer uses airbnb.android.showkase.processor.models.ShowkaseMetadata✕
- Connections
- 2 pairs of types, where a type in airbnb.android.showkase.processor.writer uses a type in airbnb.android.showkase.processor.models.ShowkaseMetadata.
- The types involved
com.airbnb.android.showkase.processor.writer.ShowkaseBrowserPropertyWriter→com.airbnb.android.showkase.processor.models.ShowkaseMetadata.Componentcom.airbnb.android.showkase.processor.writer.WriterUtilsKt→com.airbnb.android.showkase.processor.models.ShowkaseMetadata.Component
- Direction
- airbnb.android.showkase.processor.writer uses airbnb.android.showkase.processor.models.ShowkaseMetadata, so a change to airbnb.android.showkase.processor.models.ShowkaseMetadata can break airbnb.android.showkase.processor.writer, while a change to airbnb.android.showkase.processor.writer can't break airbnb.android.showkase.processor.models.ShowkaseMetadata.
- Position
- Below the diagonal: airbnb.android.showkase.processor.writer uses a module listed above it, which is the healthy direction.
30→24 airbnb.android.showkase.processor.writer uses airbnb.android.showkase.processor.models✕
- Connections
- 3 pairs of types, where a type in airbnb.android.showkase.processor.writer uses a type in airbnb.android.showkase.processor.models.
- The types involved
com.airbnb.android.showkase.processor.writer.ShowkaseBrowserPropertyWriter→com.airbnb.android.showkase.processor.models.ShowkaseMetadatacom.airbnb.android.showkase.processor.writer.ShowkaseCodegenMetadataWriter→com.airbnb.android.showkase.processor.models.ShowkaseMetadatacom.airbnb.android.showkase.processor.writer.WriterUtilsKt→com.airbnb.android.showkase.processor.models.ShowkaseMetadata
- Direction
- airbnb.android.showkase.processor.writer uses airbnb.android.showkase.processor.models, so a change to airbnb.android.showkase.processor.models can break airbnb.android.showkase.processor.writer, while a change to airbnb.android.showkase.processor.writer can't break airbnb.android.showkase.processor.models.
- Position
- Below the diagonal: airbnb.android.showkase.processor.writer uses a module listed above it, which is the healthy direction.
30→37 airbnb.android.showkase.processor.writer uses airbnb.android.showkase.processor part of a loop✕
- Connections
- 2 pairs of types, where a type in airbnb.android.showkase.processor.writer uses a type in airbnb.android.showkase.processor.
- The types involved
com.airbnb.android.showkase.processor.writer.ShowkaseBrowserProperties→com.airbnb.android.showkase.processor.ShowkaseGeneratedMetadatacom.airbnb.android.showkase.processor.writer.ShowkaseBrowserWriter→com.airbnb.android.showkase.processor.ShowkaseGeneratedMetadata
- Direction
- airbnb.android.showkase.processor.writer uses airbnb.android.showkase.processor, so a change to airbnb.android.showkase.processor can break airbnb.android.showkase.processor.writer, while a change to airbnb.android.showkase.processor.writer can't break airbnb.android.showkase.processor.
- 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.
31→25 airbnb.android.showkase.screenshot.testing.ShowkaseScreenshotType uses airbnb.android.showkase.screenshot.testing✕
- Connections
- 3 pairs of types, where a type in airbnb.android.showkase.screenshot.testing.ShowkaseScreenshotType uses a type in airbnb.android.showkase.screenshot.testing.
- The types involved
com.airbnb.android.showkase.screenshot.testing.ShowkaseScreenshotType.Color→com.airbnb.android.showkase.screenshot.testing.ShowkaseScreenshotTypecom.airbnb.android.showkase.screenshot.testing.ShowkaseScreenshotType.Composable→com.airbnb.android.showkase.screenshot.testing.ShowkaseScreenshotTypecom.airbnb.android.showkase.screenshot.testing.ShowkaseScreenshotType.Typography→com.airbnb.android.showkase.screenshot.testing.ShowkaseScreenshotType
- Direction
- airbnb.android.showkase.screenshot.testing.ShowkaseScreenshotType uses airbnb.android.showkase.screenshot.testing, so a change to airbnb.android.showkase.screenshot.testing can break airbnb.android.showkase.screenshot.testing.ShowkaseScreenshotType, while a change to airbnb.android.showkase.screenshot.testing.ShowkaseScreenshotType can't break airbnb.android.showkase.screenshot.testing.
- Position
- Below the diagonal: airbnb.android.showkase.screenshot.testing.ShowkaseScreenshotType uses a module listed above it, which is the healthy direction.
32→26 airbnb.android.showkase.screenshot.testing.paparazzi.PaparazziShowkaseScreenshotTest uses airbnb.android.showkase.screenshot.testing.paparazzi✕
- Connections
- 2 pairs of types, where a type in airbnb.android.showkase.screenshot.testing.paparazzi.PaparazziShowkaseScreenshotTest uses a type in airbnb.android.showkase.screenshot.testing.paparazzi.
- The types involved
com.airbnb.android.showkase.screenshot.testing.paparazzi.PaparazziShowkaseScreenshotTest.CompanionObject→com.airbnb.android.showkase.screenshot.testing.paparazzi.PaparazziShowkaseDeviceConfigcom.airbnb.android.showkase.screenshot.testing.paparazzi.PaparazziShowkaseScreenshotTest.CompanionObject→com.airbnb.android.showkase.screenshot.testing.paparazzi.PaparazziShowkaseUIMode
- Direction
- airbnb.android.showkase.screenshot.testing.paparazzi.PaparazziShowkaseScreenshotTest uses airbnb.android.showkase.screenshot.testing.paparazzi, so a change to airbnb.android.showkase.screenshot.testing.paparazzi can break airbnb.android.showkase.screenshot.testing.paparazzi.PaparazziShowkaseScreenshotTest, while a change to airbnb.android.showkase.screenshot.testing.paparazzi.PaparazziShowkaseScreenshotTest can't break airbnb.android.showkase.screenshot.testing.paparazzi.
- Position
- Below the diagonal: airbnb.android.showkase.screenshot.testing.paparazzi.PaparazziShowkaseScreenshotTest uses a module listed above it, which is the healthy direction.
33→26 airbnb.android.showkase.screenshot.testing.paparazzi.PaparazziShowkaseUIMode uses airbnb.android.showkase.screenshot.testing.paparazzi✕
- Connections
- 2 pairs of types, where a type in airbnb.android.showkase.screenshot.testing.paparazzi.PaparazziShowkaseUIMode uses a type in airbnb.android.showkase.screenshot.testing.paparazzi.
- The types involved
com.airbnb.android.showkase.screenshot.testing.paparazzi.PaparazziShowkaseUIMode.DARK→com.airbnb.android.showkase.screenshot.testing.paparazzi.PaparazziShowkaseUIModecom.airbnb.android.showkase.screenshot.testing.paparazzi.PaparazziShowkaseUIMode.DEFAULT→com.airbnb.android.showkase.screenshot.testing.paparazzi.PaparazziShowkaseUIMode
- Direction
- airbnb.android.showkase.screenshot.testing.paparazzi.PaparazziShowkaseUIMode uses airbnb.android.showkase.screenshot.testing.paparazzi, so a change to airbnb.android.showkase.screenshot.testing.paparazzi can break airbnb.android.showkase.screenshot.testing.paparazzi.PaparazziShowkaseUIMode, while a change to airbnb.android.showkase.screenshot.testing.paparazzi.PaparazziShowkaseUIMode can't break airbnb.android.showkase.screenshot.testing.paparazzi.
- Position
- Below the diagonal: airbnb.android.showkase.screenshot.testing.paparazzi.PaparazziShowkaseUIMode uses a module listed above it, which is the healthy direction.
34→25 airbnb.android.showkase.screenshot.testing.shot uses airbnb.android.showkase.screenshot.testing✕
- Connections
- 2 pairs of types, where a type in airbnb.android.showkase.screenshot.testing.shot uses a type in airbnb.android.showkase.screenshot.testing.
- The types involved
com.airbnb.android.showkase.screenshot.testing.shot.ShotShowkaseScreenshotTest→com.airbnb.android.showkase.screenshot.testing.ShowkaseScreenshotTestcom.airbnb.android.showkase.screenshot.testing.shot.ShotShowkaseScreenshotTest→com.airbnb.android.showkase.screenshot.testing.ShowkaseScreenshotType
- Direction
- airbnb.android.showkase.screenshot.testing.shot uses airbnb.android.showkase.screenshot.testing, so a change to airbnb.android.showkase.screenshot.testing can break airbnb.android.showkase.screenshot.testing.shot, while a change to airbnb.android.showkase.screenshot.testing.shot can't break airbnb.android.showkase.screenshot.testing.
- Position
- Below the diagonal: airbnb.android.showkase.screenshot.testing.shot uses a module listed above it, which is the healthy direction.
35→27 airbnb.android.showkase.ui.ShowkaseComponentCardType uses airbnb.android.showkase.ui✕
- Connections
- 5 pairs of types, where a type in airbnb.android.showkase.ui.ShowkaseComponentCardType uses a type in airbnb.android.showkase.ui.
- The types involved
com.airbnb.android.showkase.ui.ShowkaseComponentCardType.BASIC→com.airbnb.android.showkase.ui.ShowkaseComponentCardTypecom.airbnb.android.showkase.ui.ShowkaseComponentCardType.DARK_MODE→com.airbnb.android.showkase.ui.ShowkaseComponentCardTypecom.airbnb.android.showkase.ui.ShowkaseComponentCardType.DISPLAY_SCALED→com.airbnb.android.showkase.ui.ShowkaseComponentCardTypecom.airbnb.android.showkase.ui.ShowkaseComponentCardType.FONT_SCALE→com.airbnb.android.showkase.ui.ShowkaseComponentCardTypecom.airbnb.android.showkase.ui.ShowkaseComponentCardType.RTL→com.airbnb.android.showkase.ui.ShowkaseComponentCardType
- Direction
- airbnb.android.showkase.ui.ShowkaseComponentCardType uses airbnb.android.showkase.ui, so a change to airbnb.android.showkase.ui can break airbnb.android.showkase.ui.ShowkaseComponentCardType, while a change to airbnb.android.showkase.ui.ShowkaseComponentCardType can't break airbnb.android.showkase.ui.
- Position
- Below the diagonal: airbnb.android.showkase.ui.ShowkaseComponentCardType uses a module listed above it, which is the healthy direction.
36→30 airbnb.android.showkase.processor.logging uses airbnb.android.showkase.processor.writer✕
- Connections
- 1 pair of types, where a type in airbnb.android.showkase.processor.logging uses a type in airbnb.android.showkase.processor.writer.
- The types involved
com.airbnb.android.showkase.processor.logging.ShowkaseValidator→com.airbnb.android.showkase.processor.writer.ShowkaseBrowserProperties
- Direction
- airbnb.android.showkase.processor.logging uses airbnb.android.showkase.processor.writer, so a change to airbnb.android.showkase.processor.writer can break airbnb.android.showkase.processor.logging, while a change to airbnb.android.showkase.processor.logging can't break airbnb.android.showkase.processor.writer.
- Position
- Below the diagonal: airbnb.android.showkase.processor.logging uses a module listed above it, which is the healthy direction.
36→37 airbnb.android.showkase.processor.logging uses airbnb.android.showkase.processor part of a loop✕
- Connections
- 1 pair of types, where a type in airbnb.android.showkase.processor.logging uses a type in airbnb.android.showkase.processor.
- The types involved
com.airbnb.android.showkase.processor.logging.ShowkaseValidator→com.airbnb.android.showkase.processor.ScreenshotTestType
- Direction
- airbnb.android.showkase.processor.logging uses airbnb.android.showkase.processor, so a change to airbnb.android.showkase.processor can break airbnb.android.showkase.processor.logging, while a change to airbnb.android.showkase.processor.logging can't break airbnb.android.showkase.processor.
- 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.
37→1 airbnb.android.showkase.processor uses airbnb.android.showkase.annotation✕
- Connections
- 1 pair of types, where a type in airbnb.android.showkase.processor uses a type in airbnb.android.showkase.annotation.
- The types involved
com.airbnb.android.showkase.processor.ShowkaseProcessor→com.airbnb.android.showkase.annotation.ShowkaseRootCodegen
- Direction
- airbnb.android.showkase.processor uses airbnb.android.showkase.annotation, so a change to airbnb.android.showkase.annotation can break airbnb.android.showkase.processor, while a change to airbnb.android.showkase.processor can't break airbnb.android.showkase.annotation.
- Position
- Below the diagonal: airbnb.android.showkase.processor uses a module listed above it, which is the healthy direction.
37→4 airbnb.android.showkase.processor uses airbnb.android.showkase.processor.Timer✕
- Connections
- 1 pair of types, where a type in airbnb.android.showkase.processor uses a type in airbnb.android.showkase.processor.Timer.
- The types involved
com.airbnb.android.showkase.processor.Timer→com.airbnb.android.showkase.processor.Timer.TimingStep
- Direction
- airbnb.android.showkase.processor uses airbnb.android.showkase.processor.Timer, so a change to airbnb.android.showkase.processor.Timer can break airbnb.android.showkase.processor, while a change to airbnb.android.showkase.processor can't break airbnb.android.showkase.processor.Timer.
- Position
- Below the diagonal: airbnb.android.showkase.processor uses a module listed above it, which is the healthy direction.
37→20 airbnb.android.showkase.processor uses airbnb.android.showkase.processor.models.ShowkaseMetadata✕
- Connections
- 1 pair of types, where a type in airbnb.android.showkase.processor uses a type in airbnb.android.showkase.processor.models.ShowkaseMetadata.
- The types involved
com.airbnb.android.showkase.processor.ShowkaseProcessor→com.airbnb.android.showkase.processor.models.ShowkaseMetadata.Component
- Direction
- airbnb.android.showkase.processor uses airbnb.android.showkase.processor.models.ShowkaseMetadata, so a change to airbnb.android.showkase.processor.models.ShowkaseMetadata can break airbnb.android.showkase.processor, while a change to airbnb.android.showkase.processor can't break airbnb.android.showkase.processor.models.ShowkaseMetadata.
- Position
- Below the diagonal: airbnb.android.showkase.processor uses a module listed above it, which is the healthy direction.
37→24 airbnb.android.showkase.processor uses airbnb.android.showkase.processor.models✕
- Connections
- 1 pair of types, where a type in airbnb.android.showkase.processor uses a type in airbnb.android.showkase.processor.models.
- The types involved
com.airbnb.android.showkase.processor.ShowkaseProcessor→com.airbnb.android.showkase.processor.models.ShowkaseMetadata
- Direction
- airbnb.android.showkase.processor uses airbnb.android.showkase.processor.models, so a change to airbnb.android.showkase.processor.models can break airbnb.android.showkase.processor, while a change to airbnb.android.showkase.processor can't break airbnb.android.showkase.processor.models.
- Position
- Below the diagonal: airbnb.android.showkase.processor uses a module listed above it, which is the healthy direction.
37→30 airbnb.android.showkase.processor uses airbnb.android.showkase.processor.writer✕
- Connections
- 1 pair of types, where a type in airbnb.android.showkase.processor uses a type in airbnb.android.showkase.processor.writer.
- The types involved
com.airbnb.android.showkase.processor.ShowkaseProcessor→com.airbnb.android.showkase.processor.writer.ShowkaseBrowserProperties
- Direction
- airbnb.android.showkase.processor uses airbnb.android.showkase.processor.writer, so a change to airbnb.android.showkase.processor.writer can break airbnb.android.showkase.processor, while a change to airbnb.android.showkase.processor can't break airbnb.android.showkase.processor.writer.
- Position
- Below the diagonal: airbnb.android.showkase.processor uses a module listed above it, which is the healthy direction.
37→36 airbnb.android.showkase.processor uses airbnb.android.showkase.processor.logging✕
- Connections
- 2 pairs of types, where a type in airbnb.android.showkase.processor uses a type in airbnb.android.showkase.processor.logging.
- The types involved
com.airbnb.android.showkase.processor.ShowkaseProcessor→com.airbnb.android.showkase.processor.logging.ShowkaseExceptionLoggercom.airbnb.android.showkase.processor.ShowkaseProcessor→com.airbnb.android.showkase.processor.logging.ShowkaseValidator
- Direction
- airbnb.android.showkase.processor uses airbnb.android.showkase.processor.logging, so a change to airbnb.android.showkase.processor.logging can break airbnb.android.showkase.processor, while a change to airbnb.android.showkase.processor can't break airbnb.android.showkase.processor.logging.
- Position
- Below the diagonal: airbnb.android.showkase.processor uses a module listed above it, which is the healthy direction.
38→37 airbnb.android.showkase.processor.ScreenshotTestType uses airbnb.android.showkase.processor✕
- Connections
- 2 pairs of types, where a type in airbnb.android.showkase.processor.ScreenshotTestType uses a type in airbnb.android.showkase.processor.
- The types involved
com.airbnb.android.showkase.processor.ScreenshotTestType.PAPARAZZI_SHOWKASE→com.airbnb.android.showkase.processor.ScreenshotTestTypecom.airbnb.android.showkase.processor.ScreenshotTestType.SHOWKASE→com.airbnb.android.showkase.processor.ScreenshotTestType
- Direction
- airbnb.android.showkase.processor.ScreenshotTestType uses airbnb.android.showkase.processor, so a change to airbnb.android.showkase.processor can break airbnb.android.showkase.processor.ScreenshotTestType, while a change to airbnb.android.showkase.processor.ScreenshotTestType can't break airbnb.android.showkase.processor.
- Position
- Below the diagonal: airbnb.android.showkase.processor.ScreenshotTestType uses a module listed above it, which is the healthy direction.
39→37 airbnb.android.showkase.processor.ShowkaseGeneratedMetadataType uses airbnb.android.showkase.processor✕
- Connections
- 4 pairs of types, where a type in airbnb.android.showkase.processor.ShowkaseGeneratedMetadataType uses a type in airbnb.android.showkase.processor.
- The types involved
com.airbnb.android.showkase.processor.ShowkaseGeneratedMetadataType.COLOR→com.airbnb.android.showkase.processor.ShowkaseGeneratedMetadataTypecom.airbnb.android.showkase.processor.ShowkaseGeneratedMetadataType.COMPONENTS_WITHOUT_PARAMETER→com.airbnb.android.showkase.processor.ShowkaseGeneratedMetadataTypecom.airbnb.android.showkase.processor.ShowkaseGeneratedMetadataType.COMPONENTS_WITH_PARAMETER→com.airbnb.android.showkase.processor.ShowkaseGeneratedMetadataTypecom.airbnb.android.showkase.processor.ShowkaseGeneratedMetadataType.TYPOGRAPHY→com.airbnb.android.showkase.processor.ShowkaseGeneratedMetadataType
- Direction
- airbnb.android.showkase.processor.ShowkaseGeneratedMetadataType uses airbnb.android.showkase.processor, so a change to airbnb.android.showkase.processor can break airbnb.android.showkase.processor.ShowkaseGeneratedMetadataType, while a change to airbnb.android.showkase.processor.ShowkaseGeneratedMetadataType can't break airbnb.android.showkase.processor.
- Position
- Below the diagonal: airbnb.android.showkase.processor.ShowkaseGeneratedMetadataType uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 17 | High / Critical |
Roadmap
Top priorities: Resolve the 31 Orphaned file finding(s) in Knowledge Freshness — start with build.gradle (7), ShowkaseValidator.kt, WriterUtils.kt; Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them; Resolve the 18 Low coverage finding(s) in Code Coverage — start with ScreenshotConfig.kt, ShowkaseComposable.kt, BaseProcessor.kt.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 31 Orphaned file finding(s) in Knowledge Freshness — start with build.gradle (7), ShowkaseValidator.kt, WriterUtils.kt. | +9.5 pts | Medium | Knowledge Freshness |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +6.9 pts | Medium | Architecture documentation |
| Resolve the 18 Low coverage finding(s) in Code Coverage — start with ScreenshotConfig.kt, ShowkaseComposable.kt, BaseProcessor.kt. | +5.4 pts | Medium | Code Coverage |
| Resolve the 18 Tests reach code only in some runs finding(s) in Code Coverage — start with ScreenshotConfig.kt, ShowkaseComposable.kt, BaseProcessor.kt. | +5.4 pts | Medium | Code Coverage |
| Swallowed exception (caught, then discarded) | +2.8 pts | Medium | Exception handling |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +2.3 pts | Medium | Release Hygiene |
| Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with ShowkaseProcessor.kt, ShowkaseBrowserApp.kt, ShowkaseMetadata.kt. | +1.1 pts | Low | Knowledge Freshness |
| Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite. | +1.6 pts | Medium | Documentation (README) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| showkase-processor/src/main/java/com/airbnb/android/showkase/processor/ShowkaseProcessor.kt | 6.0 | Mixed | Explicit Debt: TodoComment |
| showkase-processor/src/main/java/com/airbnb/android/showkase/processor/models/ShowkaseMetadata.kt | 6.0 | Mixed | Explicit Debt: TodoComment |
| showkase-processor/src/main/java/com/airbnb/android/showkase/processor/logging/ShowkaseValidator.kt | 6.0 | Mixed | Explicit Debt: TodoComment |
| showkase-processor/src/main/java/com/airbnb/android/showkase/processor/writer/ShowkaseBrowserPropertyWriter.kt | 6.5 | Mixed | Code Duplication: Duplicated block (12–13 lines × 2) |
| sample/src/main/java/com/airbnb/android/showkasesample/Text.kt | 7.2 | Mixed | Code Duplication: Edited copies of one member (4 members, 16+ corresponding lines) |
| sample/src/main/java/com/airbnb/android/showkasesample/Rows.kt | 7.2 | Mixed | Code Duplication: Duplicated block (43–44 lines × 2) |
| showkase-annotation/src/main/java/com/airbnb/android/showkase/annotation/ScreenshotConfig.kt | 8.0 | Near-clean | Code Coverage: Low coverage: showkase-annotation/src/main/java/com/airbnb/android/showkase/annotation/ScreenshotConfig.kt |
| showkase-annotation/src/main/java/com/airbnb/android/showkase/annotation/ShowkaseComposable.kt | 8.0 | Near-clean | Code Coverage: Low coverage: showkase-annotation/src/main/java/com/airbnb/android/showkase/annotation/ShowkaseComposable.kt |
| showkase-processor/src/main/java/com/airbnb/android/showkase/processor/BaseProcessor.kt | 8.0 | Near-clean | Code Coverage: Low coverage: showkase-processor/src/main/java/com/airbnb/android/showkase/processor/BaseProcessor.kt |
| showkase-processor/src/main/java/com/airbnb/android/showkase/processor/Timer.kt | 8.0 | Near-clean | Code Coverage: Low coverage: showkase-processor/src/main/java/com/airbnb/android/showkase/processor/Timer.kt |
| showkase-processor/src/main/java/com/airbnb/android/showkase/processor/exceptions/ShowkaseProcessorException.kt | 8.0 | Near-clean | Code Coverage: Low coverage: showkase-processor/src/main/java/com/airbnb/android/showkase/processor/exceptions/ShowkaseProcessorException.kt |
| showkase-processor/src/main/java/com/airbnb/android/showkase/processor/logging/ShowkaseExceptionLogger.kt | 8.0 | Near-clean | Code Coverage: Low coverage: showkase-processor/src/main/java/com/airbnb/android/showkase/processor/logging/ShowkaseExceptionLogger.kt |
| showkase-processor/src/main/java/com/airbnb/android/showkase/processor/utils/KotlinMetadataUtils.kt | 8.0 | Near-clean | Code Coverage: Low coverage: showkase-processor/src/main/java/com/airbnb/android/showkase/processor/utils/KotlinMetadataUtils.kt |
| showkase-processor/src/main/java/com/airbnb/android/showkase/processor/utils/XProcessingExtensions.kt | 8.0 | Near-clean | Code Coverage: Low coverage: showkase-processor/src/main/java/com/airbnb/android/showkase/processor/utils/XProcessingExtensions.kt |
| showkase-processor/src/main/java/com/airbnb/android/showkase/processor/writer/PaparazziShowkaseScreenshotTestWriter.kt | 8.0 | Near-clean | Code Coverage: Low coverage: showkase-processor/src/main/java/com/airbnb/android/showkase/processor/writer/PaparazziShowkaseScreenshotTestWriter.kt |
| showkase-processor/src/main/java/com/airbnb/android/showkase/processor/writer/ShowkaseBrowserWriter.kt | 8.0 | Near-clean | Code Coverage: Low coverage: showkase-processor/src/main/java/com/airbnb/android/showkase/processor/writer/ShowkaseBrowserWriter.kt |
| showkase-processor/src/main/java/com/airbnb/android/showkase/processor/writer/ShowkaseCodegenMetadataWriter.kt | 8.0 | Near-clean | Code Coverage: Low coverage: showkase-processor/src/main/java/com/airbnb/android/showkase/processor/writer/ShowkaseCodegenMetadataWriter.kt |
| showkase-processor/src/main/java/com/airbnb/android/showkase/processor/writer/ShowkaseExtensionFunctionsWriter.kt | 8.0 | Near-clean | Code Coverage: Low coverage: showkase-processor/src/main/java/com/airbnb/android/showkase/processor/writer/ShowkaseExtensionFunctionsWriter.kt |
| showkase-processor/src/main/java/com/airbnb/android/showkase/processor/writer/ShowkaseScreenshotTestWriter.kt | 8.0 | Near-clean | Code Coverage: Low coverage: showkase-processor/src/main/java/com/airbnb/android/showkase/processor/writer/ShowkaseScreenshotTestWriter.kt |
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 37 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 37 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, 122 of 288 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
- 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 — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — this repository's 15 Maven/Gradle manifest(s) were read and none of the dependency coordinates they declare carries a version resolvable from the manifest itself: every one is inherited from a parent POM, a <dependencyManagement> block, an imported BOM or a Gradle version reference the catalogue does not define. Licences are resolved from the POMs Maven Central publishes, which requires a version to ask about, and grading whichever release happens to be newest today would be a verdict about a dependency graph this repository has not pinned. NOT a finding that this repository's licences are compliant: this dimension asserts nothing about its licensing in either direction.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. All 34 significant source file(s) were last meaningfully changed so long ago that no living knowledge remains — nothing since has been substantial enough to re-establish ownership (a broad, mechanical sweep that touches many files shallowly does not count, and neither does no activity at all). There is no concentration to measure, so the bus factor is not scored. This is not a clean bill: nobody currently holds working knowledge of this code (see D34 Knowledge Freshness). Counted over 33 of the 95 production source files in this repository: 61 are under the ~2,400-byte size floor this dimension measures over, and the remaining 1 have no attributable history left to measure.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated per language (docs/plans/deterministic-engine.md, P5; C# and each NeutralApiArms arm pass): 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. `showkase-processor/src/main/java/com/airbnb/android/showkase/processor/logging/ShowkaseValidator.kt`, `showkase-processor/src/main/java/com/airbnb/android/showkase/processor/models/ShowkaseMetadata.kt`, `showkase-processor/src/main/java/com/airbnb/android/showkase/processor/writer/ShowkaseBrowserPropertyWriter.kt`, `showkase-processor/src/main/java/com/airbnb/android/showkase/processor/writer/ShowkaseCodegenMetadataWriter.kt`, `showkase-processor/src/main/java/com/airbnb/android/showkase/processor/writer/WriterUtils.kt` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- AXB1 Runtime evidence locked — no reproducible boot — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: a native UI project (showkase-screenshot-testing-shot/src/main/AndroidManifest.xml). The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'androidx.room' is imported (showkase-processor/src/main/java/com/airbnb/android/showkase/processor/BaseProcessor.kt:3), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- 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.
- C3 Audit Trail — 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. 'androidx.room' is imported (showkase-processor/src/main/java/com/airbnb/android/showkase/processor/BaseProcessor.kt:3), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C4 Data Retention — 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. 'androidx.room' is imported (showkase-processor/src/main/java/com/airbnb/android/showkase/processor/BaseProcessor.kt:3), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C5 Data-Subject Rights — 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. 'androidx.room' is imported (showkase-processor/src/main/java/com/airbnb/android/showkase/processor/BaseProcessor.kt:3), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Java was found, and this repository's 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, Scala and Rust source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby, Scala or Rust was found, and this repository's 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.
- 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.
- X24 Document value interpolated into markup unescaped — 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, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, 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.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- 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").
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- 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").
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
1 god class(es) detected.
What to do
- Resolve the 1 ClassTooLong finding(s) in God Classes — start with ShowkaseProcessor.kt. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
15 duplicated block group(s) detected. 10.9 % of the production lines (827 of 7,621) are in a reported copy. A further 6 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 1 of the 21 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
What to do
- Resolve the 2 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with ShowkaseMetadata.kt, ShowkaseColorsInAGroupScreen.kt. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (28 lines × 2) finding(s) in Code Duplication — start with Scrollable.kt, BasicChip.kt. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Edited copy of a member (43 corresponding lines) finding(s) in Code Duplication — start with ShowkaseMetadata.kt. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
14 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; 3 module(s) off the main sequence, with abstractness counted on 10 of the 14 (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 3 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (3 warning-level).
D6 · Cohesion (LCOM4)
1 of 10 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with ShowkaseValidator.kt. — One of this dimension's main actionable groups (1 warning-level).
D8 · Code Coverage
Line coverage 1.1% — 18 file(s) below 50%. Measured from the Java/Kotlin suite (repository root, Gradle: the JaCoCo agent on the 3 run(s) test reliability made). Taken over 3 runs of the suite: a line counts as covered only when every run executed it. 1671 line(s) in 18 file(s) were executed in some runs and not in others, so they are not counted.
What to do
- Resolve the 18 Low coverage finding(s) in Code Coverage — start with ScreenshotConfig.kt, ShowkaseComposable.kt, BaseProcessor.kt. — One of this dimension's main actionable groups (18 warning-level).
- Resolve the 18 Tests reach code only in some runs finding(s) in Code Coverage — start with ScreenshotConfig.kt, ShowkaseComposable.kt, BaseProcessor.kt. — One of this dimension's main actionable groups (18 recommendation-level).
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: 357 artifact(s) resolved, 195 of them gradable against Maven Central, and 158 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.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
8 deducted task-comment markers across 7621 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 8 TodoComment finding(s) in Explicit Debt — start with ShowkaseValidator.kt (3), ShowkaseMetadata.kt (2), ShowkaseProcessor.kt. — One of this dimension's main actionable groups (8 warning-level).
D19 · Documentation Quality
2 of 2 documentation facets pass in full. 1 document(s) read across 14 unit(s).
D26 · Project Cohesion
0 of 10 build units (Gradle) flagged as possibly oversized/incoherent.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
17 finding(s): 0 critical, 17 high, 0 medium, 0 low. 17 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `gradlew` (line 74, line 180) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- No action in Static Analysis (SAST) — all 17 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 (17 issue-level, 0 of them charged here).
D34 · Knowledge Freshness
34 of 34 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is showkase-processor/src/main/java/com/airbnb/android/showkase/processor/ShowkaseProcessor.kt. Counted over 34 of the 95 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 31 Orphaned file finding(s) in Knowledge Freshness — start with build.gradle (7), ShowkaseValidator.kt, WriterUtils.kt. — One of this dimension's main actionable groups (31 recommendation-level).
- Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with ShowkaseProcessor.kt, ShowkaseBrowserApp.kt, ShowkaseMetadata.kt. — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 14 platform declaration(s) and 2 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 1 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:6
- `build.gradle` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — build.gradle:94
What to do
- Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
X12 · Unreachable branch
X16 · Unfloored truncation loop
X21 · Side-effecting pattern guard
X27 · Collection changed while being enumerated
X3 · Exception handling
- `catch (e: 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. — showkase-processor/src/main/java/com/airbnb/android/showkase/processor/models/ShowkaseMetadata.kt:500
What to do
- Swallowed exception (caught, then discarded)
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 75.4 | Strong | Solid. |
| Architecture | 97.3 | Exemplary | Solid. |
| Maturity | 48.8 | Weak — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 46.3 | Weak — gated by D8, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 100.0 | Checked 4 of 10 | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
Not evidenced — 5 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: this repository stores data through 'androidx.room' (showkase-processor/src/main/java/com/airbnb/android/showkase/processor/BaseProcessor.kt:3) but declares no persisted model this check reads (Room/JPA/Spring Data/MongoDB @Entity and Realm classes, Exposed and Ktorm table columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations and SQLDelight files). Personal data may be written through raw SQL or a hosted backend, so whether its changes need an audit trail could not be established, and the trail's absence is not scored.
- C4 Data Retention — Not assessed: this repository stores data through 'androidx.room' (showkase-processor/src/main/java/com/airbnb/android/showkase/processor/BaseProcessor.kt:3) but declares no persisted model this check reads (Room/JPA/Spring Data/MongoDB @Entity and Realm classes, Exposed and Ktorm table columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations and SQLDelight files). Personal data may be written through raw SQL or a hosted backend, so whether a retention limit applies here could not be established, and its absence is not scored.
- C5 Data-Subject Rights — Not assessed: this repository stores data through 'androidx.room' (showkase-processor/src/main/java/com/airbnb/android/showkase/processor/BaseProcessor.kt:3) but declares no persisted model this check reads (Room/JPA/Spring Data/MongoDB @Entity and Realm classes, Exposed and Ktorm table columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations and SQLDelight files). Personal data may be written through raw SQL or a hosted backend, so whether data-subject rights apply here could not be established, and their absence is not scored.
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 74 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.
- AX1 Captive dependencies — Not applicable: this repository's Kotlin imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Kotlin code is a Spring, JSR-330 or CDI singleton bean.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — Not assessed: this repository stores data through 'androidx.room' (showkase-processor/src/main/java/com/airbnb/android/showkase/processor/BaseProcessor.kt:3) but declares no persisted model this check reads (Room/JPA/Spring Data/MongoDB @Entity and Realm classes, Exposed and Ktorm table columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations and SQLDelight files). Personal data may be written through raw SQL or a hosted backend, so the absence of a personal-data field here is not evidence that none is stored, and encryption at rest is not scored over a subject that could not be established.
- 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.
- D10 Test Quality — ~3942 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.
- D14 License Compliance — JVM licences not graded — no declared coordinate carries a version the manifest itself resolves
- D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
- 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.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 2 candidate(s) found and not reported.
- D22 Internal API Consistency — API consistency is measured on C#, TypeScript, Go 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 .kt, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — symbol resolution incomplete — navigability not assessed
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet).
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 5 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.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet).
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (17 value object(s))
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P2 Observability — This repository's JVM source (10 module(s), 79 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage data present for 19 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — 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.
- X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no C# was loaded; this repository's Kotlin was read, and no request in it can be cancelled by a caller (Ktor, OkHttp's newCall or a URL stream, from a suspend function) — a Kotlin request outside a suspend function has no caller's cancellation to honour
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not 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
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 17 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 54 finding(s)
- Low coverage: showkase-annotation/src/main/java/com/airbnb/android/showkase/annotation/ScreenshotConfig.kt showkase-annotation/src/main/java/com/airbnb/android/showkase/annotation/ScreenshotConfig.kt:1
- Low coverage: showkase-annotation/src/main/java/com/airbnb/android/showkase/annotation/ShowkaseComposable.kt showkase-annotation/src/main/java/com/airbnb/android/showkase/annotation/ShowkaseComposable.kt:1
- Low coverage: showkase-processor/src/main/java/com/airbnb/android/showkase/processor/BaseProcessor.kt showkase-processor/src/main/java/com/airbnb/android/showkase/processor/BaseProcessor.kt:1
- Low coverage: showkase-processor/src/main/java/com/airbnb/android/showkase/processor/ShowkaseProcessor.kt showkase-processor/src/main/java/com/airbnb/android/showkase/processor/ShowkaseProcessor.kt:1
- Low coverage: showkase-processor/src/main/java/com/airbnb/android/showkase/processor/Timer.kt showkase-processor/src/main/java/com/airbnb/android/showkase/processor/Timer.kt:1
- Low coverage: showkase-processor/src/main/java/com/airbnb/android/showkase/processor/exceptions/ShowkaseProcessorException.kt showkase-processor/src/main/java/com/airbnb/android/showkase/processor/exceptions/ShowkaseProcessorException.kt:1
- Low coverage: showkase-processor/src/main/java/com/airbnb/android/showkase/processor/logging/ShowkaseExceptionLogger.kt showkase-processor/src/main/java/com/airbnb/android/showkase/processor/logging/ShowkaseExceptionLogger.kt:1
- Low coverage: showkase-processor/src/main/java/com/airbnb/android/showkase/processor/logging/ShowkaseValidator.kt showkase-processor/src/main/java/com/airbnb/android/showkase/processor/logging/ShowkaseValidator.kt:1
- Low coverage: showkase-processor/src/main/java/com/airbnb/android/showkase/processor/models/ShowkaseMetadata.kt showkase-processor/src/main/java/com/airbnb/android/showkase/processor/models/ShowkaseMetadata.kt:1
- Low coverage: showkase-processor/src/main/java/com/airbnb/android/showkase/processor/utils/KotlinMetadataUtils.kt showkase-processor/src/main/java/com/airbnb/android/showkase/processor/utils/KotlinMetadataUtils.kt:1
- Low coverage: showkase-processor/src/main/java/com/airbnb/android/showkase/processor/utils/XProcessingExtensions.kt showkase-processor/src/main/java/com/airbnb/android/showkase/processor/utils/XProcessingExtensions.kt:1
- Low coverage: showkase-processor/src/main/java/com/airbnb/android/showkase/processor/writer/PaparazziShowkaseScreenshotTestWriter.kt showkase-processor/src/main/java/com/airbnb/android/showkase/processor/writer/PaparazziShowkaseScreenshotTestWriter.kt:1
- Low coverage: showkase-processor/src/main/java/com/airbnb/android/showkase/processor/writer/ShowkaseBrowserPropertyWriter.kt showkase-processor/src/main/java/com/airbnb/android/showkase/processor/writer/ShowkaseBrowserPropertyWriter.kt:1
- Low coverage: showkase-processor/src/main/java/com/airbnb/android/showkase/processor/writer/ShowkaseBrowserWriter.kt showkase-processor/src/main/java/com/airbnb/android/showkase/processor/writer/ShowkaseBrowserWriter.kt:1
- Low coverage: showkase-processor/src/main/java/com/airbnb/android/showkase/processor/writer/ShowkaseCodegenMetadataWriter.kt showkase-processor/src/main/java/com/airbnb/android/showkase/processor/writer/ShowkaseCodegenMetadataWriter.kt:1
- Low coverage: showkase-processor/src/main/java/com/airbnb/android/showkase/processor/writer/ShowkaseExtensionFunctionsWriter.kt showkase-processor/src/main/java/com/airbnb/android/showkase/processor/writer/ShowkaseExtensionFunctionsWriter.kt:1
- Low coverage: showkase-processor/src/main/java/com/airbnb/android/showkase/processor/writer/ShowkaseScreenshotTestWriter.kt showkase-processor/src/main/java/com/airbnb/android/showkase/processor/writer/ShowkaseScreenshotTestWriter.kt:1
- Low coverage: showkase-processor/src/main/java/com/airbnb/android/showkase/processor/writer/WriterUtils.kt showkase-processor/src/main/java/com/airbnb/android/showkase/processor/writer/WriterUtils.kt:1
- TodoComment showkase-processor/src/main/java/com/airbnb/android/showkase/processor/ShowkaseProcessor.kt:617
- TodoComment showkase-processor/src/main/java/com/airbnb/android/showkase/processor/models/ShowkaseMetadata.kt:405
- TodoComment showkase-processor/src/main/java/com/airbnb/android/showkase/processor/models/ShowkaseMetadata.kt:433
- TodoComment showkase-processor/src/main/java/com/airbnb/android/showkase/processor/logging/ShowkaseValidator.kt:216
- TodoComment showkase-processor/src/main/java/com/airbnb/android/showkase/processor/logging/ShowkaseValidator.kt:243
- TodoComment showkase-processor/src/main/java/com/airbnb/android/showkase/processor/logging/ShowkaseValidator.kt:384
- TodoComment showkase/src/main/java/com/airbnb/android/showkase/ui/BackButtonHandler.kt:48
- TodoComment showkase/src/main/java/com/airbnb/android/showkase/models/ShowkaseBrowserComponent.kt:6
- Off the main sequence: :showkase
- Off the main sequence: :showkase-screenshot-testing
- Off the main sequence: :showkase-processor
- Duplicated block (12 lines × 2) showkase-processor/src/main/java/com/airbnb/android/showkase/processor/models/ShowkaseMetadata.kt:413
- Duplicated block (12 lines × 2) showkase/src/main/java/com/airbnb/android/showkase/ui/ShowkaseColorsInAGroupScreen.kt:126
- Duplicated block (28 lines × 2) sample/src/main/java/com/airbnb/android/showkasesample/Scrollable.kt:18
- Duplicated block (28 lines × 2) sample/src/main/java/com/airbnb/android/showkasesample/BasicChip.kt:22
- ClassTooLong: ShowkaseProcessor showkase-processor/src/main/java/com/airbnb/android/showkase/processor/ShowkaseProcessor.kt:49
- REDACTED
- Edited copy of a member (43 corresponding lines) showkase-processor/src/main/java/com/airbnb/android/showkase/processor/models/ShowkaseMetadata.kt:240
- Edited copy of a member (22 corresponding lines) showkase-processor/src/main/java/com/airbnb/android/showkase/processor/models/ShowkaseMetadata.kt:403
- Edited copy of a member (19 corresponding lines) showkase/src/main/java/com/airbnb/android/showkase/ui/ShowkaseBrowserApp.kt:586
- Edited copies of one member (4 members, 16+ corresponding lines) sample/src/main/java/com/airbnb/android/showkasesample/Text.kt:36
- Edited copy of a member (14 corresponding lines) sample/src/main/java/com/airbnb/android/showkasesample/Text.kt:101
- Edited copies of one member (3 members, 9+ corresponding lines) showkase/src/main/java/com/airbnb/android/showkase/ui/ShowkaseCategoriesScreen.kt:64
- Duplicated block (43–44 lines × 2) sample/src/main/java/com/airbnb/android/showkasesample/Rows.kt:118
- Duplicated block (38–40 lines × 2) sample/src/main/java/com/airbnb/android/showkasesample/Rows.kt:75
- Duplicated block (32–34 lines × 2) sample/src/main/java/com/airbnb/android/showkasesample/Rows.kt:38
- Duplicated block (29 lines × 2) showkase-processor/src/main/java/com/airbnb/android/showkase/processor/models/ShowkaseMetadata.kt:254
- Duplicated block (19 lines × 2) sample/src/main/java/com/airbnb/android/showkasesample/Navigation.kt:24
- Duplicated block (17 lines × 3) sample/src/main/java/com/airbnb/android/showkasesample/Rows.kt:128
- Duplicated block (12–13 lines × 2) showkase-processor/src/main/java/com/airbnb/android/showkase/processor/writer/ShowkaseBrowserPropertyWriter.kt:44
- Duplicated block (50 lines × 2) sample/src/main/java/com/airbnb/android/showkasesample/CustomButton.kt:21
- Duplicated block (8 lines × 2) sample/src/main/java/com/airbnb/android/showkasesample/ShowkaseTheme.kt:10
- Duplicated block (11 lines × 2) sample/src/main/java/com/airbnb/android/showkasesample/Text.kt:135
- Duplicated block (11 lines × 3) sample/src/main/java/com/airbnb/android/showkasesample/Text.kt:37
- Low cohesion: ShowkaseValidator (LCOM4 8) showkase-processor/src/main/java/com/airbnb/android/showkase/processor/logging/ShowkaseValidator.kt:32
- Swallowed exception (caught, then discarded) showkase-processor/src/main/java/com/airbnb/android/showkase/processor/models/ShowkaseMetadata.kt:500
Minor — 59 finding(s)
- Orphaned file showkase-processor/src/main/java/com/airbnb/android/showkase/processor/logging/ShowkaseValidator.kt:1
- Orphaned file showkase-processor/src/main/java/com/airbnb/android/showkase/processor/writer/WriterUtils.kt:1
- Orphaned file showkase-processor/src/main/java/com/airbnb/android/showkase/processor/writer/PaparazziShowkaseScreenshotTestWriter.kt:1
- Orphaned file showkase-processor/src/main/java/com/airbnb/android/showkase/processor/writer/ShowkaseBrowserPropertyWriter.kt:1
- Orphaned file showkase-processor/src/main/java/com/airbnb/android/showkase/processor/writer/ShowkaseBrowserWriter.kt:1
- Orphaned file showkase/src/main/java/com/airbnb/android/showkase/ui/ShowkaseComponentDetailScreen.kt:1
- Orphaned file build.gradle:1
- Orphaned file showkase-annotation/src/main/java/com/airbnb/android/showkase/annotation/ShowkaseComposable.kt:1
- Orphaned file showkase/src/main/java/com/airbnb/android/showkase/ui/ShowkaseGroupsScreen.kt:1
- Orphaned file showkase-screenshot-testing-paparazzi-sample/src/main/java/com/airbnb/android/showkase/screenshot/testing/paparazzi/sample/Rows.kt:1
- Orphaned file showkase-processor/src/main/java/com/airbnb/android/showkase/processor/writer/ShowkaseCodegenMetadataWriter.kt:1
- Orphaned file showkase-screenshot-testing-paparazzi-sample/build.gradle:1
- Orphaned file showkase-processor/src/main/java/com/airbnb/android/showkase/processor/writer/ShowkaseExtensionFunctionsWriter.kt:1
- Orphaned file sample-submodule/src/main/java/com/airbnb/android/submodule/showkasesample/payments/Payments.kt:1
- Orphaned file showkase-processor/src/main/java/com/airbnb/android/showkase/processor/writer/ShowkaseScreenshotTestWriter.kt:1
- Orphaned file showkase/src/main/java/com/airbnb/android/showkase/ui/ShowkaseColorsInAGroupScreen.kt:1
- Orphaned file showkase/src/main/java/com/airbnb/android/showkase/ui/ShowkaseTypographyInAGroupScreen.kt:1
- Orphaned file showkase/src/main/java/com/airbnb/android/showkase/ui/ShowkaseComponentStylesScreen.kt:1
- Orphaned file showkase/src/main/java/com/airbnb/android/showkase/ui/ShowkaseBrowserActivity.kt:1
- Orphaned file showkase-processor-testing/build.gradle:1
- Orphaned file showkase-screenshot-testing-paparazzi-sample/src/main/java/com/airbnb/android/showkase/screenshot/testing/paparazzi/sample/Text.kt:1
- Orphaned file showkase/src/main/java/com/airbnb/android/showkase/ui/ShowkaseComponentsInAGroupScreen.kt:1
- Orphaned file showkase/src/main/java/com/airbnb/android/showkase/ui/CommonComponents.kt:1
- Orphaned file showkase-processor/src/main/java/com/airbnb/android/showkase/processor/BaseProcessor.kt:1
- Orphaned file showkase-browser-testing/build.gradle:1
- Tests reach code only in some runs: showkase-annotation/src/main/java/com/airbnb/android/showkase/annotation/ScreenshotConfig.kt showkase-annotation/src/main/java/com/airbnb/android/showkase/annotation/ScreenshotConfig.kt:16
- Tests reach code only in some runs: showkase-annotation/src/main/java/com/airbnb/android/showkase/annotation/ShowkaseComposable.kt showkase-annotation/src/main/java/com/airbnb/android/showkase/annotation/ShowkaseComposable.kt:127
- Tests reach code only in some runs: showkase-processor/src/main/java/com/airbnb/android/showkase/processor/BaseProcessor.kt showkase-processor/src/main/java/com/airbnb/android/showkase/processor/BaseProcessor.kt:22
- Tests reach code only in some runs: showkase-processor/src/main/java/com/airbnb/android/showkase/processor/ShowkaseProcessor.kt showkase-processor/src/main/java/com/airbnb/android/showkase/processor/ShowkaseProcessor.kt:42
- Tests reach code only in some runs: showkase-processor/src/main/java/com/airbnb/android/showkase/processor/Timer.kt showkase-processor/src/main/java/com/airbnb/android/showkase/processor/Timer.kt:8
- Tests reach code only in some runs: showkase-processor/src/main/java/com/airbnb/android/showkase/processor/exceptions/ShowkaseProcessorException.kt showkase-processor/src/main/java/com/airbnb/android/showkase/processor/exceptions/ShowkaseProcessorException.kt:5
- Tests reach code only in some runs: showkase-processor/src/main/java/com/airbnb/android/showkase/processor/logging/ShowkaseExceptionLogger.kt showkase-processor/src/main/java/com/airbnb/android/showkase/processor/logging/ShowkaseExceptionLogger.kt:7
- Tests reach code only in some runs: showkase-processor/src/main/java/com/airbnb/android/showkase/processor/logging/ShowkaseValidator.kt showkase-processor/src/main/java/com/airbnb/android/showkase/processor/logging/ShowkaseValidator.kt:32
- Tests reach code only in some runs: showkase-processor/src/main/java/com/airbnb/android/showkase/processor/models/ShowkaseMetadata.kt showkase-processor/src/main/java/com/airbnb/android/showkase/processor/models/ShowkaseMetadata.kt:46
- Tests reach code only in some runs: showkase-processor/src/main/java/com/airbnb/android/showkase/processor/utils/KotlinMetadataUtils.kt showkase-processor/src/main/java/com/airbnb/android/showkase/processor/utils/KotlinMetadataUtils.kt:8
- Tests reach code only in some runs: showkase-processor/src/main/java/com/airbnb/android/showkase/processor/utils/XProcessingExtensions.kt showkase-processor/src/main/java/com/airbnb/android/showkase/processor/utils/XProcessingExtensions.kt:10
- Tests reach code only in some runs: showkase-processor/src/main/java/com/airbnb/android/showkase/processor/writer/PaparazziShowkaseScreenshotTestWriter.kt showkase-processor/src/main/java/com/airbnb/android/showkase/processor/writer/PaparazziShowkaseScreenshotTestWriter.kt:18
- Tests reach code only in some runs: showkase-processor/src/main/java/com/airbnb/android/showkase/processor/writer/ShowkaseBrowserPropertyWriter.kt showkase-processor/src/main/java/com/airbnb/android/showkase/processor/writer/ShowkaseBrowserPropertyWriter.kt:17
- Tests reach code only in some runs: showkase-processor/src/main/java/com/airbnb/android/showkase/processor/writer/ShowkaseBrowserWriter.kt showkase-processor/src/main/java/com/airbnb/android/showkase/processor/writer/ShowkaseBrowserWriter.kt:24
- Tests reach code only in some runs: showkase-processor/src/main/java/com/airbnb/android/showkase/processor/writer/ShowkaseCodegenMetadataWriter.kt showkase-processor/src/main/java/com/airbnb/android/showkase/processor/writer/ShowkaseCodegenMetadataWriter.kt:17
- Tests reach code only in some runs: showkase-processor/src/main/java/com/airbnb/android/showkase/processor/writer/ShowkaseExtensionFunctionsWriter.kt showkase-processor/src/main/java/com/airbnb/android/showkase/processor/writer/ShowkaseExtensionFunctionsWriter.kt:14
- Tests reach code only in some runs: showkase-processor/src/main/java/com/airbnb/android/showkase/processor/writer/ShowkaseScreenshotTestWriter.kt showkase-processor/src/main/java/com/airbnb/android/showkase/processor/writer/ShowkaseScreenshotTestWriter.kt:17
- Tests reach code only in some runs: showkase-processor/src/main/java/com/airbnb/android/showkase/processor/writer/WriterUtils.kt showkase-processor/src/main/java/com/airbnb/android/showkase/processor/writer/WriterUtils.kt:23
- Most significant orphaned file showkase-processor/src/main/java/com/airbnb/android/showkase/processor/ShowkaseProcessor.kt:1
- Most significant orphaned file showkase/src/main/java/com/airbnb/android/showkase/ui/ShowkaseBrowserApp.kt:1
- Most significant orphaned file showkase-processor/src/main/java/com/airbnb/android/showkase/processor/models/ShowkaseMetadata.kt:1
- Dormant codebase
- REDACTED
- No ADRs
- No architecture diagram/doc
- No SAST REDACTED:6
- No dependency-update automation build.gradle:94
- No changelog
Minor — 158 finding(s)
- Outdated (compile): org.jetbrains.kotlin:kotlin-stdlib
- Outdated (compile): org.jetbrains:annotations
- Outdated (compile): org.jetbrains.kotlin:kotlin-stdlib-jdk8
- Outdated (compile): org.jetbrains.kotlin:kotlin-stdlib-jdk7
- Outdated (compile): com.squareup:kotlinpoet
- Outdated (compile): com.squareup:kotlinpoet-jvm
- Outdated (compile): org.jetbrains.kotlin:kotlin-reflect
- Outdated (compile): com.squareup:kotlinpoet-javapoet
- Outdated (compile): org.jetbrains.kotlin:kotlin-metadata-jvm
- Outdated (compile): com.google.devtools.ksp:symbol-processing-api
- Outdated (compile): com.google.auto:auto-common
- 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.auto.value:auto-value-annotations
- Outdated (compile): org.jspecify:jspecify
- 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-common
- Outdated (compile): com.google.protobuf:protobuf-java
- Outdated (compile): org.jetbrains.kotlinx:kotlinx-coroutines-core
- Outdated (compile): org.jetbrains.kotlinx:kotlinx-coroutines-core-jvm
- Outdated (compile): org.jetbrains.kotlinx:kotlinx-coroutines-bom
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 --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-998bfa3069974bf99da46a0f6a00946a/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=143" --report-format json --report-path /tmp/watchdog-gitleaks-998bfa3069974bf99da46a0f6a00946a/history-1.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-1.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-998bfa3069974bf99da46a0f6a00946a/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 --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/class_with_@ScreenshotTest_generates_paparazzi_screenshot_test_for_all_UI_elements/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/class_with_@ScreenshotTest_generates_screenshot_test_for_all_UI_elements/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/class_with_@ScreenshotTest_only_generates_screenshot_test_for_only_non_preview_parameter_composable/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/color_property_inside_class_with_showkasecolor_annotation_and_showkaseroot_generates_1_file/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/color_property_inside_class_with_showkasecolor_annotation_and_showkaseroot_with_no_group/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/color_property_inside_object_with_ShowkaseColor_annotation_compiles_ok/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/color_property_inside_object_with_showkasecolor_annotation_and_showkaseroot_generates_1_file/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/color_with_showkase_color_annotation_inside_class_compiles_ok/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/composable_function_inside_class_with_showkase_annotation_and_showkaseroot_generates_1_file/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/composable_function_inside_companion_object_with_preview_annotation_compiles_ok/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/composable_function_inside_companion_object_with_preview_annotation_generates_only_metadata_file/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/composable_function_inside_companion_object_with_showkase_annotation_and_showkaseroot_generates_1_file/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/composable_function_inside_companion_object_with_showkase_annotation_compiles_ok/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/composable_function_inside_companion_object_with_showkase_annotation_generates_only_metadata_file/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/composable_function_inside_object_with_preview_annotation_compiles_ok/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/composable_function_inside_object_with_preview_annotation_generates_only_metadata_file/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/composable_function_inside_object_with_showkase_annotation_and_showkaseroot_generates_1_file/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/composable_function_inside_object_with_showkase_annotation_compiles_ok/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/composable_function_inside_object_with_showkase_annotation_generates_only_metadata_file/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/composable_function_that_has_default_parameters_compiles_ok/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/composable_function_with_both_annotations_gives_priority_to_showkase_annotation/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/composable_function_with_custom_preview_annotation_generates_output/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/composable_function_with_custom_preview_annotation_with_preview_param_generates_output/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/composable_function_with_kdoc_inside_object_with_showkase_annotation_and_showkaseroot_generates_2_files/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/composable_function_with_multiple_preview_annotations_stacked_generates_output/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/composable_function_with_multiple_preview_functions_compiles/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/composable_function_with_multiple_preview_functions_compiles_ksp/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/composable_function_with_multiple_repeatable_custom_preview_annotation_generates_output/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/composable_function_with_multiple_showkasecomposable_annotations_stacked_generates_output/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/composable_function_with_private_custom_preview_annotation_compiles_with_flag/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/composable_function_with_repeatable_custom_preview_annotation_generates_output/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/composable_function_with_showkase_annotation_with_capturetype_compiles_ok/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/composable_functions_with_preview_annotation_are_skipped/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/composable_previews_with_multiple_parameter_providers_should_indent_properly/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/composable_with_preview_annotation_inside_class_compiles_ok/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/composable_with_showkase_annotation_inside_class_compiles_ok/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/function_inside_class_with_preview_annotation_and_no_name_or_group/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/function_inside_class_with_showkase_annotation_and_no_name_or_group/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/function_inside_companion_object_with_preview_annotation_and_no_name_or_group/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/function_inside_companion_object_with_showkase_annotation_and_no_name_or_group/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/function_inside_object_with_preview_annotation_and_no_name_or_group/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/function_inside_object_with_showkase_annotation_and_no_name_or_group/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/multiple_composable_functions_with_preview_and_showkase_annotations_generates_only_metadata_file/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/multiple_composable_functions_with_preview_annotations_generates_only_metadata_file/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/multiple_composable_functions_with_showkase_annotations_generates_only_metadata_file/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/object_function_with_preview_annotation_and_preview_parameter_and_showkaseroot/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/object_function_with_preview_annotation_and_preview_parameter_and_showkaseroot_and_long_parameter_provider_name/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/private_composable_with_preview_annotation_and_skipPrivate_option_compiles_ok/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/private_composable_with_showkase_annotation_and_skipPrivate_option_compiles_ok/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/property_inside_class_with_showkase_color_annotation_and_no_name_or_group/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/property_inside_class_with_showkase_typography_annotation_and_no_name_or_group/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/property_inside_object_with_showkase_color_annotation_and_no_name_or_group/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/property_inside_object_with_showkase_typography_annotation_and_no_name_or_group/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/textstyle_property_inside_class_with_showkasetypography_annotation_and_showkaseroot_generates_1_file/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/textstyle_property_inside_object_with_ShowkaseTypography_annotation_compiles_ok/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/textstyle_property_inside_object_with_showkasetypography_annotation_and_showkaseroot_generates_1_file/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/textstyle_with_ShowkaseTypography_annotation_inside_class_compiles_ok/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/top_level_color_and_class_with_@ScreenshotTest_generates_paparazzi_screenshot_test_for_composable/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/top_level_color_and_class_with_@ScreenshotTest_generates_screenshot_test_for_composable/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/top_level_color_property_and_composable_function_generates_1_file/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/top_level_color_property_with_ShowkaseColor_annotation_compiles_ok/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/top_level_color_property_with_ShowkaseColor_annotation_generates_only_metadata_file/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/top_level_color_property_with_showkasecolor_and_showkaseroot_generates_1_file/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/top_level_composable_and_class_with_@ScreenshotTest_generates_Paparazzi_screenshot_test_for_composable/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/top_level_composable_and_class_with_@ScreenshotTest_generates_screenshot_test_for_composable/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/top_level_composable_function_with_preview_and_showkaseroot_generates_1_file/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/top_level_composable_function_with_preview_and_showkaseroot_with_width_and_height/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/top_level_composable_function_with_preview_annotation_compiles_ok/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/top_level_composable_function_with_preview_annotation_generates_only_metadata_file/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/top_level_composable_function_with_preview_parameter_and_preview_annotation_generates_only_metadata_file/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/top_level_composable_function_with_preview_parameter_and_showkase_composable_annotation_generates_only_metadata_file/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/top_level_composable_function_with_showkase_and_showkaseroot_generates_1_file/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/top_level_composable_function_with_showkase_and_showkaseroot_with_tags_and_metadata/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/top_level_composable_function_with_showkase_and_showkaseroot_with_width_and_height/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/top_level_composable_function_with_showkase_annotation_compiles_ok/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/top_level_composable_function_with_showkase_annotation_generates_only_metadata_file/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/top_level_composable_with_wrapped_color_property_with_ShowkaseColor_annotation_generates_only_metadata_file/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/top_level_composable_with_wrapped_textstyle_property_with_ShowkaseColor_annotation_generates_only_metadata_file/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/top_level_function_with_preview_and_preview_parameter_and_showkaseroot_and_no_name_or_group/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/top_level_function_with_preview_and_showkaseroot_and_no_name_or_group/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/top_level_function_with_preview_annotation_and_no_name_or_group/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/top_level_function_with_showkase_and_showkaseroot_and_no_name/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/top_level_function_with_showkase_and_showkaseroot_and_no_name_or_group/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/top_level_function_with_showkase_annotation_and_no_name_or_group/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/top_level_function_with_showkase_composable_and_preview_parameter_and_showkaseroot_and_no_name_or_group/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/top_level_property_with_showkase_color_annotation_and_no_name_or_group/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/top_level_property_with_showkase_typography_annotation_and_no_name_or_group/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/top_level_textstyle_and_class_with_@ScreenshotTest_generates_screenshot_test_for_composable/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/top_level_textstyle_property_and_composable_function_generates_1_file/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/top_level_textstyle_property_with_ShowkaseTypography_annotation_generates_only_metadata_file/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/top_level_textstyle_property_with_showkasetypography_and_showkaseroot_generates_1_file/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/top_level_textstyle_property_with_showkasetypography_and_showkaseroot_with_no_name/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/wrapped_composable_function_with_preview_annotation_generates_only_metadata_file/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/wrapped_composable_function_with_showkase_annotation_generates_only_metadata_file/output --exclude showkase-processor-testing/src/test/resources/ShowkaseProcessorTest/wrapped_function_with_showkase_composable_and_preview_parameter_and_showkaseroot_/output . | 17 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet). | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 5 file(s) — `showkase-processor/src/main/java/com/airbnb/android/showkase/processor/logging/ShowkaseValidator.kt`, `showkase-processor/src/main/java/com/airbnb/android/showkase/processor/models/ShowkaseMetadata.kt`, `showkase-processor/src/main/java/com/airbnb/android/showkase/processor/writer/ShowkaseBrowserPropertyWriter.kt`, `showkase-processor/src/main/java/com/airbnb/android/showkase/processor/writer/ShowkaseCodegenMetadataWriter.kt`, `showkase-processor/src/main/java/com/airbnb/android/showkase/processor/writer/WriterUtils.kt` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet). | 0 | — |