aws/deep-learning-containers

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.

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

Scan timing: clone 1.98s · analysis 67.9s · 3.8 MB · GitHub API rate-limit (preflight)

https://github.com/aws/deep-learning-containers · scanned 2026-06-05 21:30 UTC (4 days, 11 hours ago) · 10 languages

1102 raw signals (318 security + 784 graph) 40th percentile · Python · small (2-20K LoC) System graph score 70 (lower by 8)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 11 hours ago · v2 · 198 actionable findings from 2 signal sources. 489 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 · 63 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	60.0	0.15	9.00
`security_score`	4.0	0.25	1.00
`testing_score`	100.0	0.20	20.00
`documentation_score`	100.0	0.15	15.00
`practices_score`	74.0	0.15	11.10
`code_quality`	62.8	0.10	6.28
Overall		1.00	62.4

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 42 Medium 60 Low 54 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 135 System graph 63 Crowd 0 Layer: Software 96 Cicd 12 Security 8 Quality 55 Network 8 Hardware 17 Frontend 1 Api 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 2 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.

2 matching findings on this repo

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

View all duplicates & near-duplicates findings →

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

2 matching findings on this repo

info Commented-code block (5 lines) in test/efa/test_efa.py:31
info Commented-code block (6 lines) in test/efa/scripts/toy_proxy_server.py:96

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/ef7e74e6-7da3-4a12-9d46-e87eac765138/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/ef7e74e6-7da3-4a12-9d46-e87eac765138/

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.