OpenRisk
Unified Risk & Threat Intelligence Management Platform
What XERJ indexed
Snapshot
The whole repository at commit dc188eb0dd (2026-10-20). master is 267 commits ahead.
Selected work

“bind role routes to the caller's tenant (GHSA-6m8w-33j5-ff68)”. 4 files, 537 lines in backend.
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-27. Agents read it for how it works, not to copy it. Answers name the repo, the commit and the file:line.
selected for the XERJ Corpus Hublicence clearedsuggested use: approach only
cybersecuritydigital-forensicsdigital-forensics-analysisfreesoftwareincidence-response-plansecurity-toolscyber-threat-intelligenecegrc
Example questions
- How does OpenRisk implement cybersecurity?
- Where does OpenRisk handle “bind role routes to the caller's tenant (GHSA-6m8w-33j5-ff68)”?
- What does backend do in OpenRisk?
Inside the indexed corpus
- Languages by size: Go 61.8%, TypeScript 34%, Shell 1.5%, JavaScript 1.3%, CSS 0.8%.
- On GitHub since 2025-10-29, last push 2026-10-30, 2,558 commits on master.
- The pin is 267 commits behind master; the corpus answers from the pinned code, not the newest.
Licence on GitHub and in the corpus
GitHub reported AGPL-3.0 for opendefender/OpenRisk on 2026-10-31, but the LICENSE file at commit dc188eb0dd was reviewed as NOASSERTION. The corpus is the pinned commit, so answers from it follow NOASSERTION.
Contributors
Alex DEMBELE (@alex-dembele) has 1 selected repository on the hub.
Using XERJ with OpenRisk
- Batch lookup CVE and GHSA IDs offline in one query OpenRisk is tagged cybersecurity on GitHub.
- Best MCP servers for local code search in 2026, compared
- Best grep alternative for AI coding agents (2026)
- Ask questions about a GitHub repo without cloning it
The prompt
Paste it into your AI agent. It clones opendefender/OpenRisk at the pinned commit and indexes it on your machine.
Search the GitHub repository opendefender/OpenRisk with XERJ (https://hub.xerj.org/corpus/opendefender--openrisk). 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/opendefender/OpenRisk OpenRisk && git -C OpenRisk checkout dc188eb0dd1c3fcfcc51b9a0e38fba564d2af817 3. Start a local node and leave it running: xerj --insecure --data-dir ./xerj-data 4. xerj autoindex ./OpenRisk --url http://127.0.0.1:9200 --prefix openrisk --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: check the LICENSE file. Read it for the approach only, do not copy code.
Related
Alex DEMBELESecurity and vulnerabilities corporagosec-rulessmallstep-certificatescalderalunalully/lunaticmahialjaber/MiCodeKynSec/CommitGuard
Stats: GitHub API, fetched 2026-10-31. Selected work and consent: the XERJ registry.