Chetan
Chetan 's work was selected for the XERJ Corpus Hub, the open reference memory AI coding agents search before they write code. When an agent meets the same problem, it gets this implementation back as a worked example, with the author and the repository attached.
Totals across every corpus @Chetan786-pixel appears in; a commit selected for two corpora counts once. Files and lines count the selected commits; each corpus indexes the whole repository at its pinned commit.
What an agent can do with the SecureFlow corpus
GauravKarakoti/SecureFlow: GauravKarakoti/SecureFlow (TypeScript)
- Reuse a worked example: the commit “add ElevenLabs client, env config and Redis audio cache” (7 files · TypeScript).
- Answer from SecureFlow's real TypeScript source instead of memory (Security and vulnerabilities).
- Where does SecureFlow handle “add ElevenLabs client, env config and Redis audio cache”?
- What does src/lib do in SecureFlow?
Search the GitHub repository GauravKarakoti/SecureFlow with XERJ (https://hub.xerj.org/corpus/gauravkarakoti--secureflow). 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/GauravKarakoti/SecureFlow SecureFlow && git -C SecureFlow checkout 28a591156fddf7b3610718c0e0cb5d80492e2303 3. Start a local node and leave it running: xerj --insecure --data-dir ./xerj-data 4. xerj autoindex ./SecureFlow --url http://127.0.0.1:9200 --prefix secureflow --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: MIT. Keep the copyright notice and credit the authors.
corpus gauravkarakoti--secureflow · Security and vulnerabilities
Related corpora: attack-flow, bandit-plugins, capa-rules, exploit-pocs-2026
Code security audit with XERJ · Case study: reference coding for agents
Selected work
GauravKarakoti/SecureFlow
The corpus is the whole repository at the pinned commit, not only the files of the selected commit.
Not installable yet: this corpus is not in the hub registry until its licence review passes, so xerj corpus add and xerj ask cannot fetch it. It becomes installable when this card says live in the hub.
Sign in with GitHub or Hugging Face to see more: every selected commit in full (commit date, every folder, licence review state, pin) and the pack builds of each corpus.
[](https://hub.xerj.org/contributors/Chetan786-pixel)
Included with the author's permission (email, 2026-10-19), under each repository's own licence, with attribution. Want it removed? Reply to the email or open an issue on xerj-org/xerj.