Executive summary
pallets/flask is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back because we found no automated security scanning of the code, its secrets or its dependencies. It scores 69 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 61, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 7 points. Adding automated security scanning would lift Production Readiness itself, worth about 6 points. Raising Production Readiness to 70 would lift the score to about 71.
Seven known security holes in the packages the code depends on can be used by attackers. Two places in the code run text as code, which an attacker could use, and one weakness in the code could be used by an attacker. Updating the vulnerable packages, replacing text run as code with direct calls and fixing the weaknesses the scanner points to would close these risks.
The product code is 8,051 lines, about €18,000 to rebuild.
If Production Readiness rose from 61 to 70, the lowest score rated Strong, the score would rise from 69 to about 71.
New since the last survey: 8 findings
- Code Duplication · Edited copy of a member (10 corresponding lines) src/flask/templating.py
- Code Duplication · Edited copy of a member (7 corresponding lines) src/flask/app.py
- Code Duplication · Edited copy of a member (25 corresponding lines) src/flask/app.py
- Code Duplication · Edited copy of a member (21 corresponding lines) examples/tutorial/flaskr/blog.py
- Churn × Complexity Hotspots · Hotspot: src/flask/app.py src/flask/app.py
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
Fixed since the last survey: 3 findings
- Secrets (history) · Secret: generic-api-key docs/config.rst
- Secrets (history) · Secret: generic-api-key docs/config.rst
- Secrets (history) · Secret: generic-api-key docs/tutorial/deploy.rst
Rebuild cost: about €18,000 · Estimate
| Cost to rebuild | €6,000 to €30,000, for 100 to 316 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 | ×1.0 at a score of 69. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 8,051 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 docs | 2 src.flask.helpers | 3 src.flask.json | 4 src.flask.json.tag | 5 src.flask.sansio | 6 src.flask.sansio.scaffold | 7 src.flask.views | 8 src.flask.wrappers | 9 src.flask.config | 10 src.flask.debughelpers | 11 src.flask.sansio.blueprints | 12 src.flask.sessions | 13 src.flask.templating | 14 src.flask.testing | 15 src.flask.blueprints | 16 src.flask.ctx | 17 src.flask.sansio.app | 18 src.flask.app | 19 src.flask.json.provider | 20 src.flask.cli | 21 src.flask |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 docs | |||||||||||||||||||||
| 2 src.flask.helpers | |||||||||||||||||||||
| 3 src.flask.json | |||||||||||||||||||||
| 4 src.flask.json.tag | |||||||||||||||||||||
| 5 src.flask.sansio | |||||||||||||||||||||
| 6 src.flask.sansio.scaffold | |||||||||||||||||||||
| 7 src.flask.views | |||||||||||||||||||||
| 8 src.flask.wrappers | |||||||||||||||||||||
| 9 src.flask.config | 1 | ||||||||||||||||||||
| 10 src.flask.debughelpers | 2 | ||||||||||||||||||||
| 11 src.flask.sansio.blueprints | 1 | 2 | |||||||||||||||||||
| 12 src.flask.sessions | 4 | 2 | |||||||||||||||||||
| 13 src.flask.templating | 2 | ||||||||||||||||||||
| 14 src.flask.testing | 3 | ||||||||||||||||||||
| 15 src.flask.blueprints | 1 | 1 | |||||||||||||||||||
| 16 src.flask.ctx | 1 | 1 | 1 | ||||||||||||||||||
| 17 src.flask.sansio.app | 1 | 1 | 1 | 2 | |||||||||||||||||
| 18 src.flask.app | 2 | 1 | 1 | 2 | 1 | 1 | |||||||||||||||
| 19 src.flask.json.provider | 1 | ||||||||||||||||||||
| 20 src.flask.cli | 1 | ||||||||||||||||||||
| 21 src.flask | 3 | 1 | 2 | 1 | 1 |
9→17 src.flask.config uses src.flask.sansio.app part of a loop✕
- Connections
- 1 pair of types, where a type in src.flask.config uses a type in src.flask.sansio.app.
- The types involved
src.flask.config.ConfigAttribute→src.flask.sansio.app.App
- Direction
- src.flask.config uses src.flask.sansio.app, so a change to src.flask.sansio.app can break src.flask.config, while a change to src.flask.config can't break src.flask.sansio.app.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→8 src.flask.debughelpers uses src.flask.wrappers✕
- Connections
- 2 pairs of types, where a type in src.flask.debughelpers uses a type in src.flask.wrappers.
- The types involved
src.flask.debughelpers.DebugFilesKeyError→src.flask.wrappers.Requestsrc.flask.debughelpers.FormDataRoutingRedirect→src.flask.wrappers.Request
- Direction
- src.flask.debughelpers uses src.flask.wrappers, so a change to src.flask.wrappers can break src.flask.debughelpers, while a change to src.flask.debughelpers can't break src.flask.wrappers.
- Position
- Below the diagonal: src.flask.debughelpers uses a module listed above it, which is the healthy direction.
11→6 src.flask.sansio.blueprints uses src.flask.sansio.scaffold✕
- Connections
- 1 pair of types, where a type in src.flask.sansio.blueprints uses a type in src.flask.sansio.scaffold.
- The types involved
src.flask.sansio.blueprints.Blueprint→src.flask.sansio.scaffold.Scaffold
- Direction
- src.flask.sansio.blueprints uses src.flask.sansio.scaffold, so a change to src.flask.sansio.scaffold can break src.flask.sansio.blueprints, while a change to src.flask.sansio.blueprints can't break src.flask.sansio.scaffold.
- Position
- Below the diagonal: src.flask.sansio.blueprints uses a module listed above it, which is the healthy direction.
11→17 src.flask.sansio.blueprints uses src.flask.sansio.app part of a loop✕
- Connections
- 2 pairs of types, where a type in src.flask.sansio.blueprints uses a type in src.flask.sansio.app.
- The types involved
src.flask.sansio.blueprints.Blueprint→src.flask.sansio.app.Appsrc.flask.sansio.blueprints.BlueprintSetupState→src.flask.sansio.app.App
- Direction
- src.flask.sansio.blueprints uses src.flask.sansio.app, so a change to src.flask.sansio.app can break src.flask.sansio.blueprints, while a change to src.flask.sansio.blueprints can't break src.flask.sansio.app.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→8 src.flask.sessions uses src.flask.wrappers✕
- Connections
- 4 pairs of types, where a type in src.flask.sessions uses a type in src.flask.wrappers.
- The types involved
src.flask.sessions.SecureCookieSessionInterface→src.flask.wrappers.Requestsrc.flask.sessions.SecureCookieSessionInterface→src.flask.wrappers.Responsesrc.flask.sessions.SessionInterface→src.flask.wrappers.Requestsrc.flask.sessions.SessionInterface→src.flask.wrappers.Response
- Direction
- src.flask.sessions uses src.flask.wrappers, so a change to src.flask.wrappers can break src.flask.sessions, while a change to src.flask.sessions can't break src.flask.wrappers.
- Position
- Below the diagonal: src.flask.sessions uses a module listed above it, which is the healthy direction.
12→18 src.flask.sessions uses src.flask.app part of a loop✕
- Connections
- 2 pairs of types, where a type in src.flask.sessions uses a type in src.flask.app.
- The types involved
src.flask.sessions.SecureCookieSessionInterface→src.flask.app.Flasksrc.flask.sessions.SessionInterface→src.flask.app.Flask
- Direction
- src.flask.sessions uses src.flask.app, so a change to src.flask.app can break src.flask.sessions, while a change to src.flask.sessions can't break src.flask.app.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→17 src.flask.templating uses src.flask.sansio.app part of a loop✕
- Connections
- 2 pairs of types, where a type in src.flask.templating uses a type in src.flask.sansio.app.
- The types involved
src.flask.templating.DispatchingJinjaLoader→src.flask.sansio.app.Appsrc.flask.templating.Environment→src.flask.sansio.app.App
- Direction
- src.flask.templating uses src.flask.sansio.app, so a change to src.flask.sansio.app can break src.flask.templating, while a change to src.flask.templating can't break src.flask.sansio.app.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→18 src.flask.testing uses src.flask.app part of a loop✕
- Connections
- 3 pairs of types, where a type in src.flask.testing uses a type in src.flask.app.
- The types involved
src.flask.testing.EnvironBuilder→src.flask.app.Flasksrc.flask.testing.FlaskCliRunner→src.flask.app.Flasksrc.flask.testing.FlaskClient→src.flask.app.Flask
- Direction
- src.flask.testing uses src.flask.app, so a change to src.flask.app can break src.flask.testing, while a change to src.flask.testing can't break src.flask.app.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→8 src.flask.blueprints uses src.flask.wrappers✕
- Connections
- 1 pair of types, where a type in src.flask.blueprints uses a type in src.flask.wrappers.
- The types involved
src.flask.blueprints.Blueprint→src.flask.wrappers.Response
- Direction
- src.flask.blueprints uses src.flask.wrappers, so a change to src.flask.wrappers can break src.flask.blueprints, while a change to src.flask.blueprints can't break src.flask.wrappers.
- Position
- Below the diagonal: src.flask.blueprints uses a module listed above it, which is the healthy direction.
15→11 src.flask.blueprints uses src.flask.sansio.blueprints✕
- Connections
- 1 pair of types, where a type in src.flask.blueprints uses a type in src.flask.sansio.blueprints.
- The types involved
src.flask.blueprints.Blueprint→src.flask.sansio.blueprints.Blueprint
- Direction
- src.flask.blueprints uses src.flask.sansio.blueprints, so a change to src.flask.sansio.blueprints can break src.flask.blueprints, while a change to src.flask.blueprints can't break src.flask.sansio.blueprints.
- Position
- Below the diagonal: src.flask.blueprints uses a module listed above it, which is the healthy direction.
16→8 src.flask.ctx uses src.flask.wrappers✕
- Connections
- 1 pair of types, where a type in src.flask.ctx uses a type in src.flask.wrappers.
- The types involved
src.flask.ctx.AppContext→src.flask.wrappers.Request
- Direction
- src.flask.ctx uses src.flask.wrappers, so a change to src.flask.wrappers can break src.flask.ctx, while a change to src.flask.ctx can't break src.flask.wrappers.
- Position
- Below the diagonal: src.flask.ctx uses a module listed above it, which is the healthy direction.
16→12 src.flask.ctx uses src.flask.sessions✕
- Connections
- 1 pair of types, where a type in src.flask.ctx uses a type in src.flask.sessions.
- The types involved
src.flask.ctx.AppContext→src.flask.sessions.SessionMixin
- Direction
- src.flask.ctx uses src.flask.sessions, so a change to src.flask.sessions can break src.flask.ctx, while a change to src.flask.ctx can't break src.flask.sessions.
- Position
- Below the diagonal: src.flask.ctx uses a module listed above it, which is the healthy direction.
16→18 src.flask.ctx uses src.flask.app part of a loop✕
- Connections
- 1 pair of types, where a type in src.flask.ctx uses a type in src.flask.app.
- The types involved
src.flask.ctx.AppContext→src.flask.app.Flask
- Direction
- src.flask.ctx uses src.flask.app, so a change to src.flask.app can break src.flask.ctx, while a change to src.flask.ctx can't break src.flask.app.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→6 src.flask.sansio.app uses src.flask.sansio.scaffold✕
- Connections
- 1 pair of types, where a type in src.flask.sansio.app uses a type in src.flask.sansio.scaffold.
- The types involved
src.flask.sansio.app.App→src.flask.sansio.scaffold.Scaffold
- Direction
- src.flask.sansio.app uses src.flask.sansio.scaffold, so a change to src.flask.sansio.scaffold can break src.flask.sansio.app, while a change to src.flask.sansio.app can't break src.flask.sansio.scaffold.
- Position
- Below the diagonal: src.flask.sansio.app uses a module listed above it, which is the healthy direction.
17→9 src.flask.sansio.app uses src.flask.config✕
- Connections
- 1 pair of types, where a type in src.flask.sansio.app uses a type in src.flask.config.
- The types involved
src.flask.sansio.app.App→src.flask.config.Config
- Direction
- src.flask.sansio.app uses src.flask.config, so a change to src.flask.config can break src.flask.sansio.app, while a change to src.flask.sansio.app can't break src.flask.config.
- Position
- Below the diagonal: src.flask.sansio.app uses a module listed above it, which is the healthy direction.
17→11 src.flask.sansio.app uses src.flask.sansio.blueprints✕
- Connections
- 1 pair of types, where a type in src.flask.sansio.app uses a type in src.flask.sansio.blueprints.
- The types involved
src.flask.sansio.app.App→src.flask.sansio.blueprints.Blueprint
- Direction
- src.flask.sansio.app uses src.flask.sansio.blueprints, so a change to src.flask.sansio.blueprints can break src.flask.sansio.app, while a change to src.flask.sansio.app can't break src.flask.sansio.blueprints.
- Position
- Below the diagonal: src.flask.sansio.app uses a module listed above it, which is the healthy direction.
17→13 src.flask.sansio.app uses src.flask.templating✕
- Connections
- 2 pairs of types, where a type in src.flask.sansio.app uses a type in src.flask.templating.
- The types involved
src.flask.sansio.app.App→src.flask.templating.DispatchingJinjaLoadersrc.flask.sansio.app.App→src.flask.templating.Environment
- Direction
- src.flask.sansio.app uses src.flask.templating, so a change to src.flask.templating can break src.flask.sansio.app, while a change to src.flask.sansio.app can't break src.flask.templating.
- Position
- Below the diagonal: src.flask.sansio.app uses a module listed above it, which is the healthy direction.
18→8 src.flask.app uses src.flask.wrappers✕
- Connections
- 2 pairs of types, where a type in src.flask.app uses a type in src.flask.wrappers.
- The types involved
src.flask.app.Flask→src.flask.wrappers.Requestsrc.flask.app.Flask→src.flask.wrappers.Response
- Direction
- src.flask.app uses src.flask.wrappers, so a change to src.flask.wrappers can break src.flask.app, while a change to src.flask.app can't break src.flask.wrappers.
- Position
- Below the diagonal: src.flask.app uses a module listed above it, which is the healthy direction.
18→12 src.flask.app uses src.flask.sessions✕
- Connections
- 1 pair of types, where a type in src.flask.app uses a type in src.flask.sessions.
- The types involved
src.flask.app.Flask→src.flask.sessions.SessionInterface
- Direction
- src.flask.app uses src.flask.sessions, so a change to src.flask.sessions can break src.flask.app, while a change to src.flask.app can't break src.flask.sessions.
- Position
- Below the diagonal: src.flask.app uses a module listed above it, which is the healthy direction.
18→13 src.flask.app uses src.flask.templating✕
- Connections
- 1 pair of types, where a type in src.flask.app uses a type in src.flask.templating.
- The types involved
src.flask.app.Flask→src.flask.templating.Environment
- Direction
- src.flask.app uses src.flask.templating, so a change to src.flask.templating can break src.flask.app, while a change to src.flask.app can't break src.flask.templating.
- Position
- Below the diagonal: src.flask.app uses a module listed above it, which is the healthy direction.
18→14 src.flask.app uses src.flask.testing✕
- Connections
- 2 pairs of types, where a type in src.flask.app uses a type in src.flask.testing.
- The types involved
src.flask.app.Flask→src.flask.testing.FlaskCliRunnersrc.flask.app.Flask→src.flask.testing.FlaskClient
- Direction
- src.flask.app uses src.flask.testing, so a change to src.flask.testing can break src.flask.app, while a change to src.flask.app can't break src.flask.testing.
- Position
- Below the diagonal: src.flask.app uses a module listed above it, which is the healthy direction.
18→16 src.flask.app uses src.flask.ctx✕
- Connections
- 1 pair of types, where a type in src.flask.app uses a type in src.flask.ctx.
- The types involved
src.flask.app.Flask→src.flask.ctx.AppContext
- Direction
- src.flask.app uses src.flask.ctx, so a change to src.flask.ctx can break src.flask.app, while a change to src.flask.app can't break src.flask.ctx.
- Position
- Below the diagonal: src.flask.app uses a module listed above it, which is the healthy direction.
18→17 src.flask.app uses src.flask.sansio.app✕
- Connections
- 1 pair of types, where a type in src.flask.app uses a type in src.flask.sansio.app.
- The types involved
src.flask.app.Flask→src.flask.sansio.app.App
- Direction
- src.flask.app uses src.flask.sansio.app, so a change to src.flask.sansio.app can break src.flask.app, while a change to src.flask.app can't break src.flask.sansio.app.
- Position
- Below the diagonal: src.flask.app uses a module listed above it, which is the healthy direction.
19→17 src.flask.json.provider uses src.flask.sansio.app✕
- Connections
- 1 pair of types, where a type in src.flask.json.provider uses a type in src.flask.sansio.app.
- The types involved
src.flask.json.provider.JSONProvider→src.flask.sansio.app.App
- Direction
- src.flask.json.provider uses src.flask.sansio.app, so a change to src.flask.sansio.app can break src.flask.json.provider, while a change to src.flask.json.provider can't break src.flask.sansio.app.
- Position
- Below the diagonal: src.flask.json.provider uses a module listed above it, which is the healthy direction.
20→18 src.flask.cli uses src.flask.app✕
- Connections
- 1 pair of types, where a type in src.flask.cli uses a type in src.flask.app.
- The types involved
src.flask.cli.ScriptInfo→src.flask.app.Flask
- Direction
- src.flask.cli uses src.flask.app, so a change to src.flask.app can break src.flask.cli, while a change to src.flask.cli can't break src.flask.app.
- Position
- Below the diagonal: src.flask.cli uses a module listed above it, which is the healthy direction.
21→8 src.flask uses src.flask.wrappers✕
- Connections
- 3 pairs of types, where a type in src.flask uses a type in src.flask.wrappers.
- The types involved
src.flask.debughelpers→src.flask.wrappers.Requestsrc.flask.helpers→src.flask.wrappers.Responsesrc.flask.json→src.flask.wrappers.Response
- Direction
- src.flask uses src.flask.wrappers, so a change to src.flask.wrappers can break src.flask, while a change to src.flask can't break src.flask.wrappers.
- Position
- Below the diagonal: src.flask uses a module listed above it, which is the healthy direction.
21→16 src.flask uses src.flask.ctx✕
- Connections
- 1 pair of types, where a type in src.flask uses a type in src.flask.ctx.
- The types involved
src.flask.templating→src.flask.ctx.AppContext
- Direction
- src.flask uses src.flask.ctx, so a change to src.flask.ctx can break src.flask, while a change to src.flask can't break src.flask.ctx.
- Position
- Below the diagonal: src.flask uses a module listed above it, which is the healthy direction.
21→17 src.flask uses src.flask.sansio.app✕
- Connections
- 2 pairs of types, where a type in src.flask uses a type in src.flask.sansio.app.
- The types involved
src.flask.debughelpers→src.flask.sansio.app.Appsrc.flask.logging→src.flask.sansio.app.App
- Direction
- src.flask uses src.flask.sansio.app, so a change to src.flask.sansio.app can break src.flask, while a change to src.flask can't break src.flask.sansio.app.
- Position
- Below the diagonal: src.flask uses a module listed above it, which is the healthy direction.
21→18 src.flask uses src.flask.app✕
- Connections
- 1 pair of types, where a type in src.flask uses a type in src.flask.app.
- The types involved
src.flask.cli→src.flask.app.Flask
- Direction
- src.flask uses src.flask.app, so a change to src.flask.app can break src.flask, while a change to src.flask can't break src.flask.app.
- Position
- Below the diagonal: src.flask uses a module listed above it, which is the healthy direction.
21→20 src.flask uses src.flask.cli✕
- Connections
- 1 pair of types, where a type in src.flask uses a type in src.flask.cli.
- The types involved
src.flask.cli→src.flask.cli.ScriptInfo
- Direction
- src.flask uses src.flask.cli, so a change to src.flask.cli can break src.flask, while a change to src.flask can't break src.flask.cli.
- Position
- Below the diagonal: src.flask 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 |
| A05:2025 — Injection | 4 | High / Critical |
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED; Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them; Add a SAST step to CI running what this repository's stack ships: bandit, `semgrep --config=p/python`, or CodeQL's python pack — so a security regression fails the build instead of landing.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED. | +7.4 pts | Low | ADR Quality |
| Resolve the 1 Off-boarding risk finding(s) in Bus Factor. | +3.6 pts | Low | Bus Factor |
| 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.2 pts | Medium | Architecture documentation |
| Add a SAST step to CI running what this repository's stack ships: bandit, `semgrep --config=p/python`, or CodeQL's python pack — so a security regression fails the build instead of landing. | +6.2 pts | Medium | Security & performance tooling |
| Add a health-check endpoint (a /health route) so orchestrators and load balancers can probe liveness/readiness. | +1.4 pts | Medium | Observability |
| Resolve the 5 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4), REDACTED. | +0.6 pts | Low | Dependency Vulnerabilities |
| Add a build/run (quick start) section to the root README — the first thing a newcomer needs. | +1.2 pts | Medium | Documentation (README) |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +0.5 pts | Low | Static Analysis (SAST) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.4 | Slop | Dependency Vulnerabilities: Critical vulnerability: REDACTED |
| REDACTED | 4.1 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 4.3 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 6.7 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/flask/app.py | 7.0 | Mixed | Cyclomatic Complexity: Flask.make_response (cyclomatic 16) |
| src/flask/sansio/scaffold.py | 7.0 | Mixed | Cognitive Complexity: scaffold._find_package_path (cognitive 17) |
| src/flask/sansio/app.py | 7.0 | Mixed | Code Duplication: Duplicated block (23 lines × 4) |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/flask/sansio/blueprints.py | 7.8 | Mixed | Cyclomatic Complexity: Blueprint.register (cyclomatic 22) |
| examples/tutorial/flaskr/blog.py | 7.8 | Mixed | Code Duplication: Edited copy of a member (21 corresponding lines) |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| src/flask/templating.py | 8.5 | Near-clean | Code Duplication: Edited copy of a member (10 corresponding lines) |
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 41 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 — 41 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, 42 of 47 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.
- D12 Dependency Hygiene — 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. This repository's 6 shipped Python distribution(s) across 1 manifest(s) WERE read; what went unanswered is the currency half, because it grades an EXACT pin against the newest release and every declaration here is a floor or a range — which installs the newest release it admits and so cannot be behind one. So pypi.org was never asked. This is a true statement about the repository, and the healthy one, NOT a gap on our side: no reader we could write would find a currency question here.
- 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. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- 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.
- 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.
- X4 Structured logging — 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, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP log through no library that carries a message's values as fields (pino, winston, bunyan, tslog, LogTape, roarr; Python's logging, structlog; PHP's PSR-3 loggers), so its log calls cannot be judged, 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.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- 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 REDACTED, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
2 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Blueprint.register at 22.
What to do
- Bring the 2 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with Blueprint.register (cyclomatic 22), Flask.make_response (cyclomatic 16). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 9.4 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
9 method(s) exceeded the cognitive complexity threshold of 15; the worst was Blueprint.register at 24.
What to do
- Bring the 9 bodies over 15 down to 15 or less in Cognitive Complexity — start with Blueprint.register (cognitive 24), Flask.make_response (cognitive 23), Flask.url_for (cognitive 22). — 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 9 together lifts Cognitive Complexity from 8.8 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
3 god class(es) detected.
What to do
- Resolve the 2 FileTooLong finding(s) in God Classes — start with app.py, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 TooManyMethods finding(s) in God Classes — start with app.py. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
4 duplicated block group(s) detected. 2.9 % of the production lines (236 of 8,051) are in a reported copy. A further 4 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 2 of the 8 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
What to do
- Resolve the 1 Edited copy of a member (10 corresponding lines) finding(s) in Code Duplication — start with templating.py. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copy of a member (7 corresponding lines) finding(s) in Code Duplication — start with app.py. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copy of a member (25 corresponding lines) finding(s) in Code Duplication — start with app.py. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
2 of 14 classes have LCOM4 above 3.
What to do
- Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with app.py, scaffold.py. — One of this dimension's main actionable groups (2 warning-level).
D11 · Test Reliability
0 flaky across 1 measured tier(s). Python (3 distributions): measured (0 flaky).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 6 shipped Python distribution(s) use a banned license. Licences were resolved from PyPI over the distributions a consumer installs — this repository's 6 declared runtime requirement(s) closed transitively over each distribution's published `requires_dist` (0 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. 2 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 BSD-3-Clause, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
Top hotspots: src/flask/app.py (6×16=96)
What to do
- Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with app.py. — One of this dimension's main actionable groups (1 warning-level).
D16 · Bus Factor
8 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is REDACTED. Counted over 20 of the 24 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D17 · Explicit Debt
0 deducted task-comment markers across 8051 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. 76 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
56 % of calls cross a namespace and 0 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
4 finding(s): 0 critical, 3 high, 1 medium, 0 low. semgrep hit a parse error in 5 file(s) — `examples/javascript/js_example/templates/base.html` (line 33), `examples/javascript/js_example/templates/fetch.html` (lines 1–3, line 5, lines 5–9, …), `examples/javascript/js_example/templates/jquery.html` (lines 1–3, lines 4–9, line 27), `examples/javascript/js_example/templates/xhr.html` (lines 1–3, lines 5–6, line 7, …), `examples/tutorial/flaskr/templates/blog/index.html` (lines 1–3, line 5, lines 7–11, …) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D30 · Dependency Vulnerabilities
10 finding(s): 2 critical, 5 high, 3 medium, 0 low.
What to do
- Resolve the 5 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4), REDACTED. — One of this dimension's main actionable groups (5 issue-level).
- Resolve the 2 Critical vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 3 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 warning-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 20 of the 24 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
3/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 6 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
AX2 · Stateful singletons
AX3 · Project dependency cycles
AX4 · Dependency direction
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
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
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
What to do
- Add a health-check endpoint (a /health route) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add bandit, `semgrep --config=p/python`, or CodeQL's python pack as a CI step. What was searched, so you can tell an absence from a miss: the 5 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — .github/workflows/pre-commit.yaml:3
What to do
- Add a SAST step to CI running what this repository's stack ships: bandit, `semgrep --config=p/python`, or CodeQL's python pack — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
X12 · Unreachable branch
X25 · Inert configuration knob
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X3 · Exception handling
X30 · Support guard that admits what it rejects
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 96% | Exemplary | Solid. |
| Architecture | 97% | Exemplary | Strongest area. |
| Maturity | 62% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 61% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 83% | Strong | Solid. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 74 check(s) not relevant to this codebase
- AC1 Text alternatives — 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.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — 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 — ~6068 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.
- D12 Dependency Hygiene — Dependency currency not established — no declaration carries an exact pin to grade
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency does not read html yet; not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Python surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .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 — This repository is one build unit, `(repository root)` (7692 LoC, 61 module-visible types across 4 directories), within the size bounds. Not scored: a single unit of this size gives project cohesion nothing to grade.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- 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 none of the 3 signals this lens looks for
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- M4 Documentation accuracy — Not applicable: the 76 current-state document(s) make no claim of a kind M4 checks. 77 claim(s) of kinds M4 does not check were not checked (path 27, environment variable 50); M4 checks only links and versions and artefact counts.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the Python source (service entry point: src/flask/app.py:108 (Flask())
- 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
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X16 Unfloored truncation loop — not 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
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no C# was loaded; this repository's 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
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — 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
- 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
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 10 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 29 finding(s)
- REDACTED
- REDACTED
- REDACTED
- FileTooLong: flask/app.py src/flask/app.py
- FileTooLong: REDACTED REDACTED
- Low cohesion: App (LCOM4 10) src/flask/sansio/app.py:60
- Low cohesion: Scaffold (LCOM4 8) src/flask/sansio/scaffold.py:52
- Blueprint.register (cyclomatic 22) src/flask/sansio/blueprints.py:273
- Flask.make_response (cyclomatic 16) src/flask/app.py:1267
- Hotspot: src/flask/app.py src/flask/app.py:1267
- Blueprint.register (cognitive 24) src/flask/sansio/blueprints.py:273
- Flask.make_response (cognitive 23) src/flask/app.py:1267
- Flask.url_for (cognitive 22) src/flask/app.py:1145
- cli.find_best_app (cognitive 18) REDACTED:41
- cli.find_app_by_string (cognitive 18) REDACTED:120
- scaffold._find_package_path (cognitive 17) src/flask/sansio/scaffold.py:717
- Flask.preprocess_request (cognitive 16) src/flask/app.py:1409
- cli.load_dotenv (cognitive 16) REDACTED:698
- cli.routes_command (cognitive 16) REDACTED:1060
- REDACTED
- TooManyMethods: Flask src/flask/app.py:108
- Edited copy of a member (10 corresponding lines) src/flask/templating.py:124
- Edited copy of a member (7 corresponding lines) src/flask/app.py:85
- Edited copy of a member (25 corresponding lines) src/flask/app.py:364
- Duplicated block (20 lines × 2) src/flask/app.py:391
- Duplicated block (22 lines × 2) src/flask/app.py:415
- Duplicated block (23 lines × 4) src/flask/sansio/app.py:674
- Edited copy of a member (21 corresponding lines) examples/tutorial/flaskr/blog.py:63
- Duplicated block (13 lines × 2) examples/tutorial/flaskr/blog.py:64
Minor — 7 finding(s)
- Off-boarding risk: anonymized user #1
- No ADRs found REDACTED:81
- REDACTED
- REDACTED
- No ADRs
- No SAST .github/workflows/pre-commit.yaml:3
- Duplicated predicate src/flask/app.py:73
Minor — 1 finding(s)
- Dependency hygiene PARTLY measured — Python dependencies read, no exact pin to grade for currency
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-93573f11805f4fb29592ec59f0701f31/history.json --exit-code 0 --source . | 12 | 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-93573f11805f4fb29592ec59f0701f31/tree.json --exit-code 0 --source . | 6 | 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 . | 4 | 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 . | 10 | 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 | — |
| 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 |