sqlalchemy/sqlalchemy

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.

126 of your 153 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 5.28s · analysis 22.31s · 20.6 MB · GitHub API rate-limit (preflight)

https://github.com/sqlalchemy/sqlalchemy · scanned 2026-06-05 14:32 UTC (5 days, 5 hours ago) · 10 languages

1278 raw signals (150 security + 1128 graph) 35th percentile · Python · huge (>500K LoC) System graph score 77 (lower by 3)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 days, 5 hours ago · v2 · 586 actionable findings from 2 signal sources. 127 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

100.0% cov · 536 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	85.0	0.15	12.75
`security_score`	60.9	0.25	15.22
`testing_score`	97.0	0.20	19.40
`documentation_score`	85.0	0.15	12.75
`practices_score`	75.0	0.15	11.25
`code_quality`	30.6	0.10	3.06
Overall		1.00	74.4

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 2 High 12 Medium 6 Low 369 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 50 System graph 536 Crowd 0 Layer: Security 10 Quality 518 Cicd 2 Software 54 Api 1 Frontend 1

Exclude dismissed / FP Exclude test files

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.

Duplicates & near-duplicates 4 findings

What it is: Same function copy-pasted into multiple modules with minor variations.

Why it matters: Each copy drifts independently — bug fixes apply to one, miss the others.

How AI causes it: AI completes the same pattern in each file rather than refactoring to a shared helper.

Fix approach: Extract the duplicated logic into the most general module both call sites already import. Add tests at the helper level.

4 matching findings on this repo

low Near-duplicate function bodies in 2 places repo-level
low Near-duplicate function bodies in 7 places
low Near-duplicate function bodies in 5 places
low Near-duplicate function bodies in 3 places repo-level

View all duplicates & near-duplicates findings →

Legacy markers 8 findings

What it is: TODO, FIXME, XXX, HACK comments. Often indicate a known-broken path the author meant to fix.

Why it matters: Each marker is an unfinished thought. Production code shouldn't ship with debt that's documented but not tracked.

How AI causes it: AI mirrors the style of the codebase, so existing TODOs propagate into new code.

Fix approach: Convert each into a ticket. Delete the comment when the ticket lands. Use a pre-commit hook to block new TODOs without an issue link.

8 matching findings on this repo

low Old/deprecated-named symbol `test_labeling_for_unnamed_legacy` in test/ext/test…
low Old/deprecated-named symbol `test_no_uniquing_cols_legacy` in test/orm/test_fro…
low Old/deprecated-named symbol `test_criteria_post_replace_legacy` in test/orm/tes…
low Old/deprecated-named symbol `use_legacy` in test/orm/test_joins.py:237
low Old/deprecated-named symbol `test_query_cols_legacy` in lib/sqlalchemy/sql/elem…
low Old/deprecated-named symbol `_init_legacy` in lib/sqlalchemy/engine/reflection.…
low Old/deprecated-named symbol `_wrap_fn_for_legacy` in lib/sqlalchemy/event/attr.…
low Old/deprecated-named symbol `_wrap_fn_for_legacy` in lib/sqlalchemy/event/legac…

View all legacy markers findings →

Commented-out code 158 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/`.

12 matching findings on this repo

info Commented-code block (8 lines) in test/requirements.py:999
info Commented-code block (5 lines) in test/base/test_result.py:604
info Commented-code block (6 lines) in test/ext/test_associationproxy.py:4004
info Commented-code block (10 lines) in test/ext/test_baked.py:351
info Commented-code block (5 lines) in test/ext/asyncio/test_session.py:68
info Commented-code block (5 lines) in test/ext/asyncio/test_engine.py:943
info Commented-code block (5 lines) in test/sql/test_roles.py:329
info Commented-code block (7 lines) in test/sql/test_resultset.py:2517
info Commented-code block (10 lines) in test/sql/test_compiler.py:914
info Commented-code block (5 lines) in test/sql/test_lambdas.py:563
info Commented-code block (5 lines) in test/sql/test_insert.py:601
info Commented-code block (5 lines) in test/sql/test_returning.py:1454

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

low Stub function `get_current_test_name` (body is just `pass`/`return`) — lib/sqla…

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/32a48efe-ddc4-452c-a79e-2a21ab375140/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/32a48efe-ddc4-452c-a79e-2a21ab375140/

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.