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

regengine/RegEngine

https://github.com/regengine/RegEngine · scanned 2026-06-15 23:50 UTC (2 months, 3 weeks ago)

586 raw signals (0 security + 586 graph)

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

Complete repo analysis

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

JSON
Combined
57.0
/100
Security checks
57
0 findings
System graph
57
100.0% cov · 566 findings
Critical
1
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 1 High 84 Medium 56 Low 201 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 566 Crowd 0 Layer: Software 22 Frontend 63 Network 7 Hardware 2 Security 44 Cicd 3 Quality 327 Api 98
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 57.0/100 with 100.0% coverage. It contains 24120 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 586 findings — concentrated in quality (342), api (98), frontend (63). Risk profile is high: 1 critical, 84 high, 56 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 341 of 566 actionable findings. 586 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 System graph security Secrets conf 1.00 Possible secret in scripts/e2e_brutal_scenario.py
Detected pattern matching generic_api_key. Rotate the credential and move to a secret manager.
scripts/e2e_brutal_scenario.py:110
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/admin/audit/log-123 (frontend/src/test/security/audit-trail.test.ts:88)
`frontend/src/test/security/audit-trail.test.ts:88` calls `DELETE /api/admin/audit/log-123` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/audit/log-123` If this points at an external API, prefix it with `http…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/admin/delete-tenant (frontend/src/test/security/rbac.test.ts:187)
`frontend/src/test/security/rbac.test.ts:187` calls `DELETE /api/admin/delete-tenant` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/delete-tenant` If this points at an external API, prefix it with `https://` …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/admin/delete-tenant (frontend/src/test/security/rbac.test.ts:193)
`frontend/src/test/security/rbac.test.ts:193` calls `DELETE /api/admin/delete-tenant` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/delete-tenant` If this points at an external API, prefix it with `https://` …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/admin/users/delete/user-123 (frontend/src/test/security/rbac.test.ts:77)
`frontend/src/test/security/rbac.test.ts:77` calls `DELETE /api/admin/users/delete/user-123` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/users/delete/user-123` If this points at an external API, prefix it w…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin (frontend/src/test/security/api-security.test.ts:135)
`frontend/src/test/security/api-security.test.ts:135` calls `GET /api/admin` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin` 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/admin/settings (frontend/src/test/security/rbac.test.ts:97)
`frontend/src/test/security/rbac.test.ts:97` calls `GET /api/admin/settings` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/settings` 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/compliance/data-residency/eu-user-001 (frontend/src/test/compliance/data-protection.test.ts:118)
`frontend/src/test/compliance/data-protection.test.ts:118` calls `GET /api/compliance/data-residency/eu-user-001` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/compliance/data-residency/eu-user-001` If this points …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/developer/portal/dashboard (frontend/src/app/developer/portal/page.tsx:35)
`frontend/src/app/developer/portal/page.tsx:35` calls `GET /api/developer/portal/dashboard` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/developer/portal/dashboard` If this points at an external API, prefix it wit…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/developer/portal/keys (frontend/src/app/developer/portal/keys/page.tsx:37)
`frontend/src/app/developer/portal/keys/page.tsx:37` calls `GET /api/developer/portal/keys` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/developer/portal/keys` If this points at an external API, prefix it with `ht…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/developer/portal/usage?range=${timeRange} (frontend/src/app/developer/portal/usage/page.tsx:38)
`frontend/src/app/developer/portal/usage/page.tsx:38` calls `GET /api/developer/portal/usage?range=${timeRange}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/developer/portal/usage` If this points at an external A…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/fsma/customer-readiness/mappings (frontend/src/app/dashboard/integrations/page.tsx:169)
`frontend/src/app/dashboard/integrations/page.tsx:169` calls `GET /api/fsma/customer-readiness/mappings` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/fsma/customer-readiness/mappings` If this points at an external…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/fsma/lots (frontend/src/test/security/rbac.test.ts:29)
`frontend/src/test/security/rbac.test.ts:29` calls `GET /api/fsma/lots` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/fsma/lots` 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/fsma/organizations (frontend/src/hooks/use-organizations.ts:40)
`frontend/src/hooks/use-organizations.ts:40` calls `GET /api/fsma/organizations` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/fsma/organizations` 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/gdpr/audit-check/user-deleted (frontend/src/test/compliance/data-protection.test.ts:100)
`frontend/src/test/compliance/data-protection.test.ts:100` calls `GET /api/gdpr/audit-check/user-deleted` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/gdpr/audit-check/user-deleted` If this points at an external A…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/gdpr/erasure/${initData.request_id} (frontend/src/test/compliance/data-protection.test.ts:55)
`frontend/src/test/compliance/data-protection.test.ts:55` calls `GET /api/gdpr/erasure/${initData.request_id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/gdpr/erasure/<p>` If this points at an external API, pref…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/gdpr/verify/${store} (frontend/src/test/compliance/data-protection.test.ts:78)
`frontend/src/test/compliance/data-protection.test.ts:78` calls `GET /api/gdpr/verify/${store}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/gdpr/verify/<p>` If this points at an external API, prefix it with `http…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/patients/123 (frontend/src/test/compliance/data-protection.test.ts:256)
`frontend/src/test/compliance/data-protection.test.ts:256` calls `GET /api/patients/123` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/patients/<p>` 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/patients/123 (frontend/src/test/compliance/data-protection.test.ts:263)
`frontend/src/test/compliance/data-protection.test.ts:263` calls `GET /api/patients/123` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/patients/<p>` 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/patients/patient-123 (frontend/src/test/compliance/data-protection.test.ts:212)
`frontend/src/test/compliance/data-protection.test.ts:212` calls `GET /api/patients/patient-123` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/patients/patient-123` If this points at an external API, prefix it with…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/patients/patient-123 (frontend/src/test/compliance/data-protection.test.ts:227)
`frontend/src/test/compliance/data-protection.test.ts:227` calls `GET /api/patients/patient-123` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/patients/patient-123` If this points at an external API, prefix it with…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/payments/pay-001 (frontend/src/test/compliance/data-protection.test.ts:301)
`frontend/src/test/compliance/data-protection.test.ts:301` calls `GET /api/payments/pay-001` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/payments/pay-001` 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/protected (frontend/src/test/security/api-security.test.ts:123)
`frontend/src/test/security/api-security.test.ts:123` calls `GET /api/protected` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/protected` 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/protected (frontend/src/test/security/rbac.test.ts:173)
`frontend/src/test/security/rbac.test.ts:173` calls `GET /api/protected` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/protected` 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/search?q=${encodeURIComponent(payload)} (frontend/src/test/security/api-security.test.ts:36)
`frontend/src/test/security/api-security.test.ts:36` calls `GET /api/search?q=${encodeURIComponent(payload)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/search` If this points at an external API, prefix it with …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/session (frontend/src/lib/auth-context.tsx:102)
`frontend/src/lib/auth-context.tsx:102` calls `GET /api/session` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/session` 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/session (frontend/src/lib/auth-context.tsx:151)
`frontend/src/lib/auth-context.tsx:151` calls `GET /api/session` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/session` 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/test (frontend/src/test/security/api-security.test.ts:109)
`frontend/src/test/security/api-security.test.ts:109` calls `GET /api/test` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/test` 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/v1/compliance/status/${tenantId} (frontend/src/components/dashboard/compliance-status-widget.tsx:166)
`frontend/src/components/dashboard/compliance-status-widget.tsx:166` calls `GET /api/v1/compliance/status/${tenantId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/compliance/status/<p>` If this points at an ex…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:3000/api/review/items (frontend/src/app/api/__tests__/routes.test.ts:92)
`frontend/src/app/api/__tests__/routes.test.ts:92` calls `GET http://localhost:3000/api/review/items` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:3000/api/review/items` If this points at an extern…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/audit/purge (frontend/src/test/security/audit-trail.test.ts:295)
`frontend/src/test/security/audit-trail.test.ts:295` calls `POST /api/admin/audit/purge` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/audit/purge` If this points at an external API, prefix it with `https://`…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/audit/log (frontend/src/test/security/audit-trail.test.ts:212)
`frontend/src/test/security/audit-trail.test.ts:212` calls `POST /api/audit/log` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/audit/log` 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: POST /api/audit/log (frontend/src/test/security/audit-trail.test.ts:240)
`frontend/src/test/security/audit-trail.test.ts:240` calls `POST /api/audit/log` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/audit/log` 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: POST /api/audit/log (frontend/src/test/security/audit-trail.test.ts:262)
`frontend/src/test/security/audit-trail.test.ts:262` calls `POST /api/audit/log` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/audit/log` 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: POST /api/auth/supabase/sign-in (frontend/src/app/login/LoginClient.tsx:189)
`frontend/src/app/login/LoginClient.tsx:189` calls `POST /api/auth/supabase/sign-in` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/auth/supabase/sign-in` If this points at an external API, prefix it with `https://`…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/auth/supabase/sign-in (frontend/src/app/signup/page.tsx:54)
`frontend/src/app/signup/page.tsx:54` calls `POST /api/auth/supabase/sign-in` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/auth/supabase/sign-in` 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/auth/supabase/verify-otp (frontend/src/app/auth/verify/VerifyClient.tsx:46)
`frontend/src/app/auth/verify/VerifyClient.tsx:46` calls `POST /api/auth/supabase/verify-otp` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/auth/supabase/verify-otp` If this points at an external API, prefix it wit…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/data/transfer (frontend/src/test/compliance/data-protection.test.ts:131)
`frontend/src/test/compliance/data-protection.test.ts:131` calls `POST /api/data/transfer` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/data/transfer` If this points at an external API, prefix it with `https://` s…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/gdpr/erasure (frontend/src/test/compliance/data-protection.test.ts:45)
`frontend/src/test/compliance/data-protection.test.ts:45` calls `POST /api/gdpr/erasure` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/gdpr/erasure` 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/patients (frontend/src/test/compliance/data-protection.test.ts:181)
`frontend/src/test/compliance/data-protection.test.ts:181` calls `POST /api/patients` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/patients` If this points at an external API, prefix it with `https://` so the matc…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/payments (frontend/src/test/compliance/data-protection.test.ts:314)
`frontend/src/test/compliance/data-protection.test.ts:314` calls `POST /api/payments` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/payments` If this points at an external API, prefix it with `https://` so the matc…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/payments/charge (frontend/src/test/compliance/data-protection.test.ts:355)
`frontend/src/test/compliance/data-protection.test.ts:355` calls `POST /api/payments/charge` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/payments/charge` If this points at an external API, prefix it with `https:/…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/payments/tokenize (frontend/src/test/compliance/data-protection.test.ts:336)
`frontend/src/test/compliance/data-protection.test.ts:336` calls `POST /api/payments/tokenize` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/payments/tokenize` If this points at an external API, prefix it with `htt…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/assessments/retailer-readiness (frontend/src/app/retailer-readiness/page.tsx:142)
`frontend/src/app/retailer-readiness/page.tsx:142` calls `POST /api/v1/assessments/retailer-readiness` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/assessments/retailer-readiness` If this points at an external …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://localhost:3000/api/setup-demo (frontend/src/app/api/__tests__/routes.test.ts:82)
`frontend/src/app/api/__tests__/routes.test.ts:82` calls `POST http://localhost:3000/api/setup-demo` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:3000/api/setup-demo` If this points at an external …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/admin/audit/log-123 (frontend/src/test/security/audit-trail.test.ts:103)
`frontend/src/test/security/audit-trail.test.ts:103` calls `PUT /api/admin/audit/log-123` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/audit/log-123` If this points at an external API, prefix it with `https:…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/admin/users/current-user/role (frontend/src/test/security/rbac.test.ts:112)
`frontend/src/test/security/rbac.test.ts:112` calls `PUT /api/admin/users/current-user/role` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/users/current-user/role` If this points at an external API, prefix it…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/users/123/role (frontend/src/test/security/rbac.test.ts:217)
`frontend/src/test/security/rbac.test.ts:217` calls `PUT /api/users/123/role` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/users/<p>/role` If this points at an external API, prefix it with `https://` so the matche…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/users/123/role (frontend/src/test/security/rbac.test.ts:221)
`frontend/src/test/security/rbac.test.ts:221` calls `PUT /api/users/123/role` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/users/<p>/role` If this points at an external API, prefix it with `https://` so the matche…
Dangling fetchFetch
high System graph security auth conf 1.00 FastAPI POST `confirm_code` without auth dependency — services/admin/app/tool_verification_routes.py:320
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/admin/app/tool_verification_routes.py:320 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `confirm_lead_erasure` without auth dependency — services/admin/app/tool_verification_routes.py:398
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/admin/app/tool_verification_routes.py:398 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_checkout` without auth dependency — services/ingestion/app/stripe_billing/routes.py:79
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/ingestion/app/stripe_billing/routes.py:79 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_portal_session_for_tenant` without auth dependency — services/ingestion/app/stripe_billing/routes.py:352
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/ingestion/app/stripe_billing/routes.py:352 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_portal_session_legacy` without auth dependency — services/ingestion/app/stripe_billing/routes.py:545
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/ingestion/app/stripe_billing/routes.py:545 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `evaluate_event` without auth dependency — services/ingestion/app/rules_router.py:180
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/ingestion/app/rules_router.py:180 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `import_sensitech` without auth dependency — services/ingestion/app/sensitech_parser.py:214
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/ingestion/app/sensitech_parser.py:214 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `ingest_direct` without auth dependency — services/ingestion/app/routes_ingest.py:581
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/ingestion/app/routes_ingest.py:581 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `ingest_direct` without auth dependency — services/ingestion/app/routes_ingest.py:582
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/ingestion/app/routes_ingest.py:582 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `ingest_edi_856` without auth dependency — services/ingestion/app/edi_ingestion/routes.py:367
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/ingestion/app/edi_ingestion/routes.py:367 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `ingest_edi_document` without auth dependency — services/ingestion/app/edi_ingestion/routes.py:670
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/ingestion/app/edi_ingestion/routes.py:670 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `ingest_epcis_batch` without auth dependency — services/ingestion/app/epcis/router.py:102
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/ingestion/app/epcis/router.py:102 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `ingest_epcis_xml` without auth dependency — services/ingestion/app/epcis/router.py:298
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/ingestion/app/epcis/router.py:298 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `ingest_events` without auth dependency — services/ingestion/app/webhook_router_v2/routes.py:59
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/ingestion/app/webhook_router_v2/routes.py:59 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `ingest_file` without auth dependency — services/ingestion/app/routes_ingest.py:656
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/ingestion/app/routes_ingest.py:656 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `ingest_file` without auth dependency — services/ingestion/app/routes_ingest.py:657
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/ingestion/app/routes_ingest.py:657 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `ingest_regulation` without auth dependency — services/ingestion/app/routes_ingest.py:304
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/ingestion/app/routes_ingest.py:304 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `ingest_regulation` without auth dependency — services/ingestion/app/routes_ingest.py:310
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/ingestion/app/routes_ingest.py:310 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `ingest_url` without auth dependency — services/ingestion/app/routes_ingest.py:738
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/ingestion/app/routes_ingest.py:738 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `ingest_url` without auth dependency — services/ingestion/app/routes_ingest.py:739
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/ingestion/app/routes_ingest.py:739 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `ingest_url` without auth dependency — services/ingestion/app/routes_ingest.py:740
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/ingestion/app/routes_ingest.py:740 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `ingest_url` without auth dependency — services/ingestion/app/routes_ingest.py:741
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/ingestion/app/routes_ingest.py:741 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `preflight_supplier_data` without auth dependency — services/ingestion/app/supplier_portal.py:751
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/ingestion/app/supplier_portal.py:751 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `receive_webhook` without auth dependency — services/ingestion/app/integration_router.py:689
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/ingestion/app/integration_router.py:689 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `receive_webhook` without auth dependency — services/ingestion/app/integration_webhook.py:104
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/ingestion/app/integration_webhook.py:104 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `request_lead_erasure` without auth dependency — services/admin/app/tool_verification_routes.py:378
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/admin/app/tool_verification_routes.py:378 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `run_recall_drill` without auth dependency — services/ingestion/app/proof_recall_router.py:181
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/ingestion/app/proof_recall_router.py:181 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `sandbox_evaluate` without auth dependency — services/ingestion/app/sandbox/router.py:63
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/ingestion/app/sandbox/router.py:63 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `sandbox_share` without auth dependency — services/ingestion/app/sandbox/router.py:280
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/ingestion/app/sandbox/router.py:280 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `sandbox_trace` without auth dependency — services/ingestion/app/sandbox/router.py:255
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/ingestion/app/sandbox/router.py:255 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `stripe_webhook_legacy` without auth dependency — services/ingestion/app/stripe_billing/routes.py:337
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/ingestion/app/stripe_billing/routes.py:337 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `stripe_webhooks` without auth dependency — services/ingestion/app/stripe_billing/routes.py:323
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/ingestion/app/stripe_billing/routes.py:323 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `submit_supplier_data` without auth dependency — services/ingestion/app/supplier_portal.py:766
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/ingestion/app/supplier_portal.py:766 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `verify_email` without auth dependency — services/admin/app/tool_verification_routes.py:272
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/admin/app/tool_verification_routes.py:272 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `verify_export` without auth dependency — services/ingestion/app/proof_verify_router.py:517
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/ingestion/app/proof_verify_router.py:517 securityAuth fastapi unauth mutation
high System graph security security conf 1.00 Insecure pattern 'eval_used' in docs/internal/INTERNAL_TOOLS_AUDIT.json:531
Found a known-risky pattern (eval_used). Review and replace if possible.
docs/internal/INTERNAL_TOOLS_AUDIT.json:531 Eval used
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — frontend/src/__tests__/lib/json-ld.test.ts:4
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — frontend/src/app/docs/layout.tsx:47
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — frontend/src/components/seo/json-ld.tsx:18
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — frontend/src/lib/json-ld.ts:9
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/public/sw.js:56
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/__tests__/api/proxy-sanitization.test.ts:644
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/__tests__/pages/dashboard.test.tsx:74
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/__tests__/pages/inflow-lab.test.tsx:27
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/app/api/__tests__/routes.test.ts:82
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/app/api/billing/checkout/route.ts:46
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/app/api/tools/verify/route.ts:42
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/app/auth/verify/VerifyClient.tsx:46
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/app/developer/portal/codegen/page.tsx:57
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/app/developer/portal/keys/page.tsx:37
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/app/developer/portal/page.tsx:35
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/app/developer/portal/playground/page.tsx:413
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/app/developer/portal/usage/page.tsx:38
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/app/docs/page.tsx:173
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/app/docs/quickstart/page.tsx:179
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/app/login/LoginClient.tsx:189
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/app/sandbox/results/[id]/page.tsx:15
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/app/signup/page.tsx:54
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/app/sysadmin/page.tsx:56
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/fetch-with-csrf.ts:21
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/test/compliance/data-protection.test.ts:45
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/test/security/api-security.test.ts:36
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/test/security/audit-trail.test.ts:88
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/test/security/rbac.test.ts:29
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 — scripts/e2e_tests.js:83
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 — scripts/seed_demo.js:155
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: .claude/agents/sentinel-interstitial.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.
.claude/agents/sentinel-interstitial.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/commands/sentinel-check.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.
.claude/commands/sentinel-check.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/settings.json
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.
.claude/settings.json VerificationClaude instruction
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 GitHub Action is tag-pinned rather than SHA-pinned
peter-evans/create-or-update-comment@v5 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
.github/workflows/sentinel.yml:77 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/security.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in .github/workflows/review-gates.yml:96
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
.github/workflows/review-gates.yml:96 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/src/app/docs/layout.tsx:47
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/src/app/docs/layout.tsx:47 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/src/components/seo/json-ld.tsx:18
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/src/components/seo/json-ld.tsx:18 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in frontend/scripts/production-readiness.mjs:3
Found a known-risky pattern (node_child_process). Review and replace if possible.
frontend/scripts/production-readiness.mjs:3 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in frontend/scripts/verify-public-ssr.mjs:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
frontend/scripts/verify-public-ssr.mjs:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in qa/summary.js:8
Found a known-risky pattern (node_child_process). Review and replace if possible.
qa/summary.js:8 Node child process
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — regengine/swarm/coordinator.py:157
`subprocess.run(...)` 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/e2e_brutal_scenario.py:168
`subprocess.Popen(...)` 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/sentinel-backfill.py:79
`subprocess.run(...)` 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 — services/ingestion/scripts/verify_stripe_billing_e2e.py:141
`subprocess.run(...)` 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 355 placeholder/mock markers across 134 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 network Security conf 1.00 Privileged port 10 in use
Port 10 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
scripts/railway/verify_inflow_workbench_staging.sh Ports
medium System graph network Security conf 1.00 Privileged port 12 in use
Port 12 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
scripts/security/verify_audit_chain.sh Ports
medium System graph network Security conf 1.00 Privileged port 256 in use
Port 256 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
.github/workflows/infra-k8s-ci.yml Ports
medium System graph network Security conf 1.00 Privileged port 29 in use
Port 29 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
.github/workflows/infra-k8s-ci.yml Ports
medium System graph network Security conf 1.00 Privileged port 50 in use
Port 50 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
docs/nfr/slos.yaml Ports
medium System graph network Security conf 1.00 Privileged port 95 in use
Port 95 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
docs/nfr/slos.yaml Ports
medium System graph network Security conf 1.00 Privileged port 99 in use
Port 99 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
docs/nfr/slos.yaml Ports
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 241 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `ADMIN_API_URL`, `ADMIN_DB_MAX_OVERFLOW`, `ADMIN_DB_POOL_SIZE`, `ADMIN_FALLBACK_SQLITE`, `ADMIN_SERVICE_URL`, `ALLOWED_ORIGINS`, `ALLOW_BILLING_STATE_READ_FALLBACK`, `ALLOW_DISABLE_COMPLIANCE_ROUTERS` + 233 more. Add them (with a placeholder/commen…
config drift
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 762 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: 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.
lines 2, 12
frontend/Dockerfile:2, 12 (2 hits)
containersPinned dependencies
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 4, 25
Dockerfile:4, 25 (2 hits)
containersPinned dependencies
low System graph cicd CI/CD security conf 1.00 4 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/checkout@v6 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
lines 26, 35, 40, 87
.github/workflows/sentinel.yml:26, 35, 40, 87 (4 hits)
CI/CD securitySupply chainGithub actions
low System graph quality Integrity conf 1.00 13 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: scripts/check_rls_fallback.py:iter_migration_files, scripts/check_tenant_id_uuid_only.py:iter_migration_files This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document w…
13 occurrences
repo-level (13 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: services/shared/fsma_plan_builder.py:to_dict, services/shared/fsma_plan_builder.py:to_dict, services/shared/fsma_plan_builder.py:to_dict This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene)…
duplicatesduplication
low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 4 places
Functions with the same first-5-line body hash: services/nlp/app/extractors/llm_extractor.py:generate, services/nlp/app/extractors/llm_extractor.py:generate, services/nlp/app/extractors/llm_extractor.py:generate, services/nlp/app/extractors/llm_extractor.py:generate This is *the* AI-coder failure …
2 occurrences
repo-level (2 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 5 places
Functions with the same first-5-line body hash: regengine/swarm/llm.py:generate, regengine/swarm/llm.py:generate, regengine/swarm/llm.py:generate, regengine/swarm/llm.py:generate This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Cons…
duplicatesduplication
low System graph quality Integrity conf 1.00 3 occurrences Near-duplicate function bodies in 7 places
Functions with the same first-5-line body hash: regengine/swarm/agents.py:think, regengine/swarm/agents.py:think, regengine/swarm/agents.py:think, regengine/swarm/agents.py:think This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Cons…
3 occurrences
repo-level (3 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `_event_to_fda_row_v2` in services/ingestion/app/fda_export_service.py:786
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 `_event_to_fda_row_v2` in services/ingestion/tests/test_fda_export_pii_redaction.py:49
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 `_generate_csv_v2` in services/ingestion/app/fda_export/formatters.py:20
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 `_generate_csv_v2` in services/ingestion/app/fda_export/router.py:46
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 `_generate_csv_v2` in services/ingestion/tests/test_fda_export_formatters_1342.py:101
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 `_generate_csv_v2` in services/ingestion/tests/test_fda_export_service_1342.py:18
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 `_hash_v2` in services/admin/tests/test_audit_integrity_1342.py:47
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 `api_v2` in services/ingestion/app/fda_export/queries.py:469
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 `api_v2` in services/ingestion/tests/test_fda_export_queries_1342.py:883
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 `create_portal_session_legacy` in services/ingestion/app/stripe_billing/__init__.py:72
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 `cs_old` in services/ingestion/tests/test_stripe_customers_1342.py:407
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 `customer_copy` in frontend/src/app/dashboard/integrations/page.tsx:585
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 `customer_copy` in frontend/src/app/integrations/page.tsx:130
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 `customer_copy` in frontend/src/app/trust/page.tsx:483
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 `customer_copy` in frontend/src/lib/customer-readiness.ts:64
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 `doc_v1` in scripts/demo_freshness.py:106
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 `dual_write_legacy` in services/shared/canonical_persistence/legacy_dual_write.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 `dual_write_legacy` in services/shared/canonical_persistence/writer.py:340
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 `dual_write_legacy` in services/shared/tests/test_legacy_dual_write_rename_1293.py:25
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 `dual_write_legacy` in tests/shared/test_canonical_dual_write_strict_1277.py:2
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 `energy_nerc_cip_v1` in scripts/verify_fsma_only.py:37
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 `events_v1` in services/ingestion/tests/test_cte_persistence_e2e.py:716
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 `export_fda_spreadsheet_v2` in services/ingestion/tests/test_fda_export_router_1342.py:15
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 `ingesting_regulation_v2` in services/ingestion/app/regulation_loader.py:201
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 `legacy_regex_v1` in services/nlp/app/consumer/conversion.py:192
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 `legacy_regex_v1` in tests/shared/test_nlp_extraction_pg_pipeline.py:282
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 `list_objects_v2` in services/ingestion/app/s3_utils.py:369
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 `list_objects_v2` in services/ingestion/scripts/verify_pipeline.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 `list_objects_v2` in services/ingestion/tests/test_s3_utils_1342.py:111
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 `model_copy` in services/ingestion/app/integration_router.py:420
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 `naive_old` in services/admin/tests/test_graph_outbox_1342.py:279
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 `nLegacy` in scripts/check_legacy_dead_code.py:479
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 `nlp_model_v1` in services/nlp/app/consumer/review_routing.py:85
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 `payload_v1` in tests/data_integrity/test_fsma_204_freshness_phase3b.py:69
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 `recomputed_v2` in services/admin/app/audit_integrity.py:91
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 `rge_legacy` in services/admin/tests/test_review_hardening.py:515
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 `rge_live_legacy` in tests/shared/test_api_key_store.py:295
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 `rule_v1` in tests/invariants/test_invariants.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 `seed_v1` in scripts/seed_v1_data.py:25
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 `signed_legacy` in services/nlp/app/consumer/__init__.py:853
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 `stripe_webhook_legacy` in services/ingestion/app/stripe_billing/routes.py:343
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 `stripe_webhook_legacy` in services/ingestion/tests/test_stripe_routes_1342.py:445
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 `sub_bad_old` in services/ingestion/tests/test_stripe_state_1342.py:441
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_core_module_header_not_legacy` in tests/shared/test_cte_persistence_cluster_1323_1324_1334_1335.py:276
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_get_dead_letters_returns_copy` in services/scheduler/tests/test_notifications.py:176
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_mixed_per_service_and_legacy` in services/shared/tests/test_kafka_auth_kid.py:165
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_old_payload_without_schema_version_parses_as_v1` in services/shared/tests/test_canonical_event_schema_version_1197.py:173
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_send_link_db_read_ok_write_fails_with_no_memory_copy` in services/ingestion/tests/test_supplier_mgmt_1342.py:354
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 `webhook_router_v2` in frontend/next.config.js:202
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 `webhook_router_v2` in scripts/verify_inflow_to_regengine_e2e.py:161
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 `webhook_router_v2` in server/main.py:211
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 `webhook_router_v2` in services/ingestion/app/exception_router.py:37
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 `webhook_router_v2` in services/ingestion/app/identity_router.py:36
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 `webhook_router_v2` in services/ingestion/app/middleware/ratelimit_headers.py:10
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `webhook_router_v2` in services/ingestion/app/request_workflow_router.py:39
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 `webhook_router_v2` in services/ingestion/app/routes_health_metrics.py:59
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 `webhook_router_v2` in services/ingestion/app/webhook_compat.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 `webhook_router_v2` in services/ingestion/app/webhook_router_v2/__init__.py:13
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 `webhook_router_v2` in services/ingestion/app/webhook_router_v2/graph_sync.py:4
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `webhook_router_v2` in services/ingestion/app/webhook_router_v2/metrics.py:4
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `webhook_router_v2` in services/ingestion/app/webhook_router_v2/ratelimit.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 `webhook_router_v2` in services/ingestion/app/webhook_router_v2/routes.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 `webhook_router_v2` in services/ingestion/app/webhook_router_v2/rules_eval.py:4
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `webhook_router_v2` in services/ingestion/app/webhook_router_v2/security.py:4
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `webhook_router_v2` in services/ingestion/app/webhook_router_v2/tenant.py:4
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `webhook_router_v2` in services/ingestion/app/webhook_router_v2/validation.py:4
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `webhook_router_v2` in services/ingestion/main.py:131
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 `webhook_router_v2` in services/ingestion/tests/test_dual_write_timeout_1335.py:16
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 `webhook_router_v2` in services/ingestion/tests/test_inflow_lab_contract.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 `webhook_router_v2` in services/ingestion/tests/test_webhook_funnel_events.py:17
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 `webhook_router_v2` in services/ingestion/tests/test_webhook_hmac_and_replay.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 `webhook_router_v2` in services/ingestion/tests/test_webhook_rate_limit.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 `webhook_router_v2` in services/ingestion/tests/test_webhook_replay_metric.py:29
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 `webhook_router_v2` in services/ingestion/tests/test_webhook_router_v2_1342.py:1
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `webhook_router_v2` in services/ingestion/tests/test_webhook_router_v2_canonical_helper.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 `webhook_router_v2` in services/ingestion/tests/test_webhook_router_v2_enforcement.py:2
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 `webhook_router_v2` in services/ingestion/tests/test_webhook_router_v2_idor_f1.py:31
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 `webhook_router_v2` in services/ingestion/tests/test_webhook_trailing_lows_infos.py:32
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 `webhook_router_v2` in services/ingestion/tests/test_webhook_verify_api_key_1888.py:1
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `webhook_router_v2` in services/shared/cte_persistence/core.py:8
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 `webhook_router_v2` in services/shared/cte_persistence/tests/test_append_only_1334_1335.py:9
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `webhook_router_v2` in services/shared/rules/enforcement.py:57
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 `webhook_router_v2` in services/shared/tests/test_rules_enforcement_manifest.py:106
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 `webhook_router_v2` in tests/test_server_idempotency_middleware.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 software Dead code conf 1.00 Possibly dead Python function: build_demo_rules
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/seed_demo_data.py:510
low System graph software Dead code conf 1.00 Possibly dead Python function: check_correlation_middleware
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/verify_production_readiness.py:165
low System graph software Dead code conf 1.00 Possibly dead Python function: check_ftl
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
regengine/client.py:360
low System graph software Dead code conf 1.00 Possibly dead Python function: check_hash_chain_continuity
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/validate_data_integrity.py:42
low System graph software Dead code conf 1.00 Possibly dead Python function: check_orphaned_records
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/validate_data_integrity.py:66
low System graph software Dead code conf 1.00 Possibly dead Python function: check_railway_deployment_workflow
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/verify_production_readiness.py:268
low System graph software Dead code conf 1.00 Possibly dead Python function: check_rate_limit_security
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/verify_production_readiness.py:217
low System graph software Dead code conf 1.00 Possibly dead Python function: check_tenant_isolation
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/validate_data_integrity.py:96
low System graph software Dead code conf 1.00 Possibly dead Python function: check_texas_scraper_inheritance
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/verify_production_readiness.py:98
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_compliance
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
regengine/swarm/cli.py:413
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_label
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
regengine/swarm/cli.py:318
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_solve
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
regengine/swarm/cli.py:278
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_sweep
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
regengine/swarm/cli.py:401
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_troubleshoot
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
regengine/swarm/cli.py:243
low System graph software Dead code conf 1.00 Possibly dead Python function: contains_point
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
services/nlp/app/extractors/table_extractor.py:95
low System graph software Dead code conf 1.00 Possibly dead Python function: create_branch
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
regengine/swarm/github_integration.py:127
low System graph software Dead code conf 1.00 Possibly dead Python function: generate_batch_labels
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
regengine/labels.py:245
low System graph software Dead code conf 1.00 Possibly dead Python function: handle_data
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
services/nlp/app/text_loader.py:103
low System graph software Dead code conf 1.00 Possibly dead Python function: load_s3_artifact
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
services/nlp/app/s3_loader.py:32
low System graph software Dead code conf 1.00 Possibly dead Python function: query_records
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
regengine/client.py:266
low System graph software Dead code conf 1.00 Possibly dead Python function: scheduled_job
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/scheduler/fsma_auto_ingest.py:326
low System graph software Dead code conf 1.00 Possibly dead Python function: start_recall_drill
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
regengine/client.py:377
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 — frontend/src/app/developer/portal/codegen/page.tsx:74
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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — frontend/src/app/docs/page.tsx:200
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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — frontend/src/app/docs/quickstart/page.tsx:183
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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — frontend/tests/e2e/global-setup.ts:39
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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — frontend/tests/e2e/invite_flow.spec.ts:18
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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — qa/ai-analysis.js:18
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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — qa/bad-data.js:19
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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — qa/decision.js:12
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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — qa/drift-check.js:21
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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — qa/export-validate.js:19
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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — qa/fsma-lite-check.js:39
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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — qa/full-flow.js:22
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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — qa/regression.js:30
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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — qa/summary.js:75
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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — qa/tenant-test.js:15
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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/e2e_tests.js:54
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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/seed_demo.js:120
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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/test_fsma_endpoints.js:106
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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — tests/load/k6-admin-test.js:214
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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — tests/load/k6-ingestion-test.js:201
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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — tests/load/user-journey.js:184
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 quality Integrity conf 1.00 Stub function `_local_subscription` (body is just `pass`/`return`) — scripts/verify_inflow_to_regengine_e2e.py:180
Likely an AI scaffold that was never filled in. Remove or implement.
Empty handlerDead code
low System graph quality Integrity conf 1.00 Stub function `generate` (body is just `pass`/`return`) — services/nlp/app/extractors/llm_extractor.py:253
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: GET /
`server/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 /api/v1/features
`server/main.py` declares `GET /api/v1/features` 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 /billing/plans
`server/main.py` declares `GET /billing/plans` 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 /chain
`services/ingestion/app/auditor_router.py` declares `GET /chain` 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 /checklists
`services/compliance/app/routes.py` declares `GET /checklists` 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 /checklists/{checklist_id}
`services/compliance/app/routes.py` declares `GET /checklists/{checklist_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 /drill/{drill_id}
`services/ingestion/app/mock_audit.py` declares `GET /drill/{drill_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 /evaluations/{event_id}
`services/ingestion/app/rules_router.py` declares `GET /evaluations/{event_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 /events
`services/ingestion/app/auditor_router.py` declares `GET /events` 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 /events/{event_id}
`services/ingestion/app/auditor_router.py` declares `GET /events/{event_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 /exceptions
`services/ingestion/app/auditor_router.py` declares `GET /exceptions` 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 /export-log
`services/ingestion/app/auditor_router.py` declares `GET /export-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 /formats
`services/ingestion/app/epcis_export.py` declares `GET /formats` 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 /industries
`services/compliance/app/routes.py` declares `GET /industries` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /ingestion-runs
`services/ingestion/app/canonical_router.py` declares `GET /ingestion-runs` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /ingestion-runs/{run_id}
`services/ingestion/app/canonical_router.py` declares `GET /ingestion-runs/{run_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 consum…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /readiness
`server/main.py` declares `GET /readiness` 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 /ready
`services/shared/observability/health.py` declares `GET /ready` 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 /requests
`services/ingestion/app/auditor_router.py` declares `GET /requests` 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 /rules
`services/ingestion/app/auditor_router.py` declares `GET /rules` 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

Showing first 300 of 341. Refine filters or use the findings page for deep search.

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/34517643-fb21-41b7-aec9-29b49cb666dd/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/34517643-fb21-41b7-aec9-29b49cb666dd/

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.