Popular for its size, but the engineering basics lag behind the interest.
Lazy AF neovim config, well structured in lua.
Documentation
82
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 documents how to install the project.
README is present.
Licensed under MIT.
Engineering
31
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.
CI is configured (.github/workflows/ci.yml).
Issue or PR templates present.
Project health
100
Dependency manifest found (snips/package.json).
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)
- 1Forks
- 1Releaseslatest 3y ago
Community
- —Community health
- —authors own >50% of commits
- 131Watchers
Responsiveness
- <1hMedian issue response
- 2hMedian PR merge time
- 0Open issues
Repository files27 root entries
- .codegraphGood: .gitignore present.
- .githubGood: CI is configured (.github/workflows/ci.yml).Good: Dependabot configured for github-actions.Good: Issue or PR templates present.
- after
- docs
- ftdetect
- ftplugin
- lua
- nixos
- scripts
- snipsGood: Dependency manifest found (snips/package.json).
- spell
- syntax
- .gitattributes
- .gitignore
- .markdownlint.yml
- .marksman.toml
- flake.lock
- flake.nix
- init.lua
- lazy-lock.json
- LICENSEGood: Licensed under MIT.
- mise.tomlGood: Environment pinned via mise.toml.
- README.mdGood: 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
- stylua.toml
- tombi.toml
- vim.yml