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
74 of your 168 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.
Upstream (GitHub) caused delay on this scan — not Repobility.
  • GitHub API rate-limited (HTTP 403) — preflight skipped, fell back to direct git clone.
  • Clone from GitHub took 160.55s for a 409.1 MB repo slow.
  • Repobility's analysis ran in 66.06s after the clone landed.

elastic/elasticsearch

https://github.com/elastic/elasticsearch · scanned 2026-06-05 07:40 UTC (5 days, 22 hours ago) · 10 languages

2776 raw signals (132 security + 2644 graph) 11/13 scanners ran 100th percentile · Java · huge (>500K LoC) System graph score 66 (higher by 19)

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

Complete repo analysis

Last scanned 5 days, 22 hours ago · v2 · 1339 actionable findings from 2 signal sources. 114 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
70.2
/100
Security checks
75
67 findings
System graph
66
100.0% cov · 1272 findings
Critical
86
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 40.0 0.15 6.00
security_score 100.0 0.25 25.00
testing_score 100.0 0.20 20.00
documentation_score 91.0 0.15 13.65
practices_score 77.0 0.15 11.55
code_quality 80.0 0.10 8.00
Overall 1.00 84.2
security_score may be inflated — optional security scanners were skipped on this fast scan
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 86 High 135 Medium 39 Low 620 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 67 System graph 1272 Crowd 0 Layer: Cicd 22 Software 20 Quality 630 Security 636 Api 1 Network 13 Hardware 16 Frontend 1

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.

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
  • high Insecure pattern 'eval_used' in x-pack/plugin/security/qa/multi-cluster/src/jav… x-pack/plugin/security/qa/multi-cluster/src/javaR…:322
  • low Very large file: modules/legacy-geo/src/test/java/org/elasticsearch/legacygeo/G…
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 (6 lines) in dev-tools/prepare_release_update_documentatio…
View all commented-out code findings →
Config drift 12 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
  • critical Possible secret in libs/ssl-config/src/main/java/org/elasticsearch/common/ssl/S… libs/ssl-config/src/main/java/org/elasticsearch/c…:159
  • critical Possible secret in libs/ssl-config/src/main/java/org/elasticsearch/common/ssl/S… libs/ssl-config/src/main/java/org/elasticsearch/c…:59
  • critical Insecure pattern 'private_key_in_repo' in libs/ssl-config/src/main/java/org/ela… libs/ssl-config/src/main/java/org/elasticsearch/c…:63
  • critical Possible secret in libs/ssl-config/src/main/java/org/elasticsearch/common/ssl/S… libs/ssl-config/src/main/java/org/elasticsearch/c…:219
  • low Very large file: qa/vector/src/main/java/org/elasticsearch/test/knn/TestConfigu…
  • low Very large file: x-pack/plugin/security/cli/src/main/java/org/elasticsearch/xpa…
  • low Very large file: x-pack/plugin/transform/src/main/java/org/elasticsearch/xpack/…
  • low Very large file: x-pack/plugin/core/src/test/java/org/elasticsearch/xpack/core/…
  • low Very large file: x-pack/plugin/core/src/main/java/org/elasticsearch/xpack/core/…
  • low Very large file: x-pack/plugin/core/src/main/java/org/elasticsearch/xpack/core/…
  • low Very large file: x-pack/plugin/core/src/main/java/org/elasticsearch/xpack/core/…
  • low Very large file: libs/ssl-config/src/test/java/org/elasticsearch/common/ssl/Ssl…
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/d4be5fa3-841a-4364-9c0a-d77b4a437a6b/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/d4be5fa3-841a-4364-9c0a-d77b4a437a6b/

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.