Getting noticed, but rough fundamentals could turn visitors away.
Zeek-Formatted Threat Intelligence Feeds
Documentation
78
No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).
→ Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.
README is present.
README documents how to install the project.
Licensed under MIT.
Engineering
0
No tests detected anywhere in the repository.
→ Add automated tests. They prove the code works and give contributors confidence to make changes.
No CI configuration detected in this repository.
→ If your CI lives elsewhere (a private repo that builds this one) or this project is itself a CI/CD tool, mark this check Not Applicable. Otherwise add a GitHub Actions workflow that runs tests on each push. It takes 15 minutes and reassures contributors their changes won't break things.
No linter or formatter config found.
→ Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.
No dependency lockfile found (−70 pts).
→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.
No issue or PR templates found (−100 pts).
→ Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.
Project health
59
No dependency manifest detected at root.
→ Add a manifest (package.json, pyproject.toml, Cargo.toml, go.mod, etc.) so others can install dependencies in one command.
No .gitignore found (−60 pts).
→ Add a .gitignore to keep build output, node_modules, and secrets out of version control.
Repository has a description.
Actively maintained (pushed within the last month).
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- —Commits (30d / 90d)
- 50Forks
- 0Releases
Community
- —Community health
- —authors own >50% of commits
- 401Watchers
Responsiveness
- 7hMedian issue response
- 12hMedian PR merge time
- 0Open issues
Repository files48 root entries
- __load__.zeek
- abuse-ch-ipblocklist.intel
- abuse-ch-malware.intel
- abuse-ch-threatfox-ip.intel
- abuse-ch-urlhaus.intel
- abuse-ja3-fingerprints.intel
- alienvault.intel
- Amnesty_NSO_Domains.intel
- atomspam.intel
- avanzato_c2_ip.intel
- binarydefense.intel
- censys.intel
- cert-pol.intel
- cloudzy.intel
- cobaltstrike_ips.intel
- compromised-ips.intel
- cps-collected-iocs.intel
- Cyber_Threat_Coalition_Domain_Blacklist.intel
- doh-domains.intel
- drb_ra_domain.intel
- drb_ra_ip_unverified.intel
- drb_ra_ip.intel
- ellio.intel
- fangxiao.intel
- filetransferportals.intel
- gru-aa25.intel
- illuminate_ja3.intel
- illuminate.intel
- inversion.intel
- LICENSEGood: Licensed under MIT.
- lockbit_ip.intel
- log4j_ip.intel
- main.zeek
- openphish.intel
- predict_intel.intel
- protonvpn.intel
- ragnar.intel
- README.mdGood: README is present.Good: README is well structured with multiple sections.Good: README includes screenshots or visuals. Great for first impressions.Good: README has code examples.Good: README links to a live demo or deployed app.Issue: No status badges in the README (−10 pts).Fix: Add CI/build status badges from shields.io or your CI provider to signal project health.Good: README documents how to install the project.Good: README documents how to run the project.
- rutgers.intel
- salesforce-ja3-fingerprints.intel
- sans.intel
- shadowwhisperer-malware.intel
- sip.intel
- stalkerware.intel
- stark-industries.intel
- talos.intel
- tor-exit.intel
- tweetfeed.intel