aws-samples/genai-ml-platform-examples
Grade a repo

0

/ 100

GradeC

Solid foundation. Invest in docs and CI to grow from here.

Top 45% of 5,156 graded repos
Documentation64
Engineering78
Health64
Jupyter Notebook80MIT-01mo 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
    README12pt

    Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.

  3. 3
    README12pt

    Link to a deployed version, docs site, or demo video. Users want to see it running.

  4. 4
    README12pt

    Add CI/build status badges from shields.io or your CI provider to signal project health.

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

64

README12pt50

README is present.

Install and run instructions9pt55

README documents how to install the project.

Contributing guide5pt72

Contributing guide is detailed and thorough.

License6pt100

Licensed under MIT-0.

Engineering

78

Issue and PR templates6pt0

No issue or PR templates found (−100 pts).

→ Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.

Tests18pt80

Test files detected (demo-apps/mediflow/tests).

Reproducibility6pt80

Lockfile present (demo-apps/data-analysis-agent/requirements.txt). Installs are reproducible.

CI/CD14pt100

CI is configured (operations/sagemaker-mlflow-rag-pipeline-automation/.github/workflows/build_sagemaker_pipeline.yml).

Linting and formatting5pt100

Linter or formatter configured (demo-apps/health-app/client/eslint.config.js).

Project health

64

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 manifest6pt55

Dependency manifest found (pyproject.toml).

Housekeeping3pt60

.gitignore present.

Activity5pt100

Actively maintained (pushed within the last month).

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • -
    Commits (30d / 90d)
  • 51
    Forks
  • 0
    Releases

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 80
    Watchers

Responsiveness

  • <1h
    Median issue response
  • 1h
    Median PR merge time
  • 54
    Open issues
Repository files14 root entries
  • .kiro
  • demo-apps
    Good: Test files detected (demo-apps/mediflow/tests).
    Good: Linter or formatter configured (demo-apps/health-app/client/eslint.config.js).
    Good: Lockfile present (demo-apps/data-analysis-agent/requirements.txt). Installs are reproducible.
    Good: Environment pinned via demo-apps/mediflow/Dockerfile.
  • infrastructure
    Issue: Build artifacts or local files may be committed (infrastructure/.DS_Store) (−40 pts).Fix: Remove them and add to .gitignore.
  • integration
  • migration
  • operations
    Good: CI is configured (operations/sagemaker-mlflow-rag-pipeline-automation/.github/workflows/build_sagemaker_pipeline.yml).
  • platform
  • .gitignore
    Good: .gitignore present.
  • AGENT.md
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • 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.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • LICENSE
    Good: Licensed under MIT-0.
  • pyproject.toml
    Good: Dependency manifest found (pyproject.toml).
  • 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.
    Good: README has code examples.
    Issue: No live demo link in the README (−20 pts).Fix: Link to a deployed version, docs site, or demo video. Users want to see it running.
    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.
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/aws-samples/genai-ml-platform-examples)](https://www.repo-grade.com/report/aws-samples/genai-ml-platform-examples)

More graded Jupyter Notebook repos