Popular for its size, but the engineering basics lag behind the interest.
APT repository for Discord
Documentation
70
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.
README documents how to install the project.
Licensed under AGPL-3.0.
Engineering
33
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.
CI is configured (.github/workflows/pages.yml).
Lockfile present (requirements.txt). Installs are reproducible.
Issue or PR templates present.
Project health
100
Dependency manifest found (requirements.txt).
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)
- 10Forks
- 0Releases
Community
- —Community health
- —authors own >50% of commits
- 191Watchers
Responsiveness
- 1hMedian issue response
- 1hMedian PR merge time
- 0Open issues
Repository files19 root entries
- .githubGood: CI is configured (.github/workflows/pages.yml).Good: Issue or PR templates present.
- .vscode
- debian
- discord-repo
- .gitignoreGood: .gitignore present.
- .tool-versionsGood: Environment pinned via .tool-versions.
- canary_packages.json
- discord-apt.gpg
- discord-apt.gpg.asc
- discord-repo_1.1_all.deb
- discord-repo_1.2_all.deb
- get_new_package.py
- LICENSEGood: Licensed under AGPL-3.0.
- Makefile
- ptb_packages.json
- README.mdGood: README is present.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.Good: README has code examples.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.Good: README documents how to run the project.
- requirements.in
- requirements.txtGood: Lockfile present (requirements.txt). Installs are reproducible.Good: Dependency manifest found (requirements.txt).
- stable_packages.json