micasa-dev/micasa
Grade a repo

0

/ 100

GradeA

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

A modal TUI for tracking home projects, maintenance schedules, appliances, and vendor quotes.

Documentation82
Engineering98
Health100
Go1,264Apache-2.0today

Documentation

82

Install and run instructions9pt55

README documents how to install the project.

Contributing guide5pt68

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.

README12pt100

README is present.

License6pt100

Licensed under Apache-2.0.

Engineering

98

Reproducibility6pt85

Lockfile present (go.sum). Installs are reproducible.

Tests18pt100

Test files detected (cmd/micasa/cliref_test.go).

CI/CD14pt100

CI is configured (.github/workflows/ci.yml).

Linting and formatting5pt100

Formatting enforced (.golangci.yml).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (go.mod).

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)
  • 51
    Forks
  • 164
    Releaseslatest 4mo ago

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 1,264
    Watchers

Responsiveness

  • 3d 9h
    Median issue response
  • <1h
    Median PR merge time
  • 59
    Open issues
Repository files38 root entries
  • .claude
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
    Good: Issue or PR templates present.
  • ci
  • cmd
    Good: Test files detected (cmd/micasa/cliref_test.go).
  • deploy
  • docs
  • images
  • internal
  • nix
  • plans
  • videos
  • .conventionalcommits.js
  • .dockerignore
  • .envrc
  • .gitignore
    Good: .gitignore present.
  • .golangci.yml
    Good: Formatting enforced (.golangci.yml).
  • .goreleaser.yaml
  • .govulncheck-exclude
  • .releaserc.json
  • AGENTS.md
  • biome.json
  • CLAUDE.md
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • codecov.yml
  • 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.
    Good: Contributing guide explains how to run tests.
    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.
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • flake.lock
  • flake.nix
  • go.mod
    Good: Dependency manifest found (go.mod).
  • go.sum
    Good: Lockfile present (go.sum). Installs are reproducible.
  • LICENSE
    Good: Licensed under Apache-2.0.
  • LICENSE-glebarez-sqlite
  • osv-scanner.toml
  • POSTMORTEMS.md
  • 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.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
  • renovate.json
  • SECURITY.md
    Good: Security policy present.
  • VERSION