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

openmrs/openmrs-core

https://github.com/openmrs/openmrs-core.git · scanned 2026-05-16 10:58 UTC (1 day, 10 hours ago) · 10 languages

318 findings (30 legacy + 288 scanner) 1/10 scanners ran 0th percentile · Java · medium (20-100K LoC) Scanner says 66 (lower by 6)

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

Complete repo analysis

Last scanned 1 day, 10 hours ago · v3 · 119 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
69.4
/100
Repobility
73
23 legacy
9-layer
66
100.0% cov · 96 gaps
Critical
21
click to filter
Agents
6
0 votes
Crowd
0
reported
{# ── 2026-05-17 R27 #5: score breakdown panel ────────────────────── Surfaces the score_breakdown JSON that's been silently stored on Repository for months. Turns hidden math into a trust signal. #}
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 21 High 7 Medium 32 Low 52 Source: Legacy 23 9-layer 96 Crowd 0 Layer: Security 27 Cicd 33 Quality 39 Software 8 Api 1 Frontend 5 Network 2 Hardware 4

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 12 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
  • medium Duplicated implementation block across source files api/src/main/java/org/openmrs/ConceptSet.java:69
  • medium Duplicated implementation block across source files api/src/main/java/org/openmrs/ConceptNumeric.java:72
  • medium Duplicated implementation block across source files api/src/main/java/org/openmrs/ConceptNameTag.java:137
  • medium Duplicated implementation block across source files api/src/main/java/org/openmrs/ConceptNameTag.java:73
  • medium Duplicated implementation block across source files api/src/main/java/org/openmrs/ConceptNameTag.java:65
  • medium Duplicated implementation block across source files api/src/main/java/org/openmrs/ConceptNameTag.java:63
  • medium Duplicated implementation block across source files api/src/main/java/org/openmrs/ConceptName.java:123
  • medium Duplicated implementation block across source files api/src/main/java/org/openmrs/ConceptName.java:117
  • medium Duplicated implementation block across source files api/src/main/java/org/openmrs/ConceptDescription.…:71
  • medium Duplicated implementation block across source files api/src/main/java/org/openmrs/ConceptAnswer.java:74
  • medium Duplicated implementation block across source files api/src/main/java/org/openmrs/BaseOpenmrsMetadata…:57
  • medium Duplicated implementation block across source files api/src/main/java/org/openmrs/BaseCustomizableMet…:23
View all fragile runtime findings →
Legacy markers 2 findings
What it is: TODO, FIXME, XXX, HACK comments. Often indicate a known-broken path the author meant to fix.
Why it matters: Each marker is an unfinished thought. Production code shouldn't ship with debt that's documented but not tracked.
How AI causes it: AI mirrors the style of the codebase, so existing TODOs propagate into new code.
Fix approach: Convert each into a ticket. Delete the comment when the ticket lands. Use a pre-commit hook to block new TODOs without an issue link.
2 matching findings on this repo
  • low Legacy-named symbol `yearsOld` in webapp/src/main/webapp/WEB-INF/view/scripts/j…
  • low Legacy-named symbol `drag_copy` in webapp/src/main/webapp/WEB-INF/view/scripts/…
View all legacy markers 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 (10 lines) in webapp/src/main/webapp/WEB-INF/view/scripts/…
View all commented-out code findings →
{# ── 2026-05-17 Round 14: AI-agent bridge footer ────────────────────── Discoverability: the /agents/voting/ guide + MCP manifest exist but aren't linked from anywhere users actually land. Small, opt-in footer. #}
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/beef9e59-2b65-4ca8-b71d-75f2aef97c23/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/beef9e59-2b65-4ca8-b71d-75f2aef97c23/

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.