Getting noticed, but rough fundamentals could turn visitors away.
Read-only git conversion of OpenBSD's official cvs ports repository. Pull requests not accepted - send diffs to the ports@ mailing list.
Documentation
30
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
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.
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.
A license file is present.
Engineering
29
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.
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.
No dependency lockfile found (−70 pts).
→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.
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.
Test files detected (sysutils/nomad/files/ephemeral_openbsd_test.go).
Project health
100
Dependency manifest found (net/pcapdiff/files/setup.py).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- —Commits (30d / 90d)
- 139Forks
- 0Releases
Community
- —Community health
- —authors own >50% of commits
- 565Watchers
Responsiveness
- —Median issue response
- —Median PR merge time
- 0Open issues
Repository files47 root entries
- archivers
- astro
- audio
- benchmarks
- biology
- books
- cad
- chinese
- comms
- converters
- databases
- develGood: A license file is present.
- editors
- education
- emulators
- fonts
- games
- geo
- graphics
- infrastructure
- inputmethods
- japanese
- java
- korean
- lang
- mail
- math
- meta
- misc
- multimedia
- netGood: Dependency manifest found (net/pcapdiff/files/setup.py).
- news
- plan9
- print
- productivity
- security
- shells
- sysutilsGood: Test files detected (sysutils/nomad/files/ephemeral_openbsd_test.go).
- telephony
- tests
- textproc
- wayland
- www
- .cvsignore
- .gitignoreGood: .gitignore present.
- Makefile
- READMEGood: 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.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.Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.