Executive summary
skydoves/Balloon falls short of our standard for production, in part because we found no logging, tracing or health checks in the code. It scores 56 out of 100 and is rated Adequate, and all 19 of its critical findings are security problems.
Production Readiness, at 41, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 7 points. Adding a diagnostic log would lift Production Readiness itself, also worth about 7. Raising Production Readiness to 70 would lift the score to about 67.
Seventeen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One password or key is open to anyone who can read the repository, and one pipeline step installs packages that can change without warning. Pinning each tool to an exact version, replacing the exposed password or key and pinning what the pipeline installs would close these risks.
The product code is 8,901 lines, about €14,000 to rebuild.
If Production Readiness rose from 41 to 70, the lowest score rated Strong, the score would rise from 56 to about 67.
New since the last survey: 9 findings
- Code Duplication · Edited copy of a member (31 corresponding lines) samples-shared/src/commonMain/kotlin/com/skydoves/balloon/sample/BalloonDemoScreen.kt
- Code Duplication · Edited copy of a member (34 corresponding lines) samples-shared/src/commonMain/kotlin/com/skydoves/balloon/sample/BalloonDemoScreen.kt
- Code Duplication · Edited copy of a member (15 corresponding lines) samples-shared/src/commonMain/kotlin/com/skydoves/balloon/sample/labs/LabsControls.kt
- Code Duplication · Duplicated block (13 lines × 2) samples-shared/src/commonMain/kotlin/com/skydoves/balloon/sample/BalloonDemoScreen.kt
- Code Duplication · Duplicated block (13 lines × 2) samples-shared/src/commonMain/kotlin/com/skydoves/balloon/sample/BalloonDemoScreen.kt
- Code Duplication · Duplicated block (6 lines × 4) balloon/src/commonMain/kotlin/com/skydoves/balloon/BalloonShapeBuilder.kt
- Code Duplication · Duplicated block (5 lines × 3) balloon/src/commonMain/kotlin/com/skydoves/balloon/BalloonShapeBuilder.kt
- Code Duplication · Duplicated block (5 lines × 2) balloon/src/commonMain/kotlin/com/skydoves/balloon/BalloonShapeBuilder.kt
- Code Duplication · Duplicated block (12 lines × 2) samples-shared/src/commonMain/kotlin/com/skydoves/balloon/sample/BalloonDemoScreen.kt
Fixed since the last survey: 2 findings
- Code Duplication · Duplicated block (13 lines × 2) samples-shared/src/commonMain/kotlin/com/skydoves/balloon/sample/BalloonDemoScreen.kt
- Code Duplication · Duplicated block (5 lines × 3) balloon/src/commonMain/kotlin/com/skydoves/balloon/BalloonShapeBuilder.kt
Rebuild cost: about €14,000 · Estimate
| Cost to rebuild | €4,500 to €23,000, for 76 to 241 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 56. 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: 8,901 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 (global) | 2 com.skydoves.balloon.BalloonPopupProperties | 3 com.skydoves.balloon.BalloonRotateAnimation | 4 com.skydoves.balloon.kmpdemo | 5 repository | 6 com.skydoves.balloon.Balloon | 7 com.skydoves.balloon | 8 com.skydoves.balloon.AbsoluteBalloonAlign | 9 com.skydoves.balloon.ArrowOrientation | 10 com.skydoves.balloon.ArrowOrientationRules | 11 com.skydoves.balloon.ArrowPositionRules | 12 com.skydoves.balloon.BalloonAlign | 13 com.skydoves.balloon.BalloonAnimation | 14 com.skydoves.balloon.BalloonCenterAlign | 15 com.skydoves.balloon.BalloonHighlightAnimation | 16 com.skydoves.balloon.BalloonOverlayAnimation | 17 com.skydoves.balloon.BalloonOverlayShape | 18 com.skydoves.balloon.BalloonRotateDirection | 19 com.skydoves.balloon.ResolvedArrowSide | 20 com.skydoves.balloon.kmpdemo.parity |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 (global) | ||||||||||||||||||||
| 2 com.skydoves.balloon.BalloonPopupProperties | ||||||||||||||||||||
| 3 com.skydoves.balloon.BalloonRotateAnimation | ||||||||||||||||||||
| 4 com.skydoves.balloon.kmpdemo | ||||||||||||||||||||
| 5 repository | ||||||||||||||||||||
| 6 com.skydoves.balloon.Balloon | 9 | |||||||||||||||||||
| 7 com.skydoves.balloon | 2 | |||||||||||||||||||
| 8 com.skydoves.balloon.AbsoluteBalloonAlign | 6 | |||||||||||||||||||
| 9 com.skydoves.balloon.ArrowOrientation | 4 | |||||||||||||||||||
| 10 com.skydoves.balloon.ArrowOrientationRules | 2 | |||||||||||||||||||
| 11 com.skydoves.balloon.ArrowPositionRules | 2 | |||||||||||||||||||
| 12 com.skydoves.balloon.BalloonAlign | 6 | |||||||||||||||||||
| 13 com.skydoves.balloon.BalloonAnimation | 5 | |||||||||||||||||||
| 14 com.skydoves.balloon.BalloonCenterAlign | 4 | |||||||||||||||||||
| 15 com.skydoves.balloon.BalloonHighlightAnimation | 5 | |||||||||||||||||||
| 16 com.skydoves.balloon.BalloonOverlayAnimation | 2 | |||||||||||||||||||
| 17 com.skydoves.balloon.BalloonOverlayShape | 6 | |||||||||||||||||||
| 18 com.skydoves.balloon.BalloonRotateDirection | 2 | |||||||||||||||||||
| 19 com.skydoves.balloon.ResolvedArrowSide | 4 | |||||||||||||||||||
| 20 com.skydoves.balloon.kmpdemo.parity | 1 |
6→7 com.skydoves.balloon.Balloon uses com.skydoves.balloon part of a loop✕
- Connections
- 9 pairs of types, where a type in com.skydoves.balloon.Balloon uses a type in com.skydoves.balloon.
- The types involved
com.skydoves.balloon.Balloon.Builder→com.skydoves.balloon.ArrowOrientationcom.skydoves.balloon.Balloon.Builder→com.skydoves.balloon.ArrowOrientationRulescom.skydoves.balloon.Balloon.Builder→com.skydoves.balloon.ArrowPositionRulescom.skydoves.balloon.Balloon.Builder→com.skydoves.balloon.BalloonAnimationcom.skydoves.balloon.Balloon.Builder→com.skydoves.balloon.BalloonHighlightAnimationcom.skydoves.balloon.Balloon.Builder→com.skydoves.balloon.BalloonOverlayAnimationcom.skydoves.balloon.Balloon.Builder→com.skydoves.balloon.BalloonOverlayShapecom.skydoves.balloon.Balloon.Builder→com.skydoves.balloon.BalloonRotateAnimationcom.skydoves.balloon.Balloon.Builder→com.skydoves.balloon.BalloonStyle
- Direction
- com.skydoves.balloon.Balloon uses com.skydoves.balloon, so a change to com.skydoves.balloon can break com.skydoves.balloon.Balloon, while a change to com.skydoves.balloon.Balloon can't break com.skydoves.balloon.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→6 com.skydoves.balloon uses com.skydoves.balloon.Balloon✕
- Connections
- 2 pairs of types, where a type in com.skydoves.balloon uses a type in com.skydoves.balloon.Balloon.
- The types involved
com.skydoves.balloon.BalloonKt→com.skydoves.balloon.Balloon.Buildercom.skydoves.balloon.BalloonStyleKt→com.skydoves.balloon.Balloon.Builder
- Direction
- com.skydoves.balloon uses com.skydoves.balloon.Balloon, so a change to com.skydoves.balloon.Balloon can break com.skydoves.balloon, while a change to com.skydoves.balloon can't break com.skydoves.balloon.Balloon.
- Position
- Below the diagonal: com.skydoves.balloon uses a module listed above it, which is the healthy direction.
8→7 com.skydoves.balloon.AbsoluteBalloonAlign uses com.skydoves.balloon✕
- Connections
- 6 pairs of types, where a type in com.skydoves.balloon.AbsoluteBalloonAlign uses a type in com.skydoves.balloon.
- The types involved
com.skydoves.balloon.AbsoluteBalloonAlign.BOTTOM→com.skydoves.balloon.AbsoluteBalloonAligncom.skydoves.balloon.AbsoluteBalloonAlign.CENTER→com.skydoves.balloon.AbsoluteBalloonAligncom.skydoves.balloon.AbsoluteBalloonAlign.DROP_DOWN→com.skydoves.balloon.AbsoluteBalloonAligncom.skydoves.balloon.AbsoluteBalloonAlign.LEFT→com.skydoves.balloon.AbsoluteBalloonAligncom.skydoves.balloon.AbsoluteBalloonAlign.RIGHT→com.skydoves.balloon.AbsoluteBalloonAligncom.skydoves.balloon.AbsoluteBalloonAlign.TOP→com.skydoves.balloon.AbsoluteBalloonAlign
- Direction
- com.skydoves.balloon.AbsoluteBalloonAlign uses com.skydoves.balloon, so a change to com.skydoves.balloon can break com.skydoves.balloon.AbsoluteBalloonAlign, while a change to com.skydoves.balloon.AbsoluteBalloonAlign can't break com.skydoves.balloon.
- Position
- Below the diagonal: com.skydoves.balloon.AbsoluteBalloonAlign uses a module listed above it, which is the healthy direction.
9→7 com.skydoves.balloon.ArrowOrientation uses com.skydoves.balloon✕
- Connections
- 4 pairs of types, where a type in com.skydoves.balloon.ArrowOrientation uses a type in com.skydoves.balloon.
- The types involved
com.skydoves.balloon.ArrowOrientation.BOTTOM→com.skydoves.balloon.ArrowOrientationcom.skydoves.balloon.ArrowOrientation.END→com.skydoves.balloon.ArrowOrientationcom.skydoves.balloon.ArrowOrientation.START→com.skydoves.balloon.ArrowOrientationcom.skydoves.balloon.ArrowOrientation.TOP→com.skydoves.balloon.ArrowOrientation
- Direction
- com.skydoves.balloon.ArrowOrientation uses com.skydoves.balloon, so a change to com.skydoves.balloon can break com.skydoves.balloon.ArrowOrientation, while a change to com.skydoves.balloon.ArrowOrientation can't break com.skydoves.balloon.
- Position
- Below the diagonal: com.skydoves.balloon.ArrowOrientation uses a module listed above it, which is the healthy direction.
10→7 com.skydoves.balloon.ArrowOrientationRules uses com.skydoves.balloon✕
- Connections
- 2 pairs of types, where a type in com.skydoves.balloon.ArrowOrientationRules uses a type in com.skydoves.balloon.
- The types involved
com.skydoves.balloon.ArrowOrientationRules.ALIGN_ANCHOR→com.skydoves.balloon.ArrowOrientationRulescom.skydoves.balloon.ArrowOrientationRules.ALIGN_FIXED→com.skydoves.balloon.ArrowOrientationRules
- Direction
- com.skydoves.balloon.ArrowOrientationRules uses com.skydoves.balloon, so a change to com.skydoves.balloon can break com.skydoves.balloon.ArrowOrientationRules, while a change to com.skydoves.balloon.ArrowOrientationRules can't break com.skydoves.balloon.
- Position
- Below the diagonal: com.skydoves.balloon.ArrowOrientationRules uses a module listed above it, which is the healthy direction.
11→7 com.skydoves.balloon.ArrowPositionRules uses com.skydoves.balloon✕
- Connections
- 2 pairs of types, where a type in com.skydoves.balloon.ArrowPositionRules uses a type in com.skydoves.balloon.
- The types involved
com.skydoves.balloon.ArrowPositionRules.ALIGN_ANCHOR→com.skydoves.balloon.ArrowPositionRulescom.skydoves.balloon.ArrowPositionRules.ALIGN_BALLOON→com.skydoves.balloon.ArrowPositionRules
- Direction
- com.skydoves.balloon.ArrowPositionRules uses com.skydoves.balloon, so a change to com.skydoves.balloon can break com.skydoves.balloon.ArrowPositionRules, while a change to com.skydoves.balloon.ArrowPositionRules can't break com.skydoves.balloon.
- Position
- Below the diagonal: com.skydoves.balloon.ArrowPositionRules uses a module listed above it, which is the healthy direction.
12→7 com.skydoves.balloon.BalloonAlign uses com.skydoves.balloon✕
- Connections
- 6 pairs of types, where a type in com.skydoves.balloon.BalloonAlign uses a type in com.skydoves.balloon.
- The types involved
com.skydoves.balloon.BalloonAlign.BOTTOM→com.skydoves.balloon.BalloonAligncom.skydoves.balloon.BalloonAlign.CENTER→com.skydoves.balloon.BalloonAligncom.skydoves.balloon.BalloonAlign.DROP_DOWN→com.skydoves.balloon.BalloonAligncom.skydoves.balloon.BalloonAlign.END→com.skydoves.balloon.BalloonAligncom.skydoves.balloon.BalloonAlign.START→com.skydoves.balloon.BalloonAligncom.skydoves.balloon.BalloonAlign.TOP→com.skydoves.balloon.BalloonAlign
- Direction
- com.skydoves.balloon.BalloonAlign uses com.skydoves.balloon, so a change to com.skydoves.balloon can break com.skydoves.balloon.BalloonAlign, while a change to com.skydoves.balloon.BalloonAlign can't break com.skydoves.balloon.
- Position
- Below the diagonal: com.skydoves.balloon.BalloonAlign uses a module listed above it, which is the healthy direction.
13→7 com.skydoves.balloon.BalloonAnimation uses com.skydoves.balloon✕
- Connections
- 5 pairs of types, where a type in com.skydoves.balloon.BalloonAnimation uses a type in com.skydoves.balloon.
- The types involved
com.skydoves.balloon.BalloonAnimation.CIRCULAR→com.skydoves.balloon.BalloonAnimationcom.skydoves.balloon.BalloonAnimation.ELASTIC→com.skydoves.balloon.BalloonAnimationcom.skydoves.balloon.BalloonAnimation.FADE→com.skydoves.balloon.BalloonAnimationcom.skydoves.balloon.BalloonAnimation.NONE→com.skydoves.balloon.BalloonAnimationcom.skydoves.balloon.BalloonAnimation.OVERSHOOT→com.skydoves.balloon.BalloonAnimation
- Direction
- com.skydoves.balloon.BalloonAnimation uses com.skydoves.balloon, so a change to com.skydoves.balloon can break com.skydoves.balloon.BalloonAnimation, while a change to com.skydoves.balloon.BalloonAnimation can't break com.skydoves.balloon.
- Position
- Below the diagonal: com.skydoves.balloon.BalloonAnimation uses a module listed above it, which is the healthy direction.
14→7 com.skydoves.balloon.BalloonCenterAlign uses com.skydoves.balloon✕
- Connections
- 4 pairs of types, where a type in com.skydoves.balloon.BalloonCenterAlign uses a type in com.skydoves.balloon.
- The types involved
com.skydoves.balloon.BalloonCenterAlign.BOTTOM→com.skydoves.balloon.BalloonCenterAligncom.skydoves.balloon.BalloonCenterAlign.END→com.skydoves.balloon.BalloonCenterAligncom.skydoves.balloon.BalloonCenterAlign.START→com.skydoves.balloon.BalloonCenterAligncom.skydoves.balloon.BalloonCenterAlign.TOP→com.skydoves.balloon.BalloonCenterAlign
- Direction
- com.skydoves.balloon.BalloonCenterAlign uses com.skydoves.balloon, so a change to com.skydoves.balloon can break com.skydoves.balloon.BalloonCenterAlign, while a change to com.skydoves.balloon.BalloonCenterAlign can't break com.skydoves.balloon.
- Position
- Below the diagonal: com.skydoves.balloon.BalloonCenterAlign uses a module listed above it, which is the healthy direction.
15→7 com.skydoves.balloon.BalloonHighlightAnimation uses com.skydoves.balloon✕
- Connections
- 5 pairs of types, where a type in com.skydoves.balloon.BalloonHighlightAnimation uses a type in com.skydoves.balloon.
- The types involved
com.skydoves.balloon.BalloonHighlightAnimation.BREATH→com.skydoves.balloon.BalloonHighlightAnimationcom.skydoves.balloon.BalloonHighlightAnimation.HEARTBEAT→com.skydoves.balloon.BalloonHighlightAnimationcom.skydoves.balloon.BalloonHighlightAnimation.NONE→com.skydoves.balloon.BalloonHighlightAnimationcom.skydoves.balloon.BalloonHighlightAnimation.ROTATE→com.skydoves.balloon.BalloonHighlightAnimationcom.skydoves.balloon.BalloonHighlightAnimation.SHAKE→com.skydoves.balloon.BalloonHighlightAnimation
- Direction
- com.skydoves.balloon.BalloonHighlightAnimation uses com.skydoves.balloon, so a change to com.skydoves.balloon can break com.skydoves.balloon.BalloonHighlightAnimation, while a change to com.skydoves.balloon.BalloonHighlightAnimation can't break com.skydoves.balloon.
- Position
- Below the diagonal: com.skydoves.balloon.BalloonHighlightAnimation uses a module listed above it, which is the healthy direction.
16→7 com.skydoves.balloon.BalloonOverlayAnimation uses com.skydoves.balloon✕
- Connections
- 2 pairs of types, where a type in com.skydoves.balloon.BalloonOverlayAnimation uses a type in com.skydoves.balloon.
- The types involved
com.skydoves.balloon.BalloonOverlayAnimation.FADE→com.skydoves.balloon.BalloonOverlayAnimationcom.skydoves.balloon.BalloonOverlayAnimation.NONE→com.skydoves.balloon.BalloonOverlayAnimation
- Direction
- com.skydoves.balloon.BalloonOverlayAnimation uses com.skydoves.balloon, so a change to com.skydoves.balloon can break com.skydoves.balloon.BalloonOverlayAnimation, while a change to com.skydoves.balloon.BalloonOverlayAnimation can't break com.skydoves.balloon.
- Position
- Below the diagonal: com.skydoves.balloon.BalloonOverlayAnimation uses a module listed above it, which is the healthy direction.
17→7 com.skydoves.balloon.BalloonOverlayShape uses com.skydoves.balloon✕
- Connections
- 6 pairs of types, where a type in com.skydoves.balloon.BalloonOverlayShape uses a type in com.skydoves.balloon.
- The types involved
com.skydoves.balloon.BalloonOverlayShape.Circle→com.skydoves.balloon.BalloonOverlayShapecom.skydoves.balloon.BalloonOverlayShape.Empty→com.skydoves.balloon.BalloonOverlayShapecom.skydoves.balloon.BalloonOverlayShape.Oval→com.skydoves.balloon.BalloonOverlayShapecom.skydoves.balloon.BalloonOverlayShape.Rect→com.skydoves.balloon.BalloonOverlayShapecom.skydoves.balloon.BalloonOverlayShape.RoundRect→com.skydoves.balloon.BalloonOverlayShapecom.skydoves.balloon.BalloonOverlayShape.RoundRectPerCorner→com.skydoves.balloon.BalloonOverlayShape
- Direction
- com.skydoves.balloon.BalloonOverlayShape uses com.skydoves.balloon, so a change to com.skydoves.balloon can break com.skydoves.balloon.BalloonOverlayShape, while a change to com.skydoves.balloon.BalloonOverlayShape can't break com.skydoves.balloon.
- Position
- Below the diagonal: com.skydoves.balloon.BalloonOverlayShape uses a module listed above it, which is the healthy direction.
18→7 com.skydoves.balloon.BalloonRotateDirection uses com.skydoves.balloon✕
- Connections
- 2 pairs of types, where a type in com.skydoves.balloon.BalloonRotateDirection uses a type in com.skydoves.balloon.
- The types involved
com.skydoves.balloon.BalloonRotateDirection.LEFT→com.skydoves.balloon.BalloonRotateDirectioncom.skydoves.balloon.BalloonRotateDirection.RIGHT→com.skydoves.balloon.BalloonRotateDirection
- Direction
- com.skydoves.balloon.BalloonRotateDirection uses com.skydoves.balloon, so a change to com.skydoves.balloon can break com.skydoves.balloon.BalloonRotateDirection, while a change to com.skydoves.balloon.BalloonRotateDirection can't break com.skydoves.balloon.
- Position
- Below the diagonal: com.skydoves.balloon.BalloonRotateDirection uses a module listed above it, which is the healthy direction.
19→7 com.skydoves.balloon.ResolvedArrowSide uses com.skydoves.balloon✕
- Connections
- 4 pairs of types, where a type in com.skydoves.balloon.ResolvedArrowSide uses a type in com.skydoves.balloon.
- The types involved
com.skydoves.balloon.ResolvedArrowSide.BOTTOM→com.skydoves.balloon.ResolvedArrowSidecom.skydoves.balloon.ResolvedArrowSide.LEFT→com.skydoves.balloon.ResolvedArrowSidecom.skydoves.balloon.ResolvedArrowSide.RIGHT→com.skydoves.balloon.ResolvedArrowSidecom.skydoves.balloon.ResolvedArrowSide.TOP→com.skydoves.balloon.ResolvedArrowSide
- Direction
- com.skydoves.balloon.ResolvedArrowSide uses com.skydoves.balloon, so a change to com.skydoves.balloon can break com.skydoves.balloon.ResolvedArrowSide, while a change to com.skydoves.balloon.ResolvedArrowSide can't break com.skydoves.balloon.
- Position
- Below the diagonal: com.skydoves.balloon.ResolvedArrowSide uses a module listed above it, which is the healthy direction.
20→7 com.skydoves.balloon.kmpdemo.parity uses com.skydoves.balloon✕
- Connections
- 1 pair of types, where a type in com.skydoves.balloon.kmpdemo.parity uses a type in com.skydoves.balloon.
- The types involved
com.skydoves.balloon.kmpdemo.parity.KmpParityActivityKt→com.skydoves.balloon.BalloonStyle
- Direction
- com.skydoves.balloon.kmpdemo.parity uses com.skydoves.balloon, so a change to com.skydoves.balloon can break com.skydoves.balloon.kmpdemo.parity, while a change to com.skydoves.balloon.kmpdemo.parity can't break com.skydoves.balloon.
- Position
- Below the diagonal: com.skydoves.balloon.kmpdemo.parity uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 20 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 6 | Medium |
| A07:2025 — Authentication Failures | 2 | High / Critical |
Roadmap
Top priorities: Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce; Resolve the 1 No ADRs found finding(s) in ADR Quality — start with project.pbxproj; 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.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with project.pbxproj. | +7.0 pts | Low | ADR Quality |
| Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce. | +7.2 pts | Medium | Observability |
| 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.4 pts | Medium | Architecture documentation |
| 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. | +3.9 pts | Medium | Security & performance tooling |
| Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it. | +2.0 pts | Medium | Deployment & Rollback |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +2.0 pts | Medium | Release Hygiene |
| Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. | +0.7 pts | Low | Secrets (history) |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +0.7 pts | Low | Static Analysis (SAST) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.6 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| balloon/src/commonMain/kotlin/com/skydoves/balloon/BalloonPopup.kt | 7.1 | Mixed | Cyclomatic Complexity: BalloonPopupPositionProvider.calculatePosition (cyclomatic 36) |
| balloon/src/commonMain/kotlin/com/skydoves/balloon/Balloon.kt | 7.1 | Mixed | Cyclomatic Complexity: BalloonKt.BalloonContent (cyclomatic 28) |
| balloon/src/commonMain/kotlin/com/skydoves/balloon/BalloonShapeBuilder.kt | 7.1 | Mixed | Cyclomatic Complexity: BalloonShapeBuilderKt.buildBalloonPath (cyclomatic 18) |
| samples-shared/src/commonMain/kotlin/com/skydoves/balloon/sample/BalloonDemoScreen.kt | 7.1 | Mixed | Code Duplication: Edited copy of a member (31 corresponding lines) |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| androidApp/src/androidMain/kotlin/com/skydoves/balloon/kmpdemo/parity/KmpParityActivity.kt | 8.5 | Near-clean | Cognitive Complexity: KmpParityActivityKt.toStyle (cognitive 16) |
| samples-shared/src/commonMain/kotlin/com/skydoves/balloon/sample/labs/LabsControls.kt | 8.5 | Near-clean | Code Duplication: Edited copy of a member (15 corresponding lines) |
| iosApp/iosApp.xcodeproj/project.pbxproj | 9.5 | Near-clean | ADR Quality: No ADRs found |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 40 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 40 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 53 of 363 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.kt) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
- 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.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (36 contributor(s) across 1560 commit(s) sampled, automation and bot accounts excluded). One of them holds 93% of the history; the other 35 hold 0.2% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `balloon/src/commonMain/kotlin/com/skydoves/balloon/Balloon.kt`, `balloon/src/commonMain/kotlin/com/skydoves/balloon/BalloonStyle.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.
- AX6 Interface segregation — 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 is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing 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.
- 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: 1 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Kotlin, Swift is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Kotlin, Swift is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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.
- 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 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- 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.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
4 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was BalloonPopupPositionProvider.calculatePosition at 36.
What to do
- Bring the 4 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with BalloonPopupPositionProvider.calculatePosition (cyclomatic 36), BalloonKt.BalloonContent (cyclomatic 28), BalloonShapeBuilderKt.buildBalloonPath (cyclomatic 18). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cyclomatic Complexity from 8.8 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
6 method(s) exceeded the cognitive complexity threshold of 15; the worst was BalloonPopupPositionProvider.calculatePosition at 75.
What to do
- Bring the 2 bodies over 30 down to 30 or less in Cognitive Complexity — start with BalloonPopupPositionProvider.calculatePosition (cognitive 75), BalloonKt.BalloonContent (cognitive 35). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 7.5 to about 8.7/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
D3 · God Classes
4 god class(es) detected.
What to do
- Resolve the 2 MethodTooLong finding(s) in God Classes — start with Balloon.kt, BalloonPopup.kt. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 TooManyMethods finding(s) in God Classes — start with Balloon.kt. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 FileTooLong finding(s) in God Classes — start with Balloon.kt. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
6 duplicated block group(s) detected. 2.7 % of the production lines (243 of 8,901) are in a reported copy. A further 3 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 2 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with BalloonDemoScreen.kt (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Edited copy of a member (31 corresponding lines) finding(s) in Code Duplication — start with BalloonDemoScreen.kt. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copy of a member (34 corresponding lines) finding(s) in Code Duplication — start with BalloonDemoScreen.kt. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
6 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; 2 module(s) off the main sequence.
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
0 of 3 classes have LCOM4 above 3.
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: 611 artifact(s) resolved, 393 of them gradable against Maven Central, and 298 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 · REDACTED Scanning
REDACTED scan ran and found no leaked secrets.
D14 · License Compliance
0 of 8 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 9 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. A further 5 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict.
D15 · Churn × Complexity Hotspots
Top hotspots: balloon/src/commonMain/kotlin/com/skydoves/balloon/BalloonPopup.kt (6×36=216); balloon/src/commonMain/kotlin/com/skydoves/balloon/Balloon.kt (6×28=168); balloon/src/commonMain/kotlin/com/skydoves/balloon/BalloonShapeBuilder.kt (3×18=54)
What to do
- Resolve the 3 Hotspot finding(s) in Churn × Complexity Hotspots — start with BalloonPopup.kt, Balloon.kt, BalloonShapeBuilder.kt. — One of this dimension's main actionable groups (3 warning-level).
D17 · Explicit Debt
0 deducted task-comment markers across 8901 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 25 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with project.pbxproj. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
0 of 8 build units (Gradle, Xcode) flagged as possibly oversized/incoherent.
D28 · Secrets (history)
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
20 finding(s): 0 critical, 18 high, 2 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 178) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- 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
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 20 of the 43 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 6 platform declaration(s) and 13 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
M1 · Documentation (README)
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
What to do
- Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
P3 · Security & performance tooling
- 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 3 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
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.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
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.
PF1 · Benchmark discipline
- A JMH/Jetpack Benchmark suite exists but nothing turns on its allocation measurement — allocations (the main way hot code pressures a garbage collector or allocator) aren't being measured.
What to do
- Run JMH with the GC profiler (`-prof gc`, or addProfiler(GCProfiler.class)) so allocation rate regressions are visible, not just time.
PF3 · Async & latency hygiene
X1 · Async correctness
X12 · Unreachable branch
X21 · Side-effecting pattern guard
X27 · Collection changed while being enumerated
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 95% | Exemplary | Solid. |
| Architecture | 98% | Exemplary | Strongest area. |
| Maturity | 56% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 41% | Weak — gated by P2, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 73% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 86% | Strong | Solid. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 74 check(s) not relevant to this codebase
- AC1 Text alternatives — Frontend below the scale floor (8 DOM element(s) < 25) — too little surface to assess accessibility.
- AC2 Forms & labels — Frontend below the scale floor (8 DOM element(s) < 25) — too little surface to assess accessibility.
- AC3 Page structure — Frontend below the scale floor (8 DOM element(s) < 25) — too little surface to assess accessibility.
- AC4 Keyboard semantics — Frontend below the scale floor (8 DOM element(s) < 25) — too little surface to assess accessibility.
- AC5 ARIA correctness — Frontend below the scale floor (8 DOM element(s) < 25) — too little surface to assess accessibility.
- AC6 Visual & motion safety — Frontend below the scale floor (8 DOM element(s) < 25) — too little surface to assess accessibility.
- 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; this repository's Swift 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. No Swift request handler (a Vapor, Hummingbird, Kitura, Swifter or Perfect route handler, as a method or a registered closure) is declared, so no state is shared between request threads.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface 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.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~4557 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.
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (1143 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Kotlin surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .kt, .swift, 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) and a Gradle version catalogue — 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) — 2 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) and a Gradle version catalogue — 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
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (14 value object(s))
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and this analysis resolves a call's owner only where the receiver's type is written down in the source. Reported as guidance rather than measured
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- M4 Documentation accuracy — Not applicable: the 25 current-state document(s) make no claim of a kind M4 checks. 9 claim(s) of kinds M4 does not check were not checked (environment variable 9); M4 checks only links and versions and artefact counts.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM, Swift source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- 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
- X16 Unfloored truncation loop — 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 — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not 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
- X3 Exception handling — 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 — 19 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 34 finding(s)
- Hotspot: balloon/src/commonMain/kotlin/com/skydoves/balloon/BalloonPopup.kt balloon/src/commonMain/kotlin/com/skydoves/balloon/BalloonPopup.kt:531
- Hotspot: balloon/src/commonMain/kotlin/com/skydoves/balloon/Balloon.kt balloon/src/commonMain/kotlin/com/skydoves/balloon/Balloon.kt:107
- Hotspot: balloon/src/commonMain/kotlin/com/skydoves/balloon/BalloonShapeBuilder.kt balloon/src/commonMain/kotlin/com/skydoves/balloon/BalloonShapeBuilder.kt:104
- MethodTooLong: BalloonKt.BalloonContent balloon/src/commonMain/kotlin/com/skydoves/balloon/Balloon.kt:107
- MethodTooLong: BalloonPopupPositionProvider.calculatePosition balloon/src/commonMain/kotlin/com/skydoves/balloon/BalloonPopup.kt:531
- Duplicated block (13 lines × 2) samples-shared/src/commonMain/kotlin/com/skydoves/balloon/sample/BalloonDemoScreen.kt:575
- Duplicated block (13 lines × 2) samples-shared/src/commonMain/kotlin/com/skydoves/balloon/sample/BalloonDemoScreen.kt:720
- BalloonPopupPositionProvider.calculatePosition (cyclomatic 36) balloon/src/commonMain/kotlin/com/skydoves/balloon/BalloonPopup.kt:531
- BalloonKt.BalloonContent (cyclomatic 28) balloon/src/commonMain/kotlin/com/skydoves/balloon/Balloon.kt:107
- BalloonShapeBuilderKt.buildBalloonPath (cyclomatic 18) balloon/src/commonMain/kotlin/com/skydoves/balloon/BalloonShapeBuilder.kt:104
- BalloonPopupPositionProvider.resolveArrowCenter (cyclomatic 16) balloon/src/commonMain/kotlin/com/skydoves/balloon/BalloonPopup.kt:744
- BalloonPopupPositionProvider.calculatePosition (cognitive 75) balloon/src/commonMain/kotlin/com/skydoves/balloon/BalloonPopup.kt:531
- BalloonKt.BalloonContent (cognitive 35) balloon/src/commonMain/kotlin/com/skydoves/balloon/Balloon.kt:107
- BalloonShapeBuilderKt.buildBalloonPath (cognitive 19) balloon/src/commonMain/kotlin/com/skydoves/balloon/BalloonShapeBuilder.kt:104
- BalloonPopupPositionProvider.resolveArrowCenter (cognitive 17) balloon/src/commonMain/kotlin/com/skydoves/balloon/BalloonPopup.kt:744
- KmpParityActivityKt.toStyle (cognitive 16) androidApp/src/androidMain/kotlin/com/skydoves/balloon/kmpdemo/parity/KmpParityActivity.kt:110
- BalloonPopupKt.BalloonPopupLayer (cognitive 16) balloon/src/commonMain/kotlin/com/skydoves/balloon/BalloonPopup.kt:140
- REDACTED
- REDACTED
- TooManyMethods: Builder balloon/src/commonMain/kotlin/com/skydoves/balloon/Balloon.kt:477
- FileTooLong: balloon/Balloon.kt balloon/src/commonMain/kotlin/com/skydoves/balloon/Balloon.kt
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (31 corresponding lines) samples-shared/src/commonMain/kotlin/com/skydoves/balloon/sample/BalloonDemoScreen.kt:566
- Edited copy of a member (34 corresponding lines) samples-shared/src/commonMain/kotlin/com/skydoves/balloon/sample/BalloonDemoScreen.kt:525
- Edited copy of a member (15 corresponding lines) samples-shared/src/commonMain/kotlin/com/skydoves/balloon/sample/labs/LabsControls.kt:345
- Duplicated block (6 lines × 4) balloon/src/commonMain/kotlin/com/skydoves/balloon/BalloonShapeBuilder.kt:166
- Duplicated block (5 lines × 3) balloon/src/commonMain/kotlin/com/skydoves/balloon/BalloonShapeBuilder.kt:185
- Duplicated block (5 lines × 2) balloon/src/commonMain/kotlin/com/skydoves/balloon/BalloonShapeBuilder.kt:154
- Duplicated block (12 lines × 2) samples-shared/src/commonMain/kotlin/com/skydoves/balloon/sample/BalloonDemoScreen.kt:320
- Off the main sequence: :balloon
- No structured logging
Minor — 11 finding(s)
- No ADRs found iosApp/iosApp.xcodeproj/project.pbxproj:1
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- No SAST REDACTED:6
- No release approval gate
- No changelog
- Benchmarks don't track allocations
- Duplicated predicate balloon/src/commonMain/kotlin/com/skydoves/balloon/Balloon.kt:388
Minor — 299 finding(s)
- Outdated (compile): org.jetbrains.skiko:skiko-js-wasm-runtime
- Outdated (compile): org.jacoco:org.jacoco.ant
- Outdated (compile): org.jacoco:org.jacoco.core
- Outdated (compile): org.ow2.asm:asm
- Outdated (compile): org.ow2.asm:asm-commons
- Outdated (compile): org.ow2.asm:asm-tree
- Outdated (compile): org.jacoco:org.jacoco.report
- Outdated (compile): org.jacoco:org.jacoco.agent
- Outdated (compile): org.jetbrains.compose.runtime:runtime
- Outdated (compile): org.jetbrains.kotlin:kotlin-stdlib
- Outdated (compile): org.jetbrains.kotlinx:atomicfu
- Outdated (compile): org.jetbrains.kotlinx:kotlinx-coroutines-core
- Outdated (compile): org.jetbrains.compose.foundation:foundation
- Outdated (compile): org.jetbrains.compose.animation:animation
- Outdated (compile): org.jetbrains.compose.animation:animation-core
- Outdated (compile): org.jetbrains.compose.annotation-internal:annotation
- Outdated (compile): org.jetbrains.compose.collection-internal:collection
- Outdated (compile): org.jetbrains.compose.ui:ui
- Outdated (compile): org.jetbrains.androidx.lifecycle:lifecycle-common
- Outdated (compile): org.jetbrains.androidx.lifecycle:lifecycle-runtime
- Outdated (compile): org.jetbrains.androidx.lifecycle:lifecycle-runtime-compose
- Outdated (compile): org.jetbrains.androidx.lifecycle:lifecycle-viewmodel
- Outdated (compile): org.jetbrains.androidx.lifecycle:lifecycle-viewmodel-savedstate
- Outdated (compile): org.jetbrains.kotlinx:kotlinx-serialization-core
- Outdated (compile): org.jetbrains.androidx.savedstate:savedstate
- Off the main sequence: :samples-shared
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-7a012f89f51a4f499d5c4e8c0bbc0d5f/history.json --exit-code 0 --source . | 1 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-7a012f89f51a4f499d5c4e8c0bbc0d5f/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 . | 20 | 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) and a Gradle version catalogue — 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 2 file(s) — `balloon/src/commonMain/kotlin/com/skydoves/balloon/Balloon.kt`, `balloon/src/commonMain/kotlin/com/skydoves/balloon/BalloonStyle.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) and a Gradle version catalogue — not scanned yet). | 0 | — |