Popular for its size, but the engineering basics lag behind the interest.
Solus Package Monorepo & Issue Tracker
Documentation
51
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
Contributing guidance is in the README, not a dedicated CONTRIBUTING.md (−20 pts).
→ Moving it to a CONTRIBUTING.md makes it easier to find and keeps the README focused. A dedicated file earns +47 pts base.
README is present.
Licensed under Other.
Engineering
52
No tests detected anywhere in the repository.
→ Add automated tests. They prove the code works and give contributors confidence to make changes.
Lockfile present (common/Go/yabi/go.sum). Installs are reproducible.
CI is configured (.github/workflows/package_lint.yml).
Linter or formatter configured (.flake8).
Issue or PR templates present.
Project health
100
Dependency manifest found (common/Go/yabi/go.mod).
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)
- 137Forks
- 0Releases
Community
- —Community health
- —authors own >50% of commits
- 131Watchers
Responsiveness
- <1hMedian issue response
- 1d 18hMedian PR merge time
- 319Open issues
Repository files13 root entries
- .githubGood: CI is configured (.github/workflows/package_lint.yml).Good: Issue or PR templates present.
- commonGood: Lockfile present (common/Go/yabi/go.sum). Installs are reproducible.Good: Dependency manifest found (common/Go/yabi/go.mod).
- LICENSES
- packages
- repo_data
- .flake8Good: Linter or formatter configured (.flake8).
- .gitignoreGood: .gitignore present.
- .gitmodules
- .mypy.ini
- LICENSE.mdGood: Licensed under Other.
- README.mdGood: README is present.Good: README is well structured with multiple sections.Good: README includes screenshots or visuals. Great for first impressions.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.
- SECURITY.mdGood: Security policy present.
- Taskfile.yml