79

/ 100

GradeC

Solid engineering. The biggest lever is CI.

Top 33% of 5,156 graded repos

Open-source private logbook with a local agentic layer. Long-living AI agents read what you record and propose what to do next. Hardware permitting, the models runs locally too. Matrix + Vodozemac for end-to-end encrypted sync between your own devices.

Top fixes

Highest-impact changes first, ranked by point weight

13 to address
  1. 1
    Tests18pt

    Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.

  2. 2
    CI/CD14pt

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

  3. 3
    CI/CD14pt

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

  4. 4
    CI/CD14pt

    Add a lint step to catch style issues automatically.

Working through the fixes? Let every push regrade itself.

The free GitHub App rescans this repo on every push and posts the grade as a commit check, so the score climbs without coming back to rescan by hand.

Install the GitHub App

Scorecard

Every check, grouped by category and sorted worst-first

Documentation

94

Contributing guide5pt61

Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.

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

README12pt100

README is present.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under GPL-3.0.

Engineering

61

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.

CI/CD14pt40

CI is configured (.github/workflows/flutter-ios-testflight.yml).

Tests18pt80

Test files detected (docs-site/tests).

Reproducibility6pt80

Lockfile present (docs-site/package-lock.json). Installs are reproducible.

Linting and formatting5pt100

Linter or formatter configured (services/credits-service/.flake8).

Project health

100

Dependency manifest6pt100

Dependency manifest found (android/app/build.gradle).

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)
  • 114
    Forks
  • 1000
    Releaseslatest 3y ago

Community

  • 71% - Fair
    Community health
  • 1 bus factorlow
    author own >50% of commits
  • 1,153
    Watchers

Responsiveness

  • 4h
    Median issue response
  • 91d 15h
    Median PR merge time
  • 9
    Open issues
Repository files51 root entries
  • .buildkite
  • .claude
  • .fvm
  • .gemini
  • .github
    Good: CI is configured (.github/workflows/flutter-ios-testflight.yml).
  • .vscode
  • android
    Good: Dependency manifest found (android/app/build.gradle).
  • assets
  • docs
  • docs-site
    Good: Test files detected (docs-site/tests).
    Good: Lockfile present (docs-site/package-lock.json). Installs are reproducible.
  • flatpak
  • integration_test
    Good: Environment pinned via integration_test/docker/docker-compose.yml.
  • ios
  • lib
  • linux
  • macos
  • services
    Good: Linter or formatter configured (services/credits-service/.flake8).
  • shaders
  • test
  • test_driver
  • test_flows
  • test_resources
  • third_party
  • tool
  • tools
  • windows
  • .fvmrc
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .metadata
  • AGENTS.md
  • analysis_options.yaml
  • build.yaml
  • CHANGELOG.md
  • CLAUDE.md
  • codecov.yml
  • codemagic.yaml
  • CODEOWNERS
  • CONTRIBUTING.md
    Issue: Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +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.
  • dart_test.yaml
  • devtools_options.yaml
  • fluttium.yaml
  • GETTING_STARTED.md
  • l10n.yaml
  • LICENSE
    Good: Licensed under GPL-3.0.
  • Makefile
  • PRIVACY.md
  • pubspec.lock
  • pubspec.yaml
  • 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.
RepoGrade badge preview

Add this badge to your README

It updates automatically each time the repo is re-graded.

[![RepoGrade](https://www.repo-grade.com/api/badge/matthiasn/lotti)](https://www.repo-grade.com/report/matthiasn/lotti)

More graded Dart repos