facet-rs/facet
Grade a repo

80

/ 100

GradeB

Well engineered. The main gaps are issue and PR templates and setup instructions.

Top 30% of 5,156 graded repos

Rust reflection, serialization, deserialization, pretty printing, etc. — the last proc macro you should need

Documentation72
Engineering79
Health100
Rust2,568Apache-2.01mo ago

Top fixes

Highest-impact changes first, ranked by point weight

13 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
    README12pt

    Show a quick-start snippet so contributors can see what using your project looks like.

  4. 4
    Install and run instructions9pt

    Add a section showing how to install dependencies.

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

72

Install and run instructions9pt45

No install instructions found in the README (−45 pts).

→ Add a section showing how to install dependencies.

Contributing guide5pt57

CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.

→ Add setup instructions, code style notes, and how to run tests.

README12pt85

README is present.

License6pt100

Licensed under Apache-2.0.

Engineering

79

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

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

Reproducibility6pt92

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

Tests18pt100

Test files detected (facet-core/tests).

Linting and formatting5pt100

Rust linting configured (cargo clippy in CI).

Project health

100

Dependency manifest6pt100

Dependency manifest found (Cargo.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

  • 50 / 2417
    Commits (30d / 90d)
  • 128
    Forks
  • 1000
    Releaseslatest 8mo ago

Community

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

Responsiveness

  • 4h
    Median issue response
  • <1h
    Median PR merge time
  • 146
    Open issues
Repository files53 root entries
  • .cargo
  • .claude
  • .config
  • .github
    Good: CI is configured (.github/workflows/test.yml).
  • .zed
  • docs
  • examples
  • facet
  • facet-core
    Good: Test files detected (facet-core/tests).
  • facet-default
  • facet-error
  • facet-macro-parse
  • facet-macro-template
  • facet-macro-types
  • facet-macros
  • facet-macros-impl
  • facet-path
  • facet-pretty
  • facet-reflect
  • facet-showcase
  • facet-solver
  • facet-testattrs
  • facet-testhelpers
  • facet-testhelpers-macros
  • facet-validate
  • notes
  • scripts
  • static
  • .envrc
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • AGENTS.md
  • Cargo.lock
    Good: Lockfile present (Cargo.lock). Installs are reproducible.
  • Cargo.toml
    Good: Dependency manifest found (Cargo.toml).
  • CHANGELOG.md
  • clippy.toml
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CONTRIBUTING.md
    Issue: CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.
    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).
    Issue: Contributing guide lacks a PR workflow section (−8 pts).Fix: Explain how to fork, branch, and open a pull request so contributors know what to expect.
    Good: Contributing guide includes code examples.
  • depot.json
  • DEVELOP.md
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • flake.lock
  • flake.nix
  • Justfile
  • LICENSE-APACHE
  • LICENSE-MIT
  • miri-env.sh
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.
    Good: README links to a live demo or deployed app.
    Good: README includes status badges.
    Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.
    Good: README documents how to run the project.
  • release-plz.toml
  • renovate.json5
    Good: Renovate config present (renovate.json5).
  • rust-toolchain.toml
  • SECURITY.md
    Good: Security policy present.
  • shell.nix
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/facet-rs/facet)](https://www.repo-grade.com/report/facet-rs/facet)

More graded Rust repos