Executive summary
henninghall/react-native-date-picker is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back because we found no logging, tracing or health checks in the code and no automated security scanning of the code, its secrets or its dependencies. It scores 46.3 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 32.0, is the weakest lens and counts most in the score. The best first step is having someone learn and document the 18 files no active contributor knows, worth about 7.8 points. Adopting a logging library would lift Production Readiness itself, worth about 5.4 points. Raising Production Readiness to 70 would lift the score to about 57.9.
152 known security holes in the packages the code depends on can be used by attackers. Twenty-six pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and eight secrets can leak from the build pipeline. Updating the vulnerable packages, pinning each tool to an exact version and limiting each secret to its own step would close these risks. Giving the pull-request workflow read-only access would fix the pipeline that outsiders can trigger with write access. Adding the tests the test command is meant to run would take care of the test command with no tests behind it.
The product code is 6,408 lines, about €5,900 to rebuild.
If Production Readiness rose from 32.0 to 70, the lowest score rated Strong, the score would rise from 46.3 to about 57.9.
Rebuild cost: about €5,900 · Estimate
| Cost to rebuild | €1,900 to €9,800, for 32 to 103 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.7 at a score of 46. 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: 6,408 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 (global) | 2 com.henninghall.date_picker.generated | 3 com.henninghall.date_picker.models | 4 src | 5 src.fabric | 6 src.fabric.NativeRNDatePicker | 7 src.fabric.RNDatePickerNativeComponent | 8 src.propChecker | 9 com.henninghall.date_picker.pickers | 10 com.henninghall.date_picker.props | 11 com.henninghall.date_picker.wheels | 12 com.henninghall.date_picker.wheelFunctions | 13 com.henninghall.date_picker.ui | 14 com.henninghall.date_picker |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 (global) | ||||||||||||||
| 2 com.henninghall.date_picker.generated | ||||||||||||||
| 3 com.henninghall.date_picker.models | ||||||||||||||
| 4 src | ||||||||||||||
| 5 src.fabric | ||||||||||||||
| 6 src.fabric.NativeRNDatePicker | ||||||||||||||
| 7 src.fabric.RNDatePickerNativeComponent | ||||||||||||||
| 8 src.propChecker | ||||||||||||||
| 9 com.henninghall.date_picker.pickers | 5 | |||||||||||||
| 10 com.henninghall.date_picker.props | 2 | |||||||||||||
| 11 com.henninghall.date_picker.wheels | 8 | 9 | ||||||||||||
| 12 com.henninghall.date_picker.wheelFunctions | 1 | 9 | 1 | |||||||||||
| 13 com.henninghall.date_picker.ui | 1 | 2 | 11 | 1 | 3 | |||||||||
| 14 com.henninghall.date_picker | 4 | 13 | 5 |
9→2 com.henninghall.date_picker.pickers uses com.henninghall.date_picker.generated✕
- Connections
- 5 pairs of types, where a type in com.henninghall.date_picker.pickers uses a type in com.henninghall.date_picker.generated.
- The types involved
com.henninghall.date_picker.pickers.3→com.henninghall.date_picker.generated.NumberPickercom.henninghall.date_picker.pickers.3→com.henninghall.date_picker.generated.OnValueChangeListenercom.henninghall.date_picker.pickers.4→com.henninghall.date_picker.generated.NumberPickercom.henninghall.date_picker.pickers.4→com.henninghall.date_picker.generated.OnScrollListenercom.henninghall.date_picker.pickers.AndroidNative→com.henninghall.date_picker.generated.NumberPicker
- Direction
- com.henninghall.date_picker.pickers uses com.henninghall.date_picker.generated, so a change to com.henninghall.date_picker.generated can break com.henninghall.date_picker.pickers, while a change to com.henninghall.date_picker.pickers can't break com.henninghall.date_picker.generated.
- Position
- Below the diagonal: com.henninghall.date_picker.pickers uses a module listed above it, which is the healthy direction.
10→3 com.henninghall.date_picker.props uses com.henninghall.date_picker.models✕
- Connections
- 2 pairs of types, where a type in com.henninghall.date_picker.props uses a type in com.henninghall.date_picker.models.
- The types involved
com.henninghall.date_picker.props.Is24hourSourceProp→com.henninghall.date_picker.models.Is24HourSourcecom.henninghall.date_picker.props.ModeProp→com.henninghall.date_picker.models.Mode
- Direction
- com.henninghall.date_picker.props uses com.henninghall.date_picker.models, so a change to com.henninghall.date_picker.models can break com.henninghall.date_picker.props, while a change to com.henninghall.date_picker.props can't break com.henninghall.date_picker.models.
- Position
- Below the diagonal: com.henninghall.date_picker.props uses a module listed above it, which is the healthy direction.
11→9 com.henninghall.date_picker.wheels uses com.henninghall.date_picker.pickers✕
- Connections
- 8 pairs of types, where a type in com.henninghall.date_picker.wheels uses a type in com.henninghall.date_picker.pickers.
- The types involved
com.henninghall.date_picker.wheels.AmPmWheel→com.henninghall.date_picker.pickers.Pickercom.henninghall.date_picker.wheels.DateWheel→com.henninghall.date_picker.pickers.Pickercom.henninghall.date_picker.wheels.DayWheel→com.henninghall.date_picker.pickers.Pickercom.henninghall.date_picker.wheels.HourWheel→com.henninghall.date_picker.pickers.Pickercom.henninghall.date_picker.wheels.MinutesWheel→com.henninghall.date_picker.pickers.Pickercom.henninghall.date_picker.wheels.MonthWheel→com.henninghall.date_picker.pickers.Pickercom.henninghall.date_picker.wheels.Wheel→com.henninghall.date_picker.pickers.Pickercom.henninghall.date_picker.wheels.YearWheel→com.henninghall.date_picker.pickers.Picker
- Direction
- com.henninghall.date_picker.wheels uses com.henninghall.date_picker.pickers, so a change to com.henninghall.date_picker.pickers can break com.henninghall.date_picker.wheels, while a change to com.henninghall.date_picker.wheels can't break com.henninghall.date_picker.pickers.
- Position
- Below the diagonal: com.henninghall.date_picker.wheels uses a module listed above it, which is the healthy direction.
11→14 com.henninghall.date_picker.wheels uses com.henninghall.date_picker part of a loop✕
- Connections
- 9 pairs of types, where a type in com.henninghall.date_picker.wheels uses a type in com.henninghall.date_picker.
- The types involved
com.henninghall.date_picker.wheels.AmPmWheel→com.henninghall.date_picker.Statecom.henninghall.date_picker.wheels.DateWheel→com.henninghall.date_picker.Statecom.henninghall.date_picker.wheels.DayWheel→com.henninghall.date_picker.Statecom.henninghall.date_picker.wheels.HourWheel→com.henninghall.date_picker.HourDisplayBugWorkaroundcom.henninghall.date_picker.wheels.HourWheel→com.henninghall.date_picker.Statecom.henninghall.date_picker.wheels.MinutesWheel→com.henninghall.date_picker.Statecom.henninghall.date_picker.wheels.MonthWheel→com.henninghall.date_picker.Statecom.henninghall.date_picker.wheels.Wheel→com.henninghall.date_picker.Statecom.henninghall.date_picker.wheels.YearWheel→com.henninghall.date_picker.State
- Direction
- com.henninghall.date_picker.wheels uses com.henninghall.date_picker, so a change to com.henninghall.date_picker can break com.henninghall.date_picker.wheels, while a change to com.henninghall.date_picker.wheels can't break com.henninghall.date_picker.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→9 com.henninghall.date_picker.wheelFunctions uses com.henninghall.date_picker.pickers✕
- Connections
- 1 pair of types, where a type in com.henninghall.date_picker.wheelFunctions uses a type in com.henninghall.date_picker.pickers.
- The types involved
com.henninghall.date_picker.wheelFunctions.1→com.henninghall.date_picker.pickers.OnValueChangeListener
- Direction
- com.henninghall.date_picker.wheelFunctions uses com.henninghall.date_picker.pickers, so a change to com.henninghall.date_picker.pickers can break com.henninghall.date_picker.wheelFunctions, while a change to com.henninghall.date_picker.wheelFunctions can't break com.henninghall.date_picker.pickers.
- Position
- Below the diagonal: com.henninghall.date_picker.wheelFunctions uses a module listed above it, which is the healthy direction.
12→11 com.henninghall.date_picker.wheelFunctions uses com.henninghall.date_picker.wheels✕
- Connections
- 9 pairs of types, where a type in com.henninghall.date_picker.wheelFunctions uses a type in com.henninghall.date_picker.wheels.
- The types involved
com.henninghall.date_picker.wheelFunctions.AddOnChangeListener→com.henninghall.date_picker.wheels.Wheelcom.henninghall.date_picker.wheelFunctions.AnimateToDate→com.henninghall.date_picker.wheels.Wheelcom.henninghall.date_picker.wheelFunctions.Hide→com.henninghall.date_picker.wheels.Wheelcom.henninghall.date_picker.wheelFunctions.Refresh→com.henninghall.date_picker.wheels.Wheelcom.henninghall.date_picker.wheelFunctions.SetDate→com.henninghall.date_picker.wheels.Wheelcom.henninghall.date_picker.wheelFunctions.SetDividerColor→com.henninghall.date_picker.wheels.Wheelcom.henninghall.date_picker.wheelFunctions.TextColor→com.henninghall.date_picker.wheels.Wheelcom.henninghall.date_picker.wheelFunctions.UpdateVisibility→com.henninghall.date_picker.wheels.Wheelcom.henninghall.date_picker.wheelFunctions.WheelFunction→com.henninghall.date_picker.wheels.Wheel
- Direction
- com.henninghall.date_picker.wheelFunctions uses com.henninghall.date_picker.wheels, so a change to com.henninghall.date_picker.wheels can break com.henninghall.date_picker.wheelFunctions, while a change to com.henninghall.date_picker.wheelFunctions can't break com.henninghall.date_picker.wheels.
- Position
- Below the diagonal: com.henninghall.date_picker.wheelFunctions uses a module listed above it, which is the healthy direction.
12→13 com.henninghall.date_picker.wheelFunctions uses com.henninghall.date_picker.ui part of a loop✕
- Connections
- 1 pair of types, where a type in com.henninghall.date_picker.wheelFunctions uses a type in com.henninghall.date_picker.ui.
- The types involved
com.henninghall.date_picker.wheelFunctions.AddOnChangeListener→com.henninghall.date_picker.ui.WheelChangeListener
- Direction
- com.henninghall.date_picker.wheelFunctions uses com.henninghall.date_picker.ui, so a change to com.henninghall.date_picker.ui can break com.henninghall.date_picker.wheelFunctions, while a change to com.henninghall.date_picker.wheelFunctions can't break com.henninghall.date_picker.ui.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→3 com.henninghall.date_picker.ui uses com.henninghall.date_picker.models✕
- Connections
- 1 pair of types, where a type in com.henninghall.date_picker.ui uses a type in com.henninghall.date_picker.models.
- The types involved
com.henninghall.date_picker.ui.Wheels→com.henninghall.date_picker.models.WheelType
- Direction
- com.henninghall.date_picker.ui uses com.henninghall.date_picker.models, so a change to com.henninghall.date_picker.models can break com.henninghall.date_picker.ui, while a change to com.henninghall.date_picker.ui can't break com.henninghall.date_picker.models.
- Position
- Below the diagonal: com.henninghall.date_picker.ui uses a module listed above it, which is the healthy direction.
13→9 com.henninghall.date_picker.ui uses com.henninghall.date_picker.pickers✕
- Connections
- 2 pairs of types, where a type in com.henninghall.date_picker.ui uses a type in com.henninghall.date_picker.pickers.
- The types involved
com.henninghall.date_picker.ui.Accessibility→com.henninghall.date_picker.pickers.Pickercom.henninghall.date_picker.ui.Wheels→com.henninghall.date_picker.pickers.Picker
- Direction
- com.henninghall.date_picker.ui uses com.henninghall.date_picker.pickers, so a change to com.henninghall.date_picker.pickers can break com.henninghall.date_picker.ui, while a change to com.henninghall.date_picker.ui can't break com.henninghall.date_picker.pickers.
- Position
- Below the diagonal: com.henninghall.date_picker.ui uses a module listed above it, which is the healthy direction.
13→11 com.henninghall.date_picker.ui uses com.henninghall.date_picker.wheels✕
- Connections
- 11 pairs of types, where a type in com.henninghall.date_picker.ui uses a type in com.henninghall.date_picker.wheels.
- The types involved
com.henninghall.date_picker.ui.WheelChangeListener→com.henninghall.date_picker.wheels.Wheelcom.henninghall.date_picker.ui.WheelChangeListenerImpl→com.henninghall.date_picker.wheels.Wheelcom.henninghall.date_picker.ui.WheelScroller→com.henninghall.date_picker.wheels.Wheelcom.henninghall.date_picker.ui.Wheels→com.henninghall.date_picker.wheels.AmPmWheelcom.henninghall.date_picker.ui.Wheels→com.henninghall.date_picker.wheels.DateWheelcom.henninghall.date_picker.ui.Wheels→com.henninghall.date_picker.wheels.DayWheelcom.henninghall.date_picker.ui.Wheels→com.henninghall.date_picker.wheels.HourWheelcom.henninghall.date_picker.ui.Wheels→com.henninghall.date_picker.wheels.MinutesWheelcom.henninghall.date_picker.ui.Wheels→com.henninghall.date_picker.wheels.MonthWheelcom.henninghall.date_picker.ui.Wheels→com.henninghall.date_picker.wheels.Wheelcom.henninghall.date_picker.ui.Wheels→com.henninghall.date_picker.wheels.YearWheel
- Direction
- com.henninghall.date_picker.ui uses com.henninghall.date_picker.wheels, so a change to com.henninghall.date_picker.wheels can break com.henninghall.date_picker.ui, while a change to com.henninghall.date_picker.ui can't break com.henninghall.date_picker.wheels.
- Position
- Below the diagonal: com.henninghall.date_picker.ui uses a module listed above it, which is the healthy direction.
13→12 com.henninghall.date_picker.ui uses com.henninghall.date_picker.wheelFunctions✕
- Connections
- 1 pair of types, where a type in com.henninghall.date_picker.ui uses a type in com.henninghall.date_picker.wheelFunctions.
- The types involved
com.henninghall.date_picker.ui.Wheels→com.henninghall.date_picker.wheelFunctions.WheelFunction
- Direction
- com.henninghall.date_picker.ui uses com.henninghall.date_picker.wheelFunctions, so a change to com.henninghall.date_picker.wheelFunctions can break com.henninghall.date_picker.ui, while a change to com.henninghall.date_picker.ui can't break com.henninghall.date_picker.wheelFunctions.
- Position
- Below the diagonal: com.henninghall.date_picker.ui uses a module listed above it, which is the healthy direction.
13→14 com.henninghall.date_picker.ui uses com.henninghall.date_picker part of a loop✕
- Connections
- 3 pairs of types, where a type in com.henninghall.date_picker.ui uses a type in com.henninghall.date_picker.
- The types involved
com.henninghall.date_picker.ui.UIManager→com.henninghall.date_picker.Statecom.henninghall.date_picker.ui.WheelChangeListenerImpl→com.henninghall.date_picker.Statecom.henninghall.date_picker.ui.Wheels→com.henninghall.date_picker.State
- Direction
- com.henninghall.date_picker.ui uses com.henninghall.date_picker, so a change to com.henninghall.date_picker can break com.henninghall.date_picker.ui, while a change to com.henninghall.date_picker.ui can't break com.henninghall.date_picker.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→3 com.henninghall.date_picker uses com.henninghall.date_picker.models✕
- Connections
- 4 pairs of types, where a type in com.henninghall.date_picker uses a type in com.henninghall.date_picker.models.
- The types involved
com.henninghall.date_picker.DerivedData→com.henninghall.date_picker.models.WheelTypecom.henninghall.date_picker.State→com.henninghall.date_picker.models.Is24HourSourcecom.henninghall.date_picker.State→com.henninghall.date_picker.models.Modecom.henninghall.date_picker.Utils→com.henninghall.date_picker.models.WheelType
- Direction
- com.henninghall.date_picker uses com.henninghall.date_picker.models, so a change to com.henninghall.date_picker.models can break com.henninghall.date_picker, while a change to com.henninghall.date_picker can't break com.henninghall.date_picker.models.
- Position
- Below the diagonal: com.henninghall.date_picker uses a module listed above it, which is the healthy direction.
14→10 com.henninghall.date_picker uses com.henninghall.date_picker.props✕
- Connections
- 13 pairs of types, where a type in com.henninghall.date_picker uses a type in com.henninghall.date_picker.props.
- The types involved
com.henninghall.date_picker.State→com.henninghall.date_picker.props.DatePropcom.henninghall.date_picker.State→com.henninghall.date_picker.props.DividerColorPropcom.henninghall.date_picker.State→com.henninghall.date_picker.props.HeightPropcom.henninghall.date_picker.State→com.henninghall.date_picker.props.IdPropcom.henninghall.date_picker.State→com.henninghall.date_picker.props.Is24hourSourcePropcom.henninghall.date_picker.State→com.henninghall.date_picker.props.LocalePropcom.henninghall.date_picker.State→com.henninghall.date_picker.props.MaximumDatePropcom.henninghall.date_picker.State→com.henninghall.date_picker.props.MinimumDatePropcom.henninghall.date_picker.State→com.henninghall.date_picker.props.MinuteIntervalPropcom.henninghall.date_picker.State→com.henninghall.date_picker.props.ModePropcom.henninghall.date_picker.State→com.henninghall.date_picker.props.Propcom.henninghall.date_picker.State→com.henninghall.date_picker.props.TextColorPropcom.henninghall.date_picker.State→com.henninghall.date_picker.props.TimezoneOffsetInMinutesProp
- Direction
- com.henninghall.date_picker uses com.henninghall.date_picker.props, so a change to com.henninghall.date_picker.props can break com.henninghall.date_picker, while a change to com.henninghall.date_picker can't break com.henninghall.date_picker.props.
- Position
- Below the diagonal: com.henninghall.date_picker uses a module listed above it, which is the healthy direction.
14→13 com.henninghall.date_picker uses com.henninghall.date_picker.ui✕
- Connections
- 5 pairs of types, where a type in com.henninghall.date_picker uses a type in com.henninghall.date_picker.ui.
- The types involved
com.henninghall.date_picker.7→com.henninghall.date_picker.ui.SpinnerStatecom.henninghall.date_picker.7→com.henninghall.date_picker.ui.SpinnerStateListenercom.henninghall.date_picker.Emitter→com.henninghall.date_picker.ui.SpinnerStatecom.henninghall.date_picker.PickerView→com.henninghall.date_picker.ui.SpinnerStateListenercom.henninghall.date_picker.PickerView→com.henninghall.date_picker.ui.UIManager
- Direction
- com.henninghall.date_picker uses com.henninghall.date_picker.ui, so a change to com.henninghall.date_picker.ui can break com.henninghall.date_picker, while a change to com.henninghall.date_picker can't break com.henninghall.date_picker.ui.
- Position
- Below the diagonal: com.henninghall.date_picker 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 |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 246 | High / Critical |
| A05:2025 — Injection | 42 | High / Critical |
Roadmap
Top priorities: Resolve the 18 Orphaned file finding(s) in Knowledge Freshness — start with Accessibility.java, AndroidNative.java, Formats.java; 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; Adopt SLF4J (with a Logback or Log4j2 JSON encoder) and log at meaningful points in the modules you run.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 18 Orphaned file finding(s) in Knowledge Freshness — start with Accessibility.java, AndroidNative.java, Formats.java. | +7.8 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.1 pts | Medium | Architecture documentation |
| Adopt SLF4J (with a Logback or Log4j2 JSON encoder) and log at meaningful points in the modules you run. | +5.4 pts | Medium | Observability |
| Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +5.4 pts | Medium | Security & performance tooling |
| Add tests that import the unreached modules (directly or through their public entry). | +4.6 pts | Medium | Test Coverage |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +1.8 pts | Medium | Release Hygiene |
| Resolve the 6 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED (2). | +0.7 pts | Low | Static Analysis (SAST) |
| Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. | +0.7 pts | Low | Knowledge Freshness |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 1.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 1.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 1.6 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.1 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 4.8 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 4.8 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 4.8 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 53 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 — 53 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, 343 of 361 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: this repository's production source spans .ts, .tsx, .java, and our analyzer cannot run the .java test suite(s) — so no coverage was collected for the repository as a whole. The JavaScript/TypeScript half did build and run, and its own line coverage came back at 94.1% — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — coverage is excluded from the score rather than counted as a near-zero.
- D10 Test Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 20 test(s) behind this row are the ones the code-model census could read, and this repository also carries at least 4 test source file(s) (.tsx, .js) that it cannot: it reads the test types the .java frontend declared, so a suite in any other language is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT SCORED: this repository's production source includes .java, and the jvm executor ran against the .java half and could not be re-run to completion inside our analyzer environment — so reliability was not measured for the repository as a whole. The JavaScript/TypeScript (jest via `yarn install --frozen-lockfile --ignore-scripts` in the repository root (11 tests); jest via `yarn install --frozen-lockfile --ignore-scripts` in examples/Rn069/ (0 tests); jest via `yarn install --frozen-lockfile --ignore-scripts` in examples/Rn071/ (0 tests); jest via `yarn install --frozen-lockfile --ignore-scripts` in examples/Rn072/ (1 tests); jest via `yarn install --frozen-lockfile --ignore-scripts` in examples/Rn073/ (0 tests)): measured (0 flaky) suite(s) did re-run, and came back with 0 flaky across 1 measured tier(s) — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — test reliability is excluded from the score rather than counted. The remedy is our analyzer environment, not a runner nobody has built.
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its gem dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Gradle build (build.gradle/build.gradle.kts), but the licence verdict published here was taken over its gem dependencies. Nothing was read about its Gradle dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- 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 (49 contributor(s) across 647 commit(s) sampled, automation and bot accounts excluded). One of them holds 90% of the history; the other 48 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.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: it declares a published package (package.json), but no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
- 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. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- 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. These audit 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 audit controls.
- 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. These retention 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 retention controls.
- 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. These data-subject rights 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 data-subject rights controls.
- 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 none applies: this repository publishes a library and deploys nothing (no container, IaC or deployment manifest), so it holds no runtime state of its own. Any data-access dependency it declares is the store it is a CLIENT for, not one it operates. The DR control belongs to whoever runs that data.
- 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.
- X12 Unreachable branch — 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 most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- 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.
- X27 Collection changed while being enumerated — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
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.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- 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.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
1 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was AccessibilityNodeProviderImpl.performAction at 45.
What to do
- Bring the 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with AccessibilityNodeProviderImpl.performAction (cyclomatic 45). — Refactoring it lifts Cyclomatic Complexity from 8.8 to about 10.0/10.
D2 · Cognitive Complexity
7 method(s) exceeded the cognitive complexity threshold of 15; the worst was AccessibilityNodeProviderImpl.performAction at 63.
What to do
- Bring the 2 bodies over 30 down to 30 or less in Cognitive Complexity — start with AccessibilityNodeProviderImpl.performAction (cognitive 63), NumberPicker.onTouchEvent (cognitive 31). — 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.9 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
1 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 1 FunctionTooLong finding(s) in God Classes — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
3 duplicated block group(s) detected. 3.3 % of the production lines (211 of 6,408) 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. 1 of the 6 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 1 Edited copy of a member (15 corresponding lines) finding(s) in Code Duplication — start with DayWheel.java. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copy of a member (11 corresponding lines) finding(s) in Code Duplication — start with MonthWheel.java. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copy of a member (17 corresponding lines) finding(s) in Code Duplication — start with NumberPicker.java. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
2 production modules (Gradle+npm), 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; 0 module(s) off the main sequence.
D6 · Cohesion (LCOM4)
0 of 13 classes have LCOM4 above 3.
D10 · Test Quality
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 20 tests. Measured on the .java suite only — at least 4 test source file(s) (.tsx, .js) went unread, so its test quality is unmeasured and is not in these counts.
D12 · Dependency Hygiene
7 outdated direct SwiftPM dependencies, 0 pinning defect(s). 12 of 15 direct dependencies had their releases listed (0 naming no readable repository, 3 pinned to a branch or a revision rather than a version). SwiftPM has no package registry: a dependency is a repository URL and its releases are that repository's semver tags, so currency is answered by listing tags rather than by querying an index. Only a newer tag on the SAME MAJOR is reported — a `from:` requirement admits everything below the next major and nothing above it, so a major crossing needs a Package.swift edit rather than an update, and naming the update as its remedy would be wrong. Whether any dependency is DEPRECATED or ABANDONED is not graded and cannot be: a repository publishes no such marker, and there is no registry that could carry one. Known CVEs in this dependency graph are D30's question. 15 third-party CocoaPods resolved by a committed Podfile.lock were graded against the CocoaPods trunk (cdn.cocoapods.org): a pod is behind only when the trunk lists a newer release on the same major, which `pod update` reaches under a `~>` requirement. A pod sourced from a path, git URL or local podspec has no trunk release to compare and is not asked about. Carthage dependencies are not graded.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 37 shipped gem(s) use a banned license. Licences were resolved from rubygems.org over the 37 gem(s) a consumer installs — this repository's runtime declarations closed transitively over its committed REDACTED. Development-group and `add_development_dependency` gems are excluded: they are not distributed with this repository. 2 of them publish no licence on rubygems.org; that is missing data, not a violation, and none of them is charged. ★ COVERAGE OF THIS VERDICT: it grades this repository's gem dependencies and nothing else. The repository also declares package.json and a Gradle build (build.gradle/build.gradle.kts), and the licences of those dependency graphs were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
1 deducted task-comment markers across 6408 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 1 XxxComment finding(s) in Explicit Debt — start with NumberPicker.java. — One of this dimension's main actionable groups (1 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 1 document(s) read across 1 unit(s).
D26 · Project Cohesion
0 of 2 build units (Gradle, npm) flagged as possibly oversized/incoherent.
D27 · Navigability
30 % of calls cross a namespace and 11 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
42 finding(s): 0 critical, 34 high, 8 medium, 0 low. 26 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 5 file(s) — `android/gradlew` (lines 144–145, line 146, line 147, …), `examples/Rn069/android/gradlew` (line 72, line 173), `examples/Rn071/android/gradlew` (line 72, line 173), `examples/Rn072/android/gradlew` (line 72, line 177), `examples/Rn073/android/gradlew` (line 72, 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. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 6 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED (2). — One of this dimension's main actionable groups (6 issue-level).
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
- No action in Static Analysis (SAST) — all 26 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 (26 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
230 finding(s): 16 critical, 136 high, 44 medium, 34 low.
What to do
- Resolve the 136 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (103), REDACTED (17), REDACTED (16). — One of this dimension's main actionable groups (136 issue-level).
- Resolve the 16 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (14), REDACTED (2). — One of this dimension's main actionable groups (16 issue-level).
- Resolve the 44 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (39), REDACTED (5). — One of this dimension's main actionable groups (44 warning-level).
D34 · Knowledge Freshness
18 of 18 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is android/src/main/java/com/henninghall/date_picker/ui/Accessibility.java. Counted over 18 of the 63 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 18 Orphaned file finding(s) in Knowledge Freshness — start with Accessibility.java, AndroidNative.java, Formats.java. — One of this dimension's main actionable groups (18 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: DatePickerAndroid.js↔DatePickerIOS.js 55%
What to do
- Resolve the 1 Change coupling finding(s) in Change Coupling — start with DatePickerAndroid.js. — One of this dimension's main actionable groups (1 warning-level).
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 10 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (10 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 issue-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 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
AX6 · Interface segregation
- `Picker` declares 19 abstract methods: `getDisplayedValues`, `getMaxValue`, `getValue`, `getView`, `getWrapSelectorWheel`, `isSpinning`, `setDisplayedValues`, `setDividerColor`, `setMaxValue`, `setMinValue`, `setOnValueChangeListenerInScrolling`, `setOnValueChangedListener`, `setTextAlign`, `setTextColor`, `setValue`, `setVisibility`, `setWrapSelectorWheel`, `smoothScrollToValue`, `smoothScrollToValue`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 19 declarations carry 18 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 18 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — android/src/main/java/com/henninghall/date_picker/pickers/Picker.java:6
What to do
- Split fat interfaces into focused role-interfaces so clients depend only on what they use.
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
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
P1 · CI/CD gates
P10 · Library API & versioning
- 2 public types in `com.henninghall.date_picker` are marked as implementation by their own namespace, folder or name: `DatePickerManagerImpl` (android/src/main/java/com/henninghall/date_picker/DatePickerManagerImpl.java:17, name ends in `Impl`), `DatePickerModuleImpl` (android/src/main/java/com/henninghall/date_picker/DatePickerModuleImpl.java:24, name ends in `Impl`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — android/src/main/java/com/henninghall/date_picker/DatePickerManagerImpl.java:17
- 1 public type in `com.henninghall.date_picker.ui` is marked as implementation by its own namespace, folder or name: `WheelChangeListenerImpl` (android/src/main/java/com/henninghall/date_picker/ui/WheelChangeListenerImpl.java:16, name ends in `Impl`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — android/src/main/java/com/henninghall/date_picker/ui/WheelChangeListenerImpl.java:16
What to do
- Hide `com.henninghall.date_picker` (`DatePickerManagerImpl`, `DatePickerModuleImpl`) (Java: package-private (no modifier), or leave its package out of `module-info` exports): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `com.henninghall.date_picker.ui` (`WheelChangeListenerImpl`) (Java: package-private (no modifier), or leave its package out of `module-info` exports): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
P2 · Observability
- No logging call was found in the 76 JavaScript/TypeScript, JVM production file(s) this check read across 2 module(s). Each was searched for its ecosystem's logging libraries (JVM: SLF4J, Log4j2, java.util.logging, Logback, kotlin-logging, scala-logging; JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
What to do
- Adopt SLF4J (with a Logback or Log4j2 JSON encoder) and log at meaningful points in the modules you run.
- Add a health-check endpoint (Spring Boot Actuator's /actuator/health, or a /health route) so orchestrators and load balancers can probe liveness/readiness.
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 11 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:5
- `package.json` 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`. — package.json:44
What to do
- Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
P6 · Release Hygiene
- 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.
R1 · Type Safety
R10 · Code Duplication
- src/index.js:44 · src/index.js:61 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/index.js:44
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R2 · Cyclomatic Complexity
R3 · Large Files
R4 · Test Coverage
- No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×10) — src/DatePickerAndroid.js:1, src/modal.js:1, src/index.js:1, …
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness
R6 · Tooling
R7 · Dead Code
- Unreachable from the 2 application, 4 tooling and 1 test entry point(s) detected in this repo. Gate removals on `yarn run typecheck` — an undetected custom entry would make these reachable.
- no import path from any entry point (2 application, 4 tooling, 1 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/type-definitions.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/fabric/RNDatePickerNativeComponent.ts
- no import path from any entry point (2 application, 4 tooling, 1 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×4) — src/fabric/NativeRNDatePicker.ts, src/fabric/RNDatePickerNativeComponent.js, src/fabric/NativeRNDatePicker.js, …
- Nothing imports this binding — it is safe to review for removal. (×2) — src/DatePickerAndroid.js:107, src/DatePickerIOS.js:9
What to do
- Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene
- Imported but not declared in any reachable package.json — installs work only by hoisting accident. — src/installationError.js:43
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
X16 · Unfloored truncation loop
X21 · Side-effecting pattern guard
X27 · Collection changed while being enumerated
X3 · Exception handling
- `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — android/src/main/java/com/henninghall/date_picker/Utils.java:54
What to do
- Swallowed exception (caught, then discarded)
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 80.5 | Strong | Solid. |
| Architecture | 98.3 | Exemplary | Strongest area. |
| Maturity | 45.4 | Weak — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 32.0 | Weak — gated by R4, P2, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 60.4 | Checked 4 of 10 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
Not evidenced — 4 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit 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 audit 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.
- C4 Data Retention — Not assessed: these retention 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 retention 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.
- C5 Data-Subject Rights — Not assessed: these data-subject rights 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 data-subject rights 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.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 72 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 Java imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's 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 TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Java code is a Spring, JSR-330 or CDI singleton bean. No class in this Kotlin code is a Spring, JSR-330 or CDI singleton bean. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the dev server (`npm run start`) exited before it served a page. Likely cause (the repository): package.json has no "start" script, so `npm run start` could not start the app. Last output: "npm error Missing script: "start" / npm error / npm error Did you mean one of these? / npm error npm star # Mark your favorite packages / npm error npm stars # View packages marked as favorites / npm error / npm error To see a list of scripts, run: / npm error npm run / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered. The cause is in the repository, not in our sandbox: package.json has no "start" script, so `npm run start` could not start the app. Nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- D11 Test Reliability — Test reliability not scored — polyglot repository, one half's runner produced no measurement
- 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.
- 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: 1 candidate(s) found and not reported.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .java, .kt source were not judged.
- D25 ADR Conformance — no ADRs to check
- 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) — 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.
- 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.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not measured — polyglot repository, one half has no runner
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (7 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
- M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks. 4 claim(s) of kinds M4 does not check were not checked (path 1, install 3); 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, JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage data present for 2 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.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- 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.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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.
- X12 Unreachable branch — X12 reached only 31% of this repository's production lines — java (6,079 lines), objectivec (627 lines), cpp (116 lines), c (113 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- 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 — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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 Java was read, and it logs through none that an assembled message defeats: java.util.logging's level methods, log4j 1, commons-logging, JBoss Logging and Flogger take one finished message (as log4net does in C#), or it makes no call through a named logger at all. Calls made through SLF4J or log4j 2 (`org.slf4j.Logger`, `org.apache.logging.log4j.Logger`, Lombok's `@Slf4j`) 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 — 189 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Test suite declares a test script but contains no test files: examples/Rn069/
- REDACTED
- Unlisted import 'expo-constants' src/installationError.js:43
Serious — 99 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No test reaches this file src/DatePickerAndroid.js:1
- No test reaches this file src/modal.js:1
- No test reaches this file src/index.js:1
- No test reaches this file src/propChecker.js:1
- No test reaches this file src/DatePickerIOS.js:1
- No test reaches this file src/installationError.js:1
- No test reaches this file src/modules.js:1
- No test reaches this file src/fabric/RNDatePickerNativeComponent.js:1
- No test reaches this file src/fabric/NativeRNDatePicker.js:1
- No test reaches this file src/type-definitions.js:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- AccessibilityNodeProviderImpl.performAction (cyclomatic 45) android/src/main/java/com/henninghall/date_picker/generated/NumberPicker.java:2500
- XxxComment android/src/main/java/com/henninghall/date_picker/generated/NumberPicker.java:2177
- AccessibilityNodeProviderImpl.performAction (cognitive 63) android/src/main/java/com/henninghall/date_picker/generated/NumberPicker.java:2500
- NumberPicker.onTouchEvent (cognitive 31) android/src/main/java/com/henninghall/date_picker/generated/NumberPicker.java:920
- NumberPicker.dispatchKeyEvent (cognitive 20) android/src/main/java/com/henninghall/date_picker/generated/NumberPicker.java:1004
- NumberPicker.tryComputeMaxWidth (cognitive 19) android/src/main/java/com/henninghall/date_picker/generated/NumberPicker.java:1322
- NumberPicker.onInterceptTouchEvent (cognitive 18) android/src/main/java/com/henninghall/date_picker/generated/NumberPicker.java:867
- InputTextFilter.filter (cognitive 18) android/src/main/java/com/henninghall/date_picker/generated/NumberPicker.java:2189
- NumberPicker.onDraw (cognitive 16) android/src/main/java/com/henninghall/date_picker/generated/NumberPicker.java:1614
- FunctionTooLong: colorToHex.colorNameToHex REDACTED:108
- Change coupling: DatePickerAndroid.js ↔ DatePickerIOS.js src/DatePickerAndroid.js:1
- REDACTED
- REDACTED
- Edited copy of a member (15 corresponding lines) android/src/main/java/com/henninghall/date_picker/wheels/DayWheel.java:48
- Edited copy of a member (11 corresponding lines) android/src/main/java/com/henninghall/date_picker/wheels/MonthWheel.java:17
- Edited copy of a member (17 corresponding lines) android/src/main/java/com/henninghall/date_picker/generated/NumberPicker.java:1451
- Duplicated block (9–13 lines × 3) android/src/main/java/com/henninghall/date_picker/generated/NumberPicker.java:2741
- Duplicated block (7 lines × 2) android/src/main/java/com/henninghall/date_picker/wheels/DayWheel.java:49
- Duplicated block (61 lines × 2) examples/Rn071/android/app/src/main/java/com/rn071/MainApplication.java:1
- No structured logging
- Duplicated block (11 lines × 2 locations) src/index.js:44
- Dead file (~44 LoC) src/fabric/RNDatePickerNativeComponent.ts
- Dead file (~13 LoC) src/fabric/NativeRNDatePicker.ts
- Dead file (~11 LoC) src/fabric/RNDatePickerNativeComponent.js
- Dead file (~4 LoC) src/fabric/NativeRNDatePicker.js
- Dead file (~0 LoC) src/type-definitions.js
- Swallowed exception (caught, then discarded) android/src/main/java/com/henninghall/date_picker/Utils.java:54
Minor — 66 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Orphaned file android/src/main/java/com/henninghall/date_picker/ui/Accessibility.java:1
- Orphaned file android/src/main/java/com/henninghall/date_picker/pickers/AndroidNative.java:1
- Orphaned file android/src/main/java/com/henninghall/date_picker/Formats.java:1
- Orphaned file android/src/main/java/com/henninghall/date_picker/DatePickerModuleImpl.java:1
- Orphaned file android/src/main/java/com/henninghall/date_picker/ui/Wheels.java:1
- Orphaned file android/src/main/java/com/henninghall/date_picker/State.java:1
- Orphaned file android/src/main/java/com/henninghall/date_picker/ui/WheelChangeListenerImpl.java:1
- Orphaned file android/src/main/java/com/henninghall/date_picker/wheels/DayWheel.java:1
- Orphaned file android/src/main/java/com/henninghall/date_picker/DerivedData.java:1
- Orphaned file android/src/main/java/com/henninghall/date_picker/Utils.java:1
- Orphaned file android/src/main/java/com/henninghall/date_picker/wheels/Wheel.java:1
- Orphaned file android/src/main/java/com/henninghall/date_picker/LocaleUtils.java:1
- Orphaned file android/src/main/java/com/henninghall/date_picker/PickerView.java:1
- Orphaned file android/src/oldarch/java/com/henninghall/date_picker/DatePickerManager.java:1
- Orphaned file android/src/main/java/com/henninghall/date_picker/ui/UIManager.java:1
- Orphaned file android/src/main/java/com/henninghall/date_picker/DatePickerPackage.java:1
- Orphaned file android/src/main/java/com/henninghall/date_picker/DatePickerManagerImpl.java:1
- Orphaned file android/build.gradle:1
- Implementation type on the public API android/src/main/java/com/henninghall/date_picker/DatePickerManagerImpl.java:17
- Implementation type on the public API android/src/main/java/com/henninghall/date_picker/ui/WheelChangeListenerImpl.java:16
- Fat interface: Picker (19 abstract methods) android/src/main/java/com/henninghall/date_picker/pickers/Picker.java:6
- Orphaned files with no living knowledge
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- No SAST REDACTED:5
- No dependency-update automation package.json:44
- No changelog
- Unused export 'default' src/DatePickerAndroid.js:107
- Unused export 'DatePickerIOS' src/DatePickerIOS.js:9
Minor — 7 finding(s)
- Outdated: Flipper
- Outdated: Flipper
- Outdated: Flipper
- Outdated: FlipperKit
- Outdated: FlipperKit
- Outdated: FlipperKit
- Outdated: OpenSSL-Universal
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-e3e9f02a976040b78f98d9a2b8e9c684/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=484" --report-format json --report-path /tmp/watchdog-gitleaks-e3e9f02a976040b78f98d9a2b8e9c684/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-e3e9f02a976040b78f98d9a2b8e9c684/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 . | 42 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 230 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |