vetis-server/vetis
Grade a repo

92

/ 100

GradeA

Polished and well engineered. Punching above its star count.

Top 10% of 5,156 graded repos

A blazingly fast, minimalist HTTP server built for modern Rust applications.

Documentation81
Engineering96
Health100
Rust113MIT1mo ago

Top fixes

Highest-impact changes first, ranked by point weight

6 to address
  1. 1
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  2. 2
    Install and run instructions9pt

    Add a section showing how to install dependencies.

  3. 3
    Install and run instructions9pt

    Add a .env.example listing all required environment variables so contributors know what to set up.

  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

81

Install and run instructions9pt45

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

→ Add a section showing how to install dependencies.

Contributing guide5pt80

Contributing guide is detailed and thorough.

README12pt100

README is present.

License6pt100

Licensed under MIT.

Engineering

96

CI/CD14pt85

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

Tests18pt100

Test files detected (vetis-smol/src/tests).

Linting and formatting5pt100

Rust linting configured (rustfmt.toml).

Reproducibility6pt100

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

Issue and PR templates6pt100

Issue or PR templates present.

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

  • 30 / 76
    Commits (30d / 90d)
  • 3
    Forks
  • 0
    Releases

Community

  • -
    Community health
  • 1 bus factorlow
    author own >50% of commits
  • 113
    Watchers

Responsiveness

  • 1d 8h
    Median issue response
  • 4h
    Median PR merge time
  • 32
    Open issues
Repository files23 root entries
  • .cargo
  • .github
    Good: CI is configured (.github/workflows/rust.yml).
    Good: Dependabot covers 2 ecosystems (cargo, github-actions). Dependencies stay current.
    Good: Issue or PR templates present.
  • .samoyed
  • certs
  • docs
  • examples
  • vetis
  • vetis-macros
  • vetis-smol
    Good: Test files detected (vetis-smol/src/tests).
    Good: Environment pinned via vetis-smol/Dockerfile.
  • vetis-tokio
  • .commitlintrc.yaml
  • .gitignore
    Good: .gitignore present.
  • .markdownlint.yaml
  • .pre-commit-config.yaml
  • BENCHMARKS.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.
  • dist-workspace.toml
  • LICENSE
    Good: Licensed under MIT.
  • 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.
    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.
  • rustfmt.toml
    Good: Rust linting configured (rustfmt.toml).
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/vetis-server/vetis)](https://www.repo-grade.com/report/vetis-server/vetis)

More graded Rust repos