0
/ 100
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.
A low grade is a to-do list, not a judgment of your code
Most gaps here are documentation, tests, and setup, not the code itself. Closing your top 3 gaps alone would lift this repo to A (90).
See your top fixesTop fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Set scripts.test in package.json to your actual test command, e.g. "vitest" or "jest".
- 2CI/CD14pt
Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 3CI/CD14pt
Add `pull_request:` to the workflow `on:` triggers.
- 4CI/CD14pt
Add a lint step to catch style issues automatically.
Working through the fixes? Let every push regrade itself.
The free GitHub App rescans this repo on every push and posts the grade as a commit check, so the score climbs without coming back to rescan by hand.
Scorecard
Every check, grouped by category and sorted worst-first
Documentation
68
No license detected.
→ Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.
CONTRIBUTING guide found.
README is present.
README documents how to install the project.
Engineering
55
Test files detected (scripts/tests).
CI is configured (.github/workflows/auto-pr-hearth-drafts.yml).
Lockfile present (package-lock.json). Installs are reproducible.
Linter or formatter configured (eslint.config.mjs).
Issue or PR templates present.
Project health
100
Dependency manifest found (package.json).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 37Forks
- 0Releases
Community
- -Community health
- -authors own >50% of commits
- 325Watchers
Responsiveness
- <1hMedian issue response
- 4hMedian PR merge time
- 0Open issues
Repository files30 root entries
- .githubGood: CI is configured (.github/workflows/auto-pr-hearth-drafts.yml).Good: Issue or PR templates present.
- Alchemy
- Assets
- database
- docs
- Embers
- Flames
- Forge
- KeepersGood: 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
- scriptsGood: Test files detected (scripts/tests).
- src
- .gitignoreGood: .gitignore present.
- actors.html
- CNAME
- coverage-heatmap.html
- coverage.html
- eslint.config.mjsGood: Linter or formatter configured (eslint.config.mjs).
- home.html
- hunts-data.js
- index.html
- package-lock.jsonGood: Lockfile present (package-lock.json). Installs are reproducible.
- package.jsonGood: Dependency manifest found (package.json).
- pyproject.toml
- README.mdGood: 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
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/thorcollective/hearth)