aws-samples/sample-openclaw-on-aws-with-bedrock
Grade a repo

71

/ 100

GradeC

Good shape overall. A few tweaks would push it into the top tier.

Top 45% of 5,156 graded repos
Documentation96
Engineering51
Health84
Python418MIT-01mo ago

Top fixes

Highest-impact changes first, ranked by point weight

14 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 `pull_request:` to the workflow `on:` triggers.

  4. 4
    CI/CD14pt

    Add a lint step to catch style issues automatically.

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

96

Contributing guide5pt72

Contributing guide is detailed and thorough.

README12pt100

README is present.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under MIT-0.

Engineering

51

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.

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.

CI/CD14pt40

CI is configured (.github/workflows/pages.yml).

Tests18pt80

Test files detected (enterprise/admin-console/server/test_agent_factory.py).

Reproducibility6pt80

Lockfile present (enterprise/admin-console/package-lock.json). Installs are reproducible.

Project health

84

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 (enterprise/admin-console/package.json).

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)
  • 135
    Forks
  • 0
    Releases

Community

  • 75% - Good
    Community health
  • 1 bus factorlow
    author own >50% of commits
  • 418
    Watchers

Responsiveness

  • 1d 1h
    Median issue response
  • 1d 3h
    Median PR merge time
  • 3
    Open issues
Repository files27 root entries
  • .github
    Good: CI is configured (.github/workflows/pages.yml).
  • .kiro
  • docs
  • eks
  • enterprise
    Good: Test files detected (enterprise/admin-console/server/test_agent_factory.py).
    Good: Lockfile present (enterprise/admin-console/package-lock.json). Installs are reproducible.
    Good: Environment pinned via enterprise/agent-container/Dockerfile.
    Good: Dependency manifest found (enterprise/admin-console/package.json).
  • images
  • skills
  • src
  • traffic
  • .gitignore
    Good: .gitignore present.
  • CLAUDE.md
  • clawdbot-bedrock-mac.yaml
  • clawdbot-bedrock.yaml
  • clawdbot-china.yaml
  • 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.
  • DEPLOYMENT.md
  • LICENSE
    Good: Licensed under MIT-0.
  • QUICK_START_KIRO.md
  • README_CN.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    Good: README has code examples.
    Good: README links to a live demo or deployed app.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • README_ENTERPRISE_CN.md
  • README_ENTERPRISE.md
  • README.md
  • ROADMAP.md
  • SECURITY.md
    Good: Security policy present.
  • TROUBLESHOOTING.md
  • UPGRADE.md
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/sample-openclaw-on-aws-with-bedrock)](https://www.repo-grade.com/report/aws-samples/sample-openclaw-on-aws-with-bedrock)

More graded Python repos