Good community traction and solid fundamentals. Nearly in the top tier.

Yazi and Zellij with smart defaults & awesome plugins give helix/nvim a powerful yazi sidebar, git integrations, a configurable popup system (lazygit, a config ui, etc), zoxide integrations, zjstatus widgets, and more. Your terminal IDE. Written in rust and blazingly fast. Available via flake/home-manager. One line install.

Documentation

86

Contributing guide5pt52

CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.

Add setup instructions, code style notes, and how to run tests.

README12pt90

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Apache-2.0.

Engineering

66

Linting and formatting5pt0

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/CD14pt57

CI is configured (.github/workflows/ci.yml).

Reproducibility6pt70

Lockfile present (rust_core/Cargo.lock). Installs are reproducible.

Tests18pt80

Test files detected (rust_core/yazelix_core/src/zellij_commands/status/tests).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (rust_core/Cargo.toml).

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)
  • 47
    Forks
  • 6
    Releaseslatest 1mo ago

Community

  • Community health
  • authors own >50% of commits
  • 1,082
    Watchers

Responsiveness

  • 3d 20h
    Median issue response
  • <1h
    Median PR merge time
  • 40
    Open issues
Repository files29 root entries
  • .beads
    Good: .gitignore present.
  • .claude
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
    Good: Issue or PR templates present.
  • assets
  • config_metadata
  • configs
  • docs
    Issue: CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.
    Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).
    Issue: Contributing guide lacks a PR workflow section (−8 pts).Fix: Explain how to fork, branch, and open a pull request so contributors know what to expect.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • home_manager
  • nushell
  • packaging
  • rust_core
    Good: Test files detected (rust_core/yazelix_core/src/zellij_commands/status/tests).
    Good: Lockfile present (rust_core/Cargo.lock). Installs are reproducible.
    Good: Dependency manifest found (rust_core/Cargo.toml).
  • shells
  • .gitignore
  • .nu-lint.toml
  • .pre-commit-config.yaml
  • AGENTS.md
  • CHANGELOG.md
  • CLAUDE.md
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • flake.lock
  • flake.nix
  • LICENSE
    Good: Licensed under Apache-2.0.
  • maintainer_shell.nix
  • 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.
    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.
  • release_metadata.toml
  • settings_default.jsonc
  • yazelix_cursors_default.toml
  • yazelix_package.nix
  • yazelix_runtime_package.nix