namikawa07/step

0

/ 100

Documentation30
Engineering60
Health59
Dart02y ago
Grade a repo

Rough and inactive. Tests, CI, and a fuller README would revive it.

Documentation

30

License6pt0

No license detected.

→ Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.

Contributing guide5pt0

No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).

→ Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.

README12pt45

README is present.

Install and run instructions9pt45

README documents how to install the project.

Engineering

60

CI/CD14pt0

No CI configuration detected in this repository.

→ If your CI lives elsewhere (a private repo that builds this one) or this project is itself a CI/CD tool, mark this check Not Applicable. Otherwise add a GitHub Actions workflow that runs tests on each push. It takes 15 minutes and reassures contributors their changes won't break things.

Reproducibility6pt70

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

Tests18pt80

Test files detected (ios/RunnerTests/RunnerTests.swift).

Linting and formatting5pt100

Linter or formatter configured (functions/.eslintrc.js).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

59

Activity5pt5

No pushes in over 2 years. Looks unmaintained (−95 pts).

→ A recent commit signals the project is alive and worth using.

Repository metadata5pt40

No repository description set on GitHub (−60 pts).

→ Add a one-line description in the repo Settings → About. It appears in search results and social previews.

Dependency manifest6pt100

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

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • —
    Commits (30d / 90d)
  • 0
    Forks
  • 0
    Releases

Community

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

Responsiveness

  • 43d 13h
    Median issue response
  • 1h
    Median PR merge time
  • 30
    Open issues
Repository files21 root entries
  • .github
    Good: Issue or PR templates present.
  • android
    Good: Dependency manifest found (android/app/build.gradle).
  • assets
  • functions
    Good: Linter or formatter configured (functions/.eslintrc.js).
    Good: Lockfile present (functions/package-lock.json). Installs are reproducible.
  • ios
    Good: Test files detected (ios/RunnerTests/RunnerTests.swift).
  • lib
  • linux
  • macos
  • test
  • web
  • windows
  • .firebaserc
  • .gitignore
    Good: .gitignore present.
  • .metadata
  • analysis_options.yaml
  • firebase.json
  • firestore.indexes.json
  • firestore.rules
  • pubspec.lock
  • pubspec.yaml
  • README.md
    Good: README is present.
    Issue: README is fairly short (−10 pts). At 400+ chars you get partial credit; 1,500+ earns the full +20 pts.Fix: Expand with a description, install steps, usage, and examples.
    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.
    Issue: No status badges in the README (−10 pts).Fix: Add CI/build status badges from shields.io or your CI provider to signal project health.
    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.