pelican-dev/panel
Grade a repo

89

/ 100

GradeB

Well engineered. The main gaps are the repo description and topics and a contributing guide.

Top 14% of 5,156 graded repos
Documentation91
Engineering90
Health84
PHP2,223AGPL-3.06d ago

Top fixes

Highest-impact changes first, ranked by point weight

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

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

  3. 3
    Reproducibility6pt

    Add .github/dependabot.yml with at least one package-ecosystem entry, or a renovate.json, so dependencies are updated automatically.

  4. 4
    Contributing guide5pt

    Describe your linting/formatting rules and how to run them.

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

91

Contributing guide5pt79

Contributing guide is detailed and thorough.

README12pt85

README is present.

Install and run instructions9pt100

README documents how to install the project.

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/build.yaml).

Linting and formatting5pt100

PHP linting configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

84

Repository metadata5pt40

No repository description set on GitHub (−60 pts).

→ Add a one-line description in the repo Settings → About. It appears in search results and social previews.

Dependency manifest6pt100

Dependency manifest found (composer.json).

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • -
    Commits (30d / 90d)
  • 302
    Forks
  • 34
    Releaseslatest 1y ago

Community

  • 62% - Fair
    Community health
  • 2 bus factor
    authors own >50% of commits
  • 2,223
    Watchers

Responsiveness

  • 2d 14h
    Median issue response
  • 15h
    Median PR merge time
  • 22
    Open issues
Repository files40 root entries
  • .github
    Good: CI is configured (.github/workflows/build.yaml).
    Good: Issue or PR templates present.
  • app
  • bootstrap
  • config
  • database
  • docker
  • lang
  • plugins
  • public
  • resources
  • routes
  • storage
  • tests
  • .dockerignore
  • .editorconfig
    Good: PHP linting configured (.editorconfig).
  • .env.example
  • .gitignore
    Good: .gitignore present.
  • .prettierrc.json
  • artisan
  • bounties.md
  • compose-bind.yml
  • compose-full-stack.yml
  • compose.yml
  • composer.json
    Good: Dependency manifest found (composer.json).
  • composer.lock
    Good: Lockfile present (composer.lock). Installs are reproducible.
  • contributing.md
    Good: Contributing guide is detailed and thorough.
    Good: Contributing guide includes setup/install instructions.
    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).
    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.
  • contributor_license_agreement.md
  • crowdin.yml
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • Dockerfile.base
  • Dockerfile.dev
  • license
    Good: Licensed under AGPL-3.0.
  • 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.
    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.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • security.md
    Good: Security policy present.
  • vite.config.js
  • yarn.lock
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/pelican-dev/panel)](https://www.repo-grade.com/report/pelican-dev/panel)

More graded PHP repos