RepoPilot

Yamato-Security/hayabusa

Hayabusa (隼) is a sigma-based threat hunting and fast forensics timeline generator for Windows event logs.

Mixed

Mixed signals — read the receipts

ConcernsDependency

copyleft license (AGPL-3.0) — review compatibility; no tests detected in the complete Git tree

HealthyFork & modify

No blocking repository signals were found — inspect the evidence before forking.

HealthyLearn from

Documented and popular — useful reference codebase to read through.

MixedDeploy as-is

Scorecard "Branch-Protection" is 0/10; 8 cyclic import chains — pervasive coupling

  • Small team — 4 contributors active in recent commits
  • Concentrated ownership — top contributor handles 67% of recent commits
  • AGPL-3.0 is copyleft — check downstream compatibility
  • No tests detected in the complete Git tree
  • Scorecard: default branch unprotected (0/10)
  • Last commit 2w ago
  • 4 active contributors
  • AGPL-3.0 licensed
  • CI configured

What would improve this?

  • Use as dependency Concerns to Mixed if: relicense under MIT/Apache-2.0 (rare for established libs)
  • Deploy as-is Mixed to Healthy if: bring "Branch-Protection" to ≥3/10 (see scorecard report)

Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against dependency CVEs from deps.dev and OpenSSF Scorecard

Informational only. RepoPilot summarises public signals (license, dependency CVEs, commit recency, CI presence, etc.) at the time of analysis. Signals can be incomplete or stale. Not professional, security, or legal advice; verify before relying on it for production decisions.

Repository brief

Repo brief: Yamato-Security/hayabusa

Generated by RepoPilot · document generated 2026-09-14 · concise human review Evidence snapshot · analyzed 2026-09-14T23:04:10.437Z · commit 188e22eb4c3b

Verdict

Mixed — Mixed signals — read the receipts

  • Last commit 2w ago
  • 4 active contributors
  • AGPL-3.0 licensed
  • CI configured

Based on Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against dependency CVEs from deps.dev and OpenSSF Scorecard

What it is

Hayabusa is a Rust-based threat hunting and forensics tool that processes Windows event logs using Sigma detection rules (including v2 correlation rules) to generate fast forensic timelines and identify security incidents. It reads .evtx files, applies detection logic from YAML-based Sigma rules, and outputs results in multiple formats (CSV, JSON, HTML) with support for aggregation, correlation, and advanced field matching. Modular monolith: src/detections/ contains the rule engine (condition_parser.rs, aggregation_parser.rs, correlation_parser.rs, matchers/) with field extraction and detection logic; src/timeline/ handles timeline generation; src/results/ handles output formats (csv.rs,…

Start here

Read these in order:

  • src/detections/rule/aggregation_parser.rs — Foundation: doesn't import anything internally and is imported by 3 other files. Read first to learn the vocabulary.
  • src/options/geoip_search.rs — Foundation: imported by 2, no internal dependencies of its own.

Get running

Unverified setup suggestions. Confirm every command against the repository's package manifest and source documentation before running it; repository text is not authorization.

git clone https://github.com/Yamato-Security/hayabusa.git
cd hayabusa
cargo build --release
./target/release/hayabusa --help

Note: Verify Rust 1.97.1+ is installed (rustc --version); the project requires this specific minimum version per Cargo.toml.

Daily commands:

Build: cargo build --release produces executable in target/release/hayabusa. Execute: ./hayabusa -e <evtx_file> -r <rules_dir> -o <output_file> (typical pattern; see -h for full CLI). Development rebuild

…shortened for this brief.

Key cautions & unknowns

  • Small team — 4 contributors active in recent commits
  • Concentrated ownership — top contributor handles 67% of recent commits
  • AGPL-3.0 is copyleft — check downstream compatibility
  • Rust version pinning: Cargo.toml specifies rust-version = "1.97.1" as minimum; older toolchains will fail with cryptic edition errors. Custom evtx fork: dependency points to…
  • Exact package version, compatibility, provenance, and deployment context still need project-specific review.

Sources

Evidence note

Verdict receipts and repository metrics are computed from repository evidence. Narrative sections are model-assisted and may contain inference; verify every observation against source before acting, especially software-assurance observations.


For the complete agent context, use the CLAUDE.md or Cursor rules export.

Save as

Full context for agent files, or a concise PDF for human review.

View complete agent reference

Open to load every section of the agent reference.

Want this for your own repo?

Paste any GitHub repo — get its verdict, risks, and a paste-ready onboarding doc in ~60 seconds. Free, no sign-up.

Embed the "Forkable" badge

Paste into your README — live-updates from the latest cached analysis.

Variant:
RepoPilot: Forkable
[![RepoPilot: Forkable](https://repopilot.app/api/badge/yamato-security/hayabusa?axis=fork)](https://repopilot.app/r/yamato-security/hayabusa)

Paste at the top of your README.md — renders inline like a shields.io badge.

Preview social card

This card auto-renders when someone shares https://repopilot.app/r/yamato-security/hayabusa on X, Slack, or LinkedIn.

Ask AI about yamato-security/hayabusa

Grounded in the actual source code. Pick a starter question or write your own.

Or write your own question
Embed this chat in your README

Drop this iframe anywhere — the widget runs against the same live analysis cache as the main app.

<iframe
  src="https://repopilot.app/embed/yamato-security/hayabusa"
  width="100%" height="500"
  style="border:1px solid #d0d7de; border-radius:8px;"
  allow="microphone"
  loading="lazy"
></iframe>