yuexuan521/honeypot-blocklist

0

/ 100

Documentation92
Engineering79
Health82
Python223MIT1d ago
Grade a repo

Good shape overall. A few tweaks would push it into the top tier.

HFish 蜜罐威胁情报源 | High-fidelity Threat Feed derived from HFish honeypots (SSH/HTTP/DB attacks) with automated whitelisting.

Documentation

92

Contributing guide5pt66

Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.

→ Add setup instructions, code style notes, and how to run tests.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under MIT.

Engineering

79

Linting and formatting5pt0

No linter or formatter configured.

→ Add [tool.ruff] to pyproject.toml. Ruff handles linting and formatting in one tool and replaces flake8, isort, and black.

CI/CD14pt72

CI is configured (.github/workflows/data_quality.yml).

Reproducibility6pt80

Lockfile present (tools/requirements.txt). Installs are reproducible.

Tests18pt100

Test files detected (tests).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

82

Housekeeping3pt0

No .gitignore found (−60 pts).

→ Add a .gitignore to keep build output, node_modules, and secrets out of version control.

Dependency manifest6pt93

Dependency manifest found (pyproject.toml).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • —
    Commits (30d / 90d)
  • 4
    Forks
  • 1
    Releaseslatest 3mo ago

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 223
    Watchers

Responsiveness

  • 2d 15h
    Median issue response
  • —
    Median PR merge time
  • 3
    Open issues
Repository files17 root entries
  • .github
    Good: CI is configured (.github/workflows/data_quality.yml).
    Good: Issue or PR templates present.
  • integrations
  • tests
    Good: Test files detected (tests).
  • tools
    Good: Lockfile present (tools/requirements.txt). Installs are reproducible.
    Issue: Build artifacts or local files may be committed (tools/__pycache__/client.cpython-36.pyc) (−40 pts).Fix: Remove them and add to .gitignore.
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CONTRIBUTING.md
    Issue: Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.
    Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).
    Good: Contributing guide describes the PR/review workflow.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • ip_list.txt
  • LICENSE
    Good: Licensed under MIT.
  • pyproject.toml
    Good: Dependency manifest found (pyproject.toml).
  • README_CN.md
    Good: 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.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • README_ES.md
  • README_FR.md
  • README_JP.md
  • README_TW.md
  • README.md
  • SECURITY.md
    Good: Security policy present.