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.

vradulthub-cloud/eclatech-hub

https://github.com/vradulthub-cloud/eclatech-hub · scanned 2026-06-16 00:53 UTC (2 months, 1 week ago)

407 raw signals (87 security + 320 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 309 actionable findings from 2 signal sources. 316 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 · 301 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 2 High 67 Medium 30 Low 120 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 8 System graph 301 Crowd 0 Layer: Quality 154 Security 66 Software 29 Frontend 2 Network 1 Hardware 2 Cicd 2 Api 53

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 1 finding

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.

1 matching finding on this repo

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

View all duplicates & near-duplicates findings →

Legacy markers 1 finding

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.

1 matching finding on this repo

low Old/deprecated-named symbol `is_complete_legacy` in api/routers/compliance.py:8…

View all legacy markers findings →

Commented-out code 88 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 backfill_storyboard_from_photos.py:271
info Commented-code block (5 lines) in search_apps_script.js:1
info Commented-code block (5 lines) in scan_mega.py:39
info Commented-code block (6 lines) in cta_primitives.py:18
info Commented-code block (6 lines) in scrape_revenue_data.py:212
info Commented-code block (5 lines) in migrate_vrh_progress.py:39
info Commented-code block (5 lines) in s4_client.py:485
info Commented-code block (9 lines) in redesign_comp_sheet.py:29
info Commented-code block (5 lines) in audio_post/director_studio/backend/config.py:…
info Commented-code block (5 lines) in hub/tests/e2e/compliance.spec.ts:272
info Commented-code block (5 lines) in hub/tests/e2e/revenue.spec.ts:74
info Commented-code block (5 lines) in hub/tests/e2e/scripts.spec.ts:116

View all commented-out code findings →

Config drift 3 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.

3 matching findings on this repo

high Agent instruction/config may expose a secret: .claude/launch.json .claude/launch.json:15
info Commented-code block (5 lines) in audio_post/director_studio/backend/config.py:…
low Old/deprecated-named symbol `title_card_style_v2` in api/config.py:79

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/ccd8733d-d05d-4d7f-8276-27da5efd3737/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/ccd8733d-d05d-4d7f-8276-27da5efd3737/

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.