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

SECONDOAK/holmen-webbapp

https://github.com/SECONDOAK/holmen-webbapp · scanned 2026-06-16 00:06 UTC (2 months, 2 weeks ago)

117 raw signals (0 security + 117 graph)

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

Complete repo analysis

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

JSON
Combined
44.5
/100
Security checks
45
0 findings
System graph
45
77.8% cov · 117 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 12 Medium 18 Low 63 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 117 Crowd 0 Layer: Frontend 37 Security 8 Cicd 2 Quality 26 Api 44
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 44.5/100 with 77.8% coverage. It contains 3335 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 117 findings — concentrated in api (44), frontend (37), quality (26). Risk profile is high: 1 critical, 12 high, 18 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

Showing 93 of 117 actionable findings. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

critical System graph security Secrets conf 1.00 Possible secret in src/utils/mapSnapshots.ts
Detected pattern matching generic_api_key. Rotate the credential and move to a secret manager.
src/utils/mapSnapshots.ts:3
high System graph api Wiring conf 1.00 Dangling fetch: DELETE https://${projectId}.supabase.co/functions/v1/make-server-ffc89dab/departments/debug/clear-all (src/components/DepartmentsListView.tsx:206)
`src/components/DepartmentsListView.tsx:206` calls `DELETE https://${projectId}.supabase.co/functions/v1/make-server-ffc89dab/departments/debug/clear-all` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/<p>.su…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://${projectId}.supabase.co/functions/v1/make-server-ffc89dab/departments/${propertyId} (src/components/DepartmentsListView.tsx:174)
`src/components/DepartmentsListView.tsx:174` calls `GET https://${projectId}.supabase.co/functions/v1/make-server-ffc89dab/departments/${propertyId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/<p>.supabas…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://${projectId}.supabase.co/functions/v1/make-server-ffc89dab/departments/${selectedProperty.id} (src/pages/PropertiesPage.tsx:758)
`src/pages/PropertiesPage.tsx:758` calls `GET https://${projectId}.supabase.co/functions/v1/make-server-ffc89dab/departments/${selectedProperty.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/<p>.supabase…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://${projectId}.supabase.co/functions/v1/make-server-ffc89dab/departments/debug/status (src/pages/DatabaseToolsPage.tsx:18)
`src/pages/DatabaseToolsPage.tsx:18` calls `GET https://${projectId}.supabase.co/functions/v1/make-server-ffc89dab/departments/debug/status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/<p>.supabase.co/func…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://${projectId}.supabase.co/functions/v1/make-server-ffc89dab/user/${loggedInUser.id} (src/pages/AccountPage.tsx:302)
`src/pages/AccountPage.tsx:302` calls `GET https://${projectId}.supabase.co/functions/v1/make-server-ffc89dab/user/${loggedInUser.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/<p>.supabase.co/functions/…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://${projectId}.supabase.co/functions/v1/make-server-ffc89dab/debug/reinit-all (src/pages/DatabaseToolsPage.tsx:84)
`src/pages/DatabaseToolsPage.tsx:84` calls `POST https://${projectId}.supabase.co/functions/v1/make-server-ffc89dab/debug/reinit-all` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/<p>.supabase.co/functions/v…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://${projectId}.supabase.co/functions/v1/make-server-ffc89dab/debug/reinit-all (src/utils/resetDatabase.ts:59)
`src/utils/resetDatabase.ts:59` calls `POST https://${projectId}.supabase.co/functions/v1/make-server-ffc89dab/debug/reinit-all` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/<p>.supabase.co/functions/v1/mak…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://${projectId}.supabase.co/functions/v1/make-server-ffc89dab/departments/migrate-site-index (src/App.tsx:105)
`src/App.tsx:105` calls `POST https://${projectId}.supabase.co/functions/v1/make-server-ffc89dab/departments/migrate-site-index` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/<p>.supabase.co/functions/v1/mak…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://${projectId}.supabase.co/functions/v1/make-server-ffc89dab/departments/migrate-site-index (src/pages/DatabaseToolsPage.tsx:38)
`src/pages/DatabaseToolsPage.tsx:38` calls `POST https://${projectId}.supabase.co/functions/v1/make-server-ffc89dab/departments/migrate-site-index` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/<p>.supabase.…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://${projectId}.supabase.co/functions/v1/make-server-ffc89dab/departments/seed-missing (src/pages/DatabaseToolsPage.tsx:61)
`src/pages/DatabaseToolsPage.tsx:61` calls `POST https://${projectId}.supabase.co/functions/v1/make-server-ffc89dab/departments/seed-missing` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/<p>.supabase.co/fun…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://${projectId}.supabase.co/functions/v1/make-server-ffc89dab/departments/seed-missing (src/utils/resetDatabase.ts:12)
`src/utils/resetDatabase.ts:12` calls `POST https://${projectId}.supabase.co/functions/v1/make-server-ffc89dab/departments/seed-missing` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/<p>.supabase.co/function…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT https://${projectId}.supabase.co/functions/v1/make-server-ffc89dab/user/${loggedInUser.id} (src/pages/AccountPage.tsx:632)
`src/pages/AccountPage.tsx:632` calls `PUT https://${projectId}.supabase.co/functions/v1/make-server-ffc89dab/user/${loggedInUser.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/<p>.supabase.co/functions/…
Dangling fetchFetch
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — src/components/HolmenIcon.tsx:47
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — src/components/HolmenWebbIcon.tsx:67
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 — src/components/ui/chart.tsx:83
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 — src/components/DepartmentDetailsView.tsx:134
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 — src/utils/resetDatabase.ts:12
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 instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing license, tests. 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 Tests conf 1.00 CI is configured but no tests are detected
A CI pipeline exists, but the scan found no test files to gate. Opus labeled this generated-code pattern as config theater: release machinery exists, but it has little behavioral signal.
CI/CDConfig theaterRepo hardening
medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph cicd CI/CD security conf 1.00 GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
.github/workflows/deploy.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in src/supabase/functions/server/index.tsx:28
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
src/supabase/functions/server/index.tsx:28 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in src/components/HolmenIcon.tsx:47
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
src/components/HolmenIcon.tsx:47 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in src/components/HolmenWebbIcon.tsx:67
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
src/components/HolmenWebbIcon.tsx:67 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in src/components/ui/chart.tsx:83
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
src/components/ui/chart.tsx:83 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in src/pages/PropertiesPage.tsx:1984
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
src/pages/PropertiesPage.tsx:1984 Direct innerhtml assignment
medium System graph security Coverage conf 1.00 No auth library detected
The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). The repo has auth/admin/session surface indicators, so auth may live in custom code, in a separate service, or be missing.
auth
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 37 placeholder/mock markers across 18 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
1 test file(s) for 231 source file(s) (ratio 0.00). Consider adding integration or unit tests for critical paths.
Coverage
low System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, tests. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 200 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph cicd CI/CD security conf 1.00 GitHub Action is tag-pinned rather than SHA-pinned
actions/deploy-pages@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
.github/workflows/deploy.yml:41 CI/CD securitySupply chainGithub actions
low System graph quality License conf 1.00 No license file detected
No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.
Repo hardeningGenerated repo pattern
low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence
The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.
Git historyGenerated repo pattern
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — src/App.tsx:39
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — src/components/DepartmentDetailsView.tsx:129
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — src/components/DepartmentsListView.tsx:172
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — src/components/MapDrawer.tsx:483
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — src/contexts/ProfileContext.tsx:89
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — src/contexts/UserContext.tsx:34
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — src/pages/AccountPage.tsx:417
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — src/pages/PropertiesPage.tsx:461
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — src/supabase/functions/server/departments.tsx:101
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — src/supabase/functions/server/forestry-plans.tsx:270
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — src/supabase/functions/server/index.tsx:15
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — src/supabase/functions/server/notes.tsx:24
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — src/supabase/functions/server/properties.tsx:289
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — src/supabase/functions/server/users.tsx:10
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — src/utils/propertiesApi.tsx:20
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — src/utils/resetDatabase.ts:9
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /debug/clear-properties
`src/supabase/functions/server/properties.tsx` declares `DELETE /debug/clear-properties` 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 /departments/debug/clear-all
`src/supabase/functions/server/departments.tsx` declares `DELETE /departments/debug/clear-all` 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: DELETE /forestry-plans/:propertyId/:departmentId/:actionId
`src/supabase/functions/server/forestry-plans.tsx` declares `DELETE /forestry-plans/:propertyId/:departmentId/:actionId` 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: DELETE /forestry-plans/debug/clear-all
`src/supabase/functions/server/forestry-plans.tsx` declares `DELETE /forestry-plans/debug/clear-all` 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: DELETE /invites/:userId/:id
`src/supabase/functions/server/invites.tsx` declares `DELETE /invites/:userId/:id` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /notes/:propertyId/:noteId
`src/supabase/functions/server/notes.tsx` declares `DELETE /notes/:propertyId/:noteId` 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: GET /debug/all-properties
`src/supabase/functions/server/properties.tsx` declares `GET /debug/all-properties` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /departments/:propertyId
`src/supabase/functions/server/departments.tsx` declares `GET /departments/:propertyId` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who con…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /departments/:propertyId/:departmentId
`src/supabase/functions/server/departments.tsx` declares `GET /departments/:propertyId/:departmentId` 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: GET /departments/debug/status
`src/supabase/functions/server/departments.tsx` declares `GET /departments/debug/status` 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: GET /forestry-plans/:propertyId
`src/supabase/functions/server/forestry-plans.tsx` declares `GET /forestry-plans/:propertyId` 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 /forestry-plans/:propertyId/:departmentId
`src/supabase/functions/server/forestry-plans.tsx` declares `GET /forestry-plans/:propertyId/:departmentId` 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: GET /forestry-plans/:propertyId/:departmentId/:actionId
`src/supabase/functions/server/forestry-plans.tsx` declares `GET /forestry-plans/:propertyId/:departmentId/:actionId` 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: GET /forestry-plans/debug/status
`src/supabase/functions/server/forestry-plans.tsx` declares `GET /forestry-plans/debug/status` 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 /invites/:userId
`src/supabase/functions/server/invites.tsx` declares `GET /invites/:userId` 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 /make-server-ffc89dab/health
`src/supabase/functions/server/index.tsx` declares `GET /make-server-ffc89dab/health` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /notes/:propertyId
`src/supabase/functions/server/notes.tsx` declares `GET /notes/:propertyId` 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 /properties/:userId
`src/supabase/functions/server/properties.tsx` declares `GET /properties/:userId` 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: GET /properties/:userId/:propertyId
`src/supabase/functions/server/properties.tsx` declares `GET /properties/:userId/:propertyId` 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 /user/:userId
`src/supabase/functions/server/users.tsx` declares `GET /user/:userId` 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 /departments/migrate-site-index
`src/supabase/functions/server/departments.tsx` declares `POST /departments/migrate-site-index` 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 /departments/seed-missing
`src/supabase/functions/server/departments.tsx` declares `POST /departments/seed-missing` 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 /forestry-plans/:propertyId/:departmentId
`src/supabase/functions/server/forestry-plans.tsx` declares `POST /forestry-plans/:propertyId/:departmentId` 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 o…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /invites
`src/supabase/functions/server/invites.tsx` declares `POST /invites` 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 /make-server-ffc89dab/debug/reinit-all
`src/supabase/functions/server/index.tsx` declares `POST /make-server-ffc89dab/debug/reinit-all` 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 /notes
`src/supabase/functions/server/notes.tsx` declares `POST /notes` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /departments/:propertyId/:departmentId
`src/supabase/functions/server/departments.tsx` declares `PUT /departments/:propertyId/:departmentId` 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: PUT /forestry-plans/:propertyId/:departmentId/:actionId
`src/supabase/functions/server/forestry-plans.tsx` declares `PUT /forestry-plans/:propertyId/:departmentId/:actionId` 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: PUT /notes/:propertyId/:noteId
`src/supabase/functions/server/notes.tsx` declares `PUT /notes/:propertyId/:noteId` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /user/:userId
`src/supabase/functions/server/users.tsx` declares `PUT /user/:userId` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /user/:userId/notifications
`src/supabase/functions/server/users.tsx` declares `PUT /user/:userId/notifications` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consum…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /*
`src/supabase/functions/server/index.tsx` declares `USE /*` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph quality Complexity conf 1.00 Very large file: src/components/MapDrawer.tsx (1116 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/components/MobileBottomDrawer.tsx (1015 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/imports/Desktop65.tsx (1378 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/imports/Desktop67.tsx (3358 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/imports/Desktop68.tsx (1746 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/imports/Frame1.tsx (1173 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/imports/Frame2.tsx (2611 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/imports/IPhone16ProMax20.tsx (1532 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/pages/AccountPage.tsx (1714 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/pages/PropertiesPage.tsx (4227 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/3946be42-55b3-428f-bfbc-40281f54a4c3/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/3946be42-55b3-428f-bfbc-40281f54a4c3/

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.