caresmartsuits-eng/adminapplication-internal

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.

Scan timing: clone 3.47s · analysis 1.96s · 1.4 MB · GitHub API rate-limit (preflight)

caresmartsuits-eng/adminapplication-internal

https://github.com/caresmartsuits-eng/adminapplication-internal.git · scanned 2026-05-27 13:22 UTC (1 week, 2 days ago) · 10 languages

198 findings (48 legacy + 150 scanner) 5th percentile · Javascript · small (2-20K LoC) Scanner says 68 (lower by 28)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 week, 2 days ago · v2 · 123 findings from 2 sources. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	55.0	0.15	8.25
`security_score`	75.3	0.25	18.82
`testing_score`	0.0	0.20	0.00
`documentation_score`	1.0	0.15	0.15
`practices_score`	40.0	0.15	6.00
`code_quality`	74.2	0.10	7.42
Overall		1.00	40.6

Severity distribution — click a segment to filter

Active filters: layer: api × excluding tests × Reset all

Severity: Critical 6 High 29 Medium 6 Low 67 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 48 9-layer 75 Crowd 0 Layer: Security 19 Quality 37 Software 27 Frontend 11 Cicd 1 Api 28

Exclude dismissed / FP Exclude test files

Scan summary Repository scanned at 68.4/100 with 100.0% coverage. It contains 471 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 75 findings — concentrated in api (28), software (27), frontend (11). Risk profile is high: 1 critical, 2 high, 5 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

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

low 9-layer api wiring conf 1.00 Unused endpoint: GET /admin/active-config-headers

`backendmongo/src/routes/configHeaders.routes.js` declares `GET /admin/active-config-headers` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting w…

wiringunused-endpoint

low 9-layer api wiring conf 1.00 Unused endpoint: GET /admin/config-headers

`backendmongo/src/routes/configHeaders.routes.js` declares `GET /admin/config-headers` 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…

wiringunused-endpoint

low 9-layer api wiring conf 1.00 Unused endpoint: GET /admin/configurations

`backendmongo/src/routes/configs.routes.js` declares `GET /admin/configurations` 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…

wiringunused-endpoint

low 9-layer api wiring conf 1.00 Unused endpoint: GET /admin/users

`backendmongo/src/routes/users.routes.js` declares `GET /admin/users` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

wiringunused-endpoint

low 9-layer api wiring conf 1.00 Unused endpoint: GET /audits

`backendmongo/src/routes/audits.routes.js` declares `GET /audits` 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.

wiringunused-endpoint

low 9-layer api wiring conf 1.00 Unused endpoint: GET /audits/recent

`backendmongo/src/routes/audits.routes.js` declares `GET /audits/recent` 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.

wiringunused-endpoint

low 9-layer api wiring conf 1.00 Unused endpoint: GET /configurations/:category

`backendmongo/src/routes/configs.routes.js` declares `GET /configurations/:category` 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…

wiringunused-endpoint

low 9-layer api wiring conf 1.00 Unused endpoint: GET /configurations/active

`backendmongo/src/routes/configs.routes.js` declares `GET /configurations/active` 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 …

wiringunused-endpoint

low 9-layer api wiring conf 1.00 Unused endpoint: GET /orders

`backendmongo/src/routes/orders.routes.js` declares `GET /orders` 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.

wiringunused-endpoint

low 9-layer api wiring conf 1.00 Unused endpoint: GET /orders/delivery-status

`backendmongo/src/routes/orders.routes.js` declares `GET /orders/delivery-status` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes …

wiringunused-endpoint

low 9-layer api wiring conf 1.00 Unused endpoint: GET /orders/kpi-counts

`backendmongo/src/routes/orders.routes.js` declares `GET /orders/kpi-counts` 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.

wiringunused-endpoint

low 9-layer api wiring conf 1.00 Unused endpoint: GET /orders/next-snum

`backendmongo/src/routes/orders.routes.js` declares `GET /orders/next-snum` 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.

wiringunused-endpoint

low 9-layer api wiring conf 1.00 Unused endpoint: GET /orders/status-breakdown

`backendmongo/src/routes/orders.routes.js` declares `GET /orders/status-breakdown` 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…

wiringunused-endpoint

low 9-layer api wiring conf 1.00 Unused endpoint: GET /user/:username

`backendmongo/src/routes/users.routes.js` declares `GET /user/:username` 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.

wiringunused-endpoint

low 9-layer api wiring conf 1.00 Unused endpoint: GET /users/count

`backendmongo/src/routes/users.routes.js` declares `GET /users/count` 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.

wiringunused-endpoint

low 9-layer api wiring conf 1.00 Unused endpoint: POST /admin/config-headers/create

`backendmongo/src/routes/configHeaders.routes.js` declares `POST /admin/config-headers/create` 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 …

wiringunused-endpoint

low 9-layer api wiring conf 1.00 Unused endpoint: POST /admin/configurations/create

`backendmongo/src/routes/configs.routes.js` declares `POST /admin/configurations/create` 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…

wiringunused-endpoint

low 9-layer api wiring conf 1.00 Unused endpoint: POST /admin/create-user

`backendmongo/src/routes/users.routes.js` declares `POST /admin/create-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.

wiringunused-endpoint

low 9-layer api wiring conf 1.00 Unused endpoint: POST /forgot-password

`backendmongo/src/routes/users.routes.js` declares `POST /forgot-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 it.

wiringunused-endpoint

low 9-layer api wiring conf 1.00 Unused endpoint: POST /login

`backendmongo/src/routes/auth.routes.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.

wiringunused-endpoint

low 9-layer api wiring conf 1.00 Unused endpoint: POST /orders/create

`backendmongo/src/routes/orders.routes.js` declares `POST /orders/create` 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.

wiringunused-endpoint

low 9-layer api wiring conf 1.00 Unused endpoint: POST /reset-password

`backendmongo/src/routes/users.routes.js` declares `POST /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 it.

wiringunused-endpoint

low 9-layer api wiring conf 1.00 Unused endpoint: PUT /admin/config-headers/update/:id

`backendmongo/src/routes/configHeaders.routes.js` declares `PUT /admin/config-headers/update/: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 documenti…

wiringunused-endpoint

low 9-layer api wiring conf 1.00 Unused endpoint: PUT /admin/configurations/update/:id

`backendmongo/src/routes/configs.routes.js` declares `PUT /admin/configurations/update/: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…

wiringunused-endpoint

low 9-layer api wiring conf 1.00 Unused endpoint: PUT /orders/update/:id

`backendmongo/src/routes/orders.routes.js` declares `PUT /orders/update/: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.

wiringunused-endpoint

low 9-layer api wiring conf 1.00 Unused endpoint: PUT /user/:username

`backendmongo/src/routes/users.routes.js` declares `PUT /user/:username` 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.

wiringunused-endpoint

low 9-layer api wiring conf 1.00 Unused endpoint: PUT /user/:username/password

`backendmongo/src/routes/users.routes.js` declares `PUT /user/:username/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 …

wiringunused-endpoint

low 9-layer api wiring conf 1.00 Unused endpoint: USE /api

`backend/src/server.js` 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.

wiringunused-endpoint

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/48db27c5-c23e-469b-b989-fa3903222026/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/48db27c5-c23e-469b-b989-fa3903222026/

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.