keras-team/keras

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.

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

Scan timing: clone 6.82s · analysis 27.02s · 11.5 MB · GitHub preflight 471ms

https://github.com/keras-team/keras · scanned 2026-06-05 09:00 UTC (5 days, 19 hours ago) · 10 languages

678 raw signals (224 security + 454 graph) 63rd percentile · Python · large (100-500K LoC) System graph score 91 (lower by 11)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

88.9% cov · 199 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	60.0	0.15	9.00
`security_score`	81.0	0.25	20.25
`testing_score`	97.0	0.20	19.40
`documentation_score`	97.0	0.15	14.55
`practices_score`	81.0	0.15	12.15
`code_quality`	47.7	0.10	4.77
Overall		1.00	80.1

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 2 High 20 Medium 5 Low 113 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 69 System graph 199 Crowd 0 Layer: Security 10 Quality 231 Software 18 Cicd 5 Api 1 Frontend 3

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

11 matching findings on this repo

low Near-duplicate function bodies in 11 places
low Near-duplicate function bodies in 3 places repo-level
low Near-duplicate function bodies in 6 places
low Near-duplicate function bodies in 2 places repo-level
low Near-duplicate function bodies in 19 places
low Near-duplicate function bodies in 9 places repo-level
low Near-duplicate function bodies in 17 places
low Near-duplicate function bodies in 14 places repo-level
low Near-duplicate function bodies in 12 places
low Near-duplicate function bodies in 5 places
low Near-duplicate function bodies in 22 places

View all duplicates & near-duplicates findings →

Legacy markers 7 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.

7 matching findings on this repo

high [COMP001] High cognitive complexity: Function `create_legacy_directory` has cog… api_gen.py:36
low Very large file: keras/src/legacy/backend.py (2292 lines)
low Very large file: keras/src/legacy/preprocessing/image.py (1884 lines)
info Commented-code block (6 lines) in keras/src/legacy/backend.py:1464
info Commented-code block (9 lines) in keras/src/legacy/preprocessing/image.py:1856
info Commented-code block (5 lines) in keras/src/legacy/saving/serialization.py:171
low Stub function `get` (body is just `pass`/`return`) — keras/src/legacy/saving/se…

View all legacy markers findings →

Commented-out code 84 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 (11 lines) in integration_tests/model_visualization_test.p…
info Commented-code block (6 lines) in keras/src/losses/losses_test.py:2087
info Commented-code block (7 lines) in keras/src/models/model.py:895
info Commented-code block (5 lines) in keras/src/models/cloning_test.py:266
info Commented-code block (6 lines) in keras/src/models/cloning.py:173
info Commented-code block (5 lines) in keras/src/models/functional.py:526
info Commented-code block (5 lines) in keras/src/trainers/compile_utils_test.py:184
info Commented-code block (5 lines) in keras/src/trainers/trainer.py:1133
info Commented-code block (5 lines) in keras/src/trainers/compile_utils.py:317
info Commented-code block (13 lines) in keras/src/trainers/data_adapters/array_slici…
info Commented-code block (5 lines) in keras/src/testing/test_case.py:494
info Commented-code block (5 lines) in keras/src/ops/linalg_test.py:389

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/4329732e-5793-407d-8354-c73b8f78756d/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/4329732e-5793-407d-8354-c73b8f78756d/

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.