Getting noticed, but rough fundamentals could turn visitors away.
Lan Tian's NixOS Configuration
Documentation
13
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
No license detected.
→ Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.
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.
Engineering
20
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 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/dnscontrol.yml).
Lockfile present (pkgs/e164-verify/Cargo.lock). Installs are reproducible.
Project health
100
Dependency manifest found (pkgs/e164-verify/Cargo.toml).
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)
- 2Forks
- 0Releases
Community
- —Community health
- —authors own >50% of commits
- 121Watchers
Responsiveness
- 1d 18hMedian issue response
- 2hMedian PR merge time
- 0Open issues
Repository files19 root entries
- .githubGood: CI is configured (.github/workflows/dnscontrol.yml).
- dns
- flake-modules
- helpers
- home
- hosts
- nixos
- overlays
- patches
- pkgsGood: Lockfile present (pkgs/e164-verify/Cargo.lock). Installs are reproducible.Good: Dependency manifest found (pkgs/e164-verify/Cargo.toml).
- tools
- .envrc
- .gitignoreGood: .gitignore present.
- AGENTS.md
- flake.lock
- flake.nix
- Makefile
- nvfetcher.toml
- 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.Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.Issue: No live demo link in the README (−20 pts).Fix: Link to a deployed version, docs site, or demo video. Users want to see it running.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.