dusklinux/dusky
Grade a repo

0

/ 100

GradeF

Strong community interest, but tests, CI, or docs need work.

Arch-Hyprland dotfiles/distro. A true labor of Passion, Consider rewarding with a star.

Documentation78
Engineering29
Health94
Shell2,195MITtoday

Documentation

78

Contributing guide5pt0

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.

README12pt90

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

29

CI/CD14pt0

No CI configuration detected in this repository.

→ If your CI lives elsewhere (a private repo that builds this one) or this project is itself a CI/CD tool, mark this check Not Applicable. Otherwise add a GitHub Actions workflow that runs tests on each push. It takes 15 minutes and reassures contributors their changes won't break things.

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.

Reproducibility6pt0

No dependency lockfile found (−70 pts).

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

Issue and PR templates6pt0

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.

Tests18pt80

Test files detected (user_scripts/dusky_tui/bash/for_equal_assignment_delimiter_only/test).

Project health

94

Housekeeping3pt60

.gitignore present.

Dependency manifest6pt100

Dependency manifest found (.vscode-oss/extensions/rakib13332.material-code-3.1.1/package.json).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • -
    Commits (30d / 90d)
  • 97
    Forks
  • 0
    Releases

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 2,195
    Watchers

Responsiveness

  • <1h
    Median issue response
  • 1h
    Median PR merge time
  • 17
    Open issues
Repository files11 root entries
  • .config
  • .local
  • .vscode-oss
    Good: Dependency manifest found (.vscode-oss/extensions/rakib13332.material-code-3.1.1/package.json).
  • Documents
  • Pictures
  • user_scripts
    Good: Test files detected (user_scripts/dusky_tui/bash/for_equal_assignment_delimiter_only/test).
    Issue: Build artifacts or local files may be committed (user_scripts/update_dusky/python/__pycache__/update_dusky.cpython-314.pyc) (−40 pts).Fix: Remove them and add to .gitignore.
  • .git_dusky_list
  • .gitignore
    Good: .gitignore present.
  • .zshrc
  • LICENSE
    Good: Licensed under MIT.
  • 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.