hsr88/mouziNew scan
53/ 100 · F

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

A free, privacy-first automatic file organizer that quietly sorts your Downloads folder from the system tray.

Rust434 starsMITupdated 8d ago
DocumentationREADME, setup, examples, license
82
EngineeringTests, CI, linting, lockfiles
20
Project healthDescription, activity, stars, deps
89

What to fix first

The highest-impact improvements for this repo.

  1. 1
    Tests
    EngineeringIssue

    Add automated tests. They prove the code works and give contributors confidence to make changes.

  2. 2
    CI/CD
    EngineeringIssue

    Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.

  3. 3
    CI/CD
    EngineeringIssue

    Add `pull_request:` to the workflow `on:` triggers.

Detailed breakdown

Documentation

82
  • README100
    • README is present.
    • README is well structured with multiple sections.
    • README includes screenshots or visuals. Great for first impressions.
    • README has code examples.
    • README links to a live demo or deployed app.
    • README includes status badges.
  • Install and run instructions90
    • README documents how to install the project.
    • README documents how to run the project.
    • No .env.example found (−10 pts).Add a .env.example listing all required environment variables so contributors know what to set up.
  • License100
    • Licensed under MIT.
  • Contributing guide0
    • 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.
    • Optional: add a Code of Conduct.A CODE_OF_CONDUCT.md signals that your project is welcoming. GitHub has a template you can add in one click.

Engineering

20
  • Tests0
    • No tests detected anywhere in the repository.Add automated tests. They prove the code works and give contributors confidence to make changes.
  • CI/CD40

    Not applicable?

    • CI is configured (.github/workflows/build-macos-test.yml).
    • The CI workflow does not appear to run any tests (−28 pts).Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
    • CI does not appear to trigger on pull requests (−17 pts).Add `pull_request:` to the workflow `on:` triggers.
    • CI does not run a lint or format check (−15 pts).Add a lint step to catch style issues automatically.
    • Optional: add type checking to CI.Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
    • Optional: report test coverage in CI.Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.
    • CI tests across multiple environments or versions.
  • Linting and formatting0
    • No linter or formatter found.Add ESLint (eslint.config.js) and/or Prettier (.prettierrc), install them as devDependencies, and add a `lint` script to package.json.
  • Reproducibility70
    • Lockfile present (package-lock.json). Installs are reproducible.
    • No Dockerfile or runtime version pin found. Adding one earns +10 pts.Add a Dockerfile, .nvmrc, or .python-version to pin the runtime version and make the environment reproducible.
    • No Dependabot config (adding it earns up to +20 pts).Add .github/dependabot.yml with at least one package-ecosystem entry so dependencies are updated automatically.
  • Issue and PR templates0
    • 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.
    • Optional: add a SECURITY.md.A SECURITY.md explains how to responsibly disclose vulnerabilities. Worth adding once the project has real users.

Project health

89
  • Dependency manifest65
    • Dependency manifest found (package.json).
    • package.json is missing a description (−10 pts).Add a one-line description to package.json. It appears in npm search and on GitHub.
    • package.json has no repository field (−10 pts).Add a `repository` field pointing to the GitHub URL so npm knows where the source lives.
    • package.json has no keywords (−8 pts).Add a `keywords` array to help people find your package on npm.
    • package.json has no homepage field (−7 pts).Add a `homepage` field pointing to your docs or project website.
  • Repository metadata100
    • Repository has a description.
    • Primary language detected: Rust.
  • Activity100
    • Actively maintained (pushed within the last month).
    • 434 stars.
  • Housekeeping100
    • .gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • 76 / 179
    Commits (30d / 90d)
  • 18
    Forks
  • 4
    Releaseslatest 9d ago

Community

  • 42% — Weak
    Community health
  • 1 bus factorlow
    author own >50% of commits
  • 434
    Watchers

Responsiveness

  • 10h
    Median issue response
  • 7h
    Median PR merge time
  • 10
    Open issues
Repository files22 root entries
  • .github
    Good: CI is configured (.github/workflows/build-macos-test.yml).
  • .vscode
  • docs
  • posts
  • public
  • src
  • src-tauri
  • .gitignore
    Good: .gitignore present.
  • CNAME
  • index.html
  • LICENSE.md
    Good: Licensed under MIT.
  • package-lock.json
    Good: Lockfile present (package-lock.json). Installs are reproducible.
  • package.json
    Good: Dependency manifest found (package.json).
  • postcss.config.js
  • preview128.png
  • preview16.png
  • preview32.png
  • 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.
  • setup-vm.sh
  • tsconfig.json
  • tsconfig.node.json
  • vite.config.ts