learntocloud/learn-to-cloud-app

0

/ 100

Documentation87
Engineering76
Health93
Python601MIT1d ago
Grade a repo

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

The best open source courseware to learn cloud engineering

Documentation

87

README12pt70

README is present.

Contributing guide5pt88

Contributing guide is detailed and thorough.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

76

Linting and formatting5pt0

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/CD14pt72

CI is configured (.github/workflows/content-link-auditor.lock.yml).

Tests18pt85

Test files detected (api/pytest.ini).

Reproducibility6pt100

Lockfile present (uv.lock). Installs are reproducible.

Issue and PR templates6pt100

Issue or PR templates present.

Project health

93

Dependency manifest6pt79

Dependency manifest found (pyproject.toml).

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

Community

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

Responsiveness

  • 22h
    Median issue response
  • <1h
    Median PR merge time
  • 8
    Open issues
Repository files21 root entries
  • .azure
  • .devcontainer
    Good: Environment pinned via .devcontainer/Dockerfile.
  • .github
    Good: 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
  • api
    Good: Test files detected (api/pytest.ini).
  • apps
  • docs
    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.
    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
  • LICENSE
    Good: Licensed under MIT.
  • 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.
    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.md
    Good: Security policy present.
  • uv.lock
    Good: Lockfile present (uv.lock). Installs are reproducible.