torvalds/linux

0

/ 100

Documentation70
Engineering48
Health100
C237,081Other4d ago
Grade a repo

Massive community, but the engineering fundamentals haven't kept pace with the star count.

Linux kernel source tree

Documentation

70

README12pt40

This repository is large enough that GitHub truncated the file tree. The scan is based on a partial file list, so some checks may under-report.

Contributing guide5pt72

CONTRIBUTING guide found.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Other.

Engineering

48

CI/CD14pt0

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.

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.

Reproducibility6pt70

Lockfile present (Documentation/sphinx/requirements.txt). Installs are reproducible.

Tests18pt80

Test files detected (arch/riscv/kernel/tests).

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Project health

100

Dependency manifest6pt100

Dependency manifest found (Documentation/sphinx/requirements.txt).

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

  • 3059 / 13394
    Commits (30d / 90d)
  • 62,792
    Forks
  • 0
    Releases

Community

  • 42% - Weak
    Community health
  • 22 bus factor
    authors own >50% of commits
  • 237,081
    Watchers

Responsiveness

  • —
    Median issue response
  • —
    Median PR merge time
  • 3
    Open issues
Repository files25 root entries
  • arch
    Good: Test files detected (arch/riscv/kernel/tests).
  • block
  • certs
  • crypto
  • Documentation
    Good: Licensed under Other.
    Good: 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.
    Good: Lockfile present (Documentation/sphinx/requirements.txt). Installs are reproducible.
    Good: Dependency manifest found (Documentation/sphinx/requirements.txt).
  • drivers
  • fs
  • LICENSES
  • .clang-format
  • .clippy.toml
  • .cocciconfig
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .get_maintainer.ignore
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .mailmap
  • .pylintrc
  • .rustfmt.toml
  • COPYING
  • CREDITS
  • Kbuild
  • Kconfig
  • MAINTAINERS
  • Makefile
  • README
    Good: README is present.
    Issue: README has little structure (−15 pts). Add 2-3 headings for +8 pts; 4+ earns +15 pts.Fix: Break it into sections (Overview, Install, Usage, Contributing) using Markdown headings.
    Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
    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.
    Good: README documents how to install the project.
    Good: README documents how to run the project.