ulises-jeremias/dotfiles

0

/ 100

Documentation97
Engineering41
Health68
QML127MIT1d ago
Grade a repo

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

HorneroConfig is a comprehensive dotfiles framework, tailored for seamless customization of diverse window management setups across various operating systems. Just like the skilled hornero bird meticulously shapes its nest, HorneroConfig empowers you to craft a digital environment that's robust, uniquely yours, and beautifully organized!

Documentation

97

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under MIT.

Contributing guide5pt100

Contributing guide is detailed and thorough.

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/mega-linter.yml).

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

68

Dependency manifest6pt0

No dependency manifest detected at root.

→ Add a manifest (package.json, pyproject.toml, Cargo.toml, go.mod, etc.) so others can install dependencies in one command.

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)
  • 4
    Forks
  • 17
    Releaseslatest 3y ago

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 127
    Watchers

Responsiveness

  • 15d 1h
    Median issue response
  • 16h
    Median PR merge time
  • 1
    Open issues
Repository files30 root entries
  • .cursor
    Good: .gitignore present.
  • .github
    Good: Code of conduct present.
    Good: CI is configured (.github/workflows/mega-linter.yml).
    Good: Dependabot configured for github-actions.
    Good: Issue or PR templates present.
  • bin
  • docs
  • home
  • lib
  • playground
    Good: Environment pinned via playground/compose.yml.
  • reference
  • scripts
  • static
  • .chezmoiroot
  • .chezmoiversion
  • .cspell.json
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .gitignore
  • .jscpd.json
  • .markdownlint.json
  • .mega-linter.yml
  • .pre-commit-config.yaml
  • .python-version
  • .shellcheckrc
  • .yamllint.yaml
  • AGENTS.md
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Good: Contributing guide includes setup/install instructions.
    Good: Contributing guide describes code style expectations.
    Good: Contributing guide explains how to run tests.
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • install.sh
  • LICENSE
    Good: Licensed under MIT.
  • PKGBUILD
  • PKGBUILD.dev
  • 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.
  • SECURITY.md
    Good: Security policy present.