0

/ 100

GradeA

Polished and well engineered. Punching above its star count.

Lightweight GUI for managing Bhyve, Jails, ZFS, networking, and more on FreeBSD

Documentation

94

Contributing guide5pt80

Contributing guide is detailed and thorough.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under BSD-2-Clause.

Engineering

88

CI/CD14pt68

CI is configured (.github/workflows/build.yaml).

Reproducibility6pt75

Lockfile present (go.sum). Installs are reproducible.

Tests18pt100

Test files detected (cmd/sylve/console_attach_test.go).

Linting and formatting5pt100

Formatting enforced (internal/assets/zelta/.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (go.mod).

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)
  • 63
    Forks
  • 7
    Releaseslatest today

Community

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

Responsiveness

  • 2h
    Median issue response
  • <1h
    Median PR merge time
  • 6
    Open issues
Repository files16 root entries
  • .github
    Good: CI is configured (.github/workflows/build.yaml).
    Good: Issue or PR templates present.
  • .vscode
  • cmd
    Good: Test files detected (cmd/sylve/console_attach_test.go).
  • docs
    Good: Contributing guide is detailed and thorough.
    Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.
    Good: Contributing guide describes code style expectations.
    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).
    Good: Contributing guide describes the PR/review workflow.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
    Good: Code of conduct present.
  • internal
    Good: Formatting enforced (internal/assets/zelta/.editorconfig).
  • pkg
  • scripts
  • web
  • .air.toml
  • .gitignore
    Good: .gitignore present.
  • config.example.json
  • go.mod
    Good: Dependency manifest found (go.mod).
  • go.sum
    Good: Lockfile present (go.sum). Installs are reproducible.
  • LICENSE
    Good: Licensed under BSD-2-Clause.
  • Makefile
  • 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.