infosecstreams/infosecstreams.github.io

0

/ 100

Documentation44
Engineering24
Health68
HTML256Apache-2.01d ago
Grade a repo

Getting noticed, but rough fundamentals could turn visitors away.

A (hopefully) actively maintained activity-based-autosorted list of InfoSec Streamers

Documentation

44

Install and run instructions9pt0

No install instructions found in the README (−45 pts).

→ Add a section showing how to install dependencies.

Contributing guide5pt25

Contributing guidance is in the README, not a dedicated CONTRIBUTING.md (−20 pts).

→ Moving it to a CONTRIBUTING.md makes it easier to find and keeps the README focused. A dedicated file earns +47 pts base.

README12pt58

README is present.

License6pt100

Licensed under Apache-2.0.

Engineering

24

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.

Reproducibility6pt0

No dependency lockfile found (−70 pts).

→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.

CI/CD14pt40

CI is configured (.github/workflows/main.yaml).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

68

Dependency manifest6pt0

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.

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)
  • 108
    Forks
  • 0
    Releases

Community

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

Responsiveness

  • 2d 14h
    Median issue response
  • <1h
    Median PR merge time
  • 1
    Open issues
Repository files30 root entries
  • _includes
  • .github
    Good: CI is configured (.github/workflows/main.yaml).
    Good: Issue or PR templates present.
  • ar
  • assets
  • de
  • es
  • fr
  • hi
  • img
  • it
  • js
  • pt
  • templates
  • tr
  • zh
  • _config.yml
  • .gitignore
    Good: .gitignore present.
  • CNAME
  • crowdin.yml
  • faq.md
  • favicon.ico
  • inactive_streamers.csv
  • inactive.md
  • index.md
  • LICENSE
    Good: Licensed under Apache-2.0.
  • README.md
    Good: README is present.
    Issue: README is fairly short (−10 pts). At 400+ chars you get partial credit; 1,500+ earns the full +20 pts.Fix: Expand with a description, install steps, usage, and examples.
    Issue: README has some structure (−7 pts). 2-3 headings earns partial credit; 4+ earns the full +15 pts.Fix: Add more sections (Overview, Install, Usage, Contributing) using ## headings.
    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.
    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.
    Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
  • resources.md
  • robots.txt
  • sitemap.xml
  • streamers.csv