netbsd/pkgsrc

0

/ 100

Documentation59
Engineering38
Health100
Makefile3931d ago
Grade a repo

Popular for its size, but the engineering basics lag behind the interest.

Automatic conversion of the NetBSD pkgsrc CVS module, use with care

Documentation

59

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.

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 instructions9pt90

README documents how to install the project.

License6pt100

A license file is present.

Engineering

38

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.

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.

Reproducibility6pt70

Lockfile present (chat/coyim/files/go.sum). Installs are reproducible.

Tests18pt80

Test files detected (archivers/libarchive/files/cat/test).

Project health

100

Dependency manifest6pt100

Dependency manifest found (chat/coyim/files/go.mod).

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

Community

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

Responsiveness

  • 1h
    Median issue response
  • —
    Median PR merge time
  • 27
    Open issues
Repository files32 root entries
  • archivers
    Good: A license file is present.
    Good: Test files detected (archivers/libarchive/files/cat/test).
  • audio
  • benchmarks
  • biology
  • bootstrap
  • cad
  • chat
    Good: Lockfile present (chat/coyim/files/go.sum). Installs are reproducible.
    Good: Dependency manifest found (chat/coyim/files/go.mod).
  • comms
  • converters
  • cross
  • databases
  • devel
  • distfiles
  • doc
  • editors
  • emulators
  • filesystems
  • finance
  • fonts
  • games
  • geography
  • graphics
  • ham
  • inputmethod
  • lang
  • licenses
  • mail
  • math
  • .cvsignore
  • .gitignore
    Good: .gitignore present.
  • Makefile
  • 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.
    Good: README documents how to install the project.
    Good: README documents how to run the project.