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

roohullah2007/eco-listing

https://github.com/roohullah2007/eco-listing · scanned 2026-06-15 23:55 UTC (2 months, 3 weeks ago)

159 raw signals (0 security + 159 graph)

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

Complete repo analysis

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

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

Showing 107 of 159 actionable findings. 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: GET /admin/messages/${convId} (resources/js/Pages/Admin/Messages/Index.tsx:70)
`resources/js/Pages/Admin/Messages/Index.tsx:70` calls `GET /admin/messages/${convId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/admin/messages/<p>` If this points at an external API, prefix it with `https://` …
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/addresses/autocomplete (resources/js/Components/AddressAutocomplete.tsx:65)
`resources/js/Components/AddressAutocomplete.tsx:65` calls `GET /api/addresses/autocomplete` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/addresses/autocomplete` If this points at an external API, prefix it with `…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/addresses/autocomplete (resources/js/Components/AddressFieldAutocomplete.tsx:79)
`resources/js/Components/AddressFieldAutocomplete.tsx:79` calls `GET /api/addresses/autocomplete` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/addresses/autocomplete` If this points at an external API, prefix it w…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/addresses/autocomplete (resources/js/Components/ChatWidget.tsx:215)
`resources/js/Components/ChatWidget.tsx:215` calls `GET /api/addresses/autocomplete` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/addresses/autocomplete` If this points at an external API, prefix it with `https://…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/addresses/autocomplete (resources/js/Pages/Cma.tsx:257)
`resources/js/Pages/Cma.tsx:257` calls `GET /api/addresses/autocomplete` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/addresses/autocomplete` If this points at an external API, prefix it with `https://` so the mat…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/addresses/autocomplete (resources/js/Pages/HomeV2.tsx:131)
`resources/js/Pages/HomeV2.tsx:131` calls `GET /api/addresses/autocomplete` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/addresses/autocomplete` If this points at an external API, prefix it with `https://` so the …
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/addresses/autocomplete (resources/js/Pages/HomeV2.tsx:93)
`resources/js/Pages/HomeV2.tsx:93` calls `GET /api/addresses/autocomplete` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/addresses/autocomplete` If this points at an external API, prefix it with `https://` so the m…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/chat/contacts (resources/js/Components/ChatWidget.tsx:809)
`resources/js/Components/ChatWidget.tsx:809` calls `GET /api/chat/contacts` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/chat/contacts` If this points at an external API, prefix it with `https://` so the matcher s…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/chat/conversations/${id} (resources/js/Components/ChatWidget.tsx:730)
`resources/js/Components/ChatWidget.tsx:730` calls `GET /api/chat/conversations/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/chat/conversations/<p>` If this points at an external API, prefix it with `https:…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/chat/my-listings (resources/js/Components/ChatWidget.tsx:792)
`resources/js/Components/ChatWidget.tsx:792` calls `GET /api/chat/my-listings` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/chat/my-listings` If this points at an external API, prefix it with `https://` so the mat…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/chat/summary (resources/js/Components/ChatWidget.tsx:658)
`resources/js/Components/ChatWidget.tsx:658` calls `GET /api/chat/summary` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/chat/summary` If this points at an external API, prefix it with `https://` so the matcher ski…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/listings/${mlsNumber} (resources/js/Components/PropertyDetailModal.tsx:67)
`resources/js/Components/PropertyDetailModal.tsx:67` calls `GET /api/listings/${mlsNumber}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/listings/<p>` If this points at an external API, prefix it with `https://` s…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/listings/${mlsNumber}/similar (resources/js/Components/PropertyDetailModal.tsx:70)
`resources/js/Components/PropertyDetailModal.tsx:70` calls `GET /api/listings/${mlsNumber}/similar` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/listings/<p>/similar` If this points at an external API, prefix it w…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/listings/viewed (resources/js/Pages/MapSearch.tsx:1341)
`resources/js/Pages/MapSearch.tsx:1341` calls `GET /api/listings/viewed` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/listings/viewed` If this points at an external API, prefix it with `https://` so the matcher sk…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/locations/autocomplete (resources/js/Pages/HomeV2.tsx:92)
`resources/js/Pages/HomeV2.tsx:92` calls `GET /api/locations/autocomplete` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/locations/autocomplete` If this points at an external API, prefix it with `https://` so the m…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/locations/autocomplete (resources/js/Pages/MapSearch.tsx:1468)
`resources/js/Pages/MapSearch.tsx:1468` calls `GET /api/locations/autocomplete` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/locations/autocomplete` If this points at an external API, prefix it with `https://` so …
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/locations/autocomplete (resources/js/Pages/Welcome.tsx:94)
`resources/js/Pages/Welcome.tsx:94` calls `GET /api/locations/autocomplete` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/locations/autocomplete` If this points at an external API, prefix it with `https://` so the …
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/map-search/count (resources/js/Pages/MapSearch.tsx:654)
`resources/js/Pages/MapSearch.tsx:654` calls `GET /api/map-search/count` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/map-search/count` If this points at an external API, prefix it with `https://` so the matcher s…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET /messages/${convId} (resources/js/Pages/Messages.tsx:50)
`resources/js/Pages/Messages.tsx:50` calls `GET /messages/${convId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/messages/<p>` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET /notifications (resources/js/Layouts/AgentLayout.tsx:92)
`resources/js/Layouts/AgentLayout.tsx:92` calls `GET /notifications` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/notifications` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: GET /notifications (resources/js/Layouts/UserLayout.tsx:122)
`resources/js/Layouts/UserLayout.tsx:122` calls `GET /notifications` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/notifications` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST /admin/messages/${conversation.id}/reply (resources/js/Pages/Admin/ListingRequests/Show.tsx:94)
`resources/js/Pages/Admin/ListingRequests/Show.tsx:94` calls `POST /admin/messages/${conversation.id}/reply` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/admin/messages/<p>/reply` If this points at an external API…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST /admin/messages/${selectedId}/reply (resources/js/Pages/Admin/Messages/Index.tsx:88)
`resources/js/Pages/Admin/Messages/Index.tsx:88` calls `POST /admin/messages/${selectedId}/reply` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/admin/messages/<p>/reply` If this points at an external API, prefix it…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/chat/conversations (resources/js/Components/ChatWidget.tsx:820)
`resources/js/Components/ChatWidget.tsx:820` calls `POST /api/chat/conversations` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/chat/conversations` If this points at an external API, prefix it with `https://` so th…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/chat/conversations/${activeId}/reply (resources/js/Components/ChatWidget.tsx:750)
`resources/js/Components/ChatWidget.tsx:750` calls `POST /api/chat/conversations/${activeId}/reply` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/chat/conversations/<p>/reply` If this points at an external API, pre…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/chat/lead (resources/js/Components/ChatWidget.tsx:386)
`resources/js/Components/ChatWidget.tsx:386` calls `POST /api/chat/lead` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/chat/lead` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/listings/search (resources/js/Pages/MapSearch.tsx:1441)
`resources/js/Pages/MapSearch.tsx:1441` calls `POST /api/listings/search` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/listings/search` If this points at an external API, prefix it with `https://` so the matcher s…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/listings/view (resources/js/Pages/MapSearch.tsx:1362)
`resources/js/Pages/MapSearch.tsx:1362` calls `POST /api/listings/view` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/listings/view` If this points at an external API, prefix it with `https://` so the matcher skips…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/messages/listing-search (resources/js/Components/ChatWidget.tsx:772)
`resources/js/Components/ChatWidget.tsx:772` calls `POST /api/messages/listing-search` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/messages/listing-search` If this points at an external API, prefix it with `https…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/messages/listing-search (resources/js/Pages/Admin/Messages/Index.tsx:106)
`resources/js/Pages/Admin/Messages/Index.tsx:106` calls `POST /api/messages/listing-search` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/messages/listing-search` If this points at an external API, prefix it with `…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/property-images/upload (resources/js/Components/PropertyConfirmModal.tsx:117)
`resources/js/Components/PropertyConfirmModal.tsx:117` calls `POST /api/property-images/upload` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/property-images/upload` If this points at an external API, prefix it wit…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST /cma-requests (resources/js/Components/PropertyConfirmModal.tsx:225)
`resources/js/Components/PropertyConfirmModal.tsx:225` calls `POST /cma-requests` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/cma-requests` If this points at an external API, prefix it with `https://` so the matc…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST /cma-requests (resources/js/Pages/MyProperties.tsx:232)
`resources/js/Pages/MyProperties.tsx:232` calls `POST /cma-requests` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/cma-requests` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST /favourites/${mlsNumber}/toggle (resources/js/Pages/Cma.tsx:204)
`resources/js/Pages/Cma.tsx:204` calls `POST /favourites/${mlsNumber}/toggle` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/favourites/<p>/toggle` If this points at an external API, prefix it with `https://` so the…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST /favourites/${mlsNumber}/toggle (resources/js/Pages/MapSearch.tsx:1319)
`resources/js/Pages/MapSearch.tsx:1319` calls `POST /favourites/${mlsNumber}/toggle` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/favourites/<p>/toggle` If this points at an external API, prefix it with `https://`…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST /favourites/${mlsNumber}/toggle (resources/js/Pages/PropertyDetails.tsx:517)
`resources/js/Pages/PropertyDetails.tsx:517` calls `POST /favourites/${mlsNumber}/toggle` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/favourites/<p>/toggle` If this points at an external API, prefix it with `http…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST /favourites/${mlsNumber}/toggle (resources/js/Pages/PropertyDetails.tsx:532)
`resources/js/Pages/PropertyDetails.tsx:532` calls `POST /favourites/${mlsNumber}/toggle` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/favourites/<p>/toggle` If this points at an external API, prefix it with `http…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST /favourites/${mls}/toggle (resources/js/Pages/PropertyDetails.tsx:568)
`resources/js/Pages/PropertyDetails.tsx:568` calls `POST /favourites/${mls}/toggle` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/favourites/<p>/toggle` If this points at an external API, prefix it with `https://` …
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST /favourites/check (resources/js/Pages/Cma.tsx:198)
`resources/js/Pages/Cma.tsx:198` calls `POST /favourites/check` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/favourites/check` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST /favourites/check (resources/js/Pages/MapSearch.tsx:1304)
`resources/js/Pages/MapSearch.tsx:1304` calls `POST /favourites/check` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/favourites/check` If this points at an external API, prefix it with `https://` so the matcher ski…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST /favourites/check (resources/js/Pages/PropertyDetails.tsx:550)
`resources/js/Pages/PropertyDetails.tsx:550` calls `POST /favourites/check` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/favourites/check` If this points at an external API, prefix it with `https://` so the matche…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST /listing-requests (resources/js/Components/PropertyConfirmModal.tsx:230)
`resources/js/Components/PropertyConfirmModal.tsx:230` calls `POST /listing-requests` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/listing-requests` If this points at an external API, prefix it with `https://` so …
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST /listing-requests (resources/js/Pages/MyProperties.tsx:203)
`resources/js/Pages/MyProperties.tsx:203` calls `POST /listing-requests` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/listing-requests` If this points at an external API, prefix it with `https://` so the matcher s…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST /listing-requests (resources/js/Pages/PropertyEstimate.tsx:299)
`resources/js/Pages/PropertyEstimate.tsx:299` calls `POST /listing-requests` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/listing-requests` If this points at an external API, prefix it with `https://` so the match…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST /listing-services/request (resources/js/Components/AgentContactModal.tsx:134)
`resources/js/Components/AgentContactModal.tsx:134` calls `POST /listing-services/request` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/listing-services/request` If this points at an external API, prefix it with `…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST /listing-services/request (resources/js/Components/ListMyPropertyModal.tsx:42)
`resources/js/Components/ListMyPropertyModal.tsx:42` calls `POST /listing-services/request` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/listing-services/request` If this points at an external API, prefix it with …
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST /listing-services/request (resources/js/Pages/MarketTrends.tsx:481)
`resources/js/Pages/MarketTrends.tsx:481` calls `POST /listing-services/request` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/listing-services/request` If this points at an external API, prefix it with `https://` …
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST /messages/${conversation.id}/reply (resources/js/Pages/Agent/ListingRequestShow.tsx:64)
`resources/js/Pages/Agent/ListingRequestShow.tsx:64` calls `POST /messages/${conversation.id}/reply` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/messages/<p>/reply` If this points at an external API, prefix it wi…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST /messages/${selectedId}/reply (resources/js/Pages/Messages.tsx:68)
`resources/js/Pages/Messages.tsx:68` calls `POST /messages/${selectedId}/reply` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/messages/<p>/reply` If this points at an external API, prefix it with `https://` so the …
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST /notifications/mark-read (resources/js/Layouts/AgentLayout.tsx:100)
`resources/js/Layouts/AgentLayout.tsx:100` calls `POST /notifications/mark-read` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/notifications/mark-read` If this points at an external API, prefix it with `https://` s…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST /notifications/mark-read (resources/js/Layouts/UserLayout.tsx:130)
`resources/js/Layouts/UserLayout.tsx:130` calls `POST /notifications/mark-read` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/notifications/mark-read` If this points at an external API, prefix it with `https://` so…
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST /property-estimate/lookup (resources/js/Pages/MyProperties.tsx:121)
`resources/js/Pages/MyProperties.tsx:121` calls `POST /property-estimate/lookup` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/property-estimate/lookup` If this points at an external API, prefix it with `https://` …
Dangling fetchAxios
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — resources/js/Pages/Admin/ActivityLog.tsx:141
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/Pages/Admin/Blog/Index.tsx:208
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/Pages/Admin/Enquiries/Index.tsx:228
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/Pages/Admin/Listings/Featured.tsx:97
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/Pages/Admin/ShowingRequests/Index.tsx:238
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/Pages/Admin/Users/Index.tsx:239
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/Pages/Blog/Index.tsx:227
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 Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, ci, tests, operator-readme. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
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 security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in resources/js/Pages/Admin/ActivityLog.tsx:141
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
resources/js/Pages/Admin/ActivityLog.tsx:141 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in resources/js/Pages/Admin/Blog/Index.tsx:208
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
resources/js/Pages/Admin/Blog/Index.tsx:208 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in resources/js/Pages/Admin/Enquiries/Index.tsx:228
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
resources/js/Pages/Admin/Enquiries/Index.tsx:228 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in resources/js/Pages/Admin/Listings/Featured.tsx:97
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
resources/js/Pages/Admin/Listings/Featured.tsx:97 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in resources/js/Pages/Admin/ShowingRequests/Index.tsx:238
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
resources/js/Pages/Admin/ShowingRequests/Index.tsx:238 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in resources/js/Pages/Admin/Users/Index.tsx:239
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
resources/js/Pages/Admin/Users/Index.tsx:239 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in resources/js/Pages/Blog/Index.tsx:227
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
resources/js/Pages/Blog/Index.tsx:227 Dangerous innerhtml
medium System graph cicd CI/CD security conf 1.00 No CI/CD pipelines detected
No GitHub Actions, GitLab CI, or CircleCI configs found. Without CI you can't gate deploys on tests/lints.
CI/CD securityCoverage
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 182 placeholder/mock markers across 48 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
0 test file(s) for 135 source file(s) (ratio 0.00). Consider adding integration or unit tests for critical paths.
Coverage
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 Docs conf 1.00 README lacks setup or run instructions
A README exists, but it does not contain common install/setup/run markers. This matches a frequent generated-code pattern: UI is present, operational handoff is thin.
ReadmeRepo 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 api Wiring conf 1.00 Unused endpoint: DELETE /admin/settings/delete-agent-photo
`resources/js/Pages/Admin/Settings.tsx` declares `DELETE /admin/settings/delete-agent-photo` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting wh…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /admin/settings/delete-cma-pdf
`resources/js/Pages/Admin/Settings.tsx` declares `DELETE /admin/settings/delete-cma-pdf` 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: DELETE /profile/avatar
`resources/js/Pages/Profile/Partials/AvatarUploadForm.tsx` declares `DELETE /profile/avatar` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting wh…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /admin/activity-log
`resources/js/Pages/Admin/ActivityLog.tsx` declares `GET /admin/activity-log` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /admin/blog
`resources/js/Pages/Admin/Blog/Index.tsx` declares `GET /admin/blog` 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 /admin/enquiries
`resources/js/Pages/Admin/Enquiries/Index.tsx` declares `GET /admin/enquiries` 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 /admin/listings
`resources/js/Pages/Admin/Listings/Index.tsx` declares `GET /admin/listings` 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 /admin/showing-requests
`resources/js/Pages/Admin/ShowingRequests/Index.tsx` declares `GET /admin/showing-requests` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /admin/users
`resources/js/Pages/Admin/Users/Index.tsx` declares `GET /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 who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /blog
`resources/js/Pages/Blog/Index.tsx` declares `GET /blog` 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 /comparables
`resources/js/Pages/Cma.tsx` declares `GET /comparables` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /map-search
`resources/js/Pages/MapSearch.tsx` declares `GET /map-search` 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 /market-trends
`resources/js/Pages/MarketTrends.tsx` declares `GET /market-trends` 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 /admin/blog
`resources/js/Pages/Admin/Blog/Create.tsx` declares `POST /admin/blog` 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 /admin/messages
`resources/js/Pages/Admin/Messages/Index.tsx` declares `POST /admin/messages` 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 /admin/settings/upload-agent-photo
`resources/js/Pages/Admin/Settings.tsx` declares `POST /admin/settings/upload-agent-photo` 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 /admin/settings/upload-cma-pdf
`resources/js/Pages/Admin/Settings.tsx` declares `POST /admin/settings/upload-cma-pdf` 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 /cma-report/request
`resources/js/Pages/Sell.tsx` declares `POST /cma-report/request` 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 /enquiry
`resources/js/Components/AskQuestionModal.tsx` declares `POST /enquiry` 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 /profile/avatar
`resources/js/Pages/Profile/Partials/AvatarUploadForm.tsx` declares `POST /profile/avatar` 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 /saved-searches
`resources/js/Pages/PropertyDetails.tsx` declares `POST /saved-searches` 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 /showing-requests
`resources/js/Components/BookShowingModal.tsx` declares `POST /showing-requests` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes i…
Unused endpoint
low System graph quality Complexity conf 1.00 Very large file: resources/js/Components/ChatWidget.tsx (1280 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/ListingsMap.tsx (1063 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/Pages/Cma.tsx (1095 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/Pages/HomeV2.tsx (1279 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/Pages/MapSearch.tsx (2687 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/Pages/MarketAnalysis.tsx (932 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/Pages/MarketTrends.tsx (1078 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/Pages/PropertyDetails.tsx (2705 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/Pages/PropertyEstimate.tsx (1123 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/Pages/Sell.tsx (1131 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/Pages/Welcome.tsx (1189 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/ff7533ff-e4e2-44c9-ab68-ee6f54f7687a/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/ff7533ff-e4e2-44c9-ab68-ee6f54f7687a/

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.