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.
Sign up free Scan another repo

vemchance/meme_conditions

https://github.com/vemchance/meme_conditions · scanned 2026-06-16 00:48 UTC (2 months, 1 week ago)

33 raw signals (0 security + 33 graph)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 30 actionable findings from 1 signal source. 3 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
83.2
/100
Security checks
83
0 findings
System graph
83
66.7% cov · 30 findings
Critical
0
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: severity: low × excluding tests × Reset all
Severity: Critical 0 High 0 Medium 6 Low 21 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 30 Crowd 0 Layer: Software 6 Frontend 1 Security 1 Cicd 1 Quality 21
Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.
Scan summary Repository scanned at 83.2/100 with 66.7% coverage. It contains 189 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 33 findings — concentrated in quality (22), software (8), frontend (1). Risk profile is low: 0 critical, 0 high, 6 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 21 of 30 actionable findings. 33 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 47 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: scripts/04c_block_b.py:grid_row, scripts/04d_block_c.py:grid_row This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they're separate.
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: scripts/exhibit_pull.py:forward, scripts/04g_expansion.py:forward, scripts/04f_denoise.py:forward This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they're s…
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 4 places
Functions with the same first-5-line body hash: scripts/03_extract_glosses.py:emit, scripts/02_type_profile.py:emit, scripts/04_analysis.py:emit, scripts/01_gate.py:emit This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate o…
duplicatesduplication
low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 5 places
Functions with the same first-5-line body hash: scripts/04c_block_b.py:log, scripts/04e_flag_resolution.py:log, scripts/04d_block_c.py:log, scripts/04g_expansion.py:log This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or…
2 occurrences
repo-level (2 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 6 places
Functions with the same first-5-line body hash: scripts/04c_block_b.py:emit, scripts/04b_block_a.py:emit, scripts/04e_flag_resolution.py:emit, scripts/04d_block_c.py:emit This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate …
duplicatesduplication
low System graph quality License conf 1.00 No license file detected
No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.
Repo hardeningGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `03b_taxonomy_v2` in scripts/03b_taxonomy_v2.py:1
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `label_v2` in scripts/04_analysis.py:4
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `label_v2` in scripts/04c_block_b.py:339
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `label_v2` in scripts/05b_exhibits.py:156
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `label_v2` in scripts/exhibit_pull.py:188
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `watermark_candidates_v2` in scripts/03_extract_glosses.py:10
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph software Dead code conf 1.00 Possibly dead Python function: complement_head
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/03_extract_glosses.py:195
low System graph software Dead code conf 1.00 3 occurrences Possibly dead Python function: forward
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
3 files, 3 locations
scripts/04f_denoise.py:117
scripts/04g_expansion.py:127
scripts/exhibit_pull.py:79
low System graph software Dead code conf 1.00 Possibly dead Python function: match_cues
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/01_gate.py:157
low System graph software Dead code conf 1.00 Possibly dead Python function: norm_types
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/03_extract_glosses.py:226
low System graph software Dead code conf 1.00 Possibly dead Python function: norm_types
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/02_type_profile.py:130
low System graph software Dead code conf 1.00 Possibly dead Python function: strip_text
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/04_analysis.py:267
low System graph quality Docs conf 1.00 README lacks setup or run instructions
A README exists, but it does not contain common install/setup/run markers. This matches a frequent generated-code pattern: UI is present, operational handoff is thin.
ReadmeRepo hardeningGenerated repo pattern
low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence
The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.
Git historyGenerated repo pattern
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/53ae2e82-986c-4ba3-8d20-e3ae0ab342b7/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/53ae2e82-986c-4ba3-8d20-e3ae0ab342b7/

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.