Executive summary
virattt/ai-hedge-fund is rated At risk because critical security findings are open, all of them in the packages it uses. Its score is held back because we found no working pipeline that builds or tests changes to the code and no automated security scanning of the code, its secrets or its dependencies. It scores 56 out of 100, which the At risk rating leaves unchanged. We judged it as a template or a sample, against a lower bar.
Production Readiness, at 29, is the weakest lens and counts most in the score. The best first steps are adding an automated build and test pipeline and recording design decisions, each worth about 6 points. Raising Production Readiness to 52 would lift the score to about 67.
Seven known security holes in the packages the code depends on can be used by attackers. Updating the vulnerable packages would close this risk.
The product code is 10,930 lines, about €21,000 to rebuild.
If Production Readiness rose from 29 to 52, the lowest score rated Strong, the score would rise from 56 to about 67.
New since the last survey: 21 findings
- Cyclomatic Complexity · limits.apply_limits (cyclomatic 26) hedge_fund/risk/limits.py
- Cyclomatic Complexity · stages.execute_decision (cyclomatic 21) hedge_fund/pipeline/stages.py
- Cognitive Complexity · execution.build_orders (cognitive 22) hedge_fund/pipeline/execution.py
- Cognitive Complexity · FDClient._request (cognitive 19) hedge_fund/data/client.py
- Cognitive Complexity · limits._scale_book (cognitive 17) hedge_fund/risk/limits.py
- Cognitive Complexity · allocation.allocate (cognitive 16) hedge_fund/scorecard/allocation.py
- God Classes · FileTooLong: tui/report.py hedge_fund/tui/report.py
- Code Duplication · Edited copy of a member (17 corresponding lines) hedge_fund/tui/report.py
- Code Duplication · Edited copy of a member (60 corresponding lines) hedge_fund/tui/shared.py
- Code Duplication · Edited copies of one member (3 members, 8+ corresponding lines) hedge_fund/data/cached.py
- Code Duplication · Edited copy of a member (11 corresponding lines) hedge_fund/signals/__init__.py
- Code Duplication · Edited copy of a member (5 corresponding lines) hedge_fund/tui/paper.py
- Code Duplication · Edited copy of a member (6 corresponding lines) hedge_fund/data/client.py
- Code Duplication · Edited copy of a member (7 corresponding lines) hedge_fund/tui/funds.py
- Code Duplication · Edited copy of a member (7 corresponding lines) hedge_fund/data/cached.py
- Code Duplication · Edited copy of a member (8 corresponding lines) hedge_fund/brokers/models.py
- Code Duplication · Duplicated block (7–8 lines × 2) hedge_fund/tui/scorecard_view.py
- Code Duplication · Duplicated block (5 lines × 2) hedge_fund/tui/report.py
- Churn × Complexity Hotspots · Hotspot: hedge_fund/risk/limits.py hedge_fund/risk/limits.py
- Churn × Complexity Hotspots · Hotspot: hedge_fund/portfolio/construction.py hedge_fund/portfolio/construction.py
- Dependency Vulnerabilities · REDACTED
Fixed since the last survey: 5 findings
- Cognitive Complexity · report.session_overview (cognitive 23) hedge_fund/tui/report.py
- Code Duplication · Edited copy of a member (17 corresponding lines) hedge_fund/tui/report.py
- Code Duplication · Duplicated block (7 lines × 3) hedge_fund/tui/funds.py
- Code Duplication · Duplicated block (5 lines × 2) hedge_fund/tui/scorecard_view.py
- Churn × Complexity Hotspots · Hotspot: hedge_fund/tui/shared.py hedge_fund/tui/shared.py
Rebuild cost: about €21,000 · Estimate
| Cost to rebuild | €7,000 to €35,000, for 117 to 371 hours of work, about 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 56. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 10,930 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 backtesting.fund | 2 brokers.costs | 3 brokers.models | 4 data.models | 5 data.screener | 6 features.snapshot | 7 models | 8 pipeline.session | 9 risk.exposures | 10 risk.limits | 11 scorecard.models | 12 hedge_fund | 13 brokers.protocol | 14 brokers.sim | 15 data.client | 16 data.protocol | 17 fund.spec | 18 paper.ledger | 19 tui.report | 20 backtesting | 21 brokers.paper | 22 data | 23 data.cached | 24 features | 25 paper.deployed | 26 pipeline.clock | 27 pipeline.models | 28 portfolio | 29 risk | 30 signals.base | 31 tui.paper_view | 32 paper | 33 paper.tick | 34 pipeline | 35 scorecard | 36 signals.llm_agent | 37 signals.pead | 38 tui | 39 tui.backtest | 40 tui.paper |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 backtesting.fund | ||||||||||||||||||||||||||||||||||||||||
| 2 brokers.costs | ||||||||||||||||||||||||||||||||||||||||
| 3 brokers.models | ||||||||||||||||||||||||||||||||||||||||
| 4 data.models | ||||||||||||||||||||||||||||||||||||||||
| 5 data.screener | ||||||||||||||||||||||||||||||||||||||||
| 6 features.snapshot | ||||||||||||||||||||||||||||||||||||||||
| 7 models | ||||||||||||||||||||||||||||||||||||||||
| 8 pipeline.session | ||||||||||||||||||||||||||||||||||||||||
| 9 risk.exposures | ||||||||||||||||||||||||||||||||||||||||
| 10 risk.limits | ||||||||||||||||||||||||||||||||||||||||
| 11 scorecard.models | ||||||||||||||||||||||||||||||||||||||||
| 12 hedge_fund | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 13 brokers.protocol | 2 | |||||||||||||||||||||||||||||||||||||||
| 14 brokers.sim | 2 | |||||||||||||||||||||||||||||||||||||||
| 15 data.client | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 data.protocol | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 fund.spec | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 18 paper.ledger | 2 | |||||||||||||||||||||||||||||||||||||||
| 19 tui.report | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 backtesting | 4 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 21 brokers.paper | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 22 data | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 23 data.cached | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 features | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 25 paper.deployed | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 pipeline.clock | 4 | 2 | ||||||||||||||||||||||||||||||||||||||
| 27 pipeline.models | 2 | |||||||||||||||||||||||||||||||||||||||
| 28 portfolio | 1 | |||||||||||||||||||||||||||||||||||||||
| 29 risk | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 30 signals.base | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 31 tui.paper_view | 1 | |||||||||||||||||||||||||||||||||||||||
| 32 paper | 2 | 2 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 33 paper.tick | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 34 pipeline | 2 | 2 | 3 | 5 | 1 | 2 | ||||||||||||||||||||||||||||||||||
| 35 scorecard | 1 | 1 | 2 | 2 | ||||||||||||||||||||||||||||||||||||
| 36 signals.llm_agent | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 37 signals.pead | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 38 tui | 1 | 1 | 2 | 1 | 1 | 5 | 1 | 4 | 1 | |||||||||||||||||||||||||||||||
| 39 tui.backtest | 4 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 40 tui.paper | 2 | 1 | 2 | 1 |
12→8 hedge_fund uses pipeline.session✕
- Connections
- 1 pair of types, where a type in hedge_fund uses a type in pipeline.session.
- The types involved
hedge_fund.run→hedge_fund.pipeline.session.SessionRecord
- Direction
- hedge_fund uses pipeline.session, so a change to pipeline.session can break hedge_fund, while a change to hedge_fund can't break pipeline.session.
- Position
- Below the diagonal: hedge_fund uses a module listed above it, which is the healthy direction.
12→11 hedge_fund uses scorecard.models✕
- Connections
- 1 pair of types, where a type in hedge_fund uses a type in scorecard.models.
- The types involved
hedge_fund.scorecard→hedge_fund.scorecard.models.Scorecard
- Direction
- hedge_fund uses scorecard.models, so a change to scorecard.models can break hedge_fund, while a change to hedge_fund can't break scorecard.models.
- Position
- Below the diagonal: hedge_fund uses a module listed above it, which is the healthy direction.
13→3 brokers.protocol uses brokers.models✕
- Connections
- 2 pairs of types, where a type in brokers.protocol uses a type in brokers.models.
- The types involved
hedge_fund.brokers.protocol.Broker→hedge_fund.brokers.models.Fillhedge_fund.brokers.protocol.Broker→hedge_fund.brokers.models.Order
- Direction
- brokers.protocol uses brokers.models, so a change to brokers.models can break brokers.protocol, while a change to brokers.protocol can't break brokers.models.
- Position
- Below the diagonal: brokers.protocol uses a module listed above it, which is the healthy direction.
14→3 brokers.sim uses brokers.models✕
- Connections
- 2 pairs of types, where a type in brokers.sim uses a type in brokers.models.
- The types involved
hedge_fund.brokers.sim.SimBroker→hedge_fund.brokers.models.Fillhedge_fund.brokers.sim.SimBroker→hedge_fund.brokers.models.Order
- Direction
- brokers.sim uses brokers.models, so a change to brokers.models can break brokers.sim, while a change to brokers.sim can't break brokers.models.
- Position
- Below the diagonal: brokers.sim uses a module listed above it, which is the healthy direction.
15→5 data.client uses data.screener✕
- Connections
- 1 pair of types, where a type in data.client uses a type in data.screener.
- The types involved
hedge_fund.data.client.FDClient→hedge_fund.data.screener.ScreenerFields
- Direction
- data.client uses data.screener, so a change to data.screener can break data.client, while a change to data.client can't break data.screener.
- Position
- Below the diagonal: data.client uses a module listed above it, which is the healthy direction.
16→5 data.protocol uses data.screener✕
- Connections
- 1 pair of types, where a type in data.protocol uses a type in data.screener.
- The types involved
hedge_fund.data.protocol.DataClient→hedge_fund.data.screener.ScreenerFields
- Direction
- data.protocol uses data.screener, so a change to data.screener can break data.protocol, while a change to data.protocol can't break data.screener.
- Position
- Below the diagonal: data.protocol uses a module listed above it, which is the healthy direction.
17→2 fund.spec uses brokers.costs✕
- Connections
- 1 pair of types, where a type in fund.spec uses a type in brokers.costs.
- The types involved
hedge_fund.fund.spec.FundSpec→hedge_fund.brokers.costs.TradingCosts
- Direction
- fund.spec uses brokers.costs, so a change to brokers.costs can break fund.spec, while a change to fund.spec can't break brokers.costs.
- Position
- Below the diagonal: fund.spec uses a module listed above it, which is the healthy direction.
17→10 fund.spec uses risk.limits✕
- Connections
- 1 pair of types, where a type in fund.spec uses a type in risk.limits.
- The types involved
hedge_fund.fund.spec.FundSpec→hedge_fund.risk.limits.RiskLimits
- Direction
- fund.spec uses risk.limits, so a change to risk.limits can break fund.spec, while a change to fund.spec can't break risk.limits.
- Position
- Below the diagonal: fund.spec uses a module listed above it, which is the healthy direction.
18→8 paper.ledger uses pipeline.session✕
- Connections
- 2 pairs of types, where a type in paper.ledger uses a type in pipeline.session.
- The types involved
hedge_fund.paper.ledger.Ledger→hedge_fund.pipeline.session.FundStatehedge_fund.paper.ledger.Ledger→hedge_fund.pipeline.session.SessionRecord
- Direction
- paper.ledger uses pipeline.session, so a change to pipeline.session can break paper.ledger, while a change to paper.ledger can't break pipeline.session.
- Position
- Below the diagonal: paper.ledger uses a module listed above it, which is the healthy direction.
19→7 tui.report uses models✕
- Connections
- 1 pair of types, where a type in tui.report uses a type in models.
- The types involved
hedge_fund.tui.report.Desk→hedge_fund.models.Signal
- Direction
- tui.report uses models, so a change to models can break tui.report, while a change to tui.report can't break models.
- Position
- Below the diagonal: tui.report uses a module listed above it, which is the healthy direction.
20→1 backtesting uses backtesting.fund✕
- Connections
- 4 pairs of types, where a type in backtesting uses a type in backtesting.fund.
- The types involved
hedge_fund.backtesting.fund→hedge_fund.backtesting.fund.FundBacktestMetricshedge_fund.backtesting.fund→hedge_fund.backtesting.fund.FundBacktestResulthedge_fund.backtesting.fund→hedge_fund.backtesting.fund.ReplaySchedulehedge_fund.backtesting.research→hedge_fund.backtesting.fund.FundBacktestResult
- Direction
- backtesting uses backtesting.fund, so a change to backtesting.fund can break backtesting, while a change to backtesting can't break backtesting.fund.
- Position
- Below the diagonal: backtesting uses a module listed above it, which is the healthy direction.
20→16 backtesting uses data.protocol✕
- Connections
- 1 pair of types, where a type in backtesting uses a type in data.protocol.
- The types involved
hedge_fund.backtesting.fund→hedge_fund.data.protocol.DataClient
- Direction
- backtesting uses data.protocol, so a change to data.protocol can break backtesting, while a change to backtesting can't break data.protocol.
- Position
- Below the diagonal: backtesting uses a module listed above it, which is the healthy direction.
20→17 backtesting uses fund.spec✕
- Connections
- 2 pairs of types, where a type in backtesting uses a type in fund.spec.
- The types involved
hedge_fund.backtesting.fund→hedge_fund.fund.spec.Fundhedge_fund.backtesting.fund→hedge_fund.fund.spec.FundSpec
- Direction
- backtesting uses fund.spec, so a change to fund.spec can break backtesting, while a change to backtesting can't break fund.spec.
- Position
- Below the diagonal: backtesting uses a module listed above it, which is the healthy direction.
21→3 brokers.paper uses brokers.models✕
- Connections
- 2 pairs of types, where a type in brokers.paper uses a type in brokers.models.
- The types involved
hedge_fund.brokers.paper.PaperBroker→hedge_fund.brokers.models.Fillhedge_fund.brokers.paper.PaperBroker→hedge_fund.brokers.models.Order
- Direction
- brokers.paper uses brokers.models, so a change to brokers.models can break brokers.paper, while a change to brokers.paper can't break brokers.models.
- Position
- Below the diagonal: brokers.paper uses a module listed above it, which is the healthy direction.
21→14 brokers.paper uses brokers.sim✕
- Connections
- 1 pair of types, where a type in brokers.paper uses a type in brokers.sim.
- The types involved
hedge_fund.brokers.paper.PaperBroker→hedge_fund.brokers.sim.SimBroker
- Direction
- brokers.paper uses brokers.sim, so a change to brokers.sim can break brokers.paper, while a change to brokers.paper can't break brokers.sim.
- Position
- Below the diagonal: brokers.paper uses a module listed above it, which is the healthy direction.
22→16 data uses data.protocol✕
- Connections
- 1 pair of types, where a type in data uses a type in data.protocol.
- The types involved
hedge_fund.data.sessions→hedge_fund.data.protocol.DataClient
- Direction
- data uses data.protocol, so a change to data.protocol can break data, while a change to data can't break data.protocol.
- Position
- Below the diagonal: data uses a module listed above it, which is the healthy direction.
22→17 data uses fund.spec✕
- Connections
- 1 pair of types, where a type in data uses a type in fund.spec.
- The types involved
hedge_fund.data.bars→hedge_fund.fund.spec.TradingWindow
- Direction
- data uses fund.spec, so a change to fund.spec can break data, while a change to data can't break fund.spec.
- Position
- Below the diagonal: data uses a module listed above it, which is the healthy direction.
23→16 data.cached uses data.protocol✕
- Connections
- 1 pair of types, where a type in data.cached uses a type in data.protocol.
- The types involved
hedge_fund.data.cached.CachedDataClient→hedge_fund.data.protocol.DataClient
- Direction
- data.cached uses data.protocol, so a change to data.protocol can break data.cached, while a change to data.cached can't break data.protocol.
- Position
- Below the diagonal: data.cached uses a module listed above it, which is the healthy direction.
24→6 features uses features.snapshot✕
- Connections
- 1 pair of types, where a type in features uses a type in features.snapshot.
- The types involved
hedge_fund.features.snapshot→hedge_fund.features.snapshot.FundamentalsSnapshot
- Direction
- features uses features.snapshot, so a change to features.snapshot can break features, while a change to features can't break features.snapshot.
- Position
- Below the diagonal: features uses a module listed above it, which is the healthy direction.
24→16 features uses data.protocol✕
- Connections
- 2 pairs of types, where a type in features uses a type in data.protocol.
- The types involved
hedge_fund.features.intraday→hedge_fund.data.protocol.DataClienthedge_fund.features.snapshot→hedge_fund.data.protocol.DataClient
- Direction
- features uses data.protocol, so a change to data.protocol can break features, while a change to features can't break data.protocol.
- Position
- Below the diagonal: features uses a module listed above it, which is the healthy direction.
25→17 paper.deployed uses fund.spec✕
- Connections
- 1 pair of types, where a type in paper.deployed uses a type in fund.spec.
- The types involved
hedge_fund.paper.deployed.DeployedFund→hedge_fund.fund.spec.FundSpec
- Direction
- paper.deployed uses fund.spec, so a change to fund.spec can break paper.deployed, while a change to paper.deployed can't break fund.spec.
- Position
- Below the diagonal: paper.deployed uses a module listed above it, which is the healthy direction.
26→16 pipeline.clock uses data.protocol✕
- Connections
- 4 pairs of types, where a type in pipeline.clock uses a type in data.protocol.
- The types involved
hedge_fund.pipeline.clock.BarClock→hedge_fund.data.protocol.DataClienthedge_fund.pipeline.clock.DailyClock→hedge_fund.data.protocol.DataClienthedge_fund.pipeline.clock.LiveClock→hedge_fund.data.protocol.DataClienthedge_fund.pipeline.clock.PinnedQuotes→hedge_fund.data.protocol.DataClient
- Direction
- pipeline.clock uses data.protocol, so a change to data.protocol can break pipeline.clock, while a change to pipeline.clock can't break data.protocol.
- Position
- Below the diagonal: pipeline.clock uses a module listed above it, which is the healthy direction.
26→17 pipeline.clock uses fund.spec✕
- Connections
- 2 pairs of types, where a type in pipeline.clock uses a type in fund.spec.
- The types involved
hedge_fund.pipeline.clock.BarClock→hedge_fund.fund.spec.TradingWindowhedge_fund.pipeline.clock.LiveClock→hedge_fund.fund.spec.TradingWindow
- Direction
- pipeline.clock uses fund.spec, so a change to fund.spec can break pipeline.clock, while a change to pipeline.clock can't break fund.spec.
- Position
- Below the diagonal: pipeline.clock uses a module listed above it, which is the healthy direction.
27→17 pipeline.models uses fund.spec✕
- Connections
- 2 pairs of types, where a type in pipeline.models uses a type in fund.spec.
- The types involved
hedge_fund.pipeline.models.CycleRecord→hedge_fund.fund.spec.FundSpechedge_fund.pipeline.models.DecisionRecord→hedge_fund.fund.spec.FundSpec
- Direction
- pipeline.models uses fund.spec, so a change to fund.spec can break pipeline.models, while a change to pipeline.models can't break fund.spec.
- Position
- Below the diagonal: pipeline.models uses a module listed above it, which is the healthy direction.
28→17 portfolio uses fund.spec✕
- Connections
- 1 pair of types, where a type in portfolio uses a type in fund.spec.
- The types involved
hedge_fund.portfolio.validation→hedge_fund.fund.spec.FundSpec
- Direction
- portfolio uses fund.spec, so a change to fund.spec can break portfolio, while a change to portfolio can't break fund.spec.
- Position
- Below the diagonal: portfolio uses a module listed above it, which is the healthy direction.
29→9 risk uses risk.exposures✕
- Connections
- 1 pair of types, where a type in risk uses a type in risk.exposures.
- The types involved
hedge_fund.risk.exposures→hedge_fund.risk.exposures.Exposures
- Direction
- risk uses risk.exposures, so a change to risk.exposures can break risk, while a change to risk can't break risk.exposures.
- Position
- Below the diagonal: risk uses a module listed above it, which is the healthy direction.
29→10 risk uses risk.limits✕
- Connections
- 2 pairs of types, where a type in risk uses a type in risk.limits.
- The types involved
hedge_fund.risk.limits→hedge_fund.risk.limits.RiskLimitshedge_fund.risk.limits→hedge_fund.risk.limits.RiskResult
- Direction
- risk uses risk.limits, so a change to risk.limits can break risk, while a change to risk can't break risk.limits.
- Position
- Below the diagonal: risk uses a module listed above it, which is the healthy direction.
29→16 risk uses data.protocol✕
- Connections
- 1 pair of types, where a type in risk uses a type in data.protocol.
- The types involved
hedge_fund.risk.exposures→hedge_fund.data.protocol.DataClient
- Direction
- risk uses data.protocol, so a change to data.protocol can break risk, while a change to risk can't break data.protocol.
- Position
- Below the diagonal: risk uses a module listed above it, which is the healthy direction.
30→7 signals.base uses models✕
- Connections
- 1 pair of types, where a type in signals.base uses a type in models.
- The types involved
hedge_fund.signals.base.AlphaModel→hedge_fund.models.Signal
- Direction
- signals.base uses models, so a change to models can break signals.base, while a change to signals.base can't break models.
- Position
- Below the diagonal: signals.base uses a module listed above it, which is the healthy direction.
30→16 signals.base uses data.protocol✕
- Connections
- 1 pair of types, where a type in signals.base uses a type in data.protocol.
- The types involved
hedge_fund.signals.base.AlphaModel→hedge_fund.data.protocol.DataClient
- Direction
- signals.base uses data.protocol, so a change to data.protocol can break signals.base, while a change to signals.base can't break data.protocol.
- Position
- Below the diagonal: signals.base uses a module listed above it, which is the healthy direction.
31→17 tui.paper_view uses fund.spec✕
- Connections
- 1 pair of types, where a type in tui.paper_view uses a type in fund.spec.
- The types involved
hedge_fund.tui.paper_view.PaperSnapshot→hedge_fund.fund.spec.FundSpec
- Direction
- tui.paper_view uses fund.spec, so a change to fund.spec can break tui.paper_view, while a change to tui.paper_view can't break fund.spec.
- Position
- Below the diagonal: tui.paper_view uses a module listed above it, which is the healthy direction.
32→8 paper uses pipeline.session✕
- Connections
- 2 pairs of types, where a type in paper uses a type in pipeline.session.
- The types involved
hedge_fund.paper.tick→hedge_fund.pipeline.session.FundStatehedge_fund.paper.tick→hedge_fund.pipeline.session.SessionRecord
- Direction
- paper uses pipeline.session, so a change to pipeline.session can break paper, while a change to paper can't break pipeline.session.
- Position
- Below the diagonal: paper uses a module listed above it, which is the healthy direction.
32→16 paper uses data.protocol✕
- Connections
- 2 pairs of types, where a type in paper uses a type in data.protocol.
- The types involved
hedge_fund.paper.runner→hedge_fund.data.protocol.DataClienthedge_fund.paper.tick→hedge_fund.data.protocol.DataClient
- Direction
- paper uses data.protocol, so a change to data.protocol can break paper, while a change to paper can't break data.protocol.
- Position
- Below the diagonal: paper uses a module listed above it, which is the healthy direction.
32→17 paper uses fund.spec✕
- Connections
- 2 pairs of types, where a type in paper uses a type in fund.spec.
- The types involved
hedge_fund.paper.deployed→hedge_fund.fund.spec.FundSpechedge_fund.paper.tick→hedge_fund.fund.spec.FundSpec
- Direction
- paper uses fund.spec, so a change to fund.spec can break paper, while a change to paper can't break fund.spec.
- Position
- Below the diagonal: paper uses a module listed above it, which is the healthy direction.
32→18 paper uses paper.ledger✕
- Connections
- 1 pair of types, where a type in paper uses a type in paper.ledger.
- The types involved
hedge_fund.paper.tick→hedge_fund.paper.ledger.Ledger
- Direction
- paper uses paper.ledger, so a change to paper.ledger can break paper, while a change to paper can't break paper.ledger.
- Position
- Below the diagonal: paper uses a module listed above it, which is the healthy direction.
32→25 paper uses paper.deployed✕
- Connections
- 1 pair of types, where a type in paper uses a type in paper.deployed.
- The types involved
hedge_fund.paper.deployed→hedge_fund.paper.deployed.DeployedFund
- Direction
- paper uses paper.deployed, so a change to paper.deployed can break paper, while a change to paper can't break paper.deployed.
- Position
- Below the diagonal: paper uses a module listed above it, which is the healthy direction.
33→8 paper.tick uses pipeline.session✕
- Connections
- 1 pair of types, where a type in paper.tick uses a type in pipeline.session.
- The types involved
hedge_fund.paper.tick.RecordedClock→hedge_fund.pipeline.session.SessionRecord
- Direction
- paper.tick uses pipeline.session, so a change to pipeline.session can break paper.tick, while a change to paper.tick can't break pipeline.session.
- Position
- Below the diagonal: paper.tick uses a module listed above it, which is the healthy direction.
33→17 paper.tick uses fund.spec✕
- Connections
- 1 pair of types, where a type in paper.tick uses a type in fund.spec.
- The types involved
hedge_fund.paper.tick.RecordedClock→hedge_fund.fund.spec.TradingWindow
- Direction
- paper.tick uses fund.spec, so a change to fund.spec can break paper.tick, while a change to paper.tick can't break fund.spec.
- Position
- Below the diagonal: paper.tick uses a module listed above it, which is the healthy direction.
33→26 paper.tick uses pipeline.clock✕
- Connections
- 1 pair of types, where a type in paper.tick uses a type in pipeline.clock.
- The types involved
hedge_fund.paper.tick.RecordedClock→hedge_fund.pipeline.clock.Marked
- Direction
- paper.tick uses pipeline.clock, so a change to pipeline.clock can break paper.tick, while a change to paper.tick can't break pipeline.clock.
- Position
- Below the diagonal: paper.tick uses a module listed above it, which is the healthy direction.
34→8 pipeline uses pipeline.session✕
- Connections
- 2 pairs of types, where a type in pipeline uses a type in pipeline.session.
- The types involved
hedge_fund.pipeline.session→hedge_fund.pipeline.session.FundStatehedge_fund.pipeline.session→hedge_fund.pipeline.session.SessionRecord
- Direction
- pipeline uses pipeline.session, so a change to pipeline.session can break pipeline, while a change to pipeline can't break pipeline.session.
- Position
- Below the diagonal: pipeline uses a module listed above it, which is the healthy direction.
34→13 pipeline uses brokers.protocol✕
- Connections
- 2 pairs of types, where a type in pipeline uses a type in brokers.protocol.
- The types involved
hedge_fund.pipeline.session→hedge_fund.brokers.protocol.Brokerhedge_fund.pipeline.stages→hedge_fund.brokers.protocol.Broker
- Direction
- pipeline uses brokers.protocol, so a change to brokers.protocol can break pipeline, while a change to pipeline can't break brokers.protocol.
- Position
- Below the diagonal: pipeline uses a module listed above it, which is the healthy direction.
34→16 pipeline uses data.protocol✕
- Connections
- 3 pairs of types, where a type in pipeline uses a type in data.protocol.
- The types involved
hedge_fund.pipeline.clock→hedge_fund.data.protocol.DataClienthedge_fund.pipeline.session→hedge_fund.data.protocol.DataClienthedge_fund.pipeline.stages→hedge_fund.data.protocol.DataClient
- Direction
- pipeline uses data.protocol, so a change to data.protocol can break pipeline, while a change to pipeline can't break data.protocol.
- Position
- Below the diagonal: pipeline uses a module listed above it, which is the healthy direction.
34→17 pipeline uses fund.spec✕
- Connections
- 5 pairs of types, where a type in pipeline uses a type in fund.spec.
- The types involved
hedge_fund.pipeline.clock→hedge_fund.fund.spec.FundSpechedge_fund.pipeline.session→hedge_fund.fund.spec.Fundhedge_fund.pipeline.session→hedge_fund.fund.spec.FundSpechedge_fund.pipeline.stages→hedge_fund.fund.spec.Fundhedge_fund.pipeline.stages→hedge_fund.fund.spec.FundSpec
- Direction
- pipeline uses fund.spec, so a change to fund.spec can break pipeline, while a change to pipeline can't break fund.spec.
- Position
- Below the diagonal: pipeline uses a module listed above it, which is the healthy direction.
34→26 pipeline uses pipeline.clock✕
- Connections
- 1 pair of types, where a type in pipeline uses a type in pipeline.clock.
- The types involved
hedge_fund.pipeline.clock→hedge_fund.pipeline.clock.Clock
- Direction
- pipeline uses pipeline.clock, so a change to pipeline.clock can break pipeline, while a change to pipeline can't break pipeline.clock.
- Position
- Below the diagonal: pipeline uses a module listed above it, which is the healthy direction.
34→27 pipeline uses pipeline.models✕
- Connections
- 2 pairs of types, where a type in pipeline uses a type in pipeline.models.
- The types involved
hedge_fund.pipeline.stages→hedge_fund.pipeline.models.CycleRecordhedge_fund.pipeline.stages→hedge_fund.pipeline.models.DecisionRecord
- Direction
- pipeline uses pipeline.models, so a change to pipeline.models can break pipeline, while a change to pipeline can't break pipeline.models.
- Position
- Below the diagonal: pipeline uses a module listed above it, which is the healthy direction.
35→8 scorecard uses pipeline.session✕
- Connections
- 1 pair of types, where a type in scorecard uses a type in pipeline.session.
- The types involved
hedge_fund.scorecard.allocation→hedge_fund.pipeline.session.FundState
- Direction
- scorecard uses pipeline.session, so a change to pipeline.session can break scorecard, while a change to scorecard can't break pipeline.session.
- Position
- Below the diagonal: scorecard uses a module listed above it, which is the healthy direction.
35→11 scorecard uses scorecard.models✕
- Connections
- 1 pair of types, where a type in scorecard uses a type in scorecard.models.
- The types involved
hedge_fund.scorecard.analysts→hedge_fund.scorecard.models.AnalystScore
- Direction
- scorecard uses scorecard.models, so a change to scorecard.models can break scorecard, while a change to scorecard can't break scorecard.models.
- Position
- Below the diagonal: scorecard uses a module listed above it, which is the healthy direction.
35→17 scorecard uses fund.spec✕
- Connections
- 2 pairs of types, where a type in scorecard uses a type in fund.spec.
- The types involved
hedge_fund.scorecard.allocation→hedge_fund.fund.spec.AllocationPolicyhedge_fund.scorecard.allocation→hedge_fund.fund.spec.FundSpec
- Direction
- scorecard uses fund.spec, so a change to fund.spec can break scorecard, while a change to scorecard can't break fund.spec.
- Position
- Below the diagonal: scorecard uses a module listed above it, which is the healthy direction.
35→27 scorecard uses pipeline.models✕
- Connections
- 2 pairs of types, where a type in scorecard uses a type in pipeline.models.
- The types involved
hedge_fund.scorecard.allocation→hedge_fund.pipeline.models.Allocatedhedge_fund.scorecard.allocation→hedge_fund.pipeline.models.AllocationRecord
- Direction
- scorecard uses pipeline.models, so a change to pipeline.models can break scorecard, while a change to scorecard can't break pipeline.models.
- Position
- Below the diagonal: scorecard uses a module listed above it, which is the healthy direction.
36→6 signals.llm_agent uses features.snapshot✕
- Connections
- 1 pair of types, where a type in signals.llm_agent uses a type in features.snapshot.
- The types involved
hedge_fund.signals.llm_agent.LLMAgent→hedge_fund.features.snapshot.FundamentalsSnapshot
- Direction
- signals.llm_agent uses features.snapshot, so a change to features.snapshot can break signals.llm_agent, while a change to signals.llm_agent can't break features.snapshot.
- Position
- Below the diagonal: signals.llm_agent uses a module listed above it, which is the healthy direction.
36→7 signals.llm_agent uses models✕
- Connections
- 1 pair of types, where a type in signals.llm_agent uses a type in models.
- The types involved
hedge_fund.signals.llm_agent.LLMAgent→hedge_fund.models.Signal
- Direction
- signals.llm_agent uses models, so a change to models can break signals.llm_agent, while a change to signals.llm_agent can't break models.
- Position
- Below the diagonal: signals.llm_agent uses a module listed above it, which is the healthy direction.
36→16 signals.llm_agent uses data.protocol✕
- Connections
- 1 pair of types, where a type in signals.llm_agent uses a type in data.protocol.
- The types involved
hedge_fund.signals.llm_agent.LLMAgent→hedge_fund.data.protocol.DataClient
- Direction
- signals.llm_agent uses data.protocol, so a change to data.protocol can break signals.llm_agent, while a change to signals.llm_agent can't break data.protocol.
- Position
- Below the diagonal: signals.llm_agent uses a module listed above it, which is the healthy direction.
36→30 signals.llm_agent uses signals.base✕
- Connections
- 1 pair of types, where a type in signals.llm_agent uses a type in signals.base.
- The types involved
hedge_fund.signals.llm_agent.LLMAgent→hedge_fund.signals.base.AlphaModel
- Direction
- signals.llm_agent uses signals.base, so a change to signals.base can break signals.llm_agent, while a change to signals.llm_agent can't break signals.base.
- Position
- Below the diagonal: signals.llm_agent uses a module listed above it, which is the healthy direction.
37→7 signals.pead uses models✕
- Connections
- 1 pair of types, where a type in signals.pead uses a type in models.
- The types involved
hedge_fund.signals.pead.PEADModel→hedge_fund.models.Signal
- Direction
- signals.pead uses models, so a change to models can break signals.pead, while a change to signals.pead can't break models.
- Position
- Below the diagonal: signals.pead uses a module listed above it, which is the healthy direction.
37→16 signals.pead uses data.protocol✕
- Connections
- 1 pair of types, where a type in signals.pead uses a type in data.protocol.
- The types involved
hedge_fund.signals.pead.PEADModel→hedge_fund.data.protocol.DataClient
- Direction
- signals.pead uses data.protocol, so a change to data.protocol can break signals.pead, while a change to signals.pead can't break data.protocol.
- Position
- Below the diagonal: signals.pead uses a module listed above it, which is the healthy direction.
37→30 signals.pead uses signals.base✕
- Connections
- 1 pair of types, where a type in signals.pead uses a type in signals.base.
- The types involved
hedge_fund.signals.pead.PEADModel→hedge_fund.signals.base.QuantModel
- Direction
- signals.pead uses signals.base, so a change to signals.base can break signals.pead, while a change to signals.pead can't break signals.base.
- Position
- Below the diagonal: signals.pead uses a module listed above it, which is the healthy direction.
38→4 tui uses data.models✕
- Connections
- 1 pair of types, where a type in tui uses a type in data.models.
- The types involved
hedge_fund.tui.paper_view→hedge_fund.data.models.PriceSnapshot
- Direction
- tui uses data.models, so a change to data.models can break tui, while a change to tui can't break data.models.
- Position
- Below the diagonal: tui uses a module listed above it, which is the healthy direction.
38→7 tui uses models✕
- Connections
- 1 pair of types, where a type in tui uses a type in models.
- The types involved
hedge_fund.tui.report→hedge_fund.models.Signal
- Direction
- tui uses models, so a change to models can break tui, while a change to tui can't break models.
- Position
- Below the diagonal: tui uses a module listed above it, which is the healthy direction.
38→8 tui uses pipeline.session✕
- Connections
- 2 pairs of types, where a type in tui uses a type in pipeline.session.
- The types involved
hedge_fund.tui.paper_view→hedge_fund.pipeline.session.FundStatehedge_fund.tui.report→hedge_fund.pipeline.session.SessionRecord
- Direction
- tui uses pipeline.session, so a change to pipeline.session can break tui, while a change to tui can't break pipeline.session.
- Position
- Below the diagonal: tui uses a module listed above it, which is the healthy direction.
38→9 tui uses risk.exposures✕
- Connections
- 1 pair of types, where a type in tui uses a type in risk.exposures.
- The types involved
hedge_fund.tui.report→hedge_fund.risk.exposures.Exposures
- Direction
- tui uses risk.exposures, so a change to risk.exposures can break tui, while a change to tui can't break risk.exposures.
- Position
- Below the diagonal: tui uses a module listed above it, which is the healthy direction.
38→11 tui uses scorecard.models✕
- Connections
- 1 pair of types, where a type in tui uses a type in scorecard.models.
- The types involved
hedge_fund.tui.scorecard_view→hedge_fund.scorecard.models.Scorecard
- Direction
- tui uses scorecard.models, so a change to scorecard.models can break tui, while a change to tui can't break scorecard.models.
- Position
- Below the diagonal: tui uses a module listed above it, which is the healthy direction.
38→17 tui uses fund.spec✕
- Connections
- 5 pairs of types, where a type in tui uses a type in fund.spec.
- The types involved
hedge_fund.tui.builder→hedge_fund.fund.spec.TradingWindowhedge_fund.tui.funds→hedge_fund.fund.spec.FundSpechedge_fund.tui.paper_view→hedge_fund.fund.spec.FundSpechedge_fund.tui.shared→hedge_fund.fund.spec.FundSpechedge_fund.tui.shared→hedge_fund.fund.spec.StrategySpec
- Direction
- tui uses fund.spec, so a change to fund.spec can break tui, while a change to tui can't break fund.spec.
- Position
- Below the diagonal: tui uses a module listed above it, which is the healthy direction.
38→19 tui uses tui.report✕
- Connections
- 1 pair of types, where a type in tui uses a type in tui.report.
- The types involved
hedge_fund.tui.report→hedge_fund.tui.report.Desk
- Direction
- tui uses tui.report, so a change to tui.report can break tui, while a change to tui can't break tui.report.
- Position
- Below the diagonal: tui uses a module listed above it, which is the healthy direction.
38→27 tui uses pipeline.models✕
- Connections
- 4 pairs of types, where a type in tui uses a type in pipeline.models.
- The types involved
hedge_fund.tui.report→hedge_fund.pipeline.models.Allocatedhedge_fund.tui.report→hedge_fund.pipeline.models.AllocationRecordhedge_fund.tui.report→hedge_fund.pipeline.models.CycleRecordhedge_fund.tui.report→hedge_fund.pipeline.models.DecisionRecord
- Direction
- tui uses pipeline.models, so a change to pipeline.models can break tui, while a change to tui can't break pipeline.models.
- Position
- Below the diagonal: tui uses a module listed above it, which is the healthy direction.
38→31 tui uses tui.paper_view✕
- Connections
- 1 pair of types, where a type in tui uses a type in tui.paper_view.
- The types involved
hedge_fund.tui.paper_view→hedge_fund.tui.paper_view.PaperSnapshot
- Direction
- tui uses tui.paper_view, so a change to tui.paper_view can break tui, while a change to tui can't break tui.paper_view.
- Position
- Below the diagonal: tui uses a module listed above it, which is the healthy direction.
39→1 tui.backtest uses backtesting.fund✕
- Connections
- 4 pairs of types, where a type in tui.backtest uses a type in backtesting.fund.
- The types involved
hedge_fund.tui.backtest.BacktestDecisionsScreen→hedge_fund.backtesting.fund.FundBacktestResulthedge_fund.tui.backtest.BacktestScorecardScreen→hedge_fund.backtesting.fund.FundBacktestResulthedge_fund.tui.backtest.BacktestScreen→hedge_fund.backtesting.fund.DailyValuationhedge_fund.tui.backtest.BacktestScreen→hedge_fund.backtesting.fund.FundBacktestResult
- Direction
- tui.backtest uses backtesting.fund, so a change to backtesting.fund can break tui.backtest, while a change to tui.backtest can't break backtesting.fund.
- Position
- Below the diagonal: tui.backtest uses a module listed above it, which is the healthy direction.
39→17 tui.backtest uses fund.spec✕
- Connections
- 1 pair of types, where a type in tui.backtest uses a type in fund.spec.
- The types involved
hedge_fund.tui.backtest.BacktestScreen→hedge_fund.fund.spec.FundSpec
- Direction
- tui.backtest uses fund.spec, so a change to fund.spec can break tui.backtest, while a change to tui.backtest can't break fund.spec.
- Position
- Below the diagonal: tui.backtest uses a module listed above it, which is the healthy direction.
39→27 tui.backtest uses pipeline.models✕
- Connections
- 1 pair of types, where a type in tui.backtest uses a type in pipeline.models.
- The types involved
hedge_fund.tui.backtest.BacktestScreen→hedge_fund.pipeline.models.CycleRecord
- Direction
- tui.backtest uses pipeline.models, so a change to pipeline.models can break tui.backtest, while a change to tui.backtest can't break pipeline.models.
- Position
- Below the diagonal: tui.backtest uses a module listed above it, which is the healthy direction.
40→8 tui.paper uses pipeline.session✕
- Connections
- 2 pairs of types, where a type in tui.paper uses a type in pipeline.session.
- The types involved
hedge_fund.tui.paper.RunConfirmScreen→hedge_fund.pipeline.session.FundStatehedge_fund.tui.paper.RunSessionScreen→hedge_fund.pipeline.session.SessionRecord
- Direction
- tui.paper uses pipeline.session, so a change to pipeline.session can break tui.paper, while a change to tui.paper can't break pipeline.session.
- Position
- Below the diagonal: tui.paper uses a module listed above it, which is the healthy direction.
40→17 tui.paper uses fund.spec✕
- Connections
- 1 pair of types, where a type in tui.paper uses a type in fund.spec.
- The types involved
hedge_fund.tui.paper.RunSessionScreen→hedge_fund.fund.spec.FundSpec
- Direction
- tui.paper uses fund.spec, so a change to fund.spec can break tui.paper, while a change to tui.paper can't break fund.spec.
- Position
- Below the diagonal: tui.paper uses a module listed above it, which is the healthy direction.
40→25 tui.paper uses paper.deployed✕
- Connections
- 2 pairs of types, where a type in tui.paper uses a type in paper.deployed.
- The types involved
hedge_fund.tui.paper.RunConfirmScreen→hedge_fund.paper.deployed.DeployedFundhedge_fund.tui.paper.RunSessionScreen→hedge_fund.paper.deployed.DeployedFund
- Direction
- tui.paper uses paper.deployed, so a change to paper.deployed can break tui.paper, while a change to tui.paper can't break paper.deployed.
- Position
- Below the diagonal: tui.paper uses a module listed above it, which is the healthy direction.
40→31 tui.paper uses tui.paper_view✕
- Connections
- 1 pair of types, where a type in tui.paper uses a type in tui.paper_view.
- The types involved
hedge_fund.tui.paper.SessionsScreen→hedge_fund.tui.paper_view.PaperSnapshot
- Direction
- tui.paper uses tui.paper_view, so a change to tui.paper_view can break tui.paper, while a change to tui.paper can't break tui.paper_view.
- Position
- Below the diagonal: tui.paper 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 | 12 | High / Critical |
Roadmap
Top priorities: Add a CI workflow that builds and runs the test suite on every push/PR; 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; Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Add a CI workflow that builds and runs the test suite on every push/PR. | +6.4 pts | Medium | CI/CD gates |
| 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 |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +2.4 pts | Medium | Release Hygiene |
| Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite. | +2.1 pts | Medium | Documentation (README) |
| Resolve the 1 Scattered collaborators finding(s) in Navigability. | +0.7 pts | Low | Navigability |
| Resolve the 4 Hotspot finding(s) in Churn × Complexity Hotspots — start with run.py, stages.py, limits.py. | +0.3 pts | High | Churn × Complexity Hotspots |
| Bring the 6 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with validation.validate_targets (cyclomatic 35), run._paper (cyclomatic 27), limits.apply_limits (cyclomatic 26). | +0.3 pts | High | Cyclomatic Complexity |
| Bring the 4 bodies over 30 down to 30 or less in Cognitive Complexity — start with validation.validate_targets (cognitive 63), run._paper (cognitive 44), limits.apply_limits (cognitive 38). | +0.2 pts | High | Cognitive Complexity |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.4 | Slop | Dependency Vulnerabilities: Critical vulnerability: REDACTED |
| hedge_fund/tui/paper.py | 7.2 | Near-clean | God Classes: FileTooLong: tui/paper.py |
| hedge_fund/tui/report.py | 7.2 | Near-clean | God Classes: FileTooLong: tui/report.py |
| hedge_fund/risk/limits.py | 7.4 | Near-clean | Cyclomatic Complexity: limits.apply_limits (cyclomatic 26) |
| hedge_fund/pipeline/stages.py | 7.4 | Near-clean | Cyclomatic Complexity: stages.execute_decision (cyclomatic 21) |
| hedge_fund/scorecard/analysts.py | 7.4 | Near-clean | Cyclomatic Complexity: analysts._score (cyclomatic 16) |
| hedge_fund/tui/shared.py | 7.4 | Near-clean | Cognitive Complexity: shared.render_area_chart (cognitive 29) |
| hedge_fund/portfolio/validation.py | 7.8 | Near-clean | Cyclomatic Complexity: validation.validate_targets (cyclomatic 35) |
| hedge_fund/run.py | 7.8 | Near-clean | Cyclomatic Complexity: run._paper (cyclomatic 27) |
| hedge_fund/portfolio/construction.py | 7.8 | Near-clean | Cyclomatic Complexity: construction.blend_signals (cyclomatic 25) |
| hedge_fund/paper/runner.py | 7.8 | Near-clean | Cognitive Complexity: runner._run_bars (cognitive 23) |
| hedge_fund/data/client.py | 7.8 | Near-clean | Cognitive Complexity: FDClient._request (cognitive 19) |
| hedge_fund/tui/paper_view.py | 7.8 | Near-clean | Cognitive Complexity: paper_view.paper_detail (cognitive 18) |
| hedge_fund/paper/ledger.py | 7.8 | Near-clean | Cognitive Complexity: Ledger.replay (cognitive 16) |
| hedge_fund/data/cached.py | 7.8 | Near-clean | Code Duplication: Edited copies of one member (3 members, 8+ corresponding lines) |
| hedge_fund/pipeline/execution.py | 8.5 | Near-clean | Cognitive Complexity: execution.build_orders (cognitive 22) |
| hedge_fund/scorecard/strategies.py | 8.5 | Near-clean | Cognitive Complexity: strategies.score_strategies (cognitive 21) |
| hedge_fund/llm/client.py | 8.5 | Near-clean | Cognitive Complexity: client.extract_json (cognitive 19) |
| hedge_fund/scorecard/allocation.py | 8.5 | Near-clean | Cognitive Complexity: allocation.allocate (cognitive 16) |
| hedge_fund/signals/pead.py | 8.5 | Near-clean | Cognitive Complexity: PEADModel._qualifying_events (cognitive 16) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 40 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 40 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 69 of 76 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.py) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
- 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 (48 contributor(s) across 964 commit(s) sampled, automation and bot accounts excluded). One of them holds 91% of the history; the other 47 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 an ADMISSION gap, not an environment fault: no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D26 Project Cohesion — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `(repository root)` (10930 LoC, 161 module-visible types across 14 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Python is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Python is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — 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. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X29 Per-element action decided by a fixed element — 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 (Vue and Svelte components included), Java, Rust, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, Rust, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X5 Nullable reference types — 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 MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Python is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- 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.
- 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.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
6 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was validation.validate_targets at 35.
What to do
- Bring the 6 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with validation.validate_targets (cyclomatic 35), run._paper (cyclomatic 27), limits.apply_limits (cyclomatic 26). — 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 6 together lifts Cyclomatic Complexity from 8.6 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
21 method(s) exceeded the cognitive complexity threshold of 15; the worst was validation.validate_targets at 63.
What to do
- Bring the 4 bodies over 30 down to 30 or less in Cognitive Complexity — start with validation.validate_targets (cognitive 63), run._paper (cognitive 44), limits.apply_limits (cognitive 38). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cognitive Complexity from 6.3 to about 7.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
D3 · God Classes
3 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 3 FileTooLong finding(s) in God Classes — start with paper.py, report.py, builder.py. — One of this dimension's main actionable groups (3 warning-level).
D4 · Code Duplication
7 duplicated block group(s) detected. 3.1 % of the production lines (334 of 10,930) are in a reported copy. A further 9 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 2 Edited copy of a member (7 corresponding lines) finding(s) in Code Duplication — start with funds.py, cached.py. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with shared.py, report.py. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with paper.py, report.py. — One of this dimension's main actionable groups (2 warning-level).
D6 · Cohesion (LCOM4)
0 of 29 classes have LCOM4 above 3.
D11 · Test Reliability
0 flaky across 1 measured tier(s). Python (repository root, 44 test files): measured (0 flaky).
D12 · Dependency Hygiene
2 outdated, 0 yanked pinned Python distributions. 2 of 16 shipped distributions were graded against pypi.org (0 not published there, 14 declared without an exact pin, which installs the newest release the declaration admits and so cannot be behind one). Only EXACT pins are graded for currency: a floor or a range already installs the newest release it admits, so reporting one would report this repository for being current. Whether a deliberate upper cap has itself gone stale is a different and weaker question, and is not asked. Whether any distribution is UNMAINTAINED is not graded — PyPI publishes no maintenance status, and release age does not stand in for one. Lockfiles are not read (REDACTED, uv.lock, Pipfile.lock, pdm.lock), so a lock-resolved install is outside this verdict. Known CVEs in this dependency graph are D30's question.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 86 shipped Python distribution(s) use a banned license. Licences were resolved from PyPI over the distributions a consumer installs — this repository's 16 declared runtime requirement(s) closed transitively over each distribution's published `requires_dist` (70 reached that way). Requirements it states ONLY under an extra, a PEP 735 dependency group, a Poetry dev group or a dev-named requirements file are excluded: pip does not install any of them for a consumer. ★ This repository commits no dependency lockfile that this pass reads, so each licence is the one PyPI publishes for the distribution's CURRENT release rather than for a pinned version. 4 of them publish no licence on PyPI this pass can read; that is missing data, not a violation, and none of them is charged. This repository publishes itself under MIT, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
Top hotspots: hedge_fund/run.py (16×27=432); hedge_fund/pipeline/stages.py (13×21=273); hedge_fund/risk/limits.py (3×26=78)
What to do
- Resolve the 4 Hotspot finding(s) in Churn × Complexity Hotspots — start with run.py, stages.py, limits.py. — One of this dimension's main actionable groups (4 warning-level).
D17 · Explicit Debt
0 deducted task-comment markers across 10930 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 2 document(s) read across 1 unit(s).
D27 · Navigability
79 % of calls cross a namespace and 8 % go through an interface, but 32 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
What to do
- Resolve the 1 Scattered collaborators finding(s) in Navigability. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
semgrep found no security issues.
D30 · Dependency Vulnerabilities
12 finding(s): 2 critical, 5 high, 5 medium, 0 low.
What to do
- Resolve the 5 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (5). — One of this dimension's main actionable groups (5 issue-level).
- Resolve the 1 Critical vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 56 of the 83 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
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 16 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
AX5 · Architecture & structure
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
- No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
What to do
- Add a CI workflow that builds and runs the test suite on every push/PR.
P10 · Library API & versioning
P2 · Observability
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add bandit, `semgrep --config=p/python`, or CodeQL's python pack — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 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.
What to do
- Run what this repository's stack ships: bandit, `semgrep --config=p/python`, or CodeQL's python pack — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
X12 · Unreachable branch
X13 · Undrained process stream
X19 · Unrestored process-global state
X25 · Inert configuration knob
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X3 · Exception handling
X4 · Structured logging
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 93% | Exemplary | Solid. |
| Architecture | 92% | Exemplary | Solid. |
| Maturity | 65% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 29% | Weak — gated by D12, P1, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 100% | Exemplary | Strongest area. |
Unscored — 3 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X6 Hand-rolled structured-format parsing — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 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 Python 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 function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads.
- AX4 Dependency direction — not applicable to a vertical-slice architecture (the inward-dependency rule is for layered/clean styles)
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — vertical-slice architecture detected, but individual slices could not be resolved from namespaces or project layout
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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 — No access-control surface detected in the analyzed source — this repository registers no route and starts no server another machine can reach (no Flask/FastAPI/Starlette route, Django urlpatterns or class-based view, Tornado handler). Access control is therefore N/A here — a library or command-line tool is authorized by the application that serves it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Django, SQLAlchemy, SQLModel, Peewee, Tortoise or MongoEngine model, a migration or a SQL schema — and no database or data-store client (Django ORM, SQLAlchemy, psycopg, PyMongo, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential on a Django, SQLAlchemy, SQLModel, Peewee, Tortoise or mongoengine model, in a migration or in a SQL schema — and no database or data-store client (django.db, sqlalchemy, psycopg2, pymongo, sqlite3, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential on a Django, SQLAlchemy, SQLModel, Peewee, Tortoise or mongoengine model, in a migration or in a SQL schema — and no database or data-store client (django.db, sqlalchemy, psycopg2, pymongo, sqlite3, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~8132 lines of test source are present (.py) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D20 ADR Quality — N/A — this repo declares itself a template / kata / sample / demo; a formal ADR log is deferred to a real application built from it.
- D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 1 candidate(s) found and not reported.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .py, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D26 Project Cohesion — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- 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.
- D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
- 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.
- D5 Coupling — Not applicable — this Python build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (56 value object(s))
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — no CI workflow found
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Python source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for a pytest-benchmark or pytest-codspeed dependency with tests taking the `benchmark` fixture, an asv.conf.json with its `time_`/`mem_`/`peakmem_` benchmarks, or a pyperf Runner, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X16 Unfloored truncation loop — not 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
- 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 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
- X2 Cancellation propagation — no C# was loaded; this repository's Python was read, and no request in it can be cancelled by a caller — a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X21 Side-effecting pattern 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
- 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
- X29 Per-element action decided by a fixed element — 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
- 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.
- X5 Nullable reference types — 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
- 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 — 7 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 56 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Hotspot: hedge_fund/run.py hedge_fund/run.py:261
- Hotspot: hedge_fund/pipeline/stages.py hedge_fund/pipeline/stages.py:142
- Hotspot: hedge_fund/risk/limits.py hedge_fund/risk/limits.py:127
- Hotspot: hedge_fund/portfolio/construction.py hedge_fund/portfolio/construction.py:29
- FileTooLong: tui/paper.py hedge_fund/tui/paper.py
- FileTooLong: tui/report.py hedge_fund/tui/report.py
- FileTooLong: tui/builder.py hedge_fund/tui/builder.py
- Edited copy of a member (7 corresponding lines) hedge_fund/tui/funds.py:73
- Edited copy of a member (7 corresponding lines) hedge_fund/data/cached.py:149
- Duplicated block (12 lines × 2) hedge_fund/tui/shared.py:193
- Duplicated block (12 lines × 2) hedge_fund/tui/report.py:335
- Duplicated block (5 lines × 2) hedge_fund/tui/paper.py:483
- Duplicated block (5 lines × 2) hedge_fund/tui/report.py:672
- validation.validate_targets (cyclomatic 35) hedge_fund/portfolio/validation.py:16
- run._paper (cyclomatic 27) hedge_fund/run.py:261
- limits.apply_limits (cyclomatic 26) hedge_fund/risk/limits.py:127
- construction.blend_signals (cyclomatic 25) hedge_fund/portfolio/construction.py:29
- stages.execute_decision (cyclomatic 21) hedge_fund/pipeline/stages.py:142
- analysts._score (cyclomatic 16) hedge_fund/scorecard/analysts.py:104
- validation.validate_targets (cognitive 63) hedge_fund/portfolio/validation.py:16
- run._paper (cognitive 44) hedge_fund/run.py:261
- limits.apply_limits (cognitive 38) hedge_fund/risk/limits.py:127
- construction.blend_signals (cognitive 36) hedge_fund/portfolio/construction.py:29
- analysts.score_analysts (cognitive 30) hedge_fund/scorecard/analysts.py:50
- shared.render_area_chart (cognitive 29) hedge_fund/tui/shared.py:210
- stages.execute_decision (cognitive 25) hedge_fund/pipeline/stages.py:142
- runner._run_bars (cognitive 23) hedge_fund/paper/runner.py:124
- execution.build_orders (cognitive 22) hedge_fund/pipeline/execution.py:16
- stages.assess_fund (cognitive 21) hedge_fund/pipeline/stages.py:51
- strategies.score_strategies (cognitive 21) hedge_fund/scorecard/strategies.py:23
- FDClient._request (cognitive 19) hedge_fund/data/client.py:373
- client.extract_json (cognitive 19) hedge_fund/llm/client.py:333
- paper_view.paper_detail (cognitive 18) hedge_fund/tui/paper_view.py:250
- paper_view.run_plan (cognitive 18) hedge_fund/tui/paper_view.py:317
- limits._scale_book (cognitive 17) hedge_fund/risk/limits.py:228
- analysts._score (cognitive 17) hedge_fund/scorecard/analysts.py:104
- Ledger.replay (cognitive 16) hedge_fund/paper/ledger.py:147
- Ledger._trusted_checkpoint (cognitive 16) hedge_fund/paper/ledger.py:193
- allocation.allocate (cognitive 16) hedge_fund/scorecard/allocation.py:23
- PEADModel._qualifying_events (cognitive 16) hedge_fund/signals/pead.py:104
- Edited copy of a member (17 corresponding lines) hedge_fund/tui/report.py:322
- Edited copy of a member (60 corresponding lines) hedge_fund/tui/shared.py:145
- Edited copies of one member (3 members, 8+ corresponding lines) hedge_fund/data/cached.py:195
- Edited copy of a member (11 corresponding lines) hedge_fund/signals/__init__.py:29
- Edited copy of a member (5 corresponding lines) hedge_fund/tui/paper.py:482
- Edited copy of a member (6 corresponding lines) hedge_fund/data/client.py:210
- Edited copy of a member (8 corresponding lines) hedge_fund/brokers/models.py:56
- Duplicated block (9 lines × 2) hedge_fund/tui/paper.py:458
- Duplicated block (7–8 lines × 2) hedge_fund/tui/scorecard_view.py:22
- Duplicated block (6 lines × 2) hedge_fund/paper/runner.py:101
- No CI pipeline
Minor — 11 finding(s)
- Hand-rolled JSON/XML parsing via regex hedge_fund/llm/watch.py:21
- Hand-rolled JSON/XML parsing via regex hedge_fund/llm/watch.py:22
- Hand-rolled JSON/XML parsing via regex hedge_fund/llm/watch.py:23
- Silent fallback default on parse failure hedge_fund/data/client.py:45
- Silent fallback default on parse failure hedge_fund/llm/client.py:218
- Silent fallback default on parse failure hedge_fund/tui/shared.py:102
- Scattered collaborators
- No ADRs
- No SAST
- No changelog
- Duplicated predicate hedge_fund/run.py:399
Minor — 2 finding(s)
- Outdated: langchain-anthropic
- Outdated: python-dotenv
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-b0be98783e264b0697e6a5ea09c2ece2/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-b0be98783e264b0697e6a5ea09c2ece2/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 . | 0 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 12 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |