Elasticsearch ES|QL
Score-based assessment (low risk, 20/100). An AI review is available in the AI review tab.
Analysis record
- Analysed
- Today 22 November 2026
- Version
- v1.0.3
- Artifact
- SHA256 6dfc7343…dc6e64
- Detail
- Full list
Is Elasticsearch ES|QL safe?
Elasticsearch ES|QL lets you write and run ES|QL queries against an Elasticsearch cluster from inside IntelliJ. It declares no special permissions and the scan found no outbound endpoints baked into the plugin, so the only network traffic is what you configure it to send to your own cluster. That traffic goes through the bundled httpclient5-5.6.jar and elasticsearch-java-9.3.4.jar libraries, which is how an Elasticsearch client is supposed to work.
All of the flagged items are inside those bundled libraries. The finding called YARA--postinstall_file_download lands on jackson-databind-2.21.2.jar, a JSON library. If that finding were real, it would mean the plugin fetches a file and writes it during install. What the library actually does is parse the JSON your cluster sends back. A second rule, YARA--postinstall_registry_modification, lands on ST4-4.3.4.jar, a templating library that has nothing to do with the Windows registry. A third, YARA--JavaDropper, lands on the Elasticsearch client itself and is a rule known for matching ordinary configuration files inside Java archives.
The scanner tripped on the packaging, not on the plugin misbehaving. JetBrains plugins ship their Java dependencies unpacked in a lib folder, so a dozen well-known libraries each get scanned and each set off rules written to catch installers. There are no findings for stolen credentials, no hidden payloads, and no sign of the plugin reading files it has no business reading. The publisher is Elastic, the same company that makes Elasticsearch.
Evidence ledger
Ranked by severity · findings with a source location link to the code viewer
Publisher Evidence
Lowelastic
Publisher identity, store signals, distribution reach, and warning signals used for context. Treat this as supporting evidence, not a clean bill of health.
12 evidence rows available.
Finding Categories
AI Security Report
AI Security Review
Evidence context: threat category none; evidence quality weak.
The supplied findings do not establish what behavior triggered the matches. A fresh analysis with the relevant code and surrounding context is needed. These findings neither establish malicious behavior nor demonstrate that the extension is safe.
Key Reasons
- Insufficient implementation context for the supplied findings
Reviewed 2026-11-10 · version 1.0.3; recommended action: reanalyze; model confidence 97%.
About This Extension
Frequently Asked Questions
Similar Extensions
Related extensions from the same publisher or marketplace