resurrectdev1/grove

0

/ 100

Documentation75
Engineering29
Health100
Dart28GPL-3.01d ago
Grade a repo

Getting some notice. Tests and CI would be the fastest wins.

Visualize your growth.

Documentation

75

Install and run instructions9pt45

README documents how to install the project.

Contributing guide5pt72

Contributing guide is detailed and thorough.

README12pt85

README is present.

License6pt100

Licensed under GPL-3.0.

Engineering

29

Tests18pt0

No tests detected anywhere in the repository.

→ Add automated tests. They prove the code works and give contributors confidence to make changes.

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 the lockfile for this project's package manager so installs produce the same dependency versions everywhere.

CI/CD14pt57

CI is configured (.github/workflows/build-apk.yml).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

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

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)
  • 2
    Forks
  • 4
    Releaseslatest 5d ago

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 28
    Watchers

Responsiveness

  • 7h
    Median issue response
  • 11h
    Median PR merge time
  • 0
    Open issues
Repository files16 root entries
  • .github
    Good: CI is configured (.github/workflows/build-apk.yml).
    Good: Issue or PR templates present.
  • android
    Good: Dependency manifest found (android/app/build.gradle.kts).
  • assets
  • fastlane
  • lib
  • .flutter-version
  • .gitignore
    Good: .gitignore present.
  • |10n.yaml
  • analysis_options.yaml
  • CHANGELOG.md
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    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.
    Good: Contributing guide includes code examples.
  • Grove_backup_DEMO.json
  • LICENSE
    Good: Licensed under GPL-3.0.
  • 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.
    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.