coreutils/gnulib

0

/ 100

Documentation39
Engineering40
Health100
C341Other1d ago
Grade a repo

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

upstream mirror

Documentation

39

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.

README12pt20

README is present.

Install and run instructions9pt45

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

→ Add a section showing how to install dependencies.

License6pt100

Licensed under Other.

Engineering

40

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.

Reproducibility6pt0

No dependency lockfile found (−70 pts).

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

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.

Tests18pt80

Test files detected (tests).

Linting and formatting5pt100

Linter or formatter configured (pygnulib/.pylintrc).

Project health

100

Dependency manifest6pt100

Dependency manifest found (pygnulib/setup.cfg).

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

Community

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

Responsiveness

  • 7h
    Median issue response
  • —
    Median PR merge time
  • 3
    Open issues
Repository files36 root entries
  • build-aux
  • config
  • doc
  • etc
  • examples
  • gnulib-l10n
  • lib
  • m4
  • modules
  • po
  • pygnulib
    Good: Linter or formatter configured (pygnulib/.pylintrc).
    Good: Dependency manifest found (pygnulib/setup.cfg).
  • tests
    Good: Test files detected (tests).
  • top
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .gnulib-tool.py
  • all-modules
  • cfg.mk
  • ChangeLog
  • check-AC_LIBOBJ
  • check-copyright
  • check-module
  • COPYING
  • DEPENDENCIES
  • gnulib-tool
  • gnulib-tool.py
  • gnulib-tool.py.TODO
  • gnulib-tool.sh
  • HACKING
  • Makefile
  • MODULES.html.sh
  • NEWS
  • posix-modules
  • README
    Good: README is present.
    Issue: README is very short (−20 pts). 400+ characters earns +10 pts; 1,500+ earns +20 pts.Fix: Add an Overview, Install, Usage, and Contributing section at minimum.
    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.
  • STATUS-libposix
  • users.txt