0

/ 100

GradeF

Some interest. A stronger README and CI would help.

Odoo App Store Modules

Documentation

49

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.

Install and run instructions9pt45

README documents how to install the project.

README12pt48

README is present.

License6pt100

Licensed under LGPL-3.0.

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 poetry.lock, uv.lock, pdm.lock, Pipfile.lock, conda-lock.yml, or another lockfile for your Python dependency manager.

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 (muk_ai/static/tests).

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)
  • 76
    Forks
  • 0
    Releases

Community

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

Responsiveness

  • 2d 11h
    Median issue response
  • 4d 8h
    Median PR merge time
  • 0
    Open issues
Repository files31 root entries
  • cla
  • muk_ai
    Good: Test files detected (muk_ai/static/tests).
  • muk_ai_automation
  • muk_ai_enterprise
  • muk_ai_mistral
  • muk_ai_schedule
  • muk_ai_skills
  • muk_contacts
  • muk_contacts_vcard
  • muk_mail_route
  • muk_mail_utils
  • muk_mcp
  • muk_mcp_access
  • muk_product
  • muk_web_actions
  • muk_web_appsbar
  • muk_web_chatter
  • muk_web_colors
  • muk_web_dialog
  • muk_web_enterprise_theme
  • muk_web_group
  • muk_web_list_column
  • muk_web_list_mode
  • muk_web_preview
  • muk_web_refresh
  • muk_web_theme
  • muk_web_utils
  • muk_website_llms_txt
  • .gitignore
    Good: .gitignore present.
  • LICENSE
    Good: Licensed under LGPL-3.0.
  • README.md
    Good: README is present.
    Issue: README is fairly short (−10 pts). At 400+ chars you get partial credit; 1,500+ earns the full +20 pts.Fix: Expand with a description, install steps, usage, and examples.
    Issue: README has some structure (−7 pts). 2-3 headings earns partial credit; 4+ earns the full +15 pts.Fix: Add more sections (Overview, Install, Usage, Contributing) using ## headings.
    Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
    Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.
    Good: README links to a live demo or deployed app.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.