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

bherila/2025-website

https://github.com/bherila/2025-website · scanned 2026-06-17 01:41 UTC (1 month, 1 week ago)

252 raw signals (0 security + 252 graph)

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

Complete repo analysis

Last scanned 1 month, 1 week ago · v2 · last Δ -24.8 (diff) · 223 actionable findings from 1 signal source. 29 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
51.9
/100
Security checks
52
0 findings
System graph
52
100.0% cov · 223 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 56 Medium 33 Low 68 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 223 Crowd 0 Layer: Frontend 52 Hardware 2 Security 18 Cicd 2 Quality 48 Api 101
Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.
Scan summary Repository scanned at 51.9/100 with 100.0% coverage. It contains 7402 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 252 findings — concentrated in api (101), frontend (52), quality (48). Risk profile is high: 1 critical, 56 high, 42 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

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

high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/client/mgmt/companies/${companyId}/expenses/${expense.id} (resources/js/client-management/components/portal/DeleteExpenseDialog.tsx:32)
`resources/js/client-management/components/portal/DeleteExpenseDialog.tsx:32` calls `DELETE /api/client/mgmt/companies/${companyId}/expenses/${expense.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/client/mgmt/…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/client/portal/${slug}/time-entries/${entry.id} (resources/js/client-management/components/portal/NewTimeEntryModal.tsx:200)
`resources/js/client-management/components/portal/NewTimeEntryModal.tsx:200` calls `DELETE /api/client/portal/${slug}/time-entries/${entry.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/client/portal/<p>/time-e…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/genai/import/jobs/${deleteJobId} (resources/js/components/finance/import_transactions/GenAiJobsList.tsx:86)
`resources/js/components/finance/import_transactions/GenAiJobsList.tsx:86` calls `DELETE /api/genai/import/jobs/${deleteJobId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/genai/import/jobs/<p>` If this points at…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/payslips/${payslip_id} (resources/js/lib/api.ts:42)
`resources/js/lib/api.ts:42` calls `DELETE /api/payslips/${payslip_id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/payslips/<p>` If this points at an external API, prefix it with `https://` so the matcher skips …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/utility-bill-tracker/accounts/${accountId} (resources/js/components/utility-bill-tracker/UtilityBillListPage.tsx:187)
`resources/js/components/utility-bill-tracker/UtilityBillListPage.tsx:187` calls `DELETE /api/utility-bill-tracker/accounts/${accountId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/utility-bill-tracker/accounts/…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/utility-bill-tracker/accounts/${accountId}/bills/${currentBill.id}/pdf (resources/js/components/utility-bill-tracker/EditBillModal.tsx:164)
`resources/js/components/utility-bill-tracker/EditBillModal.tsx:164` calls `DELETE /api/utility-bill-tracker/accounts/${accountId}/bills/${currentBill.id}/pdf` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/utility-…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/utility-bill-tracker/accounts/${accountId}/bills/${selectedBill.id} (resources/js/components/utility-bill-tracker/UtilityBillListPage.tsx:166)
`resources/js/components/utility-bill-tracker/UtilityBillListPage.tsx:166` calls `DELETE /api/utility-bill-tracker/accounts/${accountId}/bills/${selectedBill.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/utili…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/client/mgmt/companies/${companyId}/expenses (resources/js/client-management/components/portal/ClientPortalExpensesPage.tsx:73)
`resources/js/client-management/components/portal/ClientPortalExpensesPage.tsx:73` calls `GET /api/client/mgmt/companies/${companyId}/expenses` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/client/mgmt/companies/<p…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/client/portal/${slug} (resources/js/client-management/components/portal/ClientPortalInvoicesPage.tsx:32)
`resources/js/client-management/components/portal/ClientPortalInvoicesPage.tsx:32` calls `GET /api/client/portal/${slug}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/client/portal/<p>` If this points at an extern…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/client/portal/${slug} (resources/js/client-management/components/portal/ClientPortalProjectPage.tsx:106)
`resources/js/client-management/components/portal/ClientPortalProjectPage.tsx:106` calls `GET /api/client/portal/${slug}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/client/portal/<p>` If this points at an extern…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/client/portal/${slug} (resources/js/client-management/components/portal/ClientPortalTimePage.tsx:79)
`resources/js/client-management/components/portal/ClientPortalTimePage.tsx:79` calls `GET /api/client/portal/${slug}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/client/portal/<p>` If this points at an external A…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/client/portal/${slug}/agreements/${agreementId} (resources/js/client-management/components/portal/ClientPortalAgreementPage.tsx:52)
`resources/js/client-management/components/portal/ClientPortalAgreementPage.tsx:52` calls `GET /api/client/portal/${slug}/agreements/${agreementId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/client/portal/<p>/a…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/client/portal/${slug}/invoices (resources/js/client-management/components/portal/ClientPortalAgreementPage.tsx:69)
`resources/js/client-management/components/portal/ClientPortalAgreementPage.tsx:69` calls `GET /api/client/portal/${slug}/invoices` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/client/portal/<p>/invoices` If this …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/client/portal/${slug}/invoices (resources/js/client-management/components/portal/ClientPortalInvoicesPage.tsx:44)
`resources/js/client-management/components/portal/ClientPortalInvoicesPage.tsx:44` calls `GET /api/client/portal/${slug}/invoices` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/client/portal/<p>/invoices` If this p…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/client/portal/${slug}/projects (resources/js/client-management/components/portal/ClientPortalExpensesPage.tsx:87)
`resources/js/client-management/components/portal/ClientPortalExpensesPage.tsx:87` calls `GET /api/client/portal/${slug}/projects` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/client/portal/<p>/projects` If this p…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/client/portal/${slug}/projects (resources/js/client-management/components/portal/ClientPortalTimePage.tsx:67)
`resources/js/client-management/components/portal/ClientPortalTimePage.tsx:67` calls `GET /api/client/portal/${slug}/projects` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/client/portal/<p>/projects` If this point…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/client/portal/${slug}/projects/${projectSlug}/tasks (resources/js/client-management/components/portal/ClientPortalProjectPage.tsx:92)
`resources/js/client-management/components/portal/ClientPortalProjectPage.tsx:92` calls `GET /api/client/portal/${slug}/projects/${projectSlug}/tasks` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/client/portal/<p>…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/client/portal/${slug}/time-entries (resources/js/client-management/components/portal/ClientPortalTimePage.tsx:53)
`resources/js/client-management/components/portal/ClientPortalTimePage.tsx:53` calls `GET /api/client/portal/${slug}/time-entries` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/client/portal/<p>/time-entries` If th…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/finance/chart (resources/js/components/finance/FinanceAccountsPage.tsx:55)
`resources/js/components/finance/FinanceAccountsPage.tsx:55` calls `GET /api/finance/chart` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/finance/chart` 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/login-audit?page=${p} (resources/js/user/login-audit-section.tsx:44)
`resources/js/user/login-audit-section.tsx:44` calls `GET /api/login-audit?page=${p}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/login-audit` If this points at an external API, prefix it with `https://` so the m…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/payslips/${payslip_id} (resources/js/lib/api.ts:58)
`resources/js/lib/api.ts:58` calls `GET /api/payslips/${payslip_id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/payslips/<p>` 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/user (resources/js/client-management/__tests__/portal-hydration.test.tsx:132)
`resources/js/client-management/__tests__/portal-hydration.test.tsx:132` calls `GET /api/user` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/user` 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/user (resources/js/client-management/components/portal/NewTimeEntryModal.tsx:88)
`resources/js/client-management/components/portal/NewTimeEntryModal.tsx:88` calls `GET /api/user` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/user` If this points at an external API, prefix it with `https://` so …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/user (resources/js/dashboard.tsx:34)
`resources/js/dashboard.tsx:34` calls `GET /api/user` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/user` 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/utility-bill-tracker/accounts (resources/js/components/utility-bill-tracker/UtilityAccountListPage.tsx:23)
`resources/js/components/utility-bill-tracker/UtilityAccountListPage.tsx:23` calls `GET /api/utility-bill-tracker/accounts` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/utility-bill-tracker/accounts` If this point…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/utility-bill-tracker/accounts/${accountId} (resources/js/components/utility-bill-tracker/UtilityBillListPage.tsx:51)
`resources/js/components/utility-bill-tracker/UtilityBillListPage.tsx:51` calls `GET /api/utility-bill-tracker/accounts/${accountId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/utility-bill-tracker/accounts/<p>`…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/utility-bill-tracker/accounts/${accountId}/bills (resources/js/components/utility-bill-tracker/UtilityBillListPage.tsx:52)
`resources/js/components/utility-bill-tracker/UtilityBillListPage.tsx:52` calls `GET /api/utility-bill-tracker/accounts/${accountId}/bills` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/utility-bill-tracker/account…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/utility-bill-tracker/accounts/${accountId}/bills/${bill.id}/linkable (resources/js/components/utility-bill-tracker/LinkBillModal.tsx:34)
`resources/js/components/utility-bill-tracker/LinkBillModal.tsx:34` calls `GET /api/utility-bill-tracker/accounts/${accountId}/bills/${bill.id}/linkable` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/utility-bill-t…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/client/mgmt/companies/${company.id}/invoices/generate-all (resources/js/client-management/components/portal/ClientPortalInvoicesPage.tsx:75)
`resources/js/client-management/components/portal/ClientPortalInvoicesPage.tsx:75` calls `POST /api/client/mgmt/companies/${company.id}/invoices/generate-all` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/client/mg…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/client/mgmt/companies/${companyId}/expenses/${expense.id}/mark-reimbursed (resources/js/client-management/components/portal/ClientPortalExpensesPage.tsx:104)
`resources/js/client-management/components/portal/ClientPortalExpensesPage.tsx:104` calls `POST /api/client/mgmt/companies/${companyId}/expenses/${expense.id}/mark-reimbursed` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matc…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/client/mgmt/companies/${companyId}/invoices/generate-all (resources/js/client-management/components/ClientAdminActions.tsx:37)
`resources/js/client-management/components/ClientAdminActions.tsx:37` calls `POST /api/client/mgmt/companies/${companyId}/invoices/generate-all` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/client/mgmt/companies/<…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/client/portal/${slug}/agreements/${agreementId}/sign (resources/js/client-management/components/portal/ClientPortalAgreementPage.tsx:108)
`resources/js/client-management/components/portal/ClientPortalAgreementPage.tsx:108` calls `POST /api/client/portal/${slug}/agreements/${agreementId}/sign` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/client/porta…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/client/portal/${slug}/projects (resources/js/client-management/components/portal/NewProjectModal.tsx:29)
`resources/js/client-management/components/portal/NewProjectModal.tsx:29` calls `POST /api/client/portal/${slug}/projects` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/client/portal/<p>/projects` If this points at…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/client/portal/${slug}/projects/${projectSlug}/tasks (resources/js/client-management/components/portal/NewTaskModal.tsx:44)
`resources/js/client-management/components/portal/NewTaskModal.tsx:44` calls `POST /api/client/portal/${slug}/projects/${projectSlug}/tasks` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/client/portal/<p>/projects/…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/client/portal/${slug}/time-entries (resources/js/client-management/components/portal/EditTaskModal.tsx:135)
`resources/js/client-management/components/portal/EditTaskModal.tsx:135` calls `POST /api/client/portal/${slug}/time-entries` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/client/portal/<p>/time-entries` If this po…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/finance/accounts/balance (resources/js/components/finance/EditBalanceDisplay.tsx:29)
`resources/js/components/finance/EditBalanceDisplay.tsx:29` calls `POST /api/finance/accounts/balance` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/finance/accounts/balance` If this points at an external API, pref…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/login-audit/${id}/suspicious (resources/js/user/login-audit-section.tsx:66)
`resources/js/user/login-audit-section.tsx:66` calls `POST /api/login-audit/${id}/suspicious` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/login-audit/<p>/suspicious` If this points at an external API, prefix it w…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/payslips/${payslip_id}/estimated-status (resources/js/lib/api.ts:69)
`resources/js/lib/api.ts:69` calls `POST /api/payslips/${payslip_id}/estimated-status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/payslips/<p>/estimated-status` If this points at an external API, prefix it with …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/user/update-api-key (resources/js/user/api-key.tsx:54)
`resources/js/user/api-key.tsx:54` calls `POST /api/user/update-api-key` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/user/update-api-key` 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: POST /api/user/update-email (resources/js/user/update-email.tsx:24)
`resources/js/user/update-email.tsx:24` calls `POST /api/user/update-email` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/user/update-email` If this points at an external API, prefix it with `https://` so the match…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/user/update-genai-quota (resources/js/user/genai-quota.tsx:33)
`resources/js/user/genai-quota.tsx:33` calls `POST /api/user/update-genai-quota` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/user/update-genai-quota` 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/user/update-password (resources/js/user/update-password.tsx:28)
`resources/js/user/update-password.tsx:28` calls `POST /api/user/update-password` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/user/update-password` If this points at an external API, prefix it with `https://` so …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/utility-bill-tracker/accounts (resources/js/components/utility-bill-tracker/CreateAccountModal.tsx:28)
`resources/js/components/utility-bill-tracker/CreateAccountModal.tsx:28` calls `POST /api/utility-bill-tracker/accounts` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/utility-bill-tracker/accounts` If this points a…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/utility-bill-tracker/accounts/${accountId}/bills/${bill.id}/link (resources/js/components/utility-bill-tracker/LinkBillModal.tsx:62)
`resources/js/components/utility-bill-tracker/LinkBillModal.tsx:62` calls `POST /api/utility-bill-tracker/accounts/${accountId}/bills/${bill.id}/link` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/utility-bill-trac…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/utility-bill-tracker/accounts/${accountId}/bills/${bill.id}/toggle-status (resources/js/components/utility-bill-tracker/UtilityBillListPage.tsx:132)
`resources/js/components/utility-bill-tracker/UtilityBillListPage.tsx:132` calls `POST /api/utility-bill-tracker/accounts/${accountId}/bills/${bill.id}/toggle-status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/u…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/utility-bill-tracker/accounts/${accountId}/bills/${bill.id}/unlink (resources/js/components/utility-bill-tracker/LinkBillModal.tsx:89)
`resources/js/components/utility-bill-tracker/LinkBillModal.tsx:89` calls `POST /api/utility-bill-tracker/accounts/${accountId}/bills/${bill.id}/unlink` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/utility-bill-tr…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /client/mgmt (resources/js/client-management/components/ClientManagementCreatePage.tsx:21)
`resources/js/client-management/components/ClientManagementCreatePage.tsx:21` calls `POST /client/mgmt` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/client/mgmt` If this points at an external API, prefix it with `…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/client/portal/${slug}/projects/${projectSlug} (resources/js/client-management/components/portal/ProjectPageHeader.tsx:44)
`resources/js/client-management/components/portal/ProjectPageHeader.tsx:44` calls `PUT /api/client/portal/${slug}/projects/${projectSlug}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/client/portal/<p>/projects/<p…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/client/portal/${slug}/projects/${projectSlug}/tasks/${task.id} (resources/js/client-management/components/portal/ClientPortalProjectPage.tsx:137)
`resources/js/client-management/components/portal/ClientPortalProjectPage.tsx:137` calls `PUT /api/client/portal/${slug}/projects/${projectSlug}/tasks/${task.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/clien…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/client/portal/${slug}/projects/${projectSlug}/tasks/${task.id} (resources/js/client-management/components/portal/EditTaskModal.tsx:94)
`resources/js/client-management/components/portal/EditTaskModal.tsx:94` calls `PUT /api/client/portal/${slug}/projects/${projectSlug}/tasks/${task.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/client/portal/<p…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/utility-bill-tracker/accounts/${accountId}/notes (resources/js/components/utility-bill-tracker/UtilityBillListPage.tsx:84)
`resources/js/components/utility-bill-tracker/UtilityBillListPage.tsx:84` calls `PUT /api/utility-bill-tracker/accounts/${accountId}/notes` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/utility-bill-tracker/account…
Dangling fetchFetch
high System graph security auth conf 1.00 JS POST `/api/admin/genai-jobs/${job.id}/requeue` admin endpoint without auth — resources/js/components/admin/AdminGenAiJobsPage.tsx:109
Admin-scoped JS route with no recognizable auth: no middleware-position guard, no router-level guard above it in this file, and no inline permission call within the first 15 lines of the handler. If auth is applied where this router is mounted, dismiss with reason `by_design` or tag the route `// p…
resources/js/components/admin/AdminGenAiJobsPage.tsx:109 securityAuth js admin unauth
high System graph security auth conf 1.00 JS POST `/api/admin/tax-normalization-review/acknowledge` admin endpoint without auth — resources/js/components/admin/AdminTaxNormalizationPage.tsx:112
Admin-scoped JS route with no recognizable auth: no middleware-position guard, no router-level guard above it in this file, and no inline permission call within the first 15 lines of the handler. If auth is applied where this router is mounted, dismiss with reason `by_design` or tag the route `// p…
resources/js/components/admin/AdminTaxNormalizationPage.tsx:112 securityAuth js admin unauth
high System graph security auth conf 1.00 JS POST `/api/admin/users/${user.id}/email` admin endpoint without auth — resources/js/components/user-management/UserActionsModal.tsx:109
Admin-scoped JS route with no recognizable auth: no middleware-position guard, no router-level guard above it in this file, and no inline permission call within the first 15 lines of the handler. If auth is applied where this router is mounted, dismiss with reason `by_design` or tag the route `// p…
resources/js/components/user-management/UserActionsModal.tsx:109 securityAuth js admin unauth
high System graph security auth conf 1.00 JS POST `/api/admin/users/${user.id}/login-as` admin endpoint without auth — resources/js/components/user-management/UserActionsModal.tsx:193
Admin-scoped JS route with no recognizable auth: no middleware-position guard, no router-level guard above it in this file, and no inline permission call within the first 15 lines of the handler. If auth is applied where this router is mounted, dismiss with reason `by_design` or tag the route `// p…
resources/js/components/user-management/UserActionsModal.tsx:193 securityAuth js admin unauth
high System graph security auth conf 1.00 JS POST `/api/admin/users` admin endpoint without auth — resources/js/components/user-management/CreateUserModal.tsx:50
Admin-scoped JS route with no recognizable auth: no middleware-position guard, no router-level guard above it in this file, and no inline permission call within the first 15 lines of the handler. If auth is applied where this router is mounted, dismiss with reason `by_design` or tag the route `// p…
resources/js/components/user-management/CreateUserModal.tsx:50 securityAuth js admin unauth
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — resources/js/components/markdown/MermaidBlock.tsx:98
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 — resources/js/components/markdown/sanitizeSvg.ts:2
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 — resources/js/client-management/__tests__/portal-hydration.test.tsx:132
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 — resources/js/client-management/components/portal/NewTimeEntryModal.tsx:154
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 — resources/js/components/finance/FinanceAccountsPage.tsx: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 — resources/js/components/shared/FileManager.tsx:447
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 — resources/js/components/utility-bill-tracker/EditBillModal.tsx:132
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 — resources/js/fetchWrapper.ts:25
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 — resources/js/genai-processor/useGenAiFileUpload.ts:61
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 — resources/js/lib/api.ts:6
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/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 Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/finance-mcp.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/skills/finance-mcp.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .github/copilot-instructions.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.
.github/copilot-instructions.md VerificationAgent instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .mcp.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.
.mcp.json VerificationMcp config
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: 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.
AGENTS.md VerificationAgents md
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: CLAUDE.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.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: GEMINI.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.
GEMINI.md VerificationGemini instruction
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 cicd CI/CD security conf 1.00 10 occurrences GitHub Action is tag-pinned rather than SHA-pinned
dorny/paths-filter@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
4 files, 10 locations
.github/workflows/ci.yml:34, 218, 268, 379 (4 hits)
.github/workflows/copilot-setup-steps.yml:25, 35 (2 hits)
.github/workflows/e2e-tests.yml:25, 40 (2 hits)
.github/workflows/parking-pickup-playwright.yml:39, 55 (2 hits)
CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in resources/js/components/markdown/MermaidBlock.tsx:98
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
resources/js/components/markdown/MermaidBlock.tsx:98 Dangerous innerhtml
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 369 placeholder/mock markers across 141 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
low System graph quality Integrity conf 1.00 6 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `CI`, `JEST_EXCLUDE_GAME_TESTS`, `JEST_INCLUDE_SLOW_TESTS`, `JEST_INLINE_SOURCEMAPS`, `MODE`, `PLAYWRIGHT_BASE_URL`. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.
config drift
low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
Deployment
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 6 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: mcr.microsoft.com/devcontainers/php:8.5-bookworm
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
.devcontainer/Dockerfile:1 containersPinned dependencies
low System graph cicd CI/CD security conf 1.00 21 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/upload-artifact@v5 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
6 files, 21 locations
.github/workflows/ci.yml:123, 223, 236, 262, 273, 384, 394 (7 hits)
.github/workflows/ohif-dist.yml:42, 50, 57, 83, 94 (5 hits)
.github/workflows/e2e-tests.yml:28, 47, 100 (3 hits)
.github/workflows/parking-pickup-playwright.yml:42, 61, 110 (3 hits)
.github/workflows/copilot-setup-steps.yml:22, 38 (2 hits)
.github/workflows/slow-tests.yml:40
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 Integrity conf 1.00 Old/deprecated-named symbol `next_month_starting_unused` in resources/js/client-management/components/portal/ClientPortalTimePage.tsx:314
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 `next_month_starting_unused` in resources/js/client-management/types/time-entry.ts: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 `notification_email_copy` in resources/js/components/class-action-tracker/__tests__/ClassActionTracker.test.tsx:52
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 `notification_email_copy` in resources/js/components/class-action-tracker/ClassActionTracker.tsx:87
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `withoutLegacy` in resources/js/components/planning/CareerComp/inputUtils.ts:33
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 api Wiring conf 1.00 Unused endpoint: GET /api/admin/feature-permissions
`resources/js/components/user-management/UserManagementPage.tsx` declares `GET /api/admin/feature-permissions` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/admin/users
`resources/js/components/user-management/UserManagementPage.tsx` declares `GET /api/admin/users` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documentin…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/agent/setup-tokens
`resources/js/user/agent-tokens.tsx` declares `GET /api/agent/setup-tokens` 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/class-action-claims
`resources/js/components/class-action-tracker/ClassActionTracker.tsx` declares `GET /api/class-action-claims` 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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/finance/accounts/basic
`resources/js/components/finance/useFinanceAccounts.ts` declares `GET /api/finance/accounts/basic` 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 document…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/finance/employment-entities
`resources/js/components/finance/EmploymentEntitySection.tsx` declares `GET /api/finance/employment-entities` 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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/finance/employment-entities?visible_only=true
`resources/js/components/finance/ManageTagsPage.tsx` declares `GET /api/finance/employment-entities?visible_only=true` 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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/finance/rules
`resources/js/components/finance/rules_engine/RulesList.tsx` declares `GET /api/finance/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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/finance/schedule-c
`resources/js/components/finance/ScheduleCPreview.tsx` declares `GET /api/finance/schedule-c` 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 w…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/financial-planning/career-comparison/latest
`resources/js/components/rsu/RsuPage.tsx` declares `GET /api/financial-planning/career-comparison/latest` 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 d…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/license-keys
`resources/js/components/license-manager/license-manager.tsx` declares `GET /api/license-keys` 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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/phr/patients
`resources/js/components/phr/PhrNavbar.tsx` declares `GET /api/phr/patients` 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/rsu
`resources/js/components/rsu/RsuPage.tsx` declares `GET /api/rsu` 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/user/ai-prefs
`resources/js/user/ai-configurations/AiConfigurationsSection.tsx` declares `GET /api/user/ai-prefs` 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 documen…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/admin/tax-normalization-review/acknowledge
`resources/js/components/admin/AdminTaxNormalizationPage.tsx` declares `POST /api/admin/tax-normalization-review/acknowledge` 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 — co…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/admin/users
`resources/js/components/user-management/CreateUserModal.tsx` declares `POST /api/admin/users` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/agent/setup-tokens
`resources/js/components/class-action-tracker/ClassActionTracker.tsx` declares `POST /api/agent/setup-tokens` 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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/class-action-claims
`resources/js/components/class-action-tracker/ClassActionTracker.tsx` declares `POST /api/class-action-claims` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/finance/documents
`resources/js/components/finance/DocumentImportModal.tsx` declares `POST /api/finance/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 documentin…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/finance/documents/request-upload
`resources/js/components/finance/DocumentImportModal.tsx` declares `POST /api/finance/documents/request-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 removin…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/finance/employment-entities
`resources/js/components/finance/EmploymentEntitySection.tsx` declares `POST /api/finance/employment-entities` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/finance/lot-reconciliation-links/relink
`resources/js/components/finance/LotReconciliationPage.tsx` declares `POST /api/finance/lot-reconciliation-links/relink` 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 — conside…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/finance/lots/save-assignment
`resources/js/components/finance/lots/LotMatchSearchModal.tsx` declares `POST /api/finance/lots/save-assignment` 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 removi…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/finance/lots/search-opening
`resources/js/components/finance/lots/LotMatchSearchModal.tsx` declares `POST /api/finance/lots/search-opening` 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 removin…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/finance/rules
`resources/js/components/finance/rules_engine/RuleEditorModal.tsx` declares `POST /api/finance/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 docum…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/finance/rules/preview-matches
`resources/js/components/finance/rules_engine/RuleEditorModal.tsx` declares `POST /api/finance/rules/preview-matches` 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 r…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/finance/rules/reorder
`resources/js/components/finance/rules_engine/RulesList.tsx` declares `POST /api/finance/rules/reorder` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or doc…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/finance/tags
`resources/js/components/finance/ManageTagsPage.tsx` declares `POST /api/finance/tags` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who cons…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/finance/tags/apply
`resources/js/components/finance/TransactionDetailsModal.tsx` declares `POST /api/finance/tags/apply` 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 docum…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/finance/tags/remove
`resources/js/components/finance/TransactionDetailsModal.tsx` declares `POST /api/finance/tags/remove` 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 docu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/finance/tax-documents/manual
`resources/js/components/finance/ManualJsonAttachModal.tsx` declares `POST /api/finance/tax-documents/manual` 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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/finance/tax-line-adjustments
`resources/js/components/finance/TaxLineAdjustmentPopover.tsx` declares `POST /api/finance/tax-line-adjustments` 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 removi…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/finance/transactions/batch-delete
`resources/js/components/finance/transactionTable/TransactionsTable.tsx` declares `POST /api/finance/transactions/batch-delete` 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 — …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/finance/transactions/batch-update
`resources/js/components/finance/TransactionDetailsModal.tsx` declares `POST /api/finance/transactions/batch-update` 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 re…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/finance/transactions/link
`resources/js/components/finance/TransactionLinkModal.tsx` declares `POST /api/finance/transactions/link` 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 d…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/finance/user-deductions
`resources/js/components/finance/UserDeductionsSection.tsx` declares `POST /api/finance/user-deductions` 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 do…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/finance/user-tax-states
`resources/js/components/finance/StateSelectorSection.tsx` declares `POST /api/finance/user-tax-states` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or doc…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/genai/import/jobs
`resources/js/genai-processor/useGenAiFileUpload.ts` declares `POST /api/genai/import/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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/genai/import/paste
`resources/js/components/class-action-tracker/ClassActionTracker.tsx` declares `POST /api/genai/import/paste` 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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/genai/import/request-upload
`resources/js/genai-processor/useGenAiFileUpload.ts` declares `POST /api/genai/import/request-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 docum…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/license-keys
`resources/js/components/license-manager/license-manager.tsx` declares `POST /api/license-keys` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/license-keys/import
`resources/js/components/license-manager/license-manager.tsx` declares `POST /api/license-keys/import` 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 docu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/payslips/bulk
`resources/js/components/payslip/PayslipJsonModal.tsx` declares `POST /api/payslips/bulk` 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 c…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/rsu
`resources/js/components/rsu/ManageAwardsPage.tsx` declares `POST /api/rsu` 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 /api/rsu/backfill-vest-prices
`resources/js/components/rsu/ManageAwardsPage.tsx` declares `POST /api/rsu/backfill-vest-prices` 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 documentin…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/tools/toon-json/save
`resources/js/components/toon-json/toonApi.ts` declares `POST /api/tools/toon-json/save` 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 co…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/user/ai-prefs
`resources/js/user/ai-configurations/AiConfigurationsSection.tsx` declares `POST /api/user/ai-prefs` 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 docume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/user/ai-prefs/models
`resources/js/user/ai-configurations/AiConfigurationsSection.tsx` declares `POST /api/user/ai-prefs/models` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/user/generate-mcp-api-key
`resources/js/user/mcp-api-key.tsx` declares `POST /api/user/generate-mcp-api-key` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /api/finance/form-8829
`resources/js/components/finance/Form8829InputsForm.tsx` declares `PUT /api/finance/form-8829` 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 …
Unused endpoint
low System graph quality Complexity conf 1.00 Very large file: resources/js/components/class-action-tracker/ClassActionTracker.tsx (1632 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: resources/js/components/finance/k1/K1ReviewPanel.tsx (2063 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: resources/js/components/finance/tax-preview/registry.tsx (1458 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: resources/js/components/finance/TaxDocumentReviewModal.tsx (1583 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: resources/js/components/planning/CareerComp/CareerCompForm.tsx (1967 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: resources/js/games/cars/gameEngine.ts (2145 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests-ts/washSaleEngine.test.ts (1188 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/2ce4b099-cec8-4900-9bb8-b361e1f2462a/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/2ce4b099-cec8-4900-9bb8-b361e1f2462a/

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.