83
/ 100
Good shape overall. A few tweaks would push it into the top tier.
The best open source courseware to learn cloud engineering
Top fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.
- 2CI/CD14pt
Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 3CI/CD14pt
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
- 4CI/CD14pt
Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.
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.
Scorecard
Every check, grouped by category and sorted worst-first
Documentation
87
README is present.
Contributing guide is detailed and thorough.
README documents how to install the project.
Licensed under MIT.
Engineering
76
No linter or formatter configured.
→ Add [tool.ruff] to pyproject.toml. Ruff handles linting and formatting in one tool and replaces flake8, isort, and black.
CI is configured (.github/workflows/content-link-auditor.lock.yml).
Test files detected (api/pytest.ini).
Lockfile present (uv.lock). Installs are reproducible.
Issue or PR templates present.
Project health
93
Dependency manifest found (pyproject.toml).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- 40 / 182Commits (30d / 90d)
- 20Forks
- 0Releases
Community
- 75% - GoodCommunity health
- 1 bus factorlowauthor own >50% of commits
- 607Watchers
Responsiveness
- 22hMedian issue response
- <1hMedian PR merge time
- 11Open issues
Repository files21 root entries
- .azure
- .devcontainerGood: Environment pinned via .devcontainer/Dockerfile.
- .githubGood: CI is configured (.github/workflows/content-link-auditor.lock.yml).Good: Dependabot covers 4 ecosystems (uv, npm, github-actions, terraform). Dependencies stay current.Good: Issue or PR templates present.Good: .gitignore present.
- .vscode
- apiGood: Test files detected (api/pytest.ini).
- apps
- docsGood: 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.Good: Contributing guide describes code style expectations.Good: Contributing guide explains how to run tests.Good: Contributing guide describes the PR/review workflow.Good: Contributing guide includes code examples.
- infra
- packages
- scripts
- .dockerignore
- .gitattributes
- .gitignore
- .mcp.json
- .pre-commit-config.yaml
- docker-compose.yml
- LICENSEGood: Licensed under MIT.
- pyproject.tomlGood: Dependency manifest found (pyproject.toml).
- README.mdGood: 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.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.Good: README documents how to run the project.
- SECURITY.mdGood: Security policy present.
- uv.lockGood: Lockfile present (uv.lock). Installs are reproducible.
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/learntocloud/learn-to-cloud-app)