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.

aaronvstory/selfie-gen-ultimate

https://github.com/aaronvstory/selfie-gen-ultimate · scanned 2026-06-17 01:29 UTC (1 month, 2 weeks ago)

331 raw signals (0 security + 331 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 2 weeks ago · v2 · last Δ -13.4 (diff) · 292 actionable findings from 1 signal source. 39 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

77.8% cov · 292 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 1 Medium 27 Low 86 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 292 Crowd 0 Layer: Software 27 Security 1 Cicd 3 Quality 261

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 6 places
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 `_select_model_fetch_all_legacy` in kling_automatio…

View all legacy markers findings →

Commented-out code 178 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 (10 lines) in selfie_generator.py:28
info Commented-code block (5 lines) in dependency_health_check.py:19
info Commented-code block (5 lines) in path_utils.py:22
info Commented-code block (23 lines) in similarity_engine.py:626
info Commented-code block (9 lines) in outpaint_generator.py:602
info Commented-code block (7 lines) in model_schema_manager.py:389
info Commented-code block (7 lines) in create_icon.py:251
info Commented-code block (7 lines) in kling_automation_ui.py:64
info Commented-code block (7 lines) in model_metadata.py:231
info Commented-code block (10 lines) in face_similarity.py:137
info Commented-code block (5 lines) in vision_analyzer.py:195
info Commented-code block (6 lines) in api_keys.py:15

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

low Very large file: distribution/kling_gui/config_panel.py (2849 lines)
low Very large file: kling_gui/config_panel.py (2853 lines)
info Commented-code block (5 lines) in distribution/automation/config.py:34
info Commented-code block (5 lines) in distribution/kling_gui/config_panel.py:139
info Commented-code block (5 lines) in automation/config.py:34
info Commented-code block (5 lines) in kling_gui/config_panel.py:142

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/7680e3a6-562f-48df-9664-4056fd5d2693/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/7680e3a6-562f-48df-9664-4056fd5d2693/

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.