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

vierkant14/openzorg

https://github.com/vierkant14/openzorg · scanned 2026-06-16 00:49 UTC (2 months, 1 week ago)

164 raw signals (0 security + 164 graph)

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

Complete repo analysis

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

JSON
Combined
48.6
/100
Security checks
49
0 findings
System graph
49
100.0% cov · 163 findings
Critical
3
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 3 High 37 Medium 39 Low 68 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 163 Crowd 0 Layer: Frontend 17 Network 10 Hardware 1 Security 11 Cicd 3 Quality 34 Api 87
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 48.6/100 with 100.0% coverage. It contains 2023 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 164 findings — concentrated in api (87), quality (34), frontend (17). Risk profile is high: 3 critical, 37 high, 39 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

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

critical System graph security Secrets conf 1.00 Possible secret in infra/scripts/augment-vvt-data.mjs
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
infra/scripts/augment-vvt-data.mjs:18
critical System graph security Secrets conf 1.00 Possible secret in scripts/seed-medplum.mjs
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
scripts/seed-medplum.mjs:19
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/clients/del-1 (services/ecd/src/__tests__/client.test.ts:173)
`services/ecd/src/__tests__/client.test.ts:173` calls `DELETE /api/clients/del-1` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/clients/del-1` If this points at an external API, prefix it with `https://` s…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/custom-fields (services/ecd/src/__tests__/configuratie.test.ts:89)
`services/ecd/src/__tests__/configuratie.test.ts:89` calls `GET /api/admin/custom-fields` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/custom-fields` If this points at an external API, prefix it wit…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/admin/validation-rules (services/ecd/src/__tests__/configuratie.test.ts:146)
`services/ecd/src/__tests__/configuratie.test.ts:146` calls `GET /api/admin/validation-rules` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/validation-rules` If this points at an external API, prefix…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/clients (services/ecd/src/__tests__/client.test.ts:130)
`services/ecd/src/__tests__/client.test.ts:130` calls `GET /api/clients` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/clients` If this points at an external API, prefix it with `https://` so the matcher s…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/clients/abc (services/ecd/src/__tests__/client.test.ts:145)
`services/ecd/src/__tests__/client.test.ts:145` calls `GET /api/clients/abc` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/clients/abc` If this points at an external API, prefix it with `https://` so the m…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/clients/p1/rapportages (services/ecd/src/__tests__/rapportage.test.ts:111)
`services/ecd/src/__tests__/rapportage.test.ts:111` calls `GET /api/clients/p1/rapportages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/clients/p1/rapportages` If this points at an external API, prefix i…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/clients/p1/rapportages?_count=50&date=ge2026-06-01 (services/ecd/src/__tests__/rapportage.test.ts:126)
`services/ecd/src/__tests__/rapportage.test.ts:126` calls `GET /api/clients/p1/rapportages?_count=50&date=ge2026-06-01` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/clients/p1/rapportages` If this points …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/ecd/api/admin/ai-settings (apps/web/src/components/ChatPanel.tsx:69)
`apps/web/src/components/ChatPanel.tsx:69` calls `GET /api/ecd/api/admin/ai-settings` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/ecd/api/admin/ai-settings` If this points at an external API, prefix it with `http…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/ecd/api/tenant-features (apps/web/src/lib/features.ts:73)
`apps/web/src/lib/features.ts:73` calls `GET /api/ecd/api/tenant-features` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/ecd/api/tenant-features` 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/master${cleanPath} (apps/web/src/lib/master-api.ts:20)
`apps/web/src/lib/master-api.ts:20` calls `GET /api/master${cleanPath}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/master/<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/mic-meldingen (services/ecd/src/__tests__/mic-melding.test.ts:123)
`services/ecd/src/__tests__/mic-melding.test.ts:123` calls `GET /api/mic-meldingen` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/mic-meldingen` If this points at an external API, prefix it with `https://`…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/workflow/api/bpmn-templates/${templateId} (apps/web/src/app/admin/workflows/canvas/page.tsx:319)
`apps/web/src/app/admin/workflows/canvas/page.tsx:319` calls `GET /api/workflow/api/bpmn-templates/${templateId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/workflow/api/bpmn-templates/<p>` If this points at an …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/custom-fields (services/ecd/src/__tests__/configuratie.test.ts:118)
`services/ecd/src/__tests__/configuratie.test.ts:118` calls `POST /api/admin/custom-fields` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/custom-fields` If this points at an external API, prefix it w…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/custom-fields (services/ecd/src/__tests__/configuratie.test.ts:128)
`services/ecd/src/__tests__/configuratie.test.ts:128` calls `POST /api/admin/custom-fields` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/custom-fields` If this points at an external API, prefix it w…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/custom-fields (services/ecd/src/__tests__/configuratie.test.ts:99)
`services/ecd/src/__tests__/configuratie.test.ts:99` calls `POST /api/admin/custom-fields` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/custom-fields` If this points at an external API, prefix it wi…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/validation-rules (services/ecd/src/__tests__/configuratie.test.ts:156)
`services/ecd/src/__tests__/configuratie.test.ts:156` calls `POST /api/admin/validation-rules` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/validation-rules` If this points at an external API, prefi…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/validation-rules (services/ecd/src/__tests__/configuratie.test.ts:174)
`services/ecd/src/__tests__/configuratie.test.ts:174` calls `POST /api/admin/validation-rules` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/validation-rules` If this points at an external API, prefi…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/admin/validation-rules (services/ecd/src/__tests__/configuratie.test.ts:184)
`services/ecd/src/__tests__/configuratie.test.ts:184` calls `POST /api/admin/validation-rules` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/admin/validation-rules` If this points at an external API, prefi…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/afspraken (services/planning/src/__tests__/app.test.ts:120)
`services/planning/src/__tests__/app.test.ts:120` calls `POST /api/afspraken` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/afspraken` If this points at an external API, prefix it with `https://` so the ma…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/afspraken (services/planning/src/__tests__/app.test.ts:74)
`services/planning/src/__tests__/app.test.ts:74` calls `POST /api/afspraken` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/afspraken` If this points at an external API, prefix it with `https://` so the mat…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/afspraken (services/planning/src/__tests__/app.test.ts:98)
`services/planning/src/__tests__/app.test.ts:98` calls `POST /api/afspraken` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/afspraken` If this points at an external API, prefix it with `https://` so the mat…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/auth/login (apps/web/src/app/login/page.tsx:43)
`apps/web/src/app/login/page.tsx:43` calls `POST /api/auth/login` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/auth/login` 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: POST /api/clients (services/ecd/src/__tests__/client.test.ts:34)
`services/ecd/src/__tests__/client.test.ts:34` calls `POST /api/clients` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/clients` If this points at an external API, prefix it with `https://` so the matcher s…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/clients (services/ecd/src/__tests__/client.test.ts:63)
`services/ecd/src/__tests__/client.test.ts:63` calls `POST /api/clients` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/clients` If this points at an external API, prefix it with `https://` so the matcher s…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/clients (services/ecd/src/__tests__/client.test.ts:93)
`services/ecd/src/__tests__/client.test.ts:93` calls `POST /api/clients` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/clients` If this points at an external API, prefix it with `https://` so the matcher s…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/clients/p1/rapportages (services/ecd/src/__tests__/rapportage.test.ts:26)
`services/ecd/src/__tests__/rapportage.test.ts:26` calls `POST /api/clients/p1/rapportages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/clients/p1/rapportages` If this points at an external API, prefix i…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/clients/p1/rapportages (services/ecd/src/__tests__/rapportage.test.ts:38)
`services/ecd/src/__tests__/rapportage.test.ts:38` calls `POST /api/clients/p1/rapportages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/clients/p1/rapportages` If this points at an external API, prefix i…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/clients/p1/rapportages (services/ecd/src/__tests__/rapportage.test.ts:54)
`services/ecd/src/__tests__/rapportage.test.ts:54` calls `POST /api/clients/p1/rapportages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/clients/p1/rapportages` If this points at an external API, prefix i…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/clients/p1/rapportages (services/ecd/src/__tests__/rapportage.test.ts:68)
`services/ecd/src/__tests__/rapportage.test.ts:68` calls `POST /api/clients/p1/rapportages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/clients/p1/rapportages` If this points at an external API, prefix i…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/clients/p1/rapportages (services/ecd/src/__tests__/rapportage.test.ts:94)
`services/ecd/src/__tests__/rapportage.test.ts:94` calls `POST /api/clients/p1/rapportages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/clients/p1/rapportages` If this points at an external API, prefix i…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/ecd/api/ai/chat (apps/web/src/components/ChatPanel.tsx:141)
`apps/web/src/components/ChatPanel.tsx:141` calls `POST /api/ecd/api/ai/chat` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/ecd/api/ai/chat` 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/mic-meldingen (services/ecd/src/__tests__/mic-melding.test.ts:33)
`services/ecd/src/__tests__/mic-melding.test.ts:33` calls `POST /api/mic-meldingen` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/mic-meldingen` If this points at an external API, prefix it with `https://`…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/mic-meldingen (services/ecd/src/__tests__/mic-melding.test.ts:49)
`services/ecd/src/__tests__/mic-melding.test.ts:49` calls `POST /api/mic-meldingen` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/mic-meldingen` If this points at an external API, prefix it with `https://`…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/mic-meldingen (services/ecd/src/__tests__/mic-melding.test.ts:63)
`services/ecd/src/__tests__/mic-melding.test.ts:63` calls `POST /api/mic-meldingen` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/mic-meldingen` If this points at an external API, prefix it with `https://`…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/mic-meldingen (services/ecd/src/__tests__/mic-melding.test.ts:77)
`services/ecd/src/__tests__/mic-melding.test.ts:77` calls `POST /api/mic-meldingen` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/mic-meldingen` If this points at an external API, prefix it with `https://`…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/mic-meldingen (services/ecd/src/__tests__/mic-melding.test.ts:95)
`services/ecd/src/__tests__/mic-melding.test.ts:95` calls `POST /api/mic-meldingen` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/mic-meldingen` If this points at an external API, prefix it with `https://`…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/clients/patient-1 (services/ecd/src/__tests__/client.test.ts:106)
`services/ecd/src/__tests__/client.test.ts:106` calls `PUT /api/clients/patient-1` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/clients/patient-1` If this points at an external API, prefix it with `https:…
Dangling fetchHelper:request
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — apps/web/src/app/layout.tsx:16
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 — apps/web/src/app/api/auth/login/route.ts:66
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 — apps/web/src/components/ChatPanel.tsx:141
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 — infra/scripts/augment-vvt-data.mjs:46
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — scripts/test-tenant-isolation.mjs:55
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 — services/ecd/src/lib/medplum-client.ts:50
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 — services/ecd/src/lib/ollama-client.ts:116
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 — services/ecd/src/lib/timer-service.ts:78
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 — services/ecd/src/routes/ai.ts:251
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 — services/ecd/src/routes/documenten.ts:86
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 — services/ecd/src/routes/tenants.ts:304
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 — services/ecd/src/routes/zorgplan.ts:349
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 — services/planning/src/lib/medplum-client.ts:50
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 — services/planning/src/routes/bezetting.ts:27
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — services/planning/src/routes/dienst-config.ts:50
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 — services/planning/src/routes/planning-engine.ts:73
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 lockfile. 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 GitHub Action is tag-pinned rather than SHA-pinned
appleboy/[email protected] can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
.github/workflows/deploy.yml:30 CI/CD securitySupply chainGithub actions
medium System graph cicd CI/CD security conf 1.00 GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
.github/workflows/release.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in services/ecd/src/app.ts:63
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
services/ecd/src/app.ts:63 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in services/facturatie/src/index.ts:19
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
services/facturatie/src/index.ts:19 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in services/planning/src/app.ts:26
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
services/planning/src/app.ts:26 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in services/workflow-bridge/src/app.ts:20
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
services/workflow-bridge/src/app.ts:20 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in apps/web/src/app/layout.tsx:16
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
apps/web/src/app/layout.tsx:16 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in apps/web/src/app/login/page.tsx:57
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
apps/web/src/app/login/page.tsx:57 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in apps/web/src/lib/api.ts:107
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
apps/web/src/lib/api.ts:107 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in apps/web/next.config.mjs:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
apps/web/next.config.mjs:1 Node child process
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 179 placeholder/mock markers across 55 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
medium System graph network Security conf 1.00 Privileged port 10 in use
Port 10 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
docker-compose.unraid.yml Ports
medium System graph network Security conf 1.00 Privileged port 11 in use
Port 11 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
infra/scripts/seed-planning.sh Ports
medium System graph network Security conf 1.00 Privileged port 13 in use
Port 13 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
infra/scripts/seed-planning.sh Ports
medium System graph network Security conf 1.00 Privileged port 14 in use
Port 14 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
infra/scripts/seed-planning.sh Ports
medium System graph network Security conf 1.00 Privileged port 16 in use
Port 16 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
infra/scripts/seed-planning.sh Ports
medium System graph network Security conf 1.00 Privileged port 17 in use
Port 17 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
infra/scripts/seed-planning.sh Ports
medium System graph network Security conf 1.00 Privileged port 19 in use
Port 19 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
infra/scripts/seed-planning-config.sh Ports
medium System graph network Security conf 1.00 Privileged port 23 in use
Port 23 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
infra/scripts/seed-planning.sh Ports
medium System graph network Security conf 1.00 Privileged port 30 in use
Port 30 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
infra/scripts/seed-planning.sh Ports
medium System graph network Security conf 1.00 Privileged port 7 in use
Port 7 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
infra/scripts/seed.sh Ports
low System graph quality Integrity conf 1.00 30 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `CI`, `E2E_BASE_URL`, `ECD_SERVICE_URL`, `FACTURATIE_SERVICE_URL`, `FLOWABLE_ADMIN_PASSWORD`, `FLOWABLE_ADMIN_USER`, `FLOWABLE_BASE_URL`, `GIT_SHA` + 22 more. 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 231 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph cicd CI/CD security conf 1.00 2 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/upload-artifact@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
lines 140, 148
.github/workflows/ci.yml:140, 148 (2 hits)
CI/CD securitySupply chainGithub actions
low System graph quality Tests conf 1.00 Low test-to-source ratio
34 tests / 242 src (ratio 0.14).
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: adapters/ons-import/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
adapters/ons-import/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: apps/web/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
apps/web/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/shared-config/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
packages/shared-config/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/shared-domain/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
packages/shared-domain/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/shared-ui/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
packages/shared-ui/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: services/ecd/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
services/ecd/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: services/facturatie/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
services/facturatie/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: services/planning/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
services/planning/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: services/workflow-bridge/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
services/workflow-bridge/package.json LockfileReproducibilityGenerated 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 — services/ecd/src/routes/ai-settings.ts:44
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 /:id
`services/ecd/src/routes/organisatie.ts` declares `DELETE /:id` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /:patientId/medicatie-overzicht/:id
`services/ecd/src/routes/medicatie-overzicht.ts` declares `DELETE /:patientId/medicatie-overzicht/: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 docu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /:patientId/vaccinaties/:id
`services/ecd/src/routes/vaccinatie.ts` declares `DELETE /:patientId/vaccinaties/: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 consu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /
`services/ecd/src/routes/tenant-settings.ts` declares `GET /` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /:clientId/verzekering
`services/ecd/src/routes/coverage.ts` declares `GET /:clientId/verzekering` 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 /:id
`services/ecd/src/routes/organisatie.ts` declares `GET /:id` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /:patientId/mdo
`services/ecd/src/routes/mdo.ts` declares `GET /:patientId/mdo` 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 /:patientId/medicatie-overzicht
`services/ecd/src/routes/medicatie-overzicht.ts` declares `GET /:patientId/medicatie-overzicht` 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 /:patientId/toedieningen
`services/ecd/src/routes/toediening.ts` declares `GET /:patientId/toedieningen` 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 /:patientId/toedienlijst
`services/ecd/src/routes/toediening.ts` declares `GET /:patientId/toedienlijst` 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 /:patientId/vaccinaties
`services/ecd/src/routes/vaccinatie.ts` declares `GET /:patientId/vaccinaties` 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 /:patientId/vaccinaties/:id
`services/ecd/src/routes/vaccinatie.ts` declares `GET /:patientId/vaccinaties/: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: GET /:patientId/vbm
`services/ecd/src/routes/vbm.ts` declares `GET /:patientId/vbm` 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/master/check-admin
`services/ecd/src/app.ts` declares `GET /api/master/check-admin` 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/tenant-features
`services/ecd/src/app.ts` declares `GET /api/tenant-features` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /clients/:clientId/documenten
`services/ecd/src/routes/documenten.ts` declares `GET /clients/:clientId/documenten` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consum…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /clients/:clientId/medicatie
`services/ecd/src/routes/medicatie.ts` declares `GET /clients/:clientId/medicatie` 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 /clients/:patientId/responses
`services/ecd/src/routes/vragenlijsten.ts` declares `GET /clients/:patientId/responses` 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 /config
`services/ecd/src/routes/ai.ts` declares `GET /config` 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 /medicatie-voorschriften
`services/ecd/src/routes/medicatie.ts` declares `GET /medicatie-voorschriften` 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 /models
`services/ecd/src/routes/ai.ts` declares `GET /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 documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /overzicht
`services/ecd/src/routes/vaccinatie.ts` declares `GET /overzicht` 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 /samenvatting
`services/ecd/src/routes/productie.ts` declares `GET /samenvatting` 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 /types
`services/ecd/src/routes/vbm.ts` declares `GET /types` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /:id/gelezen
`services/ecd/src/routes/berichten.ts` declares `PATCH /:id/gelezen` 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 /
`services/ecd/src/routes/productie.ts` declares `POST /` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /:clientId/verzekering
`services/ecd/src/routes/coverage.ts` declares `POST /:clientId/verzekering` 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 /:patientId/mdo
`services/ecd/src/routes/mdo.ts` declares `POST /:patientId/mdo` 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 /:patientId/mdo/:mdoId/verslag
`services/ecd/src/routes/mdo.ts` declares `POST /:patientId/mdo/:mdoId/verslag` 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 /:patientId/medicatie-overzicht
`services/ecd/src/routes/medicatie-overzicht.ts` declares `POST /:patientId/medicatie-overzicht` 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 /:patientId/toedieningen
`services/ecd/src/routes/toediening.ts` declares `POST /:patientId/toedieningen` 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 api Wiring conf 1.00 Unused endpoint: POST /:patientId/vaccinaties
`services/ecd/src/routes/vaccinatie.ts` declares `POST /:patientId/vaccinaties` 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 /:patientId/vbm
`services/ecd/src/routes/vbm.ts` declares `POST /:patientId/vbm` 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 /:patientId/vbm/:vbmId/evaluatie
`services/ecd/src/routes/vbm.ts` declares `POST /:patientId/vbm/:vbmId/evaluatie` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /ask
`services/ecd/src/routes/ai.ts` declares `POST /ask` 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 /chat
`services/ecd/src/routes/ai.ts` declares `POST /chat` 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 /clients/:clientId/documenten
`services/ecd/src/routes/documenten.ts` declares `POST /clients/:clientId/documenten` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /clients/:patientId/responses
`services/ecd/src/routes/vragenlijsten.ts` declares `POST /clients/:patientId/responses` 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 /locaties
`services/ecd/src/routes/organisatie.ts` declares `POST /locaties` 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 /summarize-rapportages
`services/ecd/src/routes/ai.ts` declares `POST /summarize-rapportages` 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 /
`services/ecd/src/routes/feature-flags.ts` declares `PUT /` 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 /:clientId/verzekering/:coverageId
`services/ecd/src/routes/coverage.ts` declares `PUT /:clientId/verzekering/:coverageId` 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: PUT /:id
`services/ecd/src/routes/organisatie.ts` declares `PUT /:id` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /:patientId/mdo/:id
`services/ecd/src/routes/mdo.ts` declares `PUT /:patientId/mdo/:id` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /:patientId/medicatie-overzicht/:id
`services/ecd/src/routes/medicatie-overzicht.ts` declares `PUT /:patientId/medicatie-overzicht/: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 documen…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /:patientId/vaccinaties/:id
`services/ecd/src/routes/vaccinatie.ts` declares `PUT /:patientId/vaccinaties/: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: PUT /:patientId/vbm/:id/beeindigen
`services/ecd/src/routes/vbm.ts` declares `PUT /:patientId/vbm/:id/beeindigen` 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 /config
`services/ecd/src/routes/ai.ts` declares `PUT /config` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/*
`services/ecd/src/app.ts` declares `USE /api/*` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/master/*
`services/ecd/src/app.ts` declares `USE /api/master/*` 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: infra/scripts/seed.sh (1293 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/5a3d2eba-49cc-4c9c-94b3-277a63c03793/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/5a3d2eba-49cc-4c9c-94b3-277a63c03793/

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.