Popular for its size, but the engineering basics lag behind the interest.

A community-driven repository for threat hunting ideas, methodologies, and research that serves as a central gathering place for hunters to share knowledge, collaborate on techniques, and advance the field of threat hunting.

Documentation

68

License6pt0

No license detected.

Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.

Contributing guide5pt72

CONTRIBUTING guide found.

README12pt85

README is present.

Install and run instructions9pt90

README documents how to install the project.

Engineering

55

Tests18pt35

Test files detected (scripts/tests).

CI/CD14pt40

CI is configured (.github/workflows/auto-pr-hearth-drafts.yml).

Reproducibility6pt70

Lockfile present (package-lock.json). Installs are reproducible.

Linting and formatting5pt100

Linter or formatter configured (eslint.config.mjs).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (package.json).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • Commits (30d / 90d)
  • 37
    Forks
  • 0
    Releases

Community

  • Community health
  • authors own >50% of commits
  • 325
    Watchers

Responsiveness

  • <1h
    Median issue response
  • 4h
    Median PR merge time
  • 0
    Open issues
Repository files30 root entries
  • .github
    Good: CI is configured (.github/workflows/auto-pr-hearth-drafts.yml).
    Good: Issue or PR templates present.
  • Alchemy
  • Assets
  • database
  • docs
  • Embers
  • Flames
  • Forge
  • Keepers
    Good: CONTRIBUTING guide found.
    Issue: CONTRIBUTING guide contents could not be read (−28 pts vs a readable file).Fix: Move the file to the repo root or docs/CONTRIBUTING.md so its setup, style, test, and PR sections can be graded.
  • Kindling
  • public
  • scripts
    Good: Test files detected (scripts/tests).
  • src
  • .gitignore
    Good: .gitignore present.
  • actors.html
  • CNAME
  • coverage-heatmap.html
  • coverage.html
  • eslint.config.mjs
    Good: Linter or formatter configured (eslint.config.mjs).
  • home.html
  • hunts-data.js
  • index.html
  • package-lock.json
    Good: Lockfile present (package-lock.json). Installs are reproducible.
  • package.json
    Good: Dependency manifest found (package.json).
  • pyproject.toml
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.
    Good: README links to a live demo or deployed app.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • requirements.txt
  • submit.html
  • tsconfig.json
  • vite.config.ts