flutter/codelabs
Grade a repo

0

/ 100

GradeD

Strong community interest, but tests, CI, or docs need work.

Flutter codelab examples

Documentation56
Engineering62
Health100
C++2,116BSD-3-Clausetoday

Documentation

56

Install and run instructions9pt0

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

→ Add a section showing how to install dependencies.

Contributing guide5pt53

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.

README12pt78

README is present.

License6pt100

Licensed under BSD-3-Clause.

Engineering

62

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.

Reproducibility6pt30

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/flutter-ci.yml).

Tests18pt80

Test files detected (animated-responsive-layout/step_03/ios/RunnerTests/RunnerTests.swift).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (animated-responsive-layout/step_03/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)
  • 1,444
    Forks
  • 0
    Releases

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 2,116
    Watchers

Responsiveness

  • -
    Median issue response
  • 4h
    Median PR merge time
  • 0
    Open issues
Repository files31 root entries
  • .gemini
  • .github
    Good: CI is configured (.github/workflows/flutter-ci.yml).
    Good: Dependabot covers 142 ecosystems (github-actions, pip, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub, pub). Dependencies stay current.
    Good: Issue or PR templates present.
  • .idx
  • animated-responsive-layout
    Good: Test files detected (animated-responsive-layout/step_03/ios/RunnerTests/RunnerTests.swift).
    Good: Dependency manifest found (animated-responsive-layout/step_03/android/app/build.gradle.kts).
  • animations
  • brick_breaker
  • colorist
  • dart-patterns-and-records
  • dartpad_codelabs
  • deeplink_cookbook
  • firebase-auth-flutterfire-ui
  • firebase-get-to-know-flutter
  • generate_crossword
  • genui-intro
  • google-maps-in-flutter
  • homescreen_codelab
  • in_app_purchases
    Good: Environment pinned via in_app_purchases/complete/dart-backend/Dockerfile.
  • namer
  • tooling
  • webview_flutter
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • analysis_options.yaml
  • AUTHORS
  • CONTRIBUTING.md
    Issue: 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).
    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.
  • flutter_ci_script_beta.sh
  • flutter_ci_script_main.sh
  • flutter_ci_script_shared.sh
  • flutter_ci_script_stable.sh
  • LICENSE
    Good: Licensed under BSD-3-Clause.
  • README.md
    Good: README is present.
    Issue: README has some structure (−7 pts). 2-3 headings earns partial credit; 4+ earns the full +15 pts.Fix: Add more sections (Overview, Install, Usage, Contributing) using ## headings.
    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.
    Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.