affaan-m/ECC

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.

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

Scan timing: clone 14.92s · analysis 5.83s · 42.6 MB · GitHub API rate-limit (preflight)

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

681 findings (115 legacy + 566 scanner) 11/13 scanners ran 86th percentile · Javascript · large (100-500K LoC) Scanner says 69 (higher by 21)

File as issue Image v2 schema

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 day, 9 hours ago · v2 · 398 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

100.0% cov · 283 gaps

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	85.0	0.15	12.75
`security_score`	100.0	0.25	25.00
`testing_score`	100.0	0.20	20.00
`documentation_score`	100.0	0.15	15.00
`practices_score`	81.0	0.15	12.15
`code_quality`	55.0	0.10	5.50
Overall		1.00	90.4

security_score may be inflated — optional security scanners were skipped on this fast scan

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 2 High 80 Medium 9 Low 259 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 115 9-layer 283 Crowd 0 Layer: Quality 158 Security 6 Software 38 Api 1 Frontend 191 Network 1 Cicd 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.

Fragile runtime 108 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 [MINED111] Bare except continues silently: Bare `except:` (or `except Exception… src/llm/tools/executor.py:54
medium [MINED111] Bare except continues silently: Bare `except:` (or `except Exception… skills/continuous-learning-v2/scripts/instinct-cl…:762
medium [MINED111] Bare except continues silently: Bare `except:` (or `except Exception… skills/continuous-learning-v2/scripts/instinct-cl…:494
medium [MINED111] Bare except continues silently: Bare `except:` (or `except Exception… ecc_dashboard.py:816
medium [SEC127] AI agent stub — TODO: implement / pass placeholder body: Function body… src/llm/core/interface.py:29
medium [SEC136] AI-typical over-broad exception handler swallowing all errors: Catch-a… scripts/preview-pack-smoke.js:169
medium [COMP001] High cognitive complexity: Function `extract_pptx` has cognitive comp… skills/frontend-slides/scripts/extract-pptx.py:18
low Duplicated implementation block across source files scripts/release-approval-gate.js:101
low Duplicated implementation block across source files scripts/preview-pack-smoke.js:129
low Duplicated implementation block across source files scripts/preview-pack-smoke.js:116
low Duplicated implementation block across source files scripts/platform-audit.js:228
low Duplicated implementation block across source files scripts/platform-audit.js:188

View all fragile runtime findings →

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

2 matching findings on this repo

low Stray `console.log` in TS/JS — tests/docs/legacy-artifact-inventory.test.js:16
low Legacy-named symbol `input_copy` in src/llm/tools/executor.py:81

View all legacy markers findings →

Commented-out code 29 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 (5 lines) in tests/plugin-manifest.test.js:287
info Commented-code block (5 lines) in tests/scripts/check-unicode-safety.test.js:112
info Commented-code block (5 lines) in tests/scripts/setup-package-manager.test.js:1…
info Commented-code block (5 lines) in tests/scripts/skill-create-output.test.js:505
info Commented-code block (6 lines) in tests/lib/session-bridge.test.js:138
info Commented-code block (5 lines) in tests/lib/utils.test.js:1045
info Commented-code block (5 lines) in tests/lib/session-manager.test.js:2499
info Commented-code block (6 lines) in tests/lib/package-manager.test.js:1539
info Commented-code block (5 lines) in tests/lib/install-targets.test.js:1055
info Commented-code block (6 lines) in tests/lib/session-aliases.test.js:1333
info Commented-code block (5 lines) in tests/hooks/evaluate-session.test.js:193
info Commented-code block (6 lines) in tests/hooks/hooks.test.js:6017

View all commented-out code findings →

Config drift 14 findings

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.

12 matching findings on this repo

high [MINED106] Phantom test coverage: test_rejects_config_with_keyword_options: Tes… tests/test_builder.py:43
low File has no detected symbols: commitlint.config.js
low File has no detected symbols: eslint.config.js
low Stray `console.log` in TS/JS — tests/codex-config.test.js:14
low Stray `console.log` in TS/JS — tests/opencode-config.test.js:14
low Stray `console.log` in TS/JS — tests/docs/configure-ecc-install-paths.test.js:21
low Stray `console.log` in TS/JS — tests/lib/install-config.test.js:19
low Stray `console.log` in TS/JS — tests/lib/mcp-config.test.js:10
low Stray `console.log` in TS/JS — tests/hooks/config-protection.test.js:16
low Stray `console.log` in TS/JS — scripts/codex/merge-mcp-config.js:121
low Stray `console.log` in TS/JS — scripts/codex/merge-codex-config.js:39
low Very large file: ecc2/src/config/mod.rs (1806 lines)

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/cee07bfa-32f3-4702-be86-74f070e7d41b/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/cee07bfa-32f3-4702-be86-74f070e7d41b/

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.