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

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, 1 day ago) · 10 languages

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

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

Complete repo analysis

Last scanned 1 week, 1 day 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
Combined
62.7
/100
Repobility
57
48 legacy
9-layer
68
100.0% cov · 75 gaps
Critical
6
click to filter
Agents
6
0 votes
Crowd
0
reported
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: 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

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Fragile runtime 31 findings
What it is: Code that runs but breaks under predictable input — division by zero, missing keys, unbounded loops, off-by-one slicing.
Why it matters: Reaches production undetected because happy-path tests pass. First user with a weird input crashes the request.
How AI causes it: AI loves writing the happy path; doesn't probe edge cases unless explicitly asked.
Fix approach: Add property-based tests. Wrap external inputs with explicit validators. Use the framework's typed deserializer (Pydantic, attrs).
12 matching findings on this repo
  • low Duplicated implementation block across source files client/src/pages/user/UserDashboard.jsx:15
  • low Duplicated implementation block across source files client/src/pages/user/ResetPassword.jsx:122
  • low Duplicated implementation block across source files client/src/pages/user/ResetPassword.jsx:66
  • low Duplicated implementation block across source files client/src/pages/user/ForgotPassword.jsx:40
  • low Duplicated implementation block across source files client/src/pages/features/orders/UpdateOrderModal…:140
  • low Duplicated implementation block across source files client/src/pages/features/orders/OrdersList.jsx:223
  • low Duplicated implementation block across source files client/src/pages/features/configs/UpdateConfigura…:8
  • low Duplicated implementation block across source files client/src/pages/features/configs/ConfigurationsL…:106
  • low Duplicated implementation block across source files backendmongo/src/models/Configuration.js:9
  • info [MINED056] React Key As Index: key={index} in map() — re-renders the wrong elem… client/src/pages/features/configs/CreateConfigura…:115
  • info [MINED056] React Key As Index: key={index} in map() — re-renders the wrong elem… client/src/pages/features/audits/AuditLogsList.jsx:195
  • info [MINED053] Placeholder Default Username: [email protected] / [email protected] / a… client/src/App.jsx:3
View all fragile runtime findings →
Commented-out code 1 finding
What it is: Lines of source that were intentionally disabled but never deleted.
Why it matters: Git already remembers history — commented code rots, becomes wrong, and adds noise to diffs.
How AI causes it: AI sometimes comments out broken code instead of fixing it. Reviewers approve out of inertia.
Fix approach: Delete. Trust `git log`. If you really need to remember, save it in a notes file under `docs/`.
1 matching finding on this repo
  • info Commented-code block (7 lines) in backendmongo/src/utils/nodemailer.js:8
View all commented-out code findings →
Config drift 26 findings
What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.
Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.
How AI causes it: AI writes new config from memory rather than reading the existing source.
Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.
12 matching findings on this repo
  • medium No CI/CD configuration found
  • critical Admin endpoint without auth: PUT /admin/config-headers/update/:id backend/src/routes/configHeaders.routes.js:66
  • critical Admin endpoint without auth: POST /admin/config-headers/create backend/src/routes/configHeaders.routes.js:36
  • critical Admin endpoint without auth: PUT /admin/configurations/update/:id backend/src/routes/configs.routes.js:59
  • critical Admin endpoint without auth: POST /admin/configurations/create backend/src/routes/configs.routes.js:34
  • low File has no detected symbols: client/vite.config.js
  • low File has no detected symbols: client/eslint.config.js
  • low File has no detected symbols: client/src/tailwind_custom_screens_config.js
  • low File has no detected symbols: client/src/tailwind.config.js
  • low File has no detected symbols: client/src/postcss.config.js
  • low File has no detected symbols: client/src/tailwind_css_config.js
  • low File has no detected symbols: backendmongo/src/models/Configuration.js
View all config drift findings →
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.