ModSecurity
ModSecurity is an open source, cross platform web application firewall (WAF) engine for Apache, IIS and Nginx. It has a robust event-based programming language which provides protection from a range of attacks against web applications and allows for HTTP traffic monitoring, logging and real-time analysis
What XERJ indexed
Snapshot
The whole repository at commit c70a4a7a71 (2026-09-30). v3/master is 64 commits ahead.
Selected work

“make configured resp CT lowercase”. 3 files, 1,381 lines in src/parser, test.
Licence
The repository
LICENSE file checked at the pinned commit; the author agreed to inclusion.
The XERJ corpus
The author agreed by email on 2026-10-06. Same terms as the repository. Answers name the repo, the commit and the file:line.
selected for the XERJ Corpus Hublicence clearedsuggested use: adapt with attribution
modsecuritynginxapacheapache2waf
Example questions
- How does ModSecurity implement nginx?
- Where does ModSecurity handle “make configured resp CT lowercase”?
- What does src/parser do in ModSecurity?
Inside the indexed corpus
- Languages by size: C++ 94.9%, M4 2.9%, Makefile 0.7%, CMake 0.5%, Shell 0.3%.
- On GitHub since 2011-02-02, last push 2026-10-31, 4,043 commits on v3/master.
- The pin is 64 commits behind v3/master; the corpus answers from the pinned code, not the newest.
Licence on GitHub and in the corpus
GitHub reported Apache-2.0 for owasp-modsecurity/ModSecurity on 2026-10-31, and the LICENSE file at commit c70a4a7a71 was reviewed as Apache-2.0. They match, so answers from this corpus carry the same terms as the live repository.
Contributors
Ervin Hegedus (@airween) has 1 selected repository on the hub.
Using XERJ with ModSecurity
- Batch lookup CVE and GHSA IDs offline in one query The hub files it under Security and vulnerabilities.
- Ask questions about a GitHub repo without cloning it
- Index a reference library for a coding agent
- ripgrep vs a code index for coding agents: 30 tasks
The prompt
Paste it into your AI agent. It clones owasp-modsecurity/ModSecurity at the pinned commit and indexes it on your machine.
Search the GitHub repository owasp-modsecurity/ModSecurity with XERJ (https://hub.xerj.org/corpus/owasp-modsecurity--modsecurity). Run these in a shell, in order, and check each result before the next: 1. xerj --help (success: it prints usage). If xerj is missing: curl -fsSL https://xerj.org/get | sh 2. git clone https://github.com/owasp-modsecurity/ModSecurity ModSecurity && git -C ModSecurity checkout c70a4a7a71a860647b4b17c1b402c06bc6802bd6 3. Start a local node and leave it running: xerj --insecure --data-dir ./xerj-data 4. xerj autoindex ./ModSecurity --url http://127.0.0.1:9200 --prefix modsecurity --progress plain 5. xerj autoindex map --url http://127.0.0.1:9200 Then answer my question from the indexed files and cite the ax_path of every hit. Query syntax: https://xerj.org/llms.txt Licence: Apache-2.0. Keep the copyright notice and credit the authors.
Related
Ervin HegedusSecurity and vulnerabilities corporabookkeeperparquet-formaticebergppomes/mod_image_resizeallinurl/goaccessFerrisMind/shadcn-rs
Stats: GitHub API, fetched 2026-10-31. Selected work and consent: the XERJ registry.