vayun-mathur/modern-apps
Grade a repo

71

/ 100

GradeC

Solid engineering. The biggest lever is CI.

Top 39% of 5,156 graded repos

A full mobile ecosystem of 36 apps

Documentation67
Engineering74
Health94
Kotlin785GPL-3.013d ago

Top fixes

Highest-impact changes first, ranked by point weight

16 to address
  1. 1
    CI/CD14pt

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

  2. 2
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  3. 3
    CI/CD14pt

    Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.

  4. 4
    CI/CD14pt

    Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.

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

67

Install and run instructions9pt45

README documents how to install the project.

README12pt65

README is present.

Contributing guide5pt72

Contributing guide is detailed and thorough.

License6pt100

Licensed under GPL-3.0.

Engineering

74

Linting and formatting5pt0

No Rust linting or formatting enforced.

→ Add `cargo clippy -- -D warnings` and `cargo fmt --check` as CI steps, and optionally a rustfmt.toml for project-specific style rules.

CI/CD14pt57

CI is configured (.github/workflows/pr-compile-check.yml).

Reproducibility6pt70

Lockfile present (Cargo.lock). Installs are reproducible.

Tests18pt100

Test files detected (appstore/src/test).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

94

Housekeeping3pt60

.gitignore present.

Dependency manifest6pt100

Dependency manifest found (Cargo.toml).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • -
    Commits (30d / 90d)
  • 43
    Forks
  • 35
    Releaseslatest 5mo ago

Community

  • 57% - Fair
    Community health
  • 1 bus factorlow
    author own >50% of commits
  • 785
    Watchers

Responsiveness

  • 15h
    Median issue response
  • 15h
    Median PR merge time
  • 79
    Open issues
Repository files91 root entries
  • .github
    Good: CI is configured (.github/workflows/pr-compile-check.yml).
    Good: Issue or PR templates present.
  • appstore
    Good: Test files detected (appstore/src/test).
  • astronomy
  • backup
  • build-logic
  • calculator
  • calendar
  • camera
  • cast
  • clock
  • code
  • communicate
  • contacts
  • education
  • email
  • euicc
  • everysync
  • files
  • findfamily
  • firmware
  • flashcards
  • fooddelivery
  • games
  • gradle
  • health
  • keyboard
  • launcher
  • library
  • lint-rules
  • logviewer
  • mapcompare
  • maps
  • measure
  • metadata_data
  • music
  • musicbrainz
  • networklocation
  • notes
  • nowplaying
  • office
  • openassistant
  • passwords
  • pdf
  • photos
  • scripts
    Issue: Build artifacts or local files may be committed (scripts/chess/__pycache__/generate_puzzles.cpython-312.pyc) (−40 pts).Fix: Remove them and add to .gitignore.
  • sdk
  • setupwizard
  • share
  • speech
  • taxi
  • things
  • third_party
  • tools
  • translate
  • travel
  • tuner
  • vpn
  • weather
  • web
  • youpipe
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • $null
  • analyze.ps1
  • build.gradle.kts
  • Cargo.lock
    Good: Lockfile present (Cargo.lock). Installs are reproducible.
  • Cargo.toml
    Good: Dependency manifest found (Cargo.toml).
  • 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.
    Good: Contributing guide explains how to run tests.
    Issue: Contributing guide lacks a PR workflow section (−8 pts).Fix: Explain how to fork, branch, and open a pull request so contributors know what to expect.
    Good: Contributing guide includes code examples.
  • FINDFAMILY_UWB_TRACKER_DESIGN.md
  • FINDFAMILY_UWB_TRACKER_HARDWARE.md
  • gradle.properties
  • gradlew
  • gradlew.bat
  • install
  • install.bat
  • install.ps1
  • interpret.rs
  • LICENSE
    Good: Licensed under GPL-3.0.
  • lint.xml
  • proguard-rules.pro
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
    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.
  • release_keystore.jks
  • release.sh
  • robustness_tests.rs
  • rust-toolchain.toml
  • settings.gradle.kts
  • subdivide.rs
  • SUPPLY_CHAIN_RISKS.md
  • transit_lane_order_by_approach.plan.md
  • transit_lane_smooth_merge.plan.md
  • version.txt
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/vayun-mathur/modern-apps)](https://www.repo-grade.com/report/vayun-mathur/modern-apps)

More graded Kotlin repos