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

TOP-PHE/UIC_OSCAR-OSdm-Compliance-Automation-Runner

https://github.com/TOP-PHE/UIC_OSCAR-OSdm-Compliance-Automation-Runner · scanned 2026-06-16 00:41 UTC (2 months, 1 week ago)

235 raw signals (0 security + 235 graph)

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

Complete repo analysis

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

JSON
Combined
48.4
/100
Security checks
48
0 findings
System graph
48
100.0% cov · 201 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 29 Medium 25 Low 93 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 201 Crowd 0 Layer: Frontend 32 Network 1 Hardware 2 Security 20 Cicd 3 Quality 67 Api 76
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.4/100 with 100.0% coverage. It contains 2233 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 235 findings — concentrated in api (76), quality (67), cicd (36). Risk profile is high: 0 critical, 29 high, 43 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

Showing 147 of 201 actionable findings. 235 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 /v1/company/datafile (Oscar_Server/public/js/scenarios.js:1158)
`Oscar_Server/public/js/scenarios.js:1158` calls `DELETE /v1/company/datafile` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/company/datafile` If this points at an external API, prefix it with `https://` so the mat…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /v1/company/datafile (Oscar_Server/public/js/scenarios.js:644)
`Oscar_Server/public/js/scenarios.js:644` calls `DELETE /v1/company/datafile` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/company/datafile` If this points at an external API, prefix it with `https://` so the matc…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /v1/company/datafile (Oscar_Server/public/js/scenarios.js:672)
`Oscar_Server/public/js/scenarios.js:672` calls `DELETE /v1/company/datafile` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/company/datafile` If this points at an external API, prefix it with `https://` so the matc…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /v1/company/datafile (Oscar_Server/public/js/scenarios.js:785)
`Oscar_Server/public/js/scenarios.js:785` calls `DELETE /v1/company/datafile` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/company/datafile` If this points at an external API, prefix it with `https://` so the matc…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /v1/company/test-framework (Oscar_Server/public/js/scenarios.js:650)
`Oscar_Server/public/js/scenarios.js:650` calls `DELETE /v1/company/test-framework` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/company/test-framework` If this points at an external API, prefix it with `https://`…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /v1/company/test-resources/${id} (Oscar_Server/public/js/scenarios.js:4753)
`Oscar_Server/public/js/scenarios.js:4753` calls `DELETE /v1/company/test-resources/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/company/test-resources/<p>` If this points at an external API, prefix it with…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /v1/company/test-resources/${r.id} (Oscar_Server/public/js/scenarios.js:647)
`Oscar_Server/public/js/scenarios.js:647` calls `DELETE /v1/company/test-resources/${r.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/company/test-resources/<p>` If this points at an external API, prefix it wit…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /v1/company/test-resources/${r.id} (Oscar_Server/public/js/scenarios.js:675)
`Oscar_Server/public/js/scenarios.js:675` calls `DELETE /v1/company/test-resources/${r.id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/company/test-resources/<p>` If this points at an external API, prefix it wit…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /v1/company/test-resources/${resourceId} (Oscar_Server/public/js/scenarios.js:726)
`Oscar_Server/public/js/scenarios.js:726` calls `DELETE /v1/company/test-resources/${resourceId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/company/test-resources/<p>` If this points at an external API, prefix …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /v1/company (Oscar_Server/public/js/scenarios.js:326)
`Oscar_Server/public/js/scenarios.js:326` calls `GET /v1/company` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/company` 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 /v1/company/datafile (Oscar_Server/public/js/scenarios.js:2912)
`Oscar_Server/public/js/scenarios.js:2912` calls `GET /v1/company/datafile` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/company/datafile` If this points at an external API, prefix it with `https://` so the matche…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /v1/company/datafile (Oscar_Server/public/js/scenarios.js:355)
`Oscar_Server/public/js/scenarios.js:355` calls `GET /v1/company/datafile` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/company/datafile` If this points at an external API, prefix it with `https://` so the matcher…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /v1/company/datafile (Oscar_Server/public/js/scenarios.js:5470)
`Oscar_Server/public/js/scenarios.js:5470` calls `GET /v1/company/datafile` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/company/datafile` If this points at an external API, prefix it with `https://` so the matche…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /v1/company/test-framework (Oscar_Server/public/js/scenarios.js:324)
`Oscar_Server/public/js/scenarios.js:324` calls `GET /v1/company/test-framework` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/company/test-framework` If this points at an external API, prefix it with `https://` so…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /v1/company/test-resources (Oscar_Server/public/js/scenarios.js:1123)
`Oscar_Server/public/js/scenarios.js:1123` calls `GET /v1/company/test-resources` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/company/test-resources` If this points at an external API, prefix it with `https://` s…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /v1/company/test-resources (Oscar_Server/public/js/scenarios.js:325)
`Oscar_Server/public/js/scenarios.js:325` calls `GET /v1/company/test-resources` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/company/test-resources` If this points at an external API, prefix it with `https://` so…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /v1/auth/logout (Oscar_Server/public/nav.js:341)
`Oscar_Server/public/nav.js:341` calls `POST /v1/auth/logout` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/auth/logout` 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 /v1/company/datafile (Oscar_Server/public/js/scenarios.js:999)
`Oscar_Server/public/js/scenarios.js:999` calls `POST /v1/company/datafile` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/company/datafile` If this points at an external API, prefix it with `https://` so the matche…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /v1/company/test-resources (Oscar_Server/public/js/scenarios.js:1140)
`Oscar_Server/public/js/scenarios.js:1140` calls `POST /v1/company/test-resources` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/company/test-resources` If this points at an external API, prefix it with `https://` …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /v1/company/test-resources/discover-timetable (Oscar_Server/public/js/scenarios.js:4284)
`Oscar_Server/public/js/scenarios.js:4284` calls `POST /v1/company/test-resources/discover-timetable` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/company/test-resources/discover-timetable` If this points at an ex…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /v1/company/test-resources/reprobe-offers (Oscar_Server/public/js/scenarios.js:6184)
`Oscar_Server/public/js/scenarios.js:6184` calls `POST /v1/company/test-resources/reprobe-offers` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/company/test-resources/reprobe-offers` If this points at an external A…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /v1/company/datafile/json (Oscar_Server/public/js/scenarios.js:2896)
`Oscar_Server/public/js/scenarios.js:2896` calls `PUT /v1/company/datafile/json` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/company/datafile/json` If this points at an external API, prefix it with `https://` so …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /v1/company/datafile/json (Oscar_Server/public/js/scenarios.js:5736)
`Oscar_Server/public/js/scenarios.js:5736` calls `PUT /v1/company/datafile/json` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/company/datafile/json` If this points at an external API, prefix it with `https://` so …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /v1/company/datafile/json (Oscar_Server/public/js/scenarios.js:736)
`Oscar_Server/public/js/scenarios.js:736` calls `PUT /v1/company/datafile/json` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/company/datafile/json` If this points at an external API, prefix it with `https://` so t…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /v1/company/test-framework (Oscar_Server/public/js/scenarios.js:1113)
`Oscar_Server/public/js/scenarios.js:1113` calls `PUT /v1/company/test-framework` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/company/test-framework` If this points at an external API, prefix it with `https://` s…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /v1/company/test-framework (Oscar_Server/public/js/scenarios.js:612)
`Oscar_Server/public/js/scenarios.js:612` calls `PUT /v1/company/test-framework` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/company/test-framework` If this points at an external API, prefix it with `https://` so…
Dangling fetchFetch
high System graph security security conf 1.00 Insecure pattern 'new_function_used' in Bruno_Collection/json_validator/ajv.js:2
Found a known-risky pattern (new_function_used). Review and replace if possible.
Bruno_Collection/json_validator/ajv.js:2 New function used
high System graph security security conf 1.00 Insecure pattern 'new_function_used' in Bruno_Collection/library-bruno/validators.js:33
Found a known-risky pattern (new_function_used). Review and replace if possible.
Bruno_Collection/library-bruno/validators.js:33 New function used
high System graph security security conf 1.00 Insecure pattern 'new_function_used' in compatibility.json:15
Found a known-risky pattern (new_function_used). Review and replace if possible.
compatibility.json:15 New function used
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — Oscar_Server/public/js/scenarios.js:736
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 — Oscar_Server/public/nav.js:25
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — Oscar_Server/src/server.js:365
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 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 17 occurrences GitHub Action is tag-pinned rather than SHA-pinned
docker/setup-buildx-action@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
6 files, 17 locations
.github/workflows/ci-server.yml:80, 83, 103, 106, 114 (5 hits)
.github/workflows/publish-image.yml:47, 56, 68, 77 (4 hits)
.github/workflows/codeql.yml:55, 66, 69 (3 hits)
.github/workflows/promote-release.yml:62, 69, 76 (3 hits)
.github/workflows/gitleaks.yml:43
.github/workflows/sonar.yml:82
CI/CD securitySupply chainGithub actions
medium System graph cicd CI/CD security conf 1.00 3 occurrences 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.
3 files, 3 locations
.github/workflows/promote-release.yml
.github/workflows/publish-image.yml
.github/workflows/render-docs-pdf.yml
CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in compatibility.json:672
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
compatibility.json:672 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in Oscar_Server/public/admin.html:469
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
Oscar_Server/public/admin.html:469 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in Oscar_Server/public/compare.html:134
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
Oscar_Server/public/compare.html:134 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in Oscar_Server/public/dashboard.html:348
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
Oscar_Server/public/dashboard.html:348 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in Oscar_Server/public/forgot-password.html:129
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
Oscar_Server/public/forgot-password.html:129 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in Oscar_Server/public/js/findings.js:109
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
Oscar_Server/public/js/findings.js:109 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in Oscar_Server/public/js/scenarios.js:316
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
Oscar_Server/public/js/scenarios.js:316 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in Oscar_Server/public/nav.js:177
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
Oscar_Server/public/nav.js:177 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in Oscar_Server/public/report-builder.html:541
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
Oscar_Server/public/report-builder.html:541 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in Oscar_Server/public/reset-password.html:131
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
Oscar_Server/public/reset-password.html:131 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in Oscar_Server/public/run-detail.html:331
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
Oscar_Server/public/run-detail.html:331 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in Oscar_Server/public/run.html:144
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
Oscar_Server/public/run.html:144 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in Oscar_Server/public/verify-email.html:133
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
Oscar_Server/public/verify-email.html:133 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in Oscar_Server/public/welcome.html:246
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
Oscar_Server/public/welcome.html:246 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_outerhtml_assignment' in Oscar_Server/public/dashboard.html:748
Found a known-risky pattern (direct_outerhtml_assignment). Review and replace if possible.
Oscar_Server/public/dashboard.html:748 Direct outerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in Oscar_Server/public/index.html:209
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
Oscar_Server/public/index.html:209 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in Oscar_Server/src/worker/runner.js:26
Found a known-risky pattern (node_child_process). Review and replace if possible.
Oscar_Server/src/worker/runner.js:26 Node child process
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 61 placeholder/mock markers across 5 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.
Bruno_Collection/02-Common Requests/Post Offer-Req param chk.yml Ports
low System graph quality Integrity conf 1.00 11 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `ALERTMANAGER_CONFIG_PATH`, `ALERTMANAGER_RELOAD_URL`, `ALERT_RECIPIENTS`, `ALERT_REPEAT_CRITICAL`, `ALERT_REPEAT_WARNING`, `ALLOWED_ORIGINS`, `AUTH_RATE_LIMIT_MAX`, `COMPATIBILITY_FILE` + 3 more. Add them (with a placeholder/comment) to .env.examp…
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 93 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:22-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
lines 11, 39
Oscar_Server/Dockerfile:11, 39 (2 hits)
containersPinned dependencies
low System graph cicd CI/CD security conf 1.00 16 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/create-github-app-token@v3 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
9 files, 16 locations
.github/workflows/ci-server.yml:42, 45, 77, 100 (4 hits)
.github/workflows/auto-tag-on-release.yml:82, 90 (2 hits)
.github/workflows/ci-collection.yml:36, 39 (2 hits)
.github/workflows/render-docs-pdf.yml:36, 42 (2 hits)
.github/workflows/sonar.yml:38, 45 (2 hits)
.github/workflows/codeql.yml:52
.github/workflows/gitleaks.yml:38
.github/workflows/promote-release.yml:57
CI/CD securitySupply chainGithub actions
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — Oscar_Server/public/js/scenarios.js:4946
A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label
Fq button no label
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: Documentation/Test_Coverage/_build_coverage_matrix.py:request_files, Documentation/Test_Coverage/_build_field_level_coverage.py:request_files This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hyg…
duplicatesduplication
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 — Bruno_Collection/json_validator/ajv.js:2
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 — Bruno_Collection/library-bruno/afterSalesRules.js:164
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 — Bruno_Collection/library-bruno/auth.js:192
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 — Bruno_Collection/library-bruno/bookings.js:1120
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 — Bruno_Collection/library-bruno/displays.js:46
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 — Bruno_Collection/library-bruno/envUtils.js:35
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 — Bruno_Collection/library-bruno/exchanges.js:307
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 — Bruno_Collection/library-bruno/expiredFlow.js:464
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 — Bruno_Collection/library-bruno/fulfillments.js:206
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 — Bruno_Collection/library-bruno/loopback.js:22
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 — Bruno_Collection/library-bruno/mergeReport.js:263
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 — Bruno_Collection/library-bruno/model.js:344
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 — Bruno_Collection/library-bruno/offers.js:122
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 — Bruno_Collection/library-bruno/osdmCompliance.js:745
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 — Bruno_Collection/library-bruno/osdmSchema.js:153
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 — Bruno_Collection/library-bruno/osdmSchemas.js:2385
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 — Bruno_Collection/library-bruno/osdmVersion.js:171
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 — Bruno_Collection/library-bruno/partialRefund.js:368
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 — Bruno_Collection/library-bruno/passengers.js:107
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 — Bruno_Collection/library-bruno/placeProbes.js:274
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 — Bruno_Collection/library-bruno/refunds.js:757
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 — Bruno_Collection/library-bruno/reportGenerator.js:87
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 — Bruno_Collection/library-bruno/requestedInformation.js:866
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 — Bruno_Collection/library-bruno/scenarioParser.js:516
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 — Bruno_Collection/library-bruno/validators.js:80
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 — Oscar_Server/public/js/scenarios.js:1147
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 — Oscar_Server/scripts/lint-inline-scripts.js:170
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 — Oscar_Server/src/db/db.js:319
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 — Oscar_Server/src/utils/at-rest.js:58
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 /companies/:id
`Oscar_Server/src/api/routes/admin.js` declares `DELETE /companies/: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 /test-framework
`Oscar_Server/src/api/routes/company-test-framework.js` declares `DELETE /test-framework` 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: DELETE /users/:id
`Oscar_Server/src/api/routes/admin.js` declares `DELETE /users/: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 /activity
`Oscar_Server/src/api/routes/admin.js` declares `GET /activity` 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 /artifacts/:runId/:filename
`Oscar_Server/src/server.js` declares `GET /artifacts/:runId/:filename` 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 /companies
`Oscar_Server/src/api/routes/admin.js` declares `GET /companies` 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 /comparisons
`Oscar_Server/src/api/routes/reports.js` declares `GET /comparisons` 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 /comparisons/:id
`Oscar_Server/src/api/routes/reports.js` declares `GET /comparisons/: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 /config
`Oscar_Server/src/api/routes/admin.js` 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 /data/:filename
`Oscar_Server/src/server.js` declares `GET /data/:filename` 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 /json_validator/datafile.schema.json
`Oscar_Server/src/server.js` declares `GET /json_validator/datafile.schema.json` 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: GET /me
`Oscar_Server/src/api/routes/auth.js` declares `GET /me` 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 /password-reset/check-token
`Oscar_Server/src/api/routes/auth.js` declares `GET /password-reset/check-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 i…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /register/check-token
`Oscar_Server/src/api/routes/auth.js` declares `GET /register/check-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: GET /register/companies
`Oscar_Server/src/api/routes/auth.js` declares `GET /register/companies` 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 /sso-check
`Oscar_Server/src/api/routes/auth.js` declares `GET /sso-check` 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 /test-framework
`Oscar_Server/src/api/routes/company-test-framework.js` declares `GET /test-framework` 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 /users
`Oscar_Server/src/api/routes/admin.js` declares `GET /users` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /v1/openapi.json
`Oscar_Server/src/server.js` declares `GET /v1/openapi.json` 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 /companies/:id
`Oscar_Server/src/api/routes/admin.js` declares `PATCH /companies/: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: PATCH /config
`Oscar_Server/src/api/routes/admin.js` declares `PATCH /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: PATCH /users/:id
`Oscar_Server/src/api/routes/admin.js` declares `PATCH /users/: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: POST /alertmanager/apply
`Oscar_Server/src/api/routes/admin.js` declares `POST /alertmanager/apply` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /bootstrap/platform-user
`Oscar_Server/src/api/routes/auth.js` declares `POST /bootstrap/platform-user` 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 /companies
`Oscar_Server/src/api/routes/admin.js` declares `POST /companies` 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 /compare
`Oscar_Server/src/api/routes/reports.js` declares `POST /compare` 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 /login
`Oscar_Server/src/api/middleware/validate.js` declares `POST /login` 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 /logout
`Oscar_Server/src/api/routes/auth.js` declares `POST /logout` 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 /password-reset/confirm
`Oscar_Server/src/api/routes/auth.js` declares `POST /password-reset/confirm` 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 /password-reset/request
`Oscar_Server/src/api/routes/auth.js` declares `POST /password-reset/request` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /register/confirm
`Oscar_Server/src/api/routes/auth.js` declares `POST /register/confirm` 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 /register/request
`Oscar_Server/src/api/routes/auth.js` declares `POST /register/request` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /rotate-jwt-secret
`Oscar_Server/src/api/routes/admin.js` declares `POST /rotate-jwt-secret` 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 /test-email
`Oscar_Server/src/api/routes/admin.js` declares `POST /test-email` 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 /users
`Oscar_Server/src/api/routes/admin.js` declares `POST /users` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /users/:id/generate-reset-link
`Oscar_Server/src/api/routes/admin.js` declares `POST /users/:id/generate-reset-link` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /users/:id/reset-password
`Oscar_Server/src/api/routes/admin.js` declares `POST /users/:id/reset-password` 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 /v1/runs/:runId/refresh-access-token
`Oscar_Server/src/server.js` declares `POST /v1/runs/:runId/refresh-access-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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /test-framework
`Oscar_Server/src/api/routes/company-test-framework.js` declares `PUT /test-framework` 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: USE /bootstrap
`Oscar_Server/src/api/routes/auth.js` declares `USE /bootstrap` 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 /login
`Oscar_Server/src/api/routes/auth.js` declares `USE /login` 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 /register
`Oscar_Server/src/api/routes/auth.js` declares `USE /register` 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 /v1/admin
`Oscar_Server/src/server.js` declares `USE /v1/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: USE /v1/auth
`Oscar_Server/src/server.js` declares `USE /v1/auth` 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 /v1/company
`Oscar_Server/src/server.js` declares `USE /v1/company` 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 /v1/company/users
`Oscar_Server/src/server.js` declares `USE /v1/company/users` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /v1/docs
`Oscar_Server/src/server.js` declares `USE /v1/docs` 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 /v1/me/credentials
`Oscar_Server/src/server.js` declares `USE /v1/me/credentials` 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 /v1/reports
`Oscar_Server/src/server.js` declares `USE /v1/reports` 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 /v1/runs
`Oscar_Server/src/server.js` declares `USE /v1/runs` 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: Bruno_Collection/library-bruno/bookings.js (1121 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: Bruno_Collection/library-bruno/offers.js (1838 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: Bruno_Collection/library-bruno/scenarioParser.js (1555 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: Oscar_Server/public/js/scenarios.js (6900 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: Oscar_Server/src/api/routes/runs.js (1219 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: Oscar_Server/src/worker/runner.js (1076 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/04ec51cb-84bf-48d4-96e5-b2375000d197/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/04ec51cb-84bf-48d4-96e5-b2375000d197/

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.