79
/ 100
Solid engineering. The biggest lever is CI.
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
- 1Tests18pt
Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.
- 2CI/CD14pt
Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 3CI/CD14pt
Add `pull_request:` to the workflow `on:` triggers.
- 4CI/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.
Scorecard
Every check, grouped by category and sorted worst-first
Documentation
94
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.
README is present.
README documents how to install the project.
Licensed under GPL-3.0.
Engineering
61
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 is configured (.github/workflows/flutter-ios-testflight.yml).
Test files detected (docs-site/tests).
Lockfile present (docs-site/package-lock.json). Installs are reproducible.
Linter or formatter configured (services/credits-service/.flake8).
Project health
100
Dependency manifest found (android/app/build.gradle).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 114Forks
- 1000Releaseslatest 3y ago
Community
- 71% - FairCommunity health
- 1 bus factorlowauthor own >50% of commits
- 1,153Watchers
Responsiveness
- 4hMedian issue response
- 91d 15hMedian PR merge time
- 9Open issues
Repository files51 root entries
- .buildkite
- .claude
- .fvm
- .gemini
- .githubGood: CI is configured (.github/workflows/flutter-ios-testflight.yml).
- .vscode
- androidGood: Dependency manifest found (android/app/build.gradle).
- assets
- docs
- docs-siteGood: Test files detected (docs-site/tests).Good: Lockfile present (docs-site/package-lock.json). Installs are reproducible.
- flatpak
- integration_testGood: Environment pinned via integration_test/docker/docker-compose.yml.
- ios
- lib
- linux
- macos
- servicesGood: Linter or formatter configured (services/credits-service/.flake8).
- shaders
- test
- test_driver
- test_flows
- test_resources
- third_party
- tool
- tools
- windows
- .fvmrc
- .gitattributes
- .gitignoreGood: .gitignore present.
- .metadata
- AGENTS.md
- analysis_options.yaml
- build.yaml
- CHANGELOG.md
- CLAUDE.md
- codecov.yml
- codemagic.yaml
- CODEOWNERS
- CONTRIBUTING.mdIssue: 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
- LICENSEGood: Licensed under GPL-3.0.
- Makefile
- PRIVACY.md
- pubspec.lock
- pubspec.yaml
- README.mdGood: 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.mdGood: Security policy present.
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/matthiasn/lotti)