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

waiff/sreality

https://github.com/waiff/sreality · scanned 2026-06-16 00:54 UTC (2 months, 1 week ago)

343 raw signals (97 security + 246 graph)

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

Complete repo analysis

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

JSON
Combined
51.3
/100
Security checks
51
8 findings
System graph
51
100.0% cov · 224 findings
Critical
2
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 2 High 40 Medium 17 Low 107 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 8 System graph 224 Crowd 0 Layer: Quality 111 Security 12 Software 9 Frontend 15 Hardware 6 Cicd 2 Api 77
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 51.3/100 with 100.0% coverage. It contains 6507 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 246 findings — concentrated in quality (121), api (77), frontend (15). Risk profile is high: 0 critical, 37 high, 18 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 166 of 232 actionable findings. 428 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.

critical Security checks quality Practices conf 0.82 3 occurrences Foundry mined mock as real or placeholder: waiff/sreality
Graph query export: Mock, sample, placeholder, or self-attested behavior treated as real Query id: mock_as_real_or_placeholder Query type: motif_query Intent: Hard negatives for fake completeness and missing real data paths. Motif: mock_as_real_or_placeholder Training usage: hard_negative Graph gol…
3 occurrences
repo-level (3 hits)
critical Security checks security auth conf 0.78 8 occurrences Foundry mined security auth guardrail gaps: waiff/sreality
Graph query export: Security/auth changes without enough guardrails Query id: security_auth_guardrail_gaps Query type: motif_query Intent: Assumption-check security/auth examples requiring stronger tests or CI. Motif: security_auth_without_guardrails Training usage: assumption_check Graph gold labe…
8 occurrences
repo-level (8 hits)
high Security checks quality Practices conf 0.84 3 occurrences Foundry mined bad chains: waiff/sreality
Comment chain pattern product: bad_chains Repo: waiff/sreality Thread: waiff/sreality#448 Outcome: claimed_resolved_unverified Thread label: thread_has_human_issue_and_fix_context Source graph label: source_backed_multi_signal_graph Reasons: source_graph_has_real_artifacts, source_graph_has_verific…
3 occurrences
repo-level (3 hits)
high Security checks quality Quality conf 0.76 19 occurrences Foundry mined schema ui api mismatch: waiff/sreality
Graph query export: Schema, UI, and API mismatch Query id: schema_ui_api_mismatch Query type: motif_query Intent: Assumption-check examples for data-path consistency across layers. Motif: schema_ui_api_mismatch Training usage: assumption_check Graph gold label: supported_by_verification_signal Repo…
19 occurrences
repo-level (19 hits)
high Security checks quality Testing conf 0.78 40 occurrences Foundry mined test ci gap after feedback: waiff/sreality
Graph query export: Feedback exposes missing tests or CI Query id: test_ci_gap_after_feedback Query type: motif_query Intent: Hard negatives for feedback/fix chains without adequate guardrails. Motif: test_ci_gap_after_feedback Training usage: hard_negative Graph gold label: supported_by_verificati…
40 occurrences
repo-level (40 hits)
high System graph security Agent instructions conf 1.00 Agent instruction/config may expose a secret: skills/rental_estimator_full_v1/SKILL.md
Agent-facing files are routinely pasted into LLM/tool contexts. Move literal tokens, keys, and passwords into a secret manager or document them as placeholders only.
skills/rental_estimator_full_v1/SKILL.md:21 SecretsSkill file
high System graph security Agent instructions conf 1.00 Agent instruction/config may expose a secret: skills/rental_estimator_v1/SKILL.md
Agent-facing files are routinely pasted into LLM/tool contexts. Move literal tokens, keys, and passwords into a secret manager or document them as placeholders only.
skills/rental_estimator_v1/SKILL.md:14 SecretsSkill file
high System graph security Agent instructions conf 1.00 Agent instruction/config may expose a secret: skills/skill_refiner_v1/SKILL.md
Agent-facing files are routinely pasted into LLM/tool contexts. Move literal tokens, keys, and passwords into a secret manager or document them as placeholders only.
skills/skill_refiner_v1/SKILL.md:7 SecretsSkill file
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /filter-presets/${encodeURIComponent(id)} (frontend/src/lib/api.ts:1068)
`frontend/src/lib/api.ts:1068` calls `DELETE /filter-presets/${encodeURIComponent(id)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/filter-presets/<p>` If this points at an external API, prefix it with `…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /admin/app_settings (frontend/src/lib/api.ts:612)
`frontend/src/lib/api.ts:612` calls `GET /admin/app_settings` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/app_settings` If this points at an external API, prefix it with `https://` so the matcher s…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /admin/app_settings/${encodeURIComponent(key)} (frontend/src/lib/api.ts:615)
`frontend/src/lib/api.ts:615` calls `GET /admin/app_settings/${encodeURIComponent(key)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/app_settings/<p>` If this points at an external API, prefix it w…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /admin/portals (frontend/src/lib/api.ts:661)
`frontend/src/lib/api.ts:661` calls `GET /admin/portals` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/portals` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /admin/rent-map (frontend/src/lib/api.ts:696)
`frontend/src/lib/api.ts:696` calls `GET /admin/rent-map` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/rent-map` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /admin/rent-map/revisions (frontend/src/lib/api.ts:699)
`frontend/src/lib/api.ts:699` calls `GET /admin/rent-map/revisions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/rent-map/revisions` If this points at an external API, prefix it with `https://` so t…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /admin/skills (frontend/src/lib/api.ts:595)
`frontend/src/lib/api.ts:595` calls `GET /admin/skills` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/skills` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /admin/skills/${encodeURIComponent(name)} (frontend/src/lib/api.ts:600)
`frontend/src/lib/api.ts:600` calls `GET /admin/skills/${encodeURIComponent(name)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/skills/<p>` If this points at an external API, prefix it with `https:…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /admin/tools (frontend/src/lib/api.ts:627)
`frontend/src/lib/api.ts:627` calls `GET /admin/tools` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/tools` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dedup/candidates (frontend/src/lib/api.ts:1103)
`frontend/src/lib/api.ts:1103` calls `GET /dedup/candidates` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dedup/candidates` If this points at an external API, prefix it with `https://` so the matcher skip…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /dedup/merges (frontend/src/lib/api.ts:1160)
`frontend/src/lib/api.ts:1160` calls `GET /dedup/merges` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dedup/merges` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /filter-presets (frontend/src/lib/api.ts:1050)
`frontend/src/lib/api.ts:1050` calls `GET /filter-presets` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/filter-presets` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /notifications/subscriptions (frontend/src/lib/api.ts:963)
`frontend/src/lib/api.ts:963` calls `GET /notifications/subscriptions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/notifications/subscriptions` If this points at an external API, prefix it with `https://…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /admin/rent-map/fetch (frontend/src/lib/api.ts:702)
`frontend/src/lib/api.ts:702` calls `POST /admin/rent-map/fetch` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/rent-map/fetch` If this points at an external API, prefix it with `https://` so the matc…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /dedup/candidates/${candidateId}/merge (frontend/src/lib/api.ts:1108)
`frontend/src/lib/api.ts:1108` calls `POST /dedup/candidates/${candidateId}/merge` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dedup/candidates/<p>/merge` If this points at an external API, prefix it wit…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /dedup/clusters/dismiss (frontend/src/lib/api.ts:1142)
`frontend/src/lib/api.ts:1142` calls `POST /dedup/clusters/dismiss` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dedup/clusters/dismiss` If this points at an external API, prefix it with `https://` so the…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /dedup/merges/${encodeURIComponent(mergeGroupId)}/unmerge (frontend/src/lib/api.ts:1167)
`frontend/src/lib/api.ts:1167` calls `POST /dedup/merges/${encodeURIComponent(mergeGroupId)}/unmerge` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dedup/merges/<p>/unmerge` If this points at an external A…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /dedup/properties/merge (frontend/src/lib/api.ts:1152)
`frontend/src/lib/api.ts:1152` calls `POST /dedup/properties/merge` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/dedup/properties/merge` If this points at an external API, prefix it with `https://` so the…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /filter-presets (frontend/src/lib/api.ts:1056)
`frontend/src/lib/api.ts:1056` calls `POST /filter-presets` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/filter-presets` If this points at an external API, prefix it with `https://` so the matcher skips i…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /notifications/dispatches/${encodeURIComponent(dispatchId)}/mark-seen (frontend/src/lib/api.ts:1016)
`frontend/src/lib/api.ts:1016` calls `POST /notifications/dispatches/${encodeURIComponent(dispatchId)}/mark-seen` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/notifications/dispatches/<p>/mark-seen` If th…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /notifications/subscriptions (frontend/src/lib/api.ts:980)
`frontend/src/lib/api.ts:980` calls `POST /notifications/subscriptions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/notifications/subscriptions` If this points at an external API, prefix it with `https:/…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PUT /admin/app_settings/${encodeURIComponent(key)} (frontend/src/lib/api.ts:621)
`frontend/src/lib/api.ts:621` calls `PUT /admin/app_settings/${encodeURIComponent(key)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/app_settings/<p>` If this points at an external API, prefix it w…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PUT /admin/condition-scoring/regions (frontend/src/lib/api.ts:758)
`frontend/src/lib/api.ts:758` calls `PUT /admin/condition-scoring/regions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/condition-scoring/regions` If this points at an external API, prefix it with `…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PUT /admin/portals/${encodeURIComponent(source)}/limits (frontend/src/lib/api.ts:667)
`frontend/src/lib/api.ts:667` calls `PUT /admin/portals/${encodeURIComponent(source)}/limits` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/portals/<p>/limits` If this points at an external API, pref…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PUT /admin/skills/${encodeURIComponent(name)} (frontend/src/lib/api.ts:606)
`frontend/src/lib/api.ts:606` calls `PUT /admin/skills/${encodeURIComponent(name)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/skills/<p>` If this points at an external API, prefix it with `https:…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PUT /filter-presets/${encodeURIComponent(id)} (frontend/src/lib/api.ts:1062)
`frontend/src/lib/api.ts:1062` calls `PUT /filter-presets/${encodeURIComponent(id)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/filter-presets/<p>` If this points at an external API, prefix it with `htt…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PUT /notifications/subscriptions/${encodeURIComponent(id)} (frontend/src/lib/api.ts:993)
`frontend/src/lib/api.ts:993` calls `PUT /notifications/subscriptions/${encodeURIComponent(id)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/notifications/subscriptions/<p>` If this points at an external…
Dangling fetchHelper:request
high System graph security auth conf 1.00 FastAPI POST `post_rent_map_fetch` without auth dependency — api/routes/admin.py:408
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
api/routes/admin.py:408 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `post_rent_map_upload` without auth dependency — api/routes/admin.py:388
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
api/routes/admin.py:388 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PUT `put_app_setting` without auth dependency — api/routes/admin.py:167
`@router.put` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
api/routes/admin.py:167 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PUT `put_condition_scoring_regions` without auth dependency — api/routes/admin.py:452
`@router.put` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
api/routes/admin.py:452 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PUT `put_filter_visibility` without auth dependency — api/routes/admin.py:245
`@router.put` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
api/routes/admin.py:245 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PUT `put_portal_limits` without auth dependency — api/routes/admin.py:338
`@router.put` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
api/routes/admin.py:338 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PUT `put_skill` without auth dependency — api/routes/admin.py:112
`@router.put` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
api/routes/admin.py:112 securityAuth fastapi unauth mutation
medium Security checks quality Practices conf 0.62 43 occurrences Foundry mined assumption checks: waiff/sreality
Comment chain pattern product: assumption_checks Repo: waiff/sreality Thread: waiff/sreality#53 Outcome: claimed_resolved_unverified Thread label: thread_has_human_issue_and_fix_context Source graph label: source_backed_multi_signal_graph Reasons: source_graph_has_real_artifacts, source_graph_has_v…
43 occurrences
repo-level (43 hits)
medium Security checks quality maintenance conf 0.70 65 occurrences Foundry mined blueprint gap alignment: waiff/sreality
Graph query export: Human feedback aligned with blueprint or architecture gaps Query id: blueprint_gap_alignment Query type: motif_query Intent: Curriculum-gap examples connecting issue threads to helicopter-view gaps. Motif: blueprint_gap_alignment Training usage: curriculum_gap Graph gold label: …
65 occurrences
repo-level (65 hits)
medium Security checks quality Practices conf 0.70 Foundry mined unresolved feedback: waiff/sreality
Graph query export: Human feedback without linked fix evidence Query id: unresolved_feedback Query type: motif_query Intent: Negative/unresolved examples that should not be hallucinated into fixes. Motif: unlinked_feedback_needs_evidence Training usage: negative_or_unresolved Graph gold label: need…
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — chrome-extension/src/api.ts:16
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — chrome-extension/vite.config.ts:7
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/lib/api.ts:528
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/pages/Watchdog.tsx:675
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: skills/skill_refiner_v1/SKILL.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
skills/skill_refiner_v1/SKILL.md VerificationSkill file
medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing license. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.
Repo hardeningGenerated repo pattern
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 hardware Security conf 1.00 Dockerfile runs as root: Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph hardware Security conf 1.00 Dockerfile runs as root: frontend/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph cicd CI/CD security conf 1.00 5 occurrences GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
5 files, 5 locations
.github/workflows/aggregate_condition_markers.yml
.github/workflows/fetch-fixtures.yml
.github/workflows/fetch_sreality_fixtures.yml
.github/workflows/refresh_population.yml
.github/workflows/seed_curated_cities.yml
CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in chrome-extension/src/content.ts:188
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
chrome-extension/src/content.ts:188 Direct innerhtml assignment
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/fetch_population_wikidata.py:96
`requests.get(...)` 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 Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 96 placeholder/mock markers across 32 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
medium System graph quality Placeholder conf 1.00 Runtime service client appears to use placeholder configuration
A runtime source file appears to wire Supabase/Firebase/AI/payment-style clients to placeholder URLs, keys, or fallback values. In the Fable corpus this often means the UI/API shape is present while the backend service is not actually configured.
Runtime configService clientGenerated repo pattern
low System graph quality Integrity conf 1.00 21 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `CORS_ALLOW_ORIGINS`, `GEMINI_API_KEY`, `GH_DISPATCH_TOKEN`, `GH_REPO`, `GITHUB_ACTOR`, `GITHUB_OUTPUT`, `GITHUB_REPOSITORY`, `GITHUB_TOKEN` + 13 more. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.
config drift
low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
Deployment
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 80 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 hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: caddy:2-alpine
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
frontend/Dockerfile:28 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: node:20-alpine
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
frontend/Dockerfile:7 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: python:3.12-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:1 containersPinned dependencies
low System graph cicd CI/CD security conf 1.00 2 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/upload-artifact@v7 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
2 files, 2 locations
.github/workflows/build-extension.yml:60
.github/workflows/scrape_price_stats.yml:156
CI/CD securitySupply chainGithub actions
low System graph quality Integrity conf 1.00 16 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: api/building_runs.py:list_building_runs, api/estimation_runs.py:list_estimation_runs 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.
16 occurrences
repo-level (16 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 3 occurrences Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: api/providers/anthropic.py:complete, api/providers/gemini.py:complete, api/providers/base.py:complete 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'…
3 occurrences
repo-level (3 hits)
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: toolkit/condition_markers.py:discover_condition_markers, toolkit/summaries.py:summarize_listing, toolkit/building_extraction.py:extract_building_units, toolkit/condition_scoring.py:score_listing_condition This is *the* AI-coder failure mode (4× more …
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 `condition_markers_v1` in frontend/src/lib/workflowDocs.generated.ts:48
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 `condition_markers_v1` in scripts/aggregate_condition_markers.py:7
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 `condition_markers_v1` in scripts/curate_condition_markers.py:3
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 `condition_rubric_v1` in scripts/seed_condition_settings.py:35
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 `condition_rubric_v1` in tests/test_condition_curator_and_rubric.py:6
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 `condition_rubric_v1` in toolkit/condition_scoring.py:631
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 `rental_estimator_full_v1` in api/schemas.py:327
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 `rental_estimator_full_v1` in frontend/src/components/estimation/RunPanel.tsx:1741
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 `rental_estimator_v1` in api/agent.py:611
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 `rental_estimator_v1` in api/building_runs.py:383
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 `rental_estimator_v1` in frontend/src/pages/Settings.tsx: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 `rental_estimator_v1` in scripts/smoke_agent.py:12
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 `rental_estimator_v1` in tests/api/_fakes.py:171
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 `rental_estimator_v1` in tests/api/test_admin_routes.py:35
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 `rental_estimator_v1` in tests/api/test_agent.py:53
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 `rental_estimator_v1` in tests/api/test_buildings_b2.py:87
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 `rental_estimator_v1` in tests/api/test_estimations.py:501
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 `rental_estimator_v1` in tests/api/test_refiner.py:28
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 `rental_estimator_v1` in tests/api/test_skills.py:14
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_recent_check_throttles_even_if_listing_old` in tests/toolkit/test_freshness.py:113
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: category_type_label
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scraper/price_stats_enums.py:97
low System graph software Dead code conf 1.00 Possibly dead Python function: date_key
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
api/rent_map.py:48
low System graph software Dead code conf 1.00 Possibly dead Python function: fetch_detail_html
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/smoke_agent.py:323
low System graph software Dead code conf 1.00 Possibly dead Python function: localities_for_obec_ids
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scraper/price_stats_db.py:206
low System graph software Dead code conf 1.00 Possibly dead Python function: locality_exists
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scraper/price_stats_db.py:306
low System graph software Dead code conf 1.00 Possibly dead Python function: portal_inactive_sweep_due
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scraper/db.py:853
low System graph software Dead code conf 1.00 Possibly dead Python function: record_portal_inactive_sweep
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scraper/db.py:878
low System graph software Dead code conf 1.00 Possibly dead Python function: register_providers
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
api/llm_client.py:113
low System graph software Dead code conf 1.00 Possibly dead Python function: run_pending_estimation
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
api/notifications.py:939
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 quality Integrity conf 1.00 Stub function `set_summary` (body is just `pass`/`return`) — api/estimation_runs.py:251
Likely an AI scaffold that was never filled in. Remove or implement.
Empty handlerDead code
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /manual_estimates/{estimate_id}
`api/main.py` declares `DELETE /manual_estimates/{estimate_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: DELETE /price-stats/datasets/{dataset_id}
`api/main.py` declares `DELETE /price-stats/datasets/{dataset_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: DELETE /subscriptions/{subscription_id}
`api/routes/notifications.py` declares `DELETE /subscriptions/{subscription_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 i…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /buildings/{building_id}/attachments
`api/main.py` declares `GET /buildings/{building_id}/attachments` 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: GET /buildings/{building_id}/attachments/{attachment_id}/raw
`api/main.py` declares `GET /buildings/{building_id}/attachments/{attachment_id}/raw` 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 consu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /collections
`api/main.py` declares `GET /collections` 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: GET /collections/{collection_id}
`api/main.py` declares `GET /collections/{collection_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: GET /dispatches
`api/routes/notifications.py` declares `GET /dispatches` 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: GET /estimations/latest-by-listing
`api/main.py` declares `GET /estimations/latest-by-listing` 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: GET /estimations/preview
`api/main.py` declares `GET /estimations/preview` 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: GET /estimations/{run_id}/feedback
`api/main.py` declares `GET /estimations/{run_id}/feedback` 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: GET /listings/{sreality_id}/manual_estimates
`api/main.py` declares `GET /listings/{sreality_id}/manual_estimates` 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: GET /listings/{sreality_id}/notes
`api/main.py` declares `GET /listings/{sreality_id}/notes` 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: GET /maps/suggest
`api/main.py` declares `GET /maps/suggest` 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: GET /price-stats/datasets
`api/main.py` declares `GET /price-stats/datasets` 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: GET /price-stats/datasets/{dataset_id}/cities/{entity_type}/{entity_id}/series
`api/main.py` declares `GET /price-stats/datasets/{dataset_id}/cities/{entity_type}/{entity_id}/series` 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 doc…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /price-stats/datasets/{dataset_id}/city-metrics
`api/main.py` declares `GET /price-stats/datasets/{dataset_id}/city-metrics` 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: GET /price-stats/datasets/{dataset_id}/summary
`api/main.py` declares `GET /price-stats/datasets/{dataset_id}/summary` 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: GET /skill-refinements/{refinement_id}
`api/main.py` declares `GET /skill-refinements/{refinement_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: GET /subscriptions
`api/routes/notifications.py` declares `GET /subscriptions` 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: GET /subscriptions/{subscription_id}
`api/routes/notifications.py` declares `GET /subscriptions/{subscription_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: GET /tags
`api/main.py` declares `GET /tags` 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: PATCH /manual_estimates/{estimate_id}
`api/main.py` declares `PATCH /manual_estimates/{estimate_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: POST /buildings
`api/main.py` declares `POST /buildings` 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: POST /buildings/{building_id}/attachments
`api/main.py` declares `POST /buildings/{building_id}/attachments` 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: POST /dispatches/{dispatch_id}/mark-seen
`api/routes/notifications.py` declares `POST /dispatches/{dispatch_id}/mark-seen` 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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /estimate_yield
`api/main.py` declares `POST /estimate_yield` 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: POST /listings/{sreality_id}/notes
`api/main.py` declares `POST /listings/{sreality_id}/notes` 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: POST /maps/resolve
`api/main.py` declares `POST /maps/resolve` 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: POST /price-stats/datasets
`api/main.py` declares `POST /price-stats/datasets` 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: POST /price-stats/datasets/{dataset_id}/run
`api/main.py` declares `POST /price-stats/datasets/{dataset_id}/run` 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: POST /subscriptions
`api/routes/notifications.py` declares `POST /subscriptions` 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: POST /tools/analyze_distribution
`api/main.py` declares `POST /tools/analyze_distribution` 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: POST /tools/cluster_comparables
`api/main.py` declares `POST /tools/cluster_comparables` 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: POST /tools/compare_listing_images
`api/main.py` declares `POST /tools/compare_listing_images` 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: POST /tools/compare_snapshots
`api/main.py` declares `POST /tools/compare_snapshots` 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: POST /tools/compute_amenity_supply
`api/main.py` declares `POST /tools/compute_amenity_supply` 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: POST /tools/compute_listing_velocity
`api/main.py` declares `POST /tools/compute_listing_velocity` 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: POST /tools/compute_market_velocity
`api/main.py` declares `POST /tools/compute_market_velocity` 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: POST /tools/compute_walkability
`api/main.py` declares `POST /tools/compute_walkability` 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: POST /tools/describe_neighborhood
`api/main.py` declares `POST /tools/describe_neighborhood` 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: POST /tools/find_anchor_amenities
`api/main.py` declares `POST /tools/find_anchor_amenities` 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: POST /tools/find_comparables
`api/main.py` declares `POST /tools/find_comparables` 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: POST /tools/find_comparables_along_axis
`api/main.py` declares `POST /tools/find_comparables_along_axis` 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: POST /tools/find_comparables_relaxed
`api/main.py` declares `POST /tools/find_comparables_relaxed` 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: POST /tools/find_distribution_outliers
`api/main.py` declares `POST /tools/find_distribution_outliers` 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: POST /tools/get_manual_rental_estimates
`api/main.py` declares `POST /tools/get_manual_rental_estimates` 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: POST /tools/summarize_listing
`api/main.py` declares `POST /tools/summarize_listing` 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: POST /tools/verify_listing_freshness
`api/main.py` declares `POST /tools/verify_listing_freshness` 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: PUT /subscriptions/{subscription_id}
`api/routes/notifications.py` declares `PUT /subscriptions/{subscription_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 quality Complexity conf 1.00 Very large file: api/agent.py (1661 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: api/estimation_runs.py (1706 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: api/main.py (1477 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: api/notifications.py (1440 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/components/estimation/RunPanel.tsx (2327 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/components/ListingMap.tsx (1805 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/lib/filterRegistry.generated.ts (2355 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/lib/filters.ts (1364 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/lib/queries.ts (1452 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/lib/workflowDocs.generated.ts (2366 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/pages/Health.tsx (2022 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: scraper/db.py (1827 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: scraper/main.py (1839 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/api/test_estimations.py (1630 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: toolkit/filter_registry.py (1924 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/f28a0d4a-8899-4fbb-884a-981d5a876ab7/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/f28a0d4a-8899-4fbb-884a-981d5a876ab7/

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.