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

YEONGJUCHO2/MSDS-App

https://github.com/YEONGJUCHO2/MSDS-App · scanned 2026-06-16 01:05 UTC (2 months, 1 week ago)

176 raw signals (22 security + 154 graph)

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

Complete repo analysis

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

JSON
Combined
72.0
/100
Security checks
72
8 findings
System graph
72
100.0% cov · 153 findings
Critical
2
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 2 High 91 Medium 10 Low 57 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 8 System graph 153 Crowd 0 Layer: Quality 23 Security 1 Frontend 8 Cicd 1 Api 128
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 72.0/100 with 100.0% coverage. It contains 1767 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 154 findings — concentrated in api (128), quality (16), frontend (8). Risk profile is high: 0 critical, 87 high, 8 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

Showing 160 of 161 actionable findings. 269 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

critical Security checks quality Practices conf 0.82 5 occurrences Foundry mined mock as real or placeholder: YEONGJUCHO2/MSDS-App
Graph query export: Mock, sample, placeholder, or self-attested behavior treated as real Query id: mock_as_real_or_placeholder Query type: motif_query Intent: Hard negatives for fake completeness and missing real data paths. Motif: mock_as_real_or_placeholder Training usage: hard_negative Graph gol…
5 occurrences
repo-level (5 hits)
critical Security checks security auth conf 0.78 2 occurrences Foundry mined security auth guardrail gaps: YEONGJUCHO2/MSDS-App
Graph query export: Security/auth changes without enough guardrails Query id: security_auth_guardrail_gaps Query type: motif_query Intent: Assumption-check security/auth examples requiring stronger tests or CI. Motif: security_auth_without_guardrails Training usage: assumption_check Graph gold labe…
2 occurrences
repo-level (2 hits)
high Security checks quality Practices conf 0.84 24 occurrences Foundry mined bad chains: YEONGJUCHO2/MSDS-App
Comment chain pattern product: bad_chains Repo: YEONGJUCHO2/MSDS-App Thread: YEONGJUCHO2/MSDS-App#8 Outcome: not_resolved_or_not_observed Thread label: thread_has_human_issue_without_fix_context Source graph label: source_backed_multi_signal_graph Reasons: source_graph_has_real_artifacts, source_gr…
24 occurrences
repo-level (24 hits)
high Security checks quality Practices conf 0.80 Foundry mined docs only runtime fix: YEONGJUCHO2/MSDS-App
Graph query export: Docs-only response to runtime or integration issue Query id: docs_only_runtime_fix Query type: motif_query Intent: Assumption-check examples where docs or claims are not enough proof. Motif: docs_only_runtime_fix Training usage: assumption_check Graph gold label: needs_more_evid…
high Security checks quality Quality conf 0.76 14 occurrences Foundry mined schema ui api mismatch: YEONGJUCHO2/MSDS-App
Graph query export: Schema, UI, and API mismatch Query id: schema_ui_api_mismatch Query type: motif_query Intent: Assumption-check examples for data-path consistency across layers. Motif: schema_ui_api_mismatch Training usage: assumption_check Graph gold label: needs_more_evidence Repo: YEONGJUCHO2…
14 occurrences
repo-level (14 hits)
high Security checks quality Testing conf 0.78 9 occurrences Foundry mined test ci gap after feedback: YEONGJUCHO2/MSDS-App
Graph query export: Feedback exposes missing tests or CI Query id: test_ci_gap_after_feedback Query type: motif_query Intent: Hard negatives for feedback/fix chains without adequate guardrails. Motif: test_ci_gap_after_feedback Training usage: hard_negative Graph gold label: supported_by_verificati…
9 occurrences
repo-level (9 hits)
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/documents/${documentId} (src/api/client.ts:300)
`src/api/client.ts:300` calls `DELETE /api/documents/${documentId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/documents/<p>` If this points at an external API, prefix it with `https://` so the matcher …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/documents/${documentId}/components/${rowId} (src/api/client.ts:335)
`src/api/client.ts:335` calls `DELETE /api/documents/${documentId}/components/${rowId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/documents/<p>/components/<p>` If this points at an external API, prefix…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/products/${productId} (src/api/client.ts:363)
`src/api/client.ts:363` calls `DELETE /api/products/${productId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/products/<p>` If this points at an external API, prefix it with `https://` so the matcher ski…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/products/sites/${siteId} (src/api/client.ts:361)
`src/api/client.ts:361` calls `DELETE /api/products/sites/${siteId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/products/sites/<p>` If this points at an external API, prefix it with `https://` so the ma…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: DELETE http://127.0.0.1:${port}/api/documents/doc-1 (tests/services/apiRoutes.test.ts:537)
`tests/services/apiRoutes.test.ts:537` calls `DELETE http://127.0.0.1:${port}/api/documents/doc-1` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/documents/doc-1` If this points at an extern…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE http://127.0.0.1:${port}/api/documents/doc-1 (tests/services/apiRoutes.test.ts:981)
`tests/services/apiRoutes.test.ts:981` calls `DELETE http://127.0.0.1:${port}/api/documents/doc-1` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/documents/doc-1` If this points at an extern…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE http://127.0.0.1:${port}/api/documents/doc-delete (tests/services/apiRoutes.test.ts:356)
`tests/services/apiRoutes.test.ts:356` calls `DELETE http://127.0.0.1:${port}/api/documents/doc-delete` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/documents/doc-delete` If this points at…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE http://127.0.0.1:${port}/api/documents/doc-delete (tests/services/apiRoutes.test.ts:445)
`tests/services/apiRoutes.test.ts:445` calls `DELETE http://127.0.0.1:${port}/api/documents/doc-delete` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/documents/doc-delete` If this points at…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE http://127.0.0.1:${port}/api/documents/doc-delete (tests/services/apiRoutes.test.ts:480)
`tests/services/apiRoutes.test.ts:480` calls `DELETE http://127.0.0.1:${port}/api/documents/doc-delete` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/documents/doc-delete` If this points at…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE http://127.0.0.1:${port}/api/documents/doc-delete (tests/services/apiRoutes.test.ts:501)
`tests/services/apiRoutes.test.ts:501` calls `DELETE http://127.0.0.1:${port}/api/documents/doc-delete` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/documents/doc-delete` If this points at…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE http://127.0.0.1:${port}/api/documents/doc-other (tests/services/apiRoutes.test.ts:392)
`tests/services/apiRoutes.test.ts:392` calls `DELETE http://127.0.0.1:${port}/api/documents/doc-other` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/documents/doc-other` If this points at a…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/documents (src/api/client.ts:288)
`src/api/client.ts:288` calls `GET /api/documents` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/documents` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/documents/${documentId}/basic-info (src/api/client.ts:307)
`src/api/client.ts:307` calls `GET /api/documents/${documentId}/basic-info` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/documents/<p>/basic-info` If this points at an external API, prefix it with `https:…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/documents/${documentId}/components (src/api/client.ts:316)
`src/api/client.ts:316` calls `GET /api/documents/${documentId}/components` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/documents/<p>/components` If this points at an external API, prefix it with `https:…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/documents/${documentId}/detail-core (src/api/client.ts:308)
`src/api/client.ts:308` calls `GET /api/documents/${documentId}/detail-core` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/documents/<p>/detail-core` If this points at an external API, prefix it with `http…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/documents/${documentId}/safety-materials (src/api/client.ts:296)
`src/api/client.ts:296` calls `GET /api/documents/${documentId}/safety-materials` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/documents/<p>/safety-materials` If this points at an external API, prefix it …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/jobs/status${suffix} (src/api/client.ts:320)
`src/api/client.ts:320` calls `GET /api/jobs/status${suffix}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/jobs/status/<p>` If this points at an external API, prefix it with `https://` so the matcher skip…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/official-lookups/status (src/api/client.ts:350)
`src/api/client.ts:350` calls `GET /api/official-lookups/status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/official-lookups/status` If this points at an external API, prefix it with `https://` so the m…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/products (src/api/client.ts:358)
`src/api/client.ts:358` calls `GET /api/products` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/products` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/products/sites (src/api/client.ts:359)
`src/api/client.ts:359` calls `GET /api/products/sites` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/products/sites` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/queues (src/api/client.ts:315)
`src/api/client.ts:315` calls `GET /api/queues` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/queues` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/watchlist (src/api/client.ts:351)
`src/api/client.ts:351` calls `GET /api/watchlist` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/watchlist` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${missingSchemaPort}/api/jobs/drain (tests/services/apiRoutes.test.ts:1060)
`tests/services/apiRoutes.test.ts:1060` calls `GET http://127.0.0.1:${missingSchemaPort}/api/jobs/drain` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/jobs/drain` If this points at an exter…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/api/documents (tests/services/apiRoutes.test.ts:59)
`tests/services/apiRoutes.test.ts:59` calls `GET http://127.0.0.1:${port}/api/documents` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/documents` If this points at an external API, prefix i…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/api/documents (tests/services/app.test.ts:15)
`tests/services/app.test.ts:15` calls `GET http://127.0.0.1:${port}/api/documents` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/documents` If this points at an external API, prefix it with…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/api/documents (tests/services/app.test.ts:49)
`tests/services/app.test.ts:49` calls `GET http://127.0.0.1:${port}/api/documents` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/documents` If this points at an external API, prefix it with…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/api/documents/doc-1/basic-info (tests/services/apiRoutes.test.ts:172)
`tests/services/apiRoutes.test.ts:172` calls `GET http://127.0.0.1:${port}/api/documents/doc-1/basic-info` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/documents/doc-1/basic-info` If this …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/api/documents/doc-1/basic-info (tests/services/apiRoutes.test.ts:212)
`tests/services/apiRoutes.test.ts:212` calls `GET http://127.0.0.1:${port}/api/documents/doc-1/basic-info` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/documents/doc-1/basic-info` If this …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/api/documents/doc-1/components (tests/services/apiRoutes.test.ts:333)
`tests/services/apiRoutes.test.ts:333` calls `GET http://127.0.0.1:${port}/api/documents/doc-1/components` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/documents/doc-1/components` If this …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/api/documents/doc-1/detail-core (tests/services/apiRoutes.test.ts:234)
`tests/services/apiRoutes.test.ts:234` calls `GET http://127.0.0.1:${port}/api/documents/doc-1/detail-core` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/documents/doc-1/detail-core` If thi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/api/documents/doc-1/detail-core (tests/services/apiRoutes.test.ts:290)
`tests/services/apiRoutes.test.ts:290` calls `GET http://127.0.0.1:${port}/api/documents/doc-1/detail-core` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/documents/doc-1/detail-core` If thi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/api/documents/doc-1/file (tests/services/apiRoutes.test.ts:313)
`tests/services/apiRoutes.test.ts:313` calls `GET http://127.0.0.1:${port}/api/documents/doc-1/file` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/documents/doc-1/file` If this points at an…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/api/documents/doc-1/safety-materials (tests/services/apiRoutes.test.ts:569)
`tests/services/apiRoutes.test.ts:569` calls `GET http://127.0.0.1:${port}/api/documents/doc-1/safety-materials` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/documents/doc-1/safety-materia…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/api/documents/doc-1/safety-materials (tests/services/apiRoutes.test.ts:604)
`tests/services/apiRoutes.test.ts:604` calls `GET http://127.0.0.1:${port}/api/documents/doc-1/safety-materials` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/documents/doc-1/safety-materia…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/api/documents/doc-1/safety-materials/warning-label/pdf (tests/services/apiRoutes.test.ts:571)
`tests/services/apiRoutes.test.ts:571` calls `GET http://127.0.0.1:${port}/api/documents/doc-1/safety-materials/warning-label/pdf` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/documents/do…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/api/documents/doc-1/safety-materials/warning-label/pptx (tests/services/apiRoutes.test.ts:570)
`tests/services/apiRoutes.test.ts:570` calls `GET http://127.0.0.1:${port}/api/documents/doc-1/safety-materials/warning-label/pptx` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/documents/d…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/api/documents/doc-1/safety-materials/warning-label/pptx (tests/services/apiRoutes.test.ts:605)
`tests/services/apiRoutes.test.ts:605` calls `GET http://127.0.0.1:${port}/api/documents/doc-1/safety-materials/warning-label/pptx` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/documents/d…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/api/documents/missing/detail-core (tests/services/apiRoutes.test.ts:291)
`tests/services/apiRoutes.test.ts:291` calls `GET http://127.0.0.1:${port}/api/documents/missing/detail-core` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/documents/missing/detail-core` If…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/api/health (tests/services/apiRoutes.test.ts:58)
`tests/services/apiRoutes.test.ts:58` calls `GET http://127.0.0.1:${port}/api/health` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/health` If this points at an external API, prefix it with…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/api/health (tests/services/app.test.ts:14)
`tests/services/app.test.ts:14` calls `GET http://127.0.0.1:${port}/api/health` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/health` If this points at an external API, prefix it with `http…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/api/jobs/drain (tests/services/apiRoutes.test.ts:1069)
`tests/services/apiRoutes.test.ts:1069` calls `GET http://127.0.0.1:${port}/api/jobs/drain` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/jobs/drain` If this points at an external API, pref…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/api/jobs/drain (tests/services/apiRoutes.test.ts:1070)
`tests/services/apiRoutes.test.ts:1070` calls `GET http://127.0.0.1:${port}/api/jobs/drain` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/jobs/drain` If this points at an external API, pref…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/api/jobs/drain (tests/services/apiRoutes.test.ts:1073)
`tests/services/apiRoutes.test.ts:1073` calls `GET http://127.0.0.1:${port}/api/jobs/drain` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/jobs/drain` If this points at an external API, pref…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/api/jobs/status (tests/services/apiRoutes.test.ts:1000)
`tests/services/apiRoutes.test.ts:1000` calls `GET http://127.0.0.1:${port}/api/jobs/status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/jobs/status` If this points at an external API, pr…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/api/jobs/status (tests/services/apiRoutes.test.ts:1001)
`tests/services/apiRoutes.test.ts:1001` calls `GET http://127.0.0.1:${port}/api/jobs/status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/jobs/status` If this points at an external API, pr…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/api/jobs/status?jobIds=job-1,job-other (tests/services/apiRoutes.test.ts:1018)
`tests/services/apiRoutes.test.ts:1018` calls `GET http://127.0.0.1:${port}/api/jobs/status?jobIds=job-1,job-other` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/jobs/status` If this points…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/api/jobs/status?jobIds=job-other (tests/services/apiRoutes.test.ts:1041)
`tests/services/apiRoutes.test.ts:1041` calls `GET http://127.0.0.1:${port}/api/jobs/status?jobIds=job-other` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/jobs/status` If this points at an…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/api/protected (tests/services/auth.test.ts:215)
`tests/services/auth.test.ts:215` calls `GET http://127.0.0.1:${port}/api/protected` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/protected` If this points at an external API, prefix it wi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/api/protected (tests/services/auth.test.ts:65)
`tests/services/auth.test.ts:65` calls `GET http://127.0.0.1:${port}/api/protected` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/protected` If this points at an external API, prefix it wit…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/api/protected (tests/services/auth.test.ts:93)
`tests/services/auth.test.ts:93` calls `GET http://127.0.0.1:${port}/api/protected` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/protected` If this points at an external API, prefix it wit…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/api/usage/report (tests/services/usageRoutes.test.ts:40)
`tests/services/usageRoutes.test.ts:40` calls `GET http://127.0.0.1:${port}/api/usage/report` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/usage/report` If this points at an external API, …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/api/watchlist/auto-recheck (tests/services/apiRoutes.test.ts:117)
`tests/services/apiRoutes.test.ts:117` calls `GET http://127.0.0.1:${port}/api/watchlist/auto-recheck` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/watchlist/auto-recheck` If this points a…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/api/watchlist/auto-recheck (tests/services/apiRoutes.test.ts:137)
`tests/services/apiRoutes.test.ts:137` calls `GET http://127.0.0.1:${port}/api/watchlist/auto-recheck` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/watchlist/auto-recheck` If this points a…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/api/watchlist/auto-recheck?secret=test-cron-secret (tests/services/apiRoutes.test.ts:153)
`tests/services/apiRoutes.test.ts:153` calls `GET http://127.0.0.1:${port}/api/watchlist/auto-recheck?secret=test-cron-secret` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/watchlist/auto-r…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /api/documents/${documentId} (src/api/client.ts:302)
`src/api/client.ts:302` calls `PATCH /api/documents/${documentId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/documents/<p>` If this points at an external API, prefix it with `https://` so the matcher s…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /api/documents/${documentId}/basic-info (src/api/client.ts:310)
`src/api/client.ts:310` calls `PATCH /api/documents/${documentId}/basic-info` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/documents/<p>/basic-info` If this points at an external API, prefix it with `http…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /api/documents/${documentId}/components/${rowId} (src/api/client.ts:329)
`src/api/client.ts:329` calls `PATCH /api/documents/${documentId}/components/${rowId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/documents/<p>/components/<p>` If this points at an external API, prefix …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PATCH http://127.0.0.1:${port}/api/documents/doc-1/basic-info (tests/services/apiRoutes.test.ts:180)
`tests/services/apiRoutes.test.ts:180` calls `PATCH http://127.0.0.1:${port}/api/documents/doc-1/basic-info` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/documents/doc-1/basic-info` If thi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PATCH http://127.0.0.1:${port}/api/documents/doc-1/basic-info (tests/services/apiRoutes.test.ts:786)
`tests/services/apiRoutes.test.ts:786` calls `PATCH http://127.0.0.1:${port}/api/documents/doc-1/basic-info` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/documents/doc-1/basic-info` If thi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/documents/${documentId}/components (src/api/client.ts:323)
`src/api/client.ts:323` calls `POST /api/documents/${documentId}/components` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/documents/<p>/components` If this points at an external API, prefix it with `https…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/documents/${documentId}/components/${rowId}/recheck (src/api/client.ts:337)
`src/api/client.ts:337` calls `POST /api/documents/${documentId}/components/${rowId}/recheck` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/documents/<p>/components/<p>/recheck` If this points at an extern…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/documents/${documentId}/components/${rowId}/review (src/api/client.ts:345)
`src/api/client.ts:345` calls `POST /api/documents/${documentId}/components/${rowId}/review` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/documents/<p>/components/<p>/review` If this points at an external…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/documents/${documentId}/replacement (src/api/client.ts:380)
`src/api/client.ts:380` calls `POST /api/documents/${documentId}/replacement` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/documents/<p>/replacement` If this points at an external API, prefix it with `htt…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/documents/recheck (src/api/client.ts:339)
`src/api/client.ts:339` calls `POST /api/documents/recheck` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/documents/recheck` If this points at an external API, prefix it with `https://` so the matcher skip…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/documents/upload (src/api/client.ts:375)
`src/api/client.ts:375` calls `POST /api/documents/upload` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/documents/upload` If this points at an external API, prefix it with `https://` so the matcher skips …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/documents/upload-batch (src/api/client.ts:390)
`src/api/client.ts:390` calls `POST /api/documents/upload-batch` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/documents/upload-batch` If this points at an external API, prefix it with `https://` so the ma…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/products (src/api/client.ts:367)
`src/api/client.ts:367` calls `POST /api/products` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/products` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/products/documents/${documentId}/revision-needed (src/api/client.ts:365)
`src/api/client.ts:365` calls `POST /api/products/documents/${documentId}/revision-needed` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/products/documents/<p>/revision-needed` If this points at an externa…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/watchlist/recheck (src/api/client.ts:353)
`src/api/client.ts:353` calls `POST /api/watchlist/recheck` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/watchlist/recheck` If this points at an external API, prefix it with `https://` so the matcher skip…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/api/documents/doc-1/components (tests/services/apiRoutes.test.ts:630)
`tests/services/apiRoutes.test.ts:630` calls `POST http://127.0.0.1:${port}/api/documents/doc-1/components` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/documents/doc-1/components` If this…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/api/documents/doc-1/components (tests/services/apiRoutes.test.ts:822)
`tests/services/apiRoutes.test.ts:822` calls `POST http://127.0.0.1:${port}/api/documents/doc-1/components` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/documents/doc-1/components` If this…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/api/documents/doc-1/components/row-1/recheck (tests/services/apiRoutes.test.ts:1093)
`tests/services/apiRoutes.test.ts:1093` calls `POST http://127.0.0.1:${port}/api/documents/doc-1/components/row-1/recheck` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/documents/doc-1/comp…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/api/documents/doc-1/replacement (tests/services/apiRoutes.test.ts:664)
`tests/services/apiRoutes.test.ts:664` calls `POST http://127.0.0.1:${port}/api/documents/doc-1/replacement` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/documents/doc-1/replacement` If th…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/api/documents/doc-1/replacement (tests/services/apiRoutes.test.ts:699)
`tests/services/apiRoutes.test.ts:699` calls `POST http://127.0.0.1:${port}/api/documents/doc-1/replacement` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/documents/doc-1/replacement` If th…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/api/documents/doc-1/replacement (tests/services/apiRoutes.test.ts:737)
`tests/services/apiRoutes.test.ts:737` calls `POST http://127.0.0.1:${port}/api/documents/doc-1/replacement` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/documents/doc-1/replacement` If th…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/api/documents/doc-1/safety-materials/regenerate (tests/services/apiRoutes.test.ts:1119)
`tests/services/apiRoutes.test.ts:1119` calls `POST http://127.0.0.1:${port}/api/documents/doc-1/safety-materials/regenerate` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/documents/doc-1/s…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/api/documents/recheck (tests/services/apiRoutes.test.ts:804)
`tests/services/apiRoutes.test.ts:804` calls `POST http://127.0.0.1:${port}/api/documents/recheck` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/documents/recheck` If this points at an exte…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/api/documents/upload (tests/services/apiRoutes.test.ts:766)
`tests/services/apiRoutes.test.ts:766` calls `POST http://127.0.0.1:${port}/api/documents/upload` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/documents/upload` If this points at an extern…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/api/documents/upload (tests/services/apiRoutes.test.ts:885)
`tests/services/apiRoutes.test.ts:885` calls `POST http://127.0.0.1:${port}/api/documents/upload` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/documents/upload` If this points at an extern…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/api/documents/upload (tests/services/apiRoutes.test.ts:908)
`tests/services/apiRoutes.test.ts:908` calls `POST http://127.0.0.1:${port}/api/documents/upload` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/documents/upload` If this points at an extern…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/api/documents/upload (tests/services/apiRoutes.test.ts:932)
`tests/services/apiRoutes.test.ts:932` calls `POST http://127.0.0.1:${port}/api/documents/upload` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/documents/upload` If this points at an extern…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/api/documents/upload (tests/services/apiRoutes.test.ts:960)
`tests/services/apiRoutes.test.ts:960` calls `POST http://127.0.0.1:${port}/api/documents/upload` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/documents/upload` If this points at an extern…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/api/imports/regulatory-seeds (tests/services/apiRoutes.test.ts:93)
`tests/services/apiRoutes.test.ts:93` calls `POST http://127.0.0.1:${port}/api/imports/regulatory-seeds` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/imports/regulatory-seeds` If this poin…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/api/products (tests/services/apiRoutes.test.ts:858)
`tests/services/apiRoutes.test.ts:858` calls `POST http://127.0.0.1:${port}/api/products` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/products` If this points at an external API, prefix i…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/api/products/from-documents (tests/services/apiRoutes.test.ts:74)
`tests/services/apiRoutes.test.ts:74` calls `POST http://127.0.0.1:${port}/api/products/from-documents` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/products/from-documents` If this points…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/api/watchlist/recheck (tests/services/apiRoutes.test.ts:840)
`tests/services/apiRoutes.test.ts:840` calls `POST http://127.0.0.1:${port}/api/watchlist/recheck` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/watchlist/recheck` If this points at an exte…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://generativelanguage.googleapis.com/v1beta/models/${encodeURIComponent(input.model)}:generateContent (server/services/geminiMsdsExtractor.ts:254)
`server/services/geminiMsdsExtractor.ts:254` calls `POST https://generativelanguage.googleapis.com/v1beta/models/${encodeURIComponent(input.model)}:generateContent` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/htt…
Dangling fetchFetch
medium Security checks quality Practices conf 0.62 29 occurrences Foundry mined assumption checks: YEONGJUCHO2/MSDS-App
Comment chain pattern product: assumption_checks Repo: YEONGJUCHO2/MSDS-App Thread: YEONGJUCHO2/MSDS-App#9 Outcome: ambiguous_needs_more_evidence Thread label: thread_has_human_issue_and_fix_context Source graph label: source_backed_multi_signal_graph Reasons: source_graph_has_real_artifacts, sourc…
29 occurrences
repo-level (29 hits)
medium Security checks quality Practices conf 0.70 31 occurrences Foundry mined unresolved feedback: YEONGJUCHO2/MSDS-App
Graph query export: Human feedback without linked fix evidence Query id: unresolved_feedback Query type: motif_query Intent: Negative/unresolved examples that should not be hallucinated into fixes. Motif: unlinked_feedback_needs_evidence Training usage: negative_or_unresolved Graph gold label: need…
31 occurrences
repo-level (31 hits)
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — server/middleware/auth.ts:246
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: .codex/hooks.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.
.codex/hooks.json VerificationCodex instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: phases/05-regulatory-watch-pipeline/AGENTS.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.
phases/05-regulatory-watch-pipeline/AGENTS.md VerificationAgents md
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: phases/06-release-defect-hardening/AGENTS.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.
phases/06-release-defect-hardening/AGENTS.md VerificationAgents md
medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing license. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.
Repo hardeningGenerated repo pattern
medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/execute.py:111
`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 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 24 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `E2E_AUTH_BROWSER_CHANNEL`, `E2E_AUTH_ORIGIN`, `E2E_AUTH_STATE`, `E2E_BASE_URL`, `E2E_QA_USER_EMAIL`, `E2E_VERCEL_BYPASS_SECRET`, `MSDS_AUTO_RECHECK_GLOBAL_MAX`, `MSDS_AUTO_RECHECK_OWNER_USER_ID` + 16 more. Add them (with a placeholder/comment) to …
config drift
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 63 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 cicd CI/CD security conf 1.00 2 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/checkout@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
lines 14, 17
.github/workflows/ci.yml:14, 17 (2 hits)
CI/CD securitySupply chainGithub actions
low System graph quality License conf 1.00 No license file detected
No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.
Repo hardeningGenerated repo pattern
low System graph quality 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 — scripts/buildClaudeDesignPacket.ts:191
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/captureE2eAuthState.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 — scripts/refreshE2eAuthState.ts:56
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 — server/index.ts:10
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 — server/scripts/backfillMvpReview.ts:27
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 — server/scripts/benchmarkGeminiExtraction.ts:81
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 — server/scripts/preflightChemicalApiCache.ts:6
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 — server/scripts/seed.ts:9
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /:documentId
`server/routes/documents.ts` declares `DELETE /:documentId` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /:documentId/components/:rowId
`server/routes/documents.ts` declares `DELETE /:documentId/components/:rowId` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /:productId
`server/routes/products.ts` declares `DELETE /:productId` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /sites/:siteId
`server/routes/products.ts` declares `DELETE /sites/:siteId` 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 /
`server/routes/watchlist.ts` 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 /:documentId/basic-info
`server/routes/documents.ts` declares `GET /:documentId/basic-info` 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 /:documentId/components
`server/routes/documents.ts` declares `GET /:documentId/components` 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 /:documentId/detail-core
`server/routes/documents.ts` declares `GET /:documentId/detail-core` 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 /:documentId/file
`server/routes/documents.ts` declares `GET /:documentId/file` 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 /:documentId/safety-materials
`server/routes/documents.ts` declares `GET /:documentId/safety-materials` 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 /:documentId/safety-materials/:kind/:format
`server/routes/documents.ts` declares `GET /:documentId/safety-materials/:kind/:format` 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 con…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/health
`server/app.ts` declares `GET /api/health` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /auto-recheck
`server/routes/watchlist.ts` declares `GET /auto-recheck` 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 /drain
`server/routes/jobs.ts` declares `GET /drain` 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 /report
`server/routes/usage.ts` declares `GET /report` 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 /sites
`server/routes/products.ts` declares `GET /sites` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /:documentId
`server/routes/documents.ts` declares `PATCH /:documentId` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /:documentId/basic-info
`server/routes/documents.ts` declares `PATCH /:documentId/basic-info` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /:documentId/components/:rowId
`server/routes/documents.ts` declares `PATCH /:documentId/components/:rowId` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /
`server/routes/products.ts` declares `POST /` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /:documentId/components
`server/routes/documents.ts` declares `POST /:documentId/components` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /:documentId/components/:rowId/recheck
`server/routes/documents.ts` declares `POST /:documentId/components/:rowId/recheck` 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 consume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /:documentId/components/:rowId/review
`server/routes/documents.ts` declares `POST /:documentId/components/:rowId/review` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /:documentId/replacement
`server/routes/documents.ts` declares `POST /:documentId/replacement` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /:documentId/safety-materials/regenerate
`server/routes/documents.ts` declares `POST /:documentId/safety-materials/regenerate` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /calculate
`server/routes/schedules.ts` declares `POST /calculate` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /diff
`server/routes/revisions.ts` declares `POST /diff` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /documents/:documentId/revision-needed
`server/routes/products.ts` declares `POST /documents/:documentId/revision-needed` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /recheck
`server/routes/watchlist.ts` declares `POST /recheck` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /upload
`server/routes/documents.ts` declares `POST /upload` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /upload-batch
`server/routes/documents.ts` declares `POST /upload-batch` 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: USE /api
`server/app.ts` declares `USE /api` 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: USE /api/documents
`server/app.ts` declares `USE /api/documents` 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: USE /api/jobs
`server/app.ts` declares `USE /api/jobs` 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: USE /api/official-lookups
`server/app.ts` declares `USE /api/official-lookups` 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: USE /api/products
`server/app.ts` declares `USE /api/products` 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: USE /api/queues
`server/app.ts` declares `USE /api/queues` 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: USE /api/revisions
`server/app.ts` declares `USE /api/revisions` 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: USE /api/schedules
`server/app.ts` declares `USE /api/schedules` 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: USE /api/usage
`server/app.ts` declares `USE /api/usage` 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: USE /api/watchlist
`server/app.ts` declares `USE /api/watchlist` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph quality Complexity conf 1.00 Very large file: src/pages/ReviewPage.tsx (1187 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/services/apiRoutes.test.ts (2018 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/services/regulatoryMatcher.test.ts (1855 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.
For AI agents + API integrations
Email me when this repo regresses
Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.
API access

This page is publicly accessible at: https://repobility.com/scan/899a6f6f-b22c-4c9c-acea-e6e3dbbafe97/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/899a6f6f-b22c-4c9c-acea-e6e3dbbafe97/

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.