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.

TheNavinHR/atlas-loom-9f4c7a2e1b

https://github.com/TheNavinHR/atlas-loom-9f4c7a2e1b · scanned 2026-06-16 00:34 UTC (2 months, 2 weeks ago)

141 raw signals (0 security + 141 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 2 weeks ago · v1 · 125 actionable findings from 1 signal source. 16 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 · 125 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 2 Medium 15 Low 87 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 125 Crowd 0 Layer: Software 20 Frontend 1 Security 3 Cicd 1 Quality 98 Api 2

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 3 places repo-level
low Near-duplicate function bodies in 5 places
low Near-duplicate function bodies in 2 places repo-level
low Near-duplicate function bodies in 4 places repo-level

View all duplicates & near-duplicates findings →

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

3 matching findings on this repo

low Old/deprecated-named symbol `test_speech_floor_boundary_exact_value_matches_leg…
low Old/deprecated-named symbol `test_session_mode_missing_cli_key_falls_back_to_le…
low Old/deprecated-named symbol `_wrap_legacy` in src/hsext_v4/gui/main_window.py:6…

View all legacy markers findings →

Commented-out code 19 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/test_reference_offset.py:136
info Commented-code block (5 lines) in tests/test_visual_spacing.py:26
info Commented-code block (5 lines) in dev/scripts/ab_cudagraph_e131.py:56
info Commented-code block (8 lines) in dev/scripts/openai_ocr_compat_server.py:265
info Commented-code block (5 lines) in dev/scripts/build_radical_leak_map.py:29
info Commented-code block (6 lines) in src/hsext_v4/gui/tabs/_pipeline_binding.py:547
info Commented-code block (5 lines) in src/hsext_v4/roi/autopilot.py:58
info Commented-code block (8 lines) in src/hsext_v4/speaker/pipeline.py:112
info Commented-code block (6 lines) in src/hsext_v4/pipeline/run_preset.py:99
info Commented-code block (6 lines) in src/hsext_v4/core/shadow_boundary_probe.py:115
info Commented-code block (7 lines) in src/hsext_v4/core/visual_spacing.py:39
info Commented-code block (5 lines) in src/hsext_v4/core/shadow_boundary.py:66

View all commented-out code findings →

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

6 matching findings on this repo

high Insecure pattern 'tls_verify_false' in src/hsext_v4/core/pipeline_config/store.… src/hsext_v4/core/pipeline_config/store.py:161
low Very large file: src/hsext_v4/gui/tabs/pipeline_config_tab.py (1628 lines)
low Old/deprecated-named symbol `model_copy` in src/hsext_v4/gui/tabs/pipeline_conf…
info Commented-code block (6 lines) in src/hsext_v4/core/pipeline_config/models.py:2…
low Old/deprecated-named symbol `model_copy` in src/hsext_v4/core/pipeline_config/s…
low Old/deprecated-named symbol `model_copy` in src/hsext_v4/core/pipeline_config/i…

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/ec81e432-e2fb-49d7-bb3a-8e66a49244d6/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/ec81e432-e2fb-49d7-bb3a-8e66a49244d6/

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.