pallets/flask

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.

https://github.com/pallets/flask.git · scanned 2026-05-16 15:07 UTC (1 day, 6 hours ago) · 10 languages

74 findings (3 legacy + 71 scanner) 95th percentile · Python · small (2-20K LoC) Scanner says 68 (higher by 20)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 day, 11 hours ago · v1 · 74 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

{# ── 2026-05-17 R27 #5: score breakdown panel ────────────────────── Surfaces the score_breakdown JSON that's been silently stored on Repository for months. Turns hidden math into a trust signal. #}

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 1 finding

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).

1 matching finding on this repo

medium Public web service has no security.txt .well-known/security.txt

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 1 finding

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.

1 matching finding on this repo

high Insecure pattern 'exec_used' in src/flask/config.py:209 src/flask/config.py:209

View all config drift findings →

{# ── 2026-05-17 Round 14: AI-agent bridge footer ────────────────────── Discoverability: the /agents/voting/ guide + MCP manifest exist but aren't linked from anywhere users actually land. Small, opt-in footer. #}

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/6d775c59-9374-4383-9b10-add804ee2792/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/6d775c59-9374-4383-9b10-add804ee2792/

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.