splunk-security-content
reference corpus · status live · domain SEC (Security and vulnerabilities) · lane A · refresh pinned · tags GLOBAL · DETECTION-RULES · SIEM · ANALYTIC-STORIES · MITRE-ATTACK
What an agent uses it for
security
curl -fsSLO https://raw.githubusercontent.com/xerj-org/xerj/corpus-hub/tools/xerj-code/hub/splunk-security-content.jsonxerj corpus add --from ./splunk-security-content.jsonxerj corpus index splunk-security-content then xerj code splunk-security-content "your question"Needs the xerj CLI and a local node running; the copy prompt covers both, checks each step, and shows how to stop only the node you started. No shell: the MCP tool xerj_code_search with corpus: "splunk-security-content", once the corpus is indexed on the node.
Sources and pins
| source | pin | licence | size | review note |
|---|---|---|---|---|
| security_content | c653da7c11fc | Apache-2.0 | 38.3 MB / 4,282 files | Decoded LICENSE = canonical Apache-2.0 (11357B, byte-identical to the reference text). Default branch is 'develop'; 313MB history: clone --depth 1. |
38.3 MB across 4,282 files. Added 2026-10-13.
Rights
Apache-2.0. Redistribution permitted with attribution per the licence review. The review block records a human opening each licence file at the pin. Detector output is a hint, never the verdict.
Retrieval spot-check (G7)
Not yet spot-checked. Queries are pre-registered in the registry before grading.