psalm/psalm-plugin-laravel
Grade a repo

84

/ 100

GradeB

Well engineered. The main gaps are a reproducible setup and a contributing guide.

Top 16% of 5,156 graded repos

Security-focused Laravel static analyser

Documentation90
Engineering82
Health100
PHP335MIT14d ago

Top fixes

Highest-impact changes first, ranked by point weight

11 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 .env.example listing all required environment variables so contributors know what to set up.

  3. 3
    Reproducibility6pt

    Commit composer.lock so Composer installs are repeatable.

  4. 4
    Reproducibility6pt

    Add a Dockerfile, .nvmrc, or .python-version to pin the runtime version and make the environment reproducible.

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

90

Contributing guide5pt52

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 instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under MIT.

Engineering

82

Reproducibility6pt12

No dependency lockfile found (−70 pts).

→ Commit composer.lock so Composer installs are repeatable.

Tests18pt80

Test files detected (phpunit.xml.dist).

CI/CD14pt100

CI is configured (.github/workflows/lint-workflows.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

  • 122 / 444
    Commits (30d / 90d)
  • 79
    Forks
  • 169
    Releaseslatest 7y ago

Community

  • 75% - Good
    Community health
  • -
    authors own >50% of commits
  • 335
    Watchers

Responsiveness

  • 2d 6h
    Median issue response
  • 14h
    Median PR merge time
  • 2
    Open issues
Repository files22 root entries
  • .github
    Good: CI is configured (.github/workflows/lint-workflows.yml).
    Good: Dependabot configured for github-actions.
    Good: Issue or PR templates present.
  • bin
  • docs
  • resources
  • src
  • stubs
  • tests
  • tools
  • _typos.toml
  • .editorconfig
    Good: PHP linting configured (.editorconfig).
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .php-cs-fixer.php
  • composer.json
    Good: Dependency manifest found (composer.json).
  • 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.
  • LICENSE
    Good: Licensed under MIT.
  • phpunit.xml.dist
    Good: Test files detected (phpunit.xml.dist).
  • psalm.xml
  • 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.
  • rector.php
  • SECURITY.md
    Good: Security policy present.
  • UPGRADING.md
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/psalm/psalm-plugin-laravel)](https://www.repo-grade.com/report/psalm/psalm-plugin-laravel)

More graded PHP repos