Popular for its size, but the engineering basics lag behind the interest.

The best and strongest dotfiles. Editor: Neovim; Shell: zsh(zinit, powerlevel10k); Terminal: WezTerm; Desktop: Hyprland, walker, dunst; OS: NixOS, ArchLinux (Ubuntu/Fedora/CentOS)

Documentation

94

Contributing guide5pt77

CONTRIBUTING guide found.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under MIT.

Engineering

41

Tests18pt0

No tests detected anywhere in the repository.

Add automated tests. They prove the code works and give contributors confidence to make changes.

Reproducibility6pt22

No dependency lockfile found (−70 pts).

Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.

CI/CD14pt57

CI is configured (.github/workflows/check-plugins.yml).

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (.config/nvim/vscode-snippets/package.json).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • Commits (30d / 90d)
  • 49
    Forks
  • 44
    Releaseslatest 7y ago

Community

  • Community health
  • authors own >50% of commits
  • 969
    Watchers

Responsiveness

  • 3h
    Median issue response
  • <1h
    Median PR merge time
  • 0
    Open issues
Repository files28 root entries
  • .claude
  • .codex
  • .config
    Good: Licensed under MIT.
    Good: Security policy present.
    Good: Dependency manifest found (.config/nvim/vscode-snippets/package.json).
  • .devcontainer
    Good: Environment pinned via .devcontainer/Dockerfile.
  • .github
    Good: CONTRIBUTING guide found.
    Issue: CONTRIBUTING guide contents could not be read (−28 pts vs a readable file).Fix: Move the file to the repo root or docs/CONTRIBUTING.md so its setup, style, test, and PR sections can be graded.
    Good: Code of conduct present.
    Good: CI is configured (.github/workflows/check-plugins.yml).
    Good: Dependabot configured for github-actions.
    Good: Issue or PR templates present.
  • .nvim
  • home-manager
  • nixos
  • system-etc
  • .cspell.json
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .editrc
  • .gitignore
    Good: .gitignore present.
  • .stylua.toml
  • .vale.ini
  • .xinitrc
  • .xprofile
  • .zshenv
  • AGENTS.md
  • CLAUDE.md
  • flake.lock
  • flake.nix
  • home.nix
  • install.sh
  • LICENSE
  • neovim.yml
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    Good: README has code examples.
    Good: README links to a live demo or deployed app.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • selene.toml