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

voho0000/NHI-FHIR-BRIDGE

https://github.com/voho0000/NHI-FHIR-BRIDGE · scanned 2026-06-16 00:52 UTC (2 months, 1 week ago)

152 raw signals (0 security + 152 graph)

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

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 151 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
50.1
/100
Security checks
50
0 findings
System graph
50
100.0% cov · 151 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 17 Medium 23 Low 40 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 151 Crowd 0 Layer: Frontend 5 Hardware 3 Security 5 Cicd 2 Quality 100 Api 36
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 50.1/100 with 100.0% coverage. It contains 894 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 152 findings — concentrated in quality (100), api (36), frontend (5). Risk profile is high: 0 critical, 17 high, 23 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

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

high System graph api Wiring conf 1.00 Dangling fetch: DELETE /sync/patient/${encodeURIComponent(HASHED_ID)} (backend-ts/tests/integration/sync-delete-patient.test.ts:87)
`backend-ts/tests/integration/sync-delete-patient.test.ts:87` calls `DELETE /sync/patient/${encodeURIComponent(HASHED_ID)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/sync/patient/<p>` If this points at…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /sync/patient/${encodeURIComponent(RAW_ID)} (backend-ts/tests/integration/sync-delete-patient.test.ts:106)
`backend-ts/tests/integration/sync-delete-patient.test.ts:106` calls `DELETE /sync/patient/${encodeURIComponent(RAW_ID)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/sync/patient/<p>` If this points at a…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /sync/patient/${encodeURIComponent(RAW_ID)} (backend-ts/tests/integration/sync-delete-patient.test.ts:72)
`backend-ts/tests/integration/sync-delete-patient.test.ts:72` calls `DELETE /sync/patient/${encodeURIComponent(RAW_ID)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/sync/patient/<p>` If this points at an…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/ihke3000/ihke3410s01/page_load (extension/src/background/auth.ts:25)
`extension/src/background/auth.ts:25` calls `GET /api/ihke3000/ihke3410s01/page_load` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/ihke3000/ihke3410s01/page_load` If this points at an external API, prefix it with …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/ihke3000/ihke3410s01/page_load (extension/src/background/auth.ts:70)
`extension/src/background/auth.ts:70` calls `GET /api/ihke3000/ihke3410s01/page_load` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/ihke3000/ihke3410s01/page_load` If this points at an external API, prefix it with …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /fhir/.well-known/smart-configuration (backend-ts/tests/integration/fhir-scope.test.ts:118)
`backend-ts/tests/integration/fhir-scope.test.ts:118` calls `GET /fhir/.well-known/smart-configuration` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/fhir/.well-known/smart-configuration` If this points at…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /fhir/metadata (backend-ts/tests/integration/fhir-scope.test.ts:116)
`backend-ts/tests/integration/fhir-scope.test.ts:116` calls `GET /fhir/metadata` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/fhir/metadata` If this points at an external API, prefix it with `https://` so…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /fhir/metadata (backend-ts/tests/integration/security-hardening.test.ts:104)
`backend-ts/tests/integration/security-hardening.test.ts:104` calls `GET /fhir/metadata` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/fhir/metadata` If this points at an external API, prefix it with `http…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /fhir/metadata (backend-ts/tests/integration/security-hardening.test.ts:32)
`backend-ts/tests/integration/security-hardening.test.ts:32` calls `GET /fhir/metadata` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/fhir/metadata` 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 /fhir/metadata (backend-ts/tests/integration/security-hardening.test.ts:42)
`backend-ts/tests/integration/security-hardening.test.ts:42` calls `GET /fhir/metadata` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/fhir/metadata` 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 /fhir/Observation (backend-ts/tests/integration/fhir-scope.test.ts:91)
`backend-ts/tests/integration/fhir-scope.test.ts:91` calls `GET /fhir/Observation` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/fhir/observation` 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 /fhir/Patient (backend-ts/tests/integration/fhir-scope.test.ts:138)
`backend-ts/tests/integration/fhir-scope.test.ts:138` calls `GET /fhir/Patient` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/fhir/patient` If this points at an external API, prefix it with `https://` so t…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /fhir/Patient (backend-ts/tests/integration/fhir-scope.test.ts:68)
`backend-ts/tests/integration/fhir-scope.test.ts:68` calls `GET /fhir/Patient` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/fhir/patient` If this points at an external API, prefix it with `https://` so th…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /fhir/Patient (backend-ts/tests/integration/fhir-scope.test.ts:78)
`backend-ts/tests/integration/fhir-scope.test.ts:78` calls `GET /fhir/Patient` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/fhir/patient` If this points at an external API, prefix it with `https://` so th…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /fhir/Patient (backend-ts/tests/integration/fhir-scope.test.ts:96)
`backend-ts/tests/integration/fhir-scope.test.ts:96` calls `GET /fhir/Patient` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/fhir/patient` If this points at an external API, prefix it with `https://` so th…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /fhir/Patient/${HASHED_ID} (backend-ts/tests/integration/fhir-scope.test.ts:105)
`backend-ts/tests/integration/fhir-scope.test.ts:105` calls `GET /fhir/Patient/${HASHED_ID}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/fhir/patient/<p>` If this points at an external API, prefix it wit…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /fhir/import (backend-ts/tests/integration/fhir-import.test.ts:24)
`backend-ts/tests/integration/fhir-import.test.ts:24` calls `POST /fhir/import` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/fhir/import` If this points at an external API, prefix it with `https://` so th…
Dangling fetchHelper:request
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — backend-ts/scripts/bench-upload.ts:16
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 — extension/src/background/backend-upload.ts:18
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 — extension/src/background/badge.ts:31
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 — extension/src/background/nhi-detail-fetchers.ts:329
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 — extension/src/background/nhi-imaging-jpeg.ts:1757
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 — extension/src/background/sync-orchestrator.ts:580
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 — extension/src/nhi-adapters.ts:719
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 — extension/src/nhi-endpoints.ts:206
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 — extension/src/popup/connection.ts:264
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 — extension/src/popup/data-state.ts:212
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 — extension/src/popup/sync-client.ts:169
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 — frontend/app/api/backend/[...path]/route.ts:95
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 — frontend/app/page.tsx:82
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
softprops/action-gh-release@v3 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
.github/workflows/release.yml:119 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 backend-ts/src/main.ts:147
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
backend-ts/src/main.ts:147 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in extension/src/popup/connection.ts:148
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
extension/src/popup/connection.ts:148 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in extension/src/background/nhi-imaging-jpeg.ts:682
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
extension/src/background/nhi-imaging-jpeg.ts:682 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/check-no-real-twid.mjs:16
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/check-no-real-twid.mjs:16 Node child process
medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in CLAUDE.md:37
Found a known-risky pattern (weak_hash). Review and replace if possible.
CLAUDE.md:37 Weak hash
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 23 placeholder/mock markers across 8 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
low System graph quality Integrity conf 1.00 6 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `BACKEND_INTERNAL_URL`, `BASE_URL`, `BIND_HOST`, `DASHBOARD_ALLOWED_HOSTS`, `DATABASE_FILE`, `NEXT_PUBLIC_API_URL`. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.
config drift
low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
Deployment
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 28 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph hardware Supply chain conf 1.00 2 occurrences Docker base image is tag-pinned but not digest-pinned: node:20-alpine
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
lines 6, 26
frontend/Dockerfile:6, 26 (2 hits)
containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: node:20-bookworm-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
backend-ts/Dockerfile:10 containersPinned dependencies
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: backend-ts/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.
backend-ts/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: extension/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.
extension/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/mapper/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/mapper/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `inpatient_legacy` in extension/src/background/bundle.ts:43
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `inpatient_legacy` in extension/src/nhi-endpoints.ts:73
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality 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 — backend-ts/scripts/bench-upload.ts:76
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 — backend-ts/src/core/migrate.ts:19
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 — backend-ts/src/main.ts:219
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 /logs
`backend-ts/src/api/sync.ts` declares `DELETE /logs` 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 /logs/:logId
`backend-ts/src/api/sync.ts` declares `DELETE /logs/:logId` 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 /patient/:patientId
`backend-ts/src/api/sync.ts` declares `DELETE /patient/:patientId` 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 /audit-log
`backend-ts/src/api/sync.ts` declares `GET /audit-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 /authorize
`backend-ts/src/api/smart.ts` declares `GET /authorize` 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 /export
`backend-ts/src/api/fhir.ts` declares `GET /export` 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 /latest-dates
`backend-ts/src/api/sync.ts` declares `GET /latest-dates` 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 /logs
`backend-ts/src/api/sync.ts` declares `GET /logs` 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 /metadata
`backend-ts/src/api/fhir.ts` declares `GET /metadata` 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 /Patient
`backend-ts/src/api/fhir.ts` declares `GET /Patient` 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 /patient-states
`backend-ts/src/api/sync.ts` declares `GET /patient-states` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /Patient/:patientId
`backend-ts/src/api/fhir.ts` declares `GET /Patient/:patientId` 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 /import
`backend-ts/src/api/fhir.ts` declares `POST /import` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /launch-context
`backend-ts/src/api/smart.ts` declares `POST /launch-context` 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 /log
`backend-ts/src/api/sync.ts` declares `POST /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: POST /token
`backend-ts/src/api/smart.ts` declares `POST /token` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /upload-structured
`backend-ts/src/api/sync.ts` declares `POST /upload-structured` 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 /Patient
`backend-ts/src/api/fhir.ts` declares `USE /Patient` 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 /Patient/*
`backend-ts/src/api/fhir.ts` declares `USE /Patient/*` 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: backend-ts/tests/unit/bundle-quality.test.ts (5064 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: extension/src/background/nhi-imaging-jpeg.ts (2126 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: extension/src/background/sync-orchestrator.ts (1498 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: extension/src/nhi-adapters.ts (1197 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: extension/tests/adapters.test.js (1709 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: packages/mapper/src/loinc-tables.ts (2043 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: packages/mapper/src/observation.ts (2477 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/a85ca68d-54a8-4af0-a0bd-386e7feee9d2/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/a85ca68d-54a8-4af0-a0bd-386e7feee9d2/

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.