vayun-mathur/modern-apps
Grade a repo

71

/ 100

GradeC

Solid engineering. The biggest lever is CI.

Top 45% of 5,156 graded repos

A full mobile ecosystem of 19 apps

Documentation63
Engineering66
Health94
C558GPL-3.015d ago

Top fixes

Highest-impact changes first, ranked by point weight

20 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 a lint step to catch style issues automatically.

  4. 4
    CI/CD14pt

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

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

63

Install and run instructions9pt45

No install instructions found in the README (−45 pts).

→ Add a section showing how to install dependencies.

Contributing guide5pt47

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.

README12pt65

README is present.

License6pt100

Licensed under GPL-3.0.

Engineering

66

Linting and formatting5pt0

No Java/Kotlin linter configured.

→ Add Checkstyle or Spotless for Java formatting, or ktlint/Detekt for Kotlin. Run it via Maven/Gradle or as a CI step.

CI/CD14pt57

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

Reproducibility6pt70

Lockfile present (camera/src/main/rust/Cargo.lock). Installs are reproducible.

Tests18pt80

Test files detected (astronomy/src/test).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

94

Housekeeping3pt60

.gitignore present.

Dependency manifest6pt100

Dependency manifest found (build.gradle.kts).

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)
  • 35
    Forks
  • 28
    Releaseslatest 3mo ago

Community

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

Responsiveness

  • 15h
    Median issue response
  • 15h
    Median PR merge time
  • 22
    Open issues
Repository files54 root entries
  • .github
    Good: CI is configured (.github/workflows/pr-compile-check.yml).
    Good: Issue or PR templates present.
  • .idea
    Issue: Build artifacts or local files may be committed (.idea/.name) (−40 pts).Fix: Remove them and add to .gitignore.
  • astronomy
    Good: Test files detected (astronomy/src/test).
  • build-logic
  • calendar
  • camera
    Good: Lockfile present (camera/src/main/rust/Cargo.lock). Installs are reproducible.
  • clock
  • contacts
  • education
  • email
  • everysync
  • files
  • findfamily
  • games
  • gradle
  • gradle-module-explorer
  • health
  • library
  • maps
  • messages
  • metadata_data
  • music
  • notes
  • office
  • openassistant
  • passwords
  • pdf
  • photos
  • scripts
  • sdk
  • things
  • third_party
  • tools
  • travel
  • weather
  • whatsapp-signal
  • youpipe
  • .gitignore
    Good: .gitignore present.
  • analyze.ps1
  • build.gradle.kts
    Good: Dependency manifest found (build.gradle.kts).
  • 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.
    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).
    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.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • gradle.properties
  • gradlew
  • gradlew.bat
  • LICENSE
    Good: Licensed under GPL-3.0.
  • lint.xml
  • NETWORK_CAPTURE_PLAN.md
  • 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.
    Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.
    Good: README documents how to run the project.
  • release_keystore.jks
  • release.sh
  • settings.gradle.kts
  • SUPPLY_CHAIN_RISKS.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 C repos