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.
Sign up free Scan another repo
75 of your 119 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 4.59s · analysis 2.56s · 24.8 MB · GitHub API rate-limit (preflight)

microsoft/markitdown

https://github.com/microsoft/markitdown · scanned 2026-06-04 04:10 UTC (1 day, 9 hours ago) · 10 languages

223 findings (115 legacy + 108 scanner) 69th percentile · Python · small (2-20K LoC) Scanner says 89 (lower by 12)

File as issue Image v2 schema
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 day, 9 hours ago · v2 · 169 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
Combined
83.0
/100
Repobility
77
115 legacy
9-layer
89
88.9% cov · 54 gaps
Critical
0
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 55.0 0.15 8.25
security_score 97.7 0.25 24.43
testing_score 85.0 0.20 17.00
documentation_score 80.0 0.15 12.00
practices_score 75.0 0.15 11.25
code_quality 43.6 0.10 4.36
Overall 1.00 77.3
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 89 Medium 9 Low 59 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 115 9-layer 54 Crowd 0 Layer: Cicd 6 Quality 115 Software 42 Api 1 Hardware 3 Frontend 1 Security 1

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 103 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 [SEC136] AI-typical over-broad exception handler swallowing all errors: Catch-a… packages/markitdown/src/markitdown/converters/_ll…:22
  • medium [SEC136] AI-typical over-broad exception handler swallowing all errors: Catch-a… packages/markitdown/src/markitdown/converters/_im…:110
  • medium [ERR001] Silent Exception Swallowing: Silently swallowing all exceptions hides … packages/markitdown-ocr/src/markitdown_ocr/_xlsx_…:211
  • medium [ERR001] Silent Exception Swallowing: Silently swallowing all exceptions hides … packages/markitdown-ocr/src/markitdown_ocr/_pptx_…:121
  • medium [ERR001] Silent Exception Swallowing: Silently swallowing all exceptions hides … packages/markitdown-ocr/src/markitdown_ocr/_docx_…:155
  • medium [SEC123] Production stack trace / debug output exposed: Debug mode left on in p… packages/markitdown-mcp/src/markitdown_mcp/__main…:129
  • medium Bare except continues silently packages/markitdown/src/markitdown/converter_util…:150
  • medium Bare except continues silently packages/markitdown/src/markitdown/converters/_pp…:262
  • medium Mutable default argument in `__init__` (list) packages/markitdown/src/markitdown/converters/_do…:133
  • medium Bare except continues silently packages/markitdown/src/markitdown/converters/_im…:112
  • medium Bare except continues silently packages/markitdown/src/markitdown/converters/_pd…:576
  • medium Bare except continues silently packages/markitdown/src/markitdown/converters/_rs…:176
View all fragile runtime findings →
Commented-out code 1 finding
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/`.
1 matching finding on this repo
  • info Commented-code block (5 lines) in packages/markitdown/src/markitdown/converters…
View all commented-out code 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/dbdaf599-dde3-40fb-aea4-0a5672c27966/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/dbdaf599-dde3-40fb-aea4-0a5672c27966/

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.