tombursch/kitchenowl
Grade a repo

0

/ 100

GradeB

A well-known project done right. Strong docs and solid engineering throughout.

KitchenOwl is a self-hosted grocery list and recipe manager. The backend is made with Flask and the frontend with Flutter. Easily add items to your shopping list before you go shopping. You can also create recipes and add items based on what you want to cook.

Documentation85
Engineering80
Health100
Dart3,423AGPL-3.0today

Documentation

85

Contributing guide5pt55

CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.

→ Add setup instructions, code style notes, and how to run tests.

README12pt85

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under AGPL-3.0.

Engineering

80

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.

Tests18pt80

Test files detected (backend/tests).

Reproducibility6pt80

Lockfile present (backend/uv.lock). Installs are reproducible.

CI/CD14pt100

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

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (backend/pyproject.toml).

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)
  • 207
    Forks
  • 76
    Releaseslatest 4y ago

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 3,423
    Watchers

Responsiveness

  • 14h
    Median issue response
  • <1h
    Median PR merge time
  • 307
    Open issues
Repository files20 root entries
  • .github
    Good: CI is configured (.github/workflows/tests.yaml).
    Good: Issue or PR templates present.
  • backend
    Good: Test files detected (backend/tests).
    Good: Lockfile present (backend/uv.lock). Installs are reproducible.
    Good: Dependency manifest found (backend/pyproject.toml).
  • docs
  • icons
  • kitchenowl
  • metadata
  • .dockerignore
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • changelog_configuration.json
  • CHANGELOG.md
  • CONTRIBUTING.md
    Issue: CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.
    Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    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.
  • docker-compose-postgres.yml
  • docker-compose-rabbitmq.yml
  • docker-compose-single.yml
  • docker-compose.yml
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • flutter
  • LICENSE
    Good: Licensed under AGPL-3.0.
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    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.
    Good: README documents how to run the project.