vitodeploy/vito
Grade a repo

89

/ 100

GradeB

A well-known project done right. Strong docs and solid engineering throughout.

Top 14% of 5,156 graded repos

Free and Self-Hosted Server Management Tool

Documentation79
Engineering90
Health100
PHP3,158AGPL-3.01mo ago

Top fixes

Highest-impact changes first, ranked by point weight

10 to address
  1. 1
    Tests18pt

    Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.

  2. 2
    Install and run instructions9pt

    Add a section showing how to start or use the project.

  3. 3
    Reproducibility6pt

    Add .github/dependabot.yml with at least one package-ecosystem entry so dependencies are updated automatically.

  4. 4
    Contributing guide5pt

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

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

79

Contributing guide5pt47

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.

Install and run instructions9pt55

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under AGPL-3.0.

Engineering

90

Tests18pt80

Test files detected (phpunit.xml).

Reproducibility6pt80

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

CI/CD14pt100

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

Linting and formatting5pt100

PHP linting configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (composer.json).

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

  • 35 / 111
    Commits (30d / 90d)
  • 409
    Forks
  • 101
    Releaseslatest 2y ago

Community

  • 62% - Fair
    Community health
  • 1 bus factorlow
    author own >50% of commits
  • 3,158
    Watchers

Responsiveness

  • <1h
    Median issue response
  • <1h
    Median PR merge time
  • 13
    Open issues
Repository files46 root entries
  • .claude
  • .github
    Good: CI is configured (.github/workflows/tests.yml).
    Good: Issue or PR templates present.
  • app
  • bootstrap
  • config
  • database
  • docker
  • docs
  • lang
  • public
  • resources
  • scripts
  • storage
  • tests
  • .coderabbit.yaml
  • .easytree.json
  • .editorconfig
    Good: PHP linting configured (.editorconfig).
  • .env.example
  • .env.prod
  • .env.sail
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .mcp.json
  • .prettierignore
  • .prettierrc
  • artisan
  • CLAUDE.md
  • components.json
  • composer.json
    Good: Dependency manifest found (composer.json).
  • composer.lock
    Good: Lockfile present (composer.lock). Installs are reproducible.
  • 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.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • docker-compose.yml
    Good: Environment pinned via docker-compose.yml.
  • eslint.config.js
  • LICENSE
    Good: Licensed under AGPL-3.0.
  • Makefile
  • package-lock.json
  • package.json
  • phpstan.neon
  • phpunit.xml
    Good: Test files detected (phpunit.xml).
  • pint.json
  • 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.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
  • rector.php
  • sail
  • SECURITY.md
    Good: Security policy present.
  • tsconfig.json
  • vite.config.ts
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/vitodeploy/vito)](https://www.repo-grade.com/report/vitodeploy/vito)

More graded PHP repos