sigma-cli
v4.0.0 open-sourceThe section your link pointed to isn't on sigma-cli's page any more, so we've brought you to the top.
CLI for managing, listing, and converting Sigma rules into SIEMSIEMSecurity information and event management, collecting logs from many systems and correlating events to find suspicious activity. Analysts use it to investigate alerts and incidents. query languages using the pySigma library.
sigma convert -t splunk -p sysmon --policy safe sigma/rules/windows/process_creation
sigma convert -t splunk -p sysmon --policy trusted --enable-template-vars sigma/rules/windows/
sigma check --policy safe --allow-external-sources sigma/rules/windows/process_creation/
sigma convert -t esql -p ecs_windows --output-dir translated/ --output-filename-template "{path}/{stem}.esql" rules/
sigma convert -t esql -p ecs_windows --output-dir translated/ --output-filename-template "{stem}-{index}.esql" rules/
brew install sigma-cli
sigma pysigma update-cache --url https://your-internal-mirror.example.com/sigma-cache.json
sigma convert -t splunk -p my_pipeline.yml --enable-template-vars --template-vars-path /opt/sigma/vars my_rules/
sigma analyze fields --group <field> <path>
sigma analyze <path>
sigma mitre analyze --level high --status stable rules/
sigma convert --verbose -t splunk -p my_pipeline.yml rules/
sigma convert -t elastic-lucene --pipeline ./pipelines/ rules/windows/
sigma analyze logsources rules/
sigma-cli -h
sigma-plugin install --force-install some-incompatible-plugin
sigma-plugin details some-plugin-name
sigma-cli version
sigma plugin list
Summary
sigma-cli is an open-source command-line tool that converts Sigma detection rules into queries for specific SIEM and log-analysis backends, built on the pySigma library. You install it with pipx, pip, or Homebrew, or run it from source via Poetry, and use it as the sigma command to convert, list, and analyze rules against backend plugins like Splunk. It's aimed at detection engineers and SOCSOCA security operations center, the team or function that monitors threats, investigates alerts and coordinates incident response. Its work can be internal, outsourced or shared. teams who maintain Sigma rule sets and need to deploy them across different query languages rather than write backend-specific queries by hand; commands for analyzing field coverage and mapping rules to MITRE ATT&CKMITRE ATT&CKA publicly maintained knowledge base of adversary tactics and techniques observed in real attacks, maintained by MITRE. Cyber tools use it as a common taxonomy to classify, map, and communicate threat behavior. support auditing rule sets before deployment. The README frames it as the official CLI companion to the Sigma rule format itself, rather than a competing product. First committed in 2022 and still under active, frequent development, with 23 contributors and a release only 45 days old, though its own status badge still marks it pre-release.
CLI for managing, listing, and converting Sigma rules into SIEM query languages using the pySigma library.
How sigma-cli helps
How do I turn a directory of Sigma rules into queries my SIEM actually understands?
it walks the rule files through a chosen backend and pipeline and prints or writes the equivalent queries, ready to load into that system
Which Sigma rules will fail or behave unexpectedly against a given backend before I deploy them?
conversion runs with verbose output shows how each rule is processed through the pipeline, surfacing the step where a rule breaks or resolves unexpectedly
How much of MITRE ATT&CK does my current rule set actually cover?
it analyzes the rules and produces an ATT&CK Navigator layer, filterable by rule severity or status, showing which techniques have detections and which don't
Which log sources are my Sigma rules written against, and are any environments left uncovered?
it scans the rule set and lists the log sources referenced, letting you check that against what your environment actually generates before rollout
How do I keep converted queries organized in a rule repository instead of one big output blob?
it can write each converted rule to its own file, mirroring the source directory layout or using a filename template, including an index suffix when one rule yields multiple queries
Languages
Command line
No command matches.
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for sigma-cli, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail sigma-cli puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Website history
sigmahq.io, every changeSigmaHQ's home page and 7 more pages as they looked each month from October 2023 to October 2026: 27 renders, 9 changes of tagline or palette. Step through them, play them, or put any two months side by side.
Website history is included with Researcher and Business.
See plans → Already subscribed? Sign in →← → or h l a month · Shift a year · [ ] previous / next change · Space play · 1 2 3 page · T whole page · C compare · F full size
← → or h l the right month · Shift the left · S swap · W wipe · T whole page · Esc back
Rebranding timeline
Dates bound when a change appeared between captures. Possible rebrands are AI suggestions; a redesign alone does not establish a rebrand.
Releases
19 entries
No entries match these filters.
- October 20261
- July 20262
- April 20263
- November 20251
- April 20251
- January 20251
- June 20241
- January 20241
- November 20231
- August 20231
- May 20231
- April 20231
- February 20232
- October 20221
- August 20221
Project health
Issue, contributor and maintainer activity in SigmaHQ/sigma-cli, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 9 +3 vs prior 12 months
- Maintainers 2 +1 joined · −1 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed 75% of issues opened, last 12 months
- Median time to close 224 days first maintainer reply 21 hours
- Open backlog 0 of 35 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 0
- Contributors / month 1
- Commits / month 1
- Stars 211
- other 100%
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
Libraries its release ships
What its latest release locks, checked against known advisories.None of its release's images build from a lockfile we can read.
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.