git404hub

what is sigwood fr?

helixmap/sigwood — explained in plain English

Analysis updated 2026-05-18

97PythonAudience · ops devopsComplexity · 3/5LicenseSetup · easy

tl;dr

A local, no-server command-line tool that hunts for suspicious activity in Zeek, Pi-hole, syslog, and CloudTrail logs you already have.

vibe map

mindmap
  root((sigwood))
    What it does
      Hunts logs for threats
      Names detection technique
      Runs fully local
    Tech stack
      Python
      Zeek
      CloudTrail
    Use cases
      Detect beaconing
      Spot suspicious DNS
      Flag rare syslog events
    Audience
      Self-hosters
      Blue team analysts
    Setup
      pipx install sigwood
      Point at log directory

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

what do people make with this?

VIBE 1

Scan self-hosted server logs for signs of compromise without deploying a SIEM

VIBE 2

Detect beaconing, suspicious DNS, or port scans in Zeek network logs

VIBE 3

Spot rare or unusual events in syslog or the systemd journal

VIBE 4

Flag anomalous per-user activity in AWS CloudTrail logs

what's the stack?

PythonZeekCloudTrailHDBSCANdrain3

how it stacks up fr

helixmap/sigwoodchenj-freedom/bilibili_downloadergianluca-improta/cinekive
Stars979797
LanguagePythonPythonPython
Setup difficultyeasymoderatemoderate
Complexity3/52/53/5
Audienceops devopsgeneralgeneral

Figures from each repo's GitHub metadata at analysis time.

how do i run it?

Difficulty · easy time til it works · 5min

Install with pipx or pip, no config, database, or account required to run against existing logs.

Use freely for any purpose, including commercial use, as long as you keep the copyright notice.

in plain english

sigwood is a command-line tool for threat hunting through logs you already have, built for people who self-host and want to check their own systems for signs of compromise. You point it at a folder of logs from Zeek, Pi-hole, syslog, or CloudTrail, and it profiles what is in them, then runs a set of detectors looking for things like periodic network callbacks, suspicious DNS lookups, port scans, rare syslog events, unusually long connections, and unusual CloudTrail activity. The project is explicit about what it is not: not a SIEM, not an agent, not a magic black box. There is nothing to deploy, no database, no background service, and no account to create. You install it, point it at a directory of logs sitting on disk, and read the output, and your logs never leave your machine. Each finding names the specific technique behind it, such as an FFT analysis of connection timing or clustering over DNS query behavior, so you can understand why something was flagged rather than just trusting a score. Before running the full set of detectors, you can use a digest command to get a quick factual summary of a log file, like its time span and top talkers, so you know where to focus. There is also a graph command that turns activity into a visual HTML report. The tool ships with a small synthetic set of example logs, including one simulated compromised host, so you can try it out before pointing it at real data. It filters out known-harmless infrastructure by default before analysis, and reports how much noise it removed. Output can be produced as readable text, HTML, or PDF reports, as JSON for scripting, as CSV for triage lists, or as an animated graph. It requires Python 3.11 or newer and can be installed with pipx or pip. The project describes itself as early and pre-1.0, though its six detectors are covered by tests. It is released under the MIT license.

prompts (copy fr)

prompt 1
Run sigwood against my /var/log directory and explain the findings.
prompt 2
Help me generate the synthetic demo corpus and walk through a sample hunt.
prompt 3
Explain how sigwood's beacon detector uses FFT over connection timing.
prompt 4
Show me how to export sigwood's findings as an HTML report.

Frequently asked questions

what is sigwood fr?

A local, no-server command-line tool that hunts for suspicious activity in Zeek, Pi-hole, syslog, and CloudTrail logs you already have.

What language is sigwood written in?

Mainly Python. The stack also includes Python, Zeek, CloudTrail.

What license does sigwood use?

Use freely for any purpose, including commercial use, as long as you keep the copyright notice.

How hard is sigwood to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is sigwood for?

Mainly ops devops.

peek the repo → explain another one

This repo across BitVibe Labs

double-check against the repo, no cap.