Public scan — anyone with this URL can view this analysis. Sign up to track your own repos privately, run scheduled re-scans, and get AI fix prompts via your dashboard.
64 of your 113 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 1.48s · analysis 16.75s · 1.8 MB · GitHub API rate-limit (preflight)

pallets/flask

https://github.com/pallets/flask · scanned 2026-06-04 21:59 UTC (18 hours, 19 minutes ago) · 10 languages

250 findings (112 legacy + 138 scanner) 67th percentile · Python · small (2-20K LoC) Scanner says 68 (higher by 10)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 18 hours, 17 minutes ago · v2 · 181 findings from 2 sources. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 100.0 0.15 15.00
security_score 50.1 0.25 12.53
testing_score 100.0 0.20 20.00
documentation_score 73.0 0.15 10.95
practices_score 82.0 0.15 12.30
code_quality 64.0 0.10 6.40
Overall 1.00 77.2
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Fragile runtime 70 findings
What it is: Code that runs but breaks under predictable input — division by zero, missing keys, unbounded loops, off-by-one slicing.
Why it matters: Reaches production undetected because happy-path tests pass. First user with a weird input crashes the request.
How AI causes it: AI loves writing the happy path; doesn't probe edge cases unless explicitly asked.
Fix approach: Add property-based tests. Wrap external inputs with explicit validators. Use the framework's typed deserializer (Pydantic, attrs).
12 matching findings on this repo
  • medium Public web service has no security.txt .well-known/security.txt
  • medium [COMP001] High cognitive complexity: Function `explain_template_loading_attempt… src/flask/debughelpers.py:124
  • medium [COMP001] High cognitive complexity: Function `_dump_loader_info` has cognitive… src/flask/debughelpers.py:107
  • medium Bare except continues silently src/flask/cli.py:650
  • medium Bare except continues silently src/flask/cli.py:956
  • medium Bare except continues silently src/flask/app.py:1598
  • medium Bare except continues silently src/flask/app.py:1017
  • low [COMP001] High cognitive complexity: Function `register` has cognitive complexi… examples/tutorial/flaskr/auth.py:47
  • info [MINED050] Stub Only Function: Function declared but body is just pass, return … src/flask/views.py:83
  • info [MINED050] Stub Only Function: Function declared but body is just pass, return … src/flask/json/tag.py:75
  • info [MINED050] Stub Only Function: Function declared but body is just pass, return … src/flask/json/provider.py:47
  • info [MINED055] Npm Install No Lockfile: Production image runs npm install (resolves… .devcontainer/on-create-command.sh:5
View all fragile runtime findings →
Commented-out code 3 findings
What it is: Lines of source that were intentionally disabled but never deleted.
Why it matters: Git already remembers history — commented code rots, becomes wrong, and adds noise to diffs.
How AI causes it: AI sometimes comments out broken code instead of fixing it. Reviewers approve out of inertia.
Fix approach: Delete. Trust `git log`. If you really need to remember, save it in a notes file under `docs/`.
3 matching findings on this repo
  • info Commented-code block (5 lines) in src/flask/views.py:124
  • info Commented-code block (5 lines) in src/flask/app.py:346
  • info Commented-code block (6 lines) in src/flask/typing.py:73
View all commented-out code findings →
Config drift 7 findings
What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.
Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.
How AI causes it: AI writes new config from memory rather than reading the existing source.
Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.
7 matching findings on this repo
  • high Phantom test coverage: test_config_from_class tests/test_config.py:132
  • high Phantom test coverage: test_config_from_mapping tests/test_config.py:110
  • high Phantom test coverage: test_config_from_file_toml tests/test_config.py:38
  • high Phantom test coverage: test_config_from_file_json tests/test_config.py:31
  • high Phantom test coverage: test_config_from_object tests/test_config.py:25
  • high Phantom test coverage: test_config_from_pyfile tests/test_config.py:19
  • high Insecure pattern 'exec_used' in src/flask/config.py:209 src/flask/config.py:209
View all config drift findings →
For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.
For AI agents + API integrations
Email me when this repo regresses
Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.
API access

This page is publicly accessible at: https://repobility.com/scan/36f0902f-1f35-47f9-80e0-336870c8415f/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/36f0902f-1f35-47f9-80e0-336870c8415f/

Important — please don't re-submit the same URL repeatedly. The submission endpoint is idempotent: re-submitting the same git URL returns this same scan_token, not a new one. To re-scan this repo, sign up free and use the dashboard.