macports/macports-ports

0

/ 100

Documentation48
Engineering66
Health100
Tcl1,799Othertoday
Grade a repo

Strong community interest, but tests, CI, or docs need work.

The MacPorts ports tree

Documentation

48

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.

README12pt45

README is present.

Install and run instructions9pt45

README documents how to install the project.

License6pt100

Licensed under Other.

Engineering

66

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.

CI/CD14pt57

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

Reproducibility6pt70

Lockfile present (graphics/svgcleaner/files/Cargo.lock). Installs are reproducible.

Tests18pt80

Test files detected (_resources/port1.0/group/tests).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (python/py-backports/files/setup.py).

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

  • 895 / 4075
    Commits (30d / 90d)
  • 1,512
    Forks
  • 0
    Releases

Community

  • 62% - Fair
    Community health
  • 8 bus factor
    authors own >50% of commits
  • 1,799
    Watchers

Responsiveness

  • —
    Median issue response
  • 20h
    Median PR merge time
  • 78
    Open issues
Repository files65 root entries
  • _resources
    Good: Test files detected (_resources/port1.0/group/tests).
  • .github
    Good: CI is configured (.github/workflows/main.yml).
    Good: Issue or PR templates present.
  • aqua
  • archivers
  • audio
  • benchmarks
  • cad
  • comms
  • cross
  • databases
  • devel
  • dotnet
  • editors
  • emulators
  • erlang
  • finance
  • fonts
  • fortran
  • fuse
  • games
  • genealogy
  • gis
  • gnome
  • gnustep
  • graphics
    Good: Lockfile present (graphics/svgcleaner/files/Cargo.lock). Installs are reproducible.
  • guile
  • irc
  • janet
  • java
  • kde
  • lang
  • lisp
  • llm
  • lua
  • mail
  • math
  • multimedia
  • net
  • news
  • ocaml
  • octave
  • office
  • palm
  • perl
  • php
  • print
  • pure
  • python
    Good: Dependency manifest found (python/py-backports/files/setup.py).
  • R
  • ruby
  • scheme
  • science
  • security
  • shells
  • sysutils
  • tex
  • textproc
  • www
  • x11
  • xfce
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .mailmap
  • LICENSE
    Good: Licensed under Other.
  • 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.
    Good: README is well structured with multiple sections.
    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.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.