netbsd/src

0

/ 100

Documentation58
Engineering80
Health100
C9491d ago
Grade a repo

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

Automatic conversion of the NetBSD src CVS module, use with care. Please submit bugs/changes via https://gnats.netbsd.org

Documentation

58

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.

Install and run instructions9pt45

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

→ Add a section showing how to install dependencies.

Contributing guide5pt72

CONTRIBUTING guide found.

License6pt100

A license file is present.

Engineering

80

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.

Tests18pt80

Test files detected (bin/ed/test).

Reproducibility6pt80

Lockfile present (external/apache2/llvm/dist/clang/utils/analyzer/requirements.txt). Installs are reproducible.

CI/CD14pt100

CI is configured (crypto/external/bsd/openssl.old/dist/appveyor.yml).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (common/dist/zlib/contrib/dotzlib/DotZLib.sln).

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

Community

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

Responsiveness

  • —
    Median issue response
  • —
    Median PR merge time
  • 16
    Open issues
Repository files15 root entries
  • bin
    Good: Test files detected (bin/ed/test).
  • common
    Good: A license file is present.
    Good: Dependency manifest found (common/dist/zlib/contrib/dotzlib/DotZLib.sln).
  • compat
  • crypto
    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: CI is configured (crypto/external/bsd/openssl.old/dist/appveyor.yml).
    Good: Environment pinned via crypto/external/apache2/openssl/dist/test/quic-openssl-docker/Dockerfile.
    Good: .gitignore present.
  • dist
  • distrib
  • doc
  • etc
  • external
    Good: Lockfile present (external/apache2/llvm/dist/clang/utils/analyzer/requirements.txt). Installs are reproducible.
    Good: Issue or PR templates present.
    Good: Security policy present.
  • build.sh
  • BUILDING
  • Makefile
  • Makefile.inc
  • README.md
    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.
    Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.
    Good: README documents how to run the project.
  • UPDATING