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.

rajtrafficradius/LEAD_FORGE_LEAD_GENERATOR

https://github.com/rajtrafficradius/LEAD_FORGE_LEAD_GENERATOR · scanned 2026-06-15 23:46 UTC (2 months, 4 weeks ago)

106 raw signals (0 security + 106 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 10 Medium 6 Low 65 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 93 Crowd 0 Layer: Software 24 Frontend 1 Security 11 Cicd 1 Quality 31 Api 25

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

3 matching findings on this repo

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

View all duplicates & near-duplicates 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

medium Insecure pattern 'direct_innerhtml_assignment' in index_legacy.html:674 index_legacy.html:674
low Old/deprecated-named symbol `_archive_legacy` in build_master_keyword_bank.py:9

View all legacy markers findings →

Commented-out code 11 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/`.

11 matching findings on this repo

info Commented-code block (5 lines) in keyword_bank.py:110
info Commented-code block (5 lines) in google_ads_transparency.py:397
info Commented-code block (9 lines) in db.py:130
info Commented-code block (5 lines) in auth.py:87
info Commented-code block (5 lines) in city_pipeline.py:51
info Commented-code block (5 lines) in wsgi.py:165
info Commented-code block (7 lines) in V5.py:73
info Commented-code block (5 lines) in test_semrush_budget.py:81
info Commented-code block (13 lines) in build_master_keyword_bank.py:11
info Commented-code block (5 lines) in build_ecom_index.py:47
info Commented-code block (8 lines) in google_places_intent.py:72

View all commented-out code 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/1f39d77c-584a-44ca-a3ea-8ef91543712c/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/1f39d77c-584a-44ca-a3ea-8ef91543712c/

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.