leptos-rs/leptos
Grade a repo

94

/ 100

GradeA

A top-tier open source project. Docs, tests, and CI are all in excellent shape.

Top 7% of 5,156 graded repos

Build fast web applications with Rust.

Documentation97
Engineering92
Health94
Rust21,007MIT1mo ago

Top fixes

Highest-impact changes first, ranked by point weight

7 to address
  1. 1
    CI/CD14pt

    Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.

  2. 2
    CI/CD14pt

    Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.

  3. 3
    CI/CD14pt

    Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.

  4. 4
    Contributing guide5pt

    Show new contributors how to get a local dev environment running.

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

97

Contributing guide5pt80

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.

Engineering

92

CI/CD14pt72

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

Tests18pt100

Test files detected (any_spawner/tests).

Linting and formatting5pt100

Rust linting configured (rustfmt.toml, cargo fmt in CI).

Reproducibility6pt100

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

Issue and PR templates6pt100

Issue or PR templates present.

Project health

94

Housekeeping3pt60

.gitignore present.

Dependency manifest6pt100

Dependency manifest found (Cargo.toml).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • 22 / 47
    Commits (30d / 90d)
  • 873
    Forks
  • 90
    Releaseslatest 3y ago

Community

  • 87% - Good
    Community health
  • 1 bus factorlow
    author own >50% of commits
  • 21,007
    Watchers

Responsiveness

  • 10h
    Median issue response
  • 2h
    Median PR merge time
  • 122
    Open issues
Repository files47 root entries
  • .config
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
    Good: Dependabot covers 2 ecosystems (github-actions, cargo). Dependencies stay current.
    Good: Issue or PR templates present.
  • any_error
  • any_spawner
    Good: Test files detected (any_spawner/tests).
  • benchmarks
  • cargo-make
  • const_str_slice_concat
  • docs
  • either_of
  • examples
    Good: Environment pinned via examples/hackernews_islands_axum/Dockerfile.
    Issue: Build artifacts or local files may be committed (examples/axum_js_ssr/node_modules/@highlightjs) (−40 pts).Fix: Remove them and add to .gitignore.
  • hydration_context
  • integrations
  • leptos
  • leptos_config
  • leptos_dom
  • leptos_hot_reload
  • leptos_macro
  • leptos_server
  • logos
  • meta
  • next_tuple
  • oco
  • or_poisoned
  • projects
  • reactive_graph
  • reactive_stores
  • reactive_stores_macro
  • router
  • router_macro
  • scripts
  • server_fn
  • server_fn_macro
  • tachys
  • .gitignore
    Good: .gitignore present.
  • AI_POLICY.md
  • ARCHITECTURE.md
  • Cargo.lock
    Good: Lockfile present (Cargo.lock). Installs are reproducible.
  • Cargo.toml
    Good: Dependency manifest found (Cargo.toml).
  • 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.
    Good: Contributing guide describes code style expectations.
    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.
  • flake.lock
  • flake.nix
  • LICENSE
    Good: Licensed under MIT.
  • Makefile.toml
  • README.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.
  • rustfmt.toml
    Good: Rust linting configured (rustfmt.toml, cargo fmt in CI).
  • SECURITY.md
    Good: Security policy present.
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/leptos-rs/leptos)](https://www.repo-grade.com/report/leptos-rs/leptos)

More graded Rust repos