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

scottxxxxx/contextquilt

https://github.com/scottxxxxx/contextquilt · scanned 2026-06-16 00:05 UTC (2 months, 3 weeks ago)

154 raw signals (0 security + 154 graph)

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

Complete repo analysis

Last scanned 2 months, 3 weeks ago · v1 · 144 actionable findings from 1 signal source. 10 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
0 findings
System graph
51
100.0% cov · 144 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 39 Medium 11 Low 75 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 144 Crowd 0 Layer: Software 9 Frontend 2 Hardware 2 Security 4 Cicd 2 Quality 37 Api 88
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 1487 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 154 findings — concentrated in api (88), quality (44), software (9). Risk profile is high: 0 critical, 39 high, 13 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

Showing 125 of 144 actionable findings. 154 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 api Wiring conf 1.00 Dangling fetch: DELETE /api/dashboard/alerts/recipients/${id} (src/dashboard/app.js:2296)
`src/dashboard/app.js:2296` calls `DELETE /api/dashboard/alerts/recipients/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/dashboard/alerts/recipients/<p>` If this points at an external API, prefix it with `ht…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/dashboard/patches/${patchId} (src/dashboard/app.js:1193)
`src/dashboard/app.js:1193` calls `DELETE /api/dashboard/patches/${patchId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/dashboard/patches/<p>` If this points at an external API, prefix it with `https://` so the …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/dashboard/alerts/categories (src/dashboard/app.js:2184)
`src/dashboard/app.js:2184` calls `GET /api/dashboard/alerts/categories` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/dashboard/alerts/categories` If this points at an external API, prefix it with `https://` so th…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/dashboard/alerts/incidents?limit=100 (src/dashboard/app.js:2351)
`src/dashboard/app.js:2351` calls `GET /api/dashboard/alerts/incidents?limit=100` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/dashboard/alerts/incidents` If this points at an external API, prefix it with `https:/…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/dashboard/alerts/recipients (src/dashboard/app.js:2211)
`src/dashboard/app.js:2211` calls `GET /api/dashboard/alerts/recipients` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/dashboard/alerts/recipients` If this points at an external API, prefix it with `https://` so th…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/dashboard/backup/history?limit=30 (src/dashboard/app.js:385)
`src/dashboard/app.js:385` calls `GET /api/dashboard/backup/history?limit=30` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/dashboard/backup/history` If this points at an external API, prefix it with `https://` so …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/dashboard/backup/status (src/dashboard/app.js:384)
`src/dashboard/app.js:384` calls `GET /api/dashboard/backup/status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/dashboard/backup/status` If this points at an external API, prefix it with `https://` so the matcher…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/dashboard/config (src/dashboard/app.js:464)
`src/dashboard/app.js:464` calls `GET /api/dashboard/config` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/dashboard/config` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/dashboard/connections (src/dashboard/app.js:146)
`src/dashboard/app.js:146` calls `GET /api/dashboard/connections` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/dashboard/connections` If this points at an external API, prefix it with `https://` so the matcher ski…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/dashboard/health-check (src/dashboard/app.js:298)
`src/dashboard/app.js:298` calls `GET /api/dashboard/health-check` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/dashboard/health-check` If this points at an external API, prefix it with `https://` so the matcher s…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/dashboard/ingestion-log?limit=50 (src/dashboard/app.js:636)
`src/dashboard/app.js:636` calls `GET /api/dashboard/ingestion-log?limit=50` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/dashboard/ingestion-log` If this points at an external API, prefix it with `https://` so th…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/dashboard/memory-health?days=30 (src/dashboard/app.js:2567)
`src/dashboard/app.js:2567` calls `GET /api/dashboard/memory-health?days=30` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/dashboard/memory-health` If this points at an external API, prefix it with `https://` so th…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/dashboard/metrics/cost?days=30 (src/dashboard/app.js:217)
`src/dashboard/app.js:217` calls `GET /api/dashboard/metrics/cost?days=30` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/dashboard/metrics/cost` If this points at an external API, prefix it with `https://` so the m…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/dashboard/metrics/models?days=30 (src/dashboard/app.js:248)
`src/dashboard/app.js:248` calls `GET /api/dashboard/metrics/models?days=30` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/dashboard/metrics/models` If this points at an external API, prefix it with `https://` so t…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/dashboard/metrics/recent?limit=50 (src/dashboard/app.js:270)
`src/dashboard/app.js:270` calls `GET /api/dashboard/metrics/recent?limit=50` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/dashboard/metrics/recent` If this points at an external API, prefix it with `https://` so …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/dashboard/metrics/summary?days=30 (src/dashboard/app.js:206)
`src/dashboard/app.js:206` calls `GET /api/dashboard/metrics/summary?days=30` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/dashboard/metrics/summary` If this points at an external API, prefix it with `https://` so…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/dashboard/patch-types (src/dashboard/app.js:85)
`src/dashboard/app.js:85` calls `GET /api/dashboard/patch-types` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/dashboard/patch-types` If this points at an external API, prefix it with `https://` so the matcher skip…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/dashboard/patches/distribution?group_by=${groupBy}&${params} (src/dashboard/app.js:1779)
`src/dashboard/app.js:1779` calls `GET /api/dashboard/patches/distribution?group_by=${groupBy}&${params}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/dashboard/patches/distribution` If this points at an external …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/dashboard/patches/history?${params}&granularity=${currentGranularity.unit} (src/dashboard/app.js:686)
`src/dashboard/app.js:686` calls `GET /api/dashboard/patches/history?${params}&granularity=${currentGranularity.unit}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/dashboard/patches/history` If this points at an e…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/dashboard/prompts (src/dashboard/app.js:490)
`src/dashboard/app.js:490` calls `GET /api/dashboard/prompts` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/dashboard/prompts` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/dashboard/provider-health (src/dashboard/app.js:2413)
`src/dashboard/app.js:2413` calls `GET /api/dashboard/provider-health` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/dashboard/provider-health` If this points at an external API, prefix it with `https://` so the ma…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/dashboard/providers (src/dashboard/app.js:2412)
`src/dashboard/app.js:2412` calls `GET /api/dashboard/providers` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/dashboard/providers` If this points at an external API, prefix it with `https://` so the matcher skips …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/dashboard/stats?${params} (src/dashboard/app.js:1594)
`src/dashboard/app.js:1594` calls `GET /api/dashboard/stats?${params}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/dashboard/stats` If this points at an external API, prefix it with `https://` so the matcher skip…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/dashboard/users (src/dashboard/app.js:740)
`src/dashboard/app.js:740` calls `GET /api/dashboard/users` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/dashboard/users` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/dashboard/users/${encodeURIComponent(userId)}/quilt (src/dashboard/app.js:921)
`src/dashboard/app.js:921` calls `GET /api/dashboard/users/${encodeURIComponent(userId)}/quilt` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/dashboard/users/<p>/quilt` If this points at an external API, prefix it …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/dashboard/users/${userId}/quilt (src/dashboard/app.js:1177)
`src/dashboard/app.js:1177` calls `GET /api/dashboard/users/${userId}/quilt` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/dashboard/users/<p>/quilt` If this points at an external API, prefix it with `https://` so …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/dashboard/users/${userId}/quilt (src/dashboard/app.js:1199)
`src/dashboard/app.js:1199` calls `GET /api/dashboard/users/${userId}/quilt` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/dashboard/users/<p>/quilt` If this points at an external API, prefix it with `https://` so …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /api/dashboard/alerts/recipients/${id} (src/dashboard/app.js:2281)
`src/dashboard/app.js:2281` calls `PATCH /api/dashboard/alerts/recipients/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/dashboard/alerts/recipients/<p>` If this points at an external API, prefix it with `htt…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /api/dashboard/patches/${patchId} (src/dashboard/app.js:1169)
`src/dashboard/app.js:1169` calls `PATCH /api/dashboard/patches/${patchId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/dashboard/patches/<p>` If this points at an external API, prefix it with `https://` so the m…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/dashboard/alerts/recipients (src/dashboard/app.js:2261)
`src/dashboard/app.js:2261` calls `POST /api/dashboard/alerts/recipients` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/dashboard/alerts/recipients` If this points at an external API, prefix it with `https://` so t…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/dashboard/alerts/test-send (src/dashboard/app.js:2317)
`src/dashboard/app.js:2317` calls `POST /api/dashboard/alerts/test-send` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/dashboard/alerts/test-send` If this points at an external API, prefix it with `https://` so the…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/dashboard/connections (src/dashboard/app.js:181)
`src/dashboard/app.js:181` calls `POST /api/dashboard/connections` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/dashboard/connections` If this points at an external API, prefix it with `https://` so the matcher sk…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/dashboard/patch-types (src/dashboard/app.js:133)
`src/dashboard/app.js:133` calls `POST /api/dashboard/patch-types` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/dashboard/patch-types` If this points at an external API, prefix it with `https://` so the matcher sk…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/dashboard/test-pipeline (src/dashboard/app.js:2026)
`src/dashboard/app.js:2026` calls `POST /api/dashboard/test-pipeline` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/dashboard/test-pipeline` If this points at an external API, prefix it with `https://` so the match…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/dashboard/test-provider (src/dashboard/app.js:2524)
`src/dashboard/app.js:2524` calls `POST /api/dashboard/test-provider` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/dashboard/test-provider` If this points at an external API, prefix it with `https://` so the match…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/dashboard/update-key (src/dashboard/app.js:2499)
`src/dashboard/app.js:2499` calls `POST /api/dashboard/update-key` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/dashboard/update-key` If this points at an external API, prefix it with `https://` so the matcher ski…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/dashboard/patch-types/${typeKey} (src/dashboard/app.js:116)
`src/dashboard/app.js:116` calls `PUT /api/dashboard/patch-types/${typeKey}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/dashboard/patch-types/<p>` If this points at an external API, prefix it with `https://` so …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/dashboard/prompts/${key} (src/dashboard/app.js:520)
`src/dashboard/app.js:520` calls `PUT /api/dashboard/prompts/${key}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/dashboard/prompts/<p>` If this points at an external API, prefix it with `https://` so the matcher …
Dangling fetchFetch
high System graph security auth conf 1.00 FastAPI PATCH `update_application` without auth dependency — src/main.py:2761
`@router.patch` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/main.py:2761 securityAuth fastapi unauth mutation
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/dashboard/app.js:1177
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 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 cicd CI/CD security conf 1.00 3 occurrences GitHub Action is tag-pinned rather than SHA-pinned
docker/login-action@v3 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
lines 25, 32, 45
.github/workflows/deploy.yml:25, 32, 45 (3 hits)
CI/CD securitySupply chainGithub actions
medium System graph cicd CI/CD security conf 1.00 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.
.github/workflows/deploy.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in main.py:26
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
main.py:26 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in src/main.py:83
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
src/main.py:83 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in src/dashboard/app.js:94
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
src/dashboard/app.js:94 Direct innerhtml assignment
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/seed_data.py:139
`urllib.request.urlopen(...)` 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 — scripts/verify_passive_learning.py:39
`urllib.request.urlopen(...)` 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 — scripts/verify_person_ownership_enforcer.py:95
`subprocess.check_output(...)` 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 24 placeholder/mock markers across 12 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 12 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `CQ_BASE_URL`, `CQ_GCP_PROJECT`, `CQ_SSH_KEY`, `CQ_SSH_TARGET`, `DATABASE_URL`, `MEETINGS_PATH`, `MODE`, `OPENAI_API_KEY` + 4 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 463 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 2 occurrences Docker base image is tag-pinned but not digest-pinned: python:3.11-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
lines 7, 25
Dockerfile:7, 25 (2 hits)
containersPinned dependencies
low System graph quality Integrity conf 1.00 6 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: scripts/verify_users_query.py:test_users_query, src/dashboard/router.py:get_users 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.
6 occurrences
repo-level (6 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: scripts/backfill_strip_you_marker.py:main, scripts/backfill_archive_placeholder_persons.py:main, scripts/backfill_person_name_hygiene.py:main This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hyg…
2 occurrences
repo-level (2 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 5 places
Functions with the same first-5-line body hash: scripts/load_seed_data.py:main, scripts/migrate_normalization.py:migrate_normalization, scripts/migrate_profile_identity.py:migrate_profile_identity, scripts/migrate_prompt_versions.py:migrate_prompt_versions This is *the* AI-coder failure mode (4× m…
2 occurrences
repo-level (2 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `expected_legacy` in verify_context_patch_flow.py:26
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 `is_v2` in tests/benchmark/test_extraction_dryrun.py:157
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 `stitcher_v2` in src/contextquilt/utils/context_quilt_utils.py:79
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: check_delete_access
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/contextquilt/access.py:46
low System graph software Dead code conf 1.00 Possibly dead Python function: check_write_access
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/contextquilt/access.py:32
low System graph software Dead code conf 1.00 Possibly dead Python function: health
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/mcp_server.py:512
low System graph software Dead code conf 1.00 Possibly dead Python function: store_memory
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/contextquilt/memory/layer.py:69
low System graph software Dead code conf 1.00 Possibly dead Python function: transform_to_patches
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/contextquilt/utils/context_quilt_utils.py:50
low System graph software Dead code conf 1.00 Possibly dead Python function: verify_admin_key
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/dashboard/router.py:25
low System graph software Dead code conf 1.00 Possibly dead Python function: verify_admin_key
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/contextquilt/routers/app_schemas.py:31
low System graph software Dead code conf 1.00 Possibly dead Python function: verify_api_key
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
main.py:100
low System graph software Dead code conf 1.00 Possibly dead Python function: verify_application_access
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/main.py:292
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 — src/dashboard/app.js:902
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: DELETE /patches/{patch_id}
`src/dashboard/router.py` declares `DELETE /patches/{patch_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 /v1/quilt/{user_id}
`src/main.py` declares `DELETE /v1/quilt/{user_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 /v1/quilt/{user_id}/connections
`src/main.py` declares `DELETE /v1/quilt/{user_id}/connections` 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 /v1/quilt/{user_id}/patches/{patch_id}
`src/main.py` declares `DELETE /v1/quilt/{user_id}/patches/{patch_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 /
`main.py` declares `GET /` 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 /apps
`src/dashboard/router.py` declares `GET /apps` 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 /config
`src/dashboard/router.py` declares `GET /config` 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 /connections
`src/dashboard/router.py` declares `GET /connections` 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 /ingestion-log
`src/dashboard/router.py` declares `GET /ingestion-log` 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 /patch-types
`src/dashboard/router.py` declares `GET /patch-types` 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 /patches/distribution
`src/dashboard/router.py` declares `GET /patches/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: GET /patches/history
`src/dashboard/router.py` declares `GET /patches/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: GET /patches/recent
`src/dashboard/router.py` declares `GET /patches/recent` 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 /prompts
`src/dashboard/router.py` declares `GET /prompts` 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 /provider-health
`src/dashboard/router.py` declares `GET /provider-health` 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 /providers
`src/dashboard/router.py` declares `GET /providers` 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 /stats
`src/dashboard/router.py` declares `GET /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: GET /users
`src/dashboard/router.py` declares `GET /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: GET /users/{user_id}/quilt
`src/dashboard/router.py` declares `GET /users/{user_id}/quilt` 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 /v1/memory/{user_id}
`main.py` declares `GET /v1/memory/{user_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 /v1/profile/{user_id}
`src/main.py` declares `GET /v1/profile/{user_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 /v1/projects/{user_id}
`src/main.py` declares `GET /v1/projects/{user_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 /v1/quilt/{user_id}
`src/main.py` declares `GET /v1/quilt/{user_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 /v1/schema
`src/main.py` declares `GET /v1/schema` 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 /verify-key
`src/dashboard/router.py` declares `GET /verify-key` 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 /patches/{patch_id}
`src/dashboard/router.py` declares `PATCH /patches/{patch_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: PATCH /v1/projects/{user_id}/{project_id}
`src/main.py` declares `PATCH /v1/projects/{user_id}/{project_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: PATCH /v1/quilt/{user_id}/patches/{patch_id}
`src/main.py` declares `PATCH /v1/quilt/{user_id}/patches/{patch_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 /connections
`src/dashboard/router.py` declares `POST /connections` 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 /patch-types
`src/dashboard/router.py` declares `POST /patch-types` 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 /test-pipeline
`src/dashboard/router.py` declares `POST /test-pipeline` 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 /test-provider
`src/dashboard/router.py` declares `POST /test-provider` 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 /update-key
`src/dashboard/router.py` declares `POST /update-key` 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 /v1/auth/token
`src/main.py` declares `POST /v1/auth/token` 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 /v1/chat
`main.py` declares `POST /v1/chat` 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 /v1/enrich
`src/main.py` declares `POST /v1/enrich` 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 /v1/memory
`src/main.py` declares `POST /v1/memory` 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 /v1/origins/{user_id}/{origin_type}/{origin_id}/assign-project
`src/main.py` declares `POST /v1/origins/{user_id}/{origin_type}/{origin_id}/assign-project` 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 wh…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /v1/prewarm
`src/main.py` declares `POST /v1/prewarm` 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 /v1/projects/{user_id}
`src/main.py` declares `POST /v1/projects/{user_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 /v1/quilt/{user_id}/connections
`src/main.py` declares `POST /v1/quilt/{user_id}/connections` 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 /v1/quilt/{user_id}/patches
`src/main.py` declares `POST /v1/quilt/{user_id}/patches` 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 /v1/quilt/{user_id}/patches/{patch_id}/complete
`src/main.py` declares `POST /v1/quilt/{user_id}/patches/{patch_id}/complete` 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 /v1/quilt/{user_id}/reassign-speaker
`src/main.py` declares `POST /v1/quilt/{user_id}/reassign-speaker` 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 /v1/quilt/{user_id}/rename-speaker
`src/main.py` declares `POST /v1/quilt/{user_id}/rename-speaker` 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 /v1/recall
`src/main.py` declares `POST /v1/recall` 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 /connections/{label}
`src/dashboard/router.py` declares `PUT /connections/{label}` 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 /patch-types/{type_key}
`src/dashboard/router.py` declares `PUT /patch-types/{type_key}` 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 /prompts/{prompt_key}
`src/dashboard/router.py` declares `PUT /prompts/{prompt_key}` 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 /v1/memory/{user_id}
`main.py` declares `PUT /v1/memory/{user_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: src/dashboard/app.js (2628 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/dashboard/router.py (2135 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/main.py (2789 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/worker.py (2804 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/c53905fd-bba0-4e49-b49d-967eff9bb6b6/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/c53905fd-bba0-4e49-b49d-967eff9bb6b6/

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.