Getting noticed, but rough fundamentals could turn visitors away.
PKGBUILDS for packages used in our repository
Documentation
34
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.
README is present.
A license file is present.
Engineering
11
No tests detected anywhere in the repository.
→ Add automated tests. They prove the code works and give contributors confidence to make changes.
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.
CI is configured (.github/workflows/gitlab.yml).
Project health
59
No dependency manifest detected at root.
→ Add a manifest (package.json, pyproject.toml, Cargo.toml, go.mod, etc.) so others can install dependencies in one command.
No .gitignore found (−60 pts).
→ Add a .gitignore to keep build output, node_modules, and secrets out of version control.
Repository has a description.
Actively maintained (pushed within the last month).
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- —Commits (30d / 90d)
- 85Forks
- 0Releases
Community
- —Community health
- —authors own >50% of commits
- 142Watchers
Responsiveness
- 12hMedian issue response
- 20hMedian PR merge time
- 6Open issues
Repository files68 root entries
- .githubGood: CI is configured (.github/workflows/gitlab.yml).
- akm
- arc-gtk-theme-eos
- b43-firmware
- calamares
- calamares-git
- ckbcomp
- dracut
- endeavouros-branding
- endeavouros-developer-mirrorlist
- endeavouros-keyring
- endeavouros-konsole-colors
- endeavouros-mirrorlist
- endeavouros-mirrorlist-testing
- endeavouros-xfce4-terminal-colors
- eos-apps-info
- eos-bash-shared
- eos-breeze-sddm
- eos-downgrade
- eos-dracut
- eos-hooks
- eos-hwtool
- eos-iso-hotfix
- eos-lightdm-gtk-theme
- eos-lightdm-slick-theme
- eos-log-tool
- eos-lxdm-gtk3
- eos-manual-intervention
- eos-packagelist
- eos-pkgbuild-setup
- eos-qogir-icons
- eos-quickstart
- eos-rankmirrors
- eos-reboot-recommended
- eos-repo-before-arch-repos
- eos-sddm-theme
- eos-settings-budgie
- eos-settings-cinnamon
- eos-settings-cosmic
- eos-settings-gnome
- eos-settings-i3wm
- eos-settings-lxde
- eos-settings-lxqt
- eos-settings-mate
- eos-settings-plasma
- eos-settings-sway
- eos-settings-xfce4
- eos-sway-tools
- eos-translations
- eos-update
- eos-update-notifier
- eos-xfce-tweaks-devel
- fetch-iso
- iso-create-ml
- kernel-install-for-dracut
- keyserver-rank
- nvidia-hook
- nvidia-inst
- openswapGood: A license file is present.
- pahis
- power-profiles-switcher
- qemu-arm-aarch64-static-bin
- rami
- reflector-bash-completion
- reflector-simple
- welcome
- yad
- README.mdGood: 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.Good: README includes status badges.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.