mthcht/awesome-lists

0

/ 100

Documentation76
Engineering20
Health100
YARA1,668MIT1d ago
Grade a repo

Strong community interest, but tests, CI, or docs need work.

Awesome Security lists for SOC/CERT/CTI

Documentation

76

Contributing guide5pt0

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.

README12pt85

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

20

Tests18pt0

No tests detected anywhere in the repository.

→ Add automated tests. They prove the code works and give contributors confidence to make changes.

Linting and formatting5pt0

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.

Issue and PR templates6pt0

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.

CI/CD14pt40

CI is configured (.github/workflows/build-tor-history.yml).

Reproducibility6pt70

Lockfile present (Lists/DYNDNS/dyn-dns-list-mthcht_corrected/scripts/package-lock.json). Installs are reproducible.

Project health

100

Dependency manifest6pt100

Dependency manifest found (Lists/DYNDNS/dyn-dns-list-mthcht_corrected/scripts/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)
  • 194
    Forks
  • 1
    Releaseslatest 1y ago

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 1,668
    Watchers

Responsiveness

  • 9h
    Median issue response
  • 10h
    Median PR merge time
  • 22
    Open issues
Repository files6 root entries
  • _utils
  • .github
    Good: CI is configured (.github/workflows/build-tor-history.yml).
  • Lists
    Good: Lockfile present (Lists/DYNDNS/dyn-dns-list-mthcht_corrected/scripts/package-lock.json). Installs are reproducible.
    Good: Dependency manifest found (Lists/DYNDNS/dyn-dns-list-mthcht_corrected/scripts/package.json).
  • .gitignore
    Good: .gitignore present.
  • LICENSE
    Good: Licensed under MIT.
  • 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.