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

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
Combined
70.4
/100
Security checks
70
0 findings
System graph
70
100.0% cov · 93 findings
Critical
0
click to filter
Agents
10
0 votes
Crowd
0
reported
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
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 70.4/100 with 100.0% coverage. It contains 722 nodes across 27 cross-layer flows, written primarily in mixed languages. Engine surfaced 106 findings — concentrated in quality (44), api (25), software (24). Risk profile is high: 0 critical, 10 high, 6 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 81 of 93 actionable findings. 106 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.

high System graph security auth conf 1.00 Flask mutation route `api_save_pricing` without `@login_required` — wsgi.py:687
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
wsgi.py:687 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `apollo_phone_callback` without `@login_required` — wsgi.py:1520
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
wsgi.py:1520 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `cancel` without `@login_required` — wsgi.py:1474
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
wsgi.py:1474 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `db_clear_all` without `@login_required` — wsgi.py:583
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
wsgi.py:583 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `generate_city` without `@login_required` — wsgi.py:1044
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
wsgi.py:1044 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `generate_multi` without `@login_required` — wsgi.py:1224
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
wsgi.py:1224 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `generate` without `@login_required` — wsgi.py:839
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
wsgi.py:839 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `login` without `@login_required` — wsgi.py:170
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
wsgi.py:170 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `logout` without `@login_required` — wsgi.py:203
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
wsgi.py:203 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `refresh_credits` without `@login_required` — wsgi.py:480
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
wsgi.py:480 securityAuth flask unauth route
medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in index_legacy.html:674
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
index_legacy.html:674 Direct innerhtml assignment
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — rate_limiter.py:49
`requests.post(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — V5.py:12972
`requests.post(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph cicd CI/CD security conf 1.00 No CI/CD pipelines detected
No GitHub Actions, GitLab CI, or CircleCI configs found. Without CI you can't gate deploys on tests/lints.
CI/CD securityCoverage
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 12 placeholder/mock markers across 7 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
low System graph quality Integrity conf 1.00 8 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `ATC_SWEEP_MAX`, `CLEAR_DB_ON_STARTUP`, `HUNTER_API_KEY`, `PAID_ONLY_ALL`, `PORT`, `SEMRUSH_DB`, `SMART_KEYWORDS`, `WEBHOOK_BASE_URL`. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.
config drift
low System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, ci. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 56 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 Tests conf 1.00 Low test-to-source ratio
5 tests / 26 src (ratio 0.19).
low System graph quality Integrity conf 1.00 10 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: db.py:list_page, db.py:list_page 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.
10 occurrences
repo-level (10 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 5 occurrences Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: wsgi.py:log_cb, wsgi.py:log_cb, wsgi.py:log_cb 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.
5 occurrences
repo-level (5 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 5 places
Functions with the same first-5-line body hash: wsgi.py:progress_cb, wsgi.py:progress_cb, wsgi.py:progress_cb, V5.py:progress_cb 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 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 `_archive_legacy` in build_master_keyword_bank.py:9
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 `test_pricing_math_and_monthly_unused` in tests/test_pipeline_smoke.py:260
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: advertiser_url
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
google_ads_transparency.py:71
low System graph software Dead code conf 1.00 Possibly dead Python function: bank_stats
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
keyword_bank.py:327
low System graph software Dead code conf 1.00 Possibly dead Python function: deduplicate_leads
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
utils.py:219
low System graph software Dead code conf 1.00 Possibly dead Python function: do_login
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
auth.py:165
low System graph software Dead code conf 1.00 Possibly dead Python function: extract_domain_from_email
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
utils.py:96
low System graph software Dead code conf 1.00 Possibly dead Python function: has_keywords_for
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
secondary_keywords.py:31
low System graph software Dead code conf 1.00 Possibly dead Python function: infer_personal_email
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
V5.py:4436
low System graph software Dead code conf 1.00 Possibly dead Python function: is_available
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
db.py:173
low System graph software Dead code conf 1.00 Possibly dead Python function: is_decision_maker
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
V5.py:1979
low System graph software Dead code conf 1.00 Possibly dead Python function: is_disposable_email
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
utils.py:77
low System graph software Dead code conf 1.00 Possibly dead Python function: is_master_known
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
lead_pool.py:110
low System graph software Dead code conf 1.00 Possibly dead Python function: is_valid_domain
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
utils.py:177
low System graph software Dead code conf 1.00 Possibly dead Python function: is_valid_phone
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
utils.py:49
low System graph software Dead code conf 1.00 Possibly dead Python function: main_gui
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
V5.py:11794
low System graph software Dead code conf 1.00 Possibly dead Python function: name_to_initials
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
utils.py:127
low System graph software Dead code conf 1.00 Possibly dead Python function: pool_error
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
db.py:178
low System graph software Dead code conf 1.00 Possibly dead Python function: progress_cb
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
wsgi.py:1282
low System graph software Dead code conf 1.00 Possibly dead Python function: progress_cb
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
V5.py:12674
low System graph software Dead code conf 1.00 Possibly dead Python function: read_leads_csv
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
utils.py:209
low System graph software Dead code conf 1.00 Possibly dead Python function: slug_to_name
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
utils.py:137
low System graph software Dead code conf 1.00 Possibly dead Python function: snapshot
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
rate_limiter.py:105
low System graph software Dead code conf 1.00 Possibly dead Python function: to_dict
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
auth.py:68
low System graph software Dead code conf 1.00 Possibly dead Python function: verify_credentials
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
auth.py:152
low System graph software Dead code conf 1.00 Possibly dead Python function: write_leads_csv
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
utils.py:195
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
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — user-flow-chart/build-preview.js:67
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph api Wiring conf 1.00 Unused endpoint: ANY /
`wsgi.py` declares `ANY /` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /<path:filename>
`wsgi.py` declares `ANY /<path:filename>` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /admin
`wsgi.py` declares `ANY /admin` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /admin/runs
`wsgi.py` declares `ANY /admin/runs` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /admin/users
`wsgi.py` declares `ANY /admin/users` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/au-cities
`wsgi.py` declares `ANY /api/au-cities` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/credits
`wsgi.py` declares `ANY /api/credits` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/credits/refresh
`wsgi.py` declares `ANY /api/credits/refresh` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/db/clear-all
`wsgi.py` declares `ANY /api/db/clear-all` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/db/debug
`wsgi.py` declares `ANY /api/db/debug` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/db/master-leads
`wsgi.py` declares `ANY /api/db/master-leads` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/db/run-history
`wsgi.py` declares `ANY /api/db/run-history` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/master-stats
`wsgi.py` declares `ANY /api/master-stats` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/pricing
`wsgi.py` declares `ANY /api/pricing` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/test-google-places
`V5.py` declares `ANY /api/test-google-places` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /apollo-phone-callback
`wsgi.py` declares `ANY /apollo-phone-callback` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /cancel
`wsgi.py` declares `ANY /cancel` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /download-partial/<job_id>
`wsgi.py` declares `ANY /download-partial/<job_id>` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /generate
`wsgi.py` declares `ANY /generate` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /generate-city
`wsgi.py` declares `ANY /generate-city` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /generate-multi
`wsgi.py` declares `ANY /generate-multi` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /industries
`wsgi.py` declares `ANY /industries` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /login
`wsgi.py` declares `ANY /login` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /logout
`wsgi.py` declares `ANY /logout` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /whoami
`wsgi.py` declares `ANY /whoami` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph quality Complexity conf 1.00 Very large file: city_pipeline.py (2021 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: user-flow-chart/UserFlowChart.jsx (1024 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: V5.py (13036 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: wsgi.py (1550 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
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.