koreacomk/visao-libertaria-site
Grade a repo

66

/ 100

GradeD

A workable base with real gaps. Start with the README and issue and PR templates.

Top 50% of 5,156 graded repos

Nova versão do site do projeto Visão Libertária

Documentation51
Engineering63
Health100
PHP57MIT8d ago

A low grade is a to-do list, not a judgment of your code

Most gaps here are documentation, tests, and setup, not the code itself. Closing your top 3 gaps alone would lift this repo to B (82).

See your top fixes
Now
D
66
Potential
B
82

Top fixes

Highest-impact changes first, ranked by point weight

18 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
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  3. 3
    CI/CD14pt

    Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.

  4. 4
    CI/CD14pt

    Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.

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

51

Contributing guide5pt0

No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).

→ Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.

README12pt18

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

63

Linting and formatting5pt0

No PHP linter or static analysis tool configured.

→ Add PHP_CodeSniffer (phpcs.xml) for style or PHPStan (phpstan.neon) for static analysis. Run either in CI.

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.

Tests18pt80

Test files detected (phpunit.xml.dist).

Reproducibility6pt80

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

CI/CD14pt85

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

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

  • -
    Commits (30d / 90d)
  • 13
    Forks
  • 0
    Releases

Community

  • 42% - Weak
    Community health
  • -
    authors own >50% of commits
  • 57
    Watchers

Responsiveness

  • 1d 2h
    Median issue response
  • 10h
    Median PR merge time
  • 14
    Open issues
Repository files22 root entries
  • .docker
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
  • app
  • public
  • tests
  • writable
  • .gitignore
    Good: .gitignore present.
  • .htaccess
  • builds
  • composer.json
    Good: Dependency manifest found (composer.json).
  • composer.lock
    Good: Lockfile present (composer.lock). Installs are reproducible.
  • docker-compose.yml
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • env
  • env.docker
  • index.php
  • LICENSE
    Good: Licensed under MIT.
  • Makefile
  • phpunit.xml.dist
    Good: Test files detected (phpunit.xml.dist).
  • preload.php
  • README.md
    Good: README is present.
    Issue: README is fairly short (−10 pts). At 400+ chars you get partial credit; 1,500+ earns the full +20 pts.Fix: Expand with a description, install steps, usage, and examples.
    Issue: README has some structure (−7 pts). 2-3 headings earns partial credit; 4+ earns the full +15 pts.Fix: Add more sections (Overview, Install, Usage, Contributing) using ## headings.
    Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
    Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.
    Issue: No live demo link in the README (−20 pts).Fix: Link to a deployed version, docs site, or demo video. Users want to see it running.
    Issue: No status badges in the README (−10 pts).Fix: Add CI/build status badges from shields.io or your CI provider to signal project health.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • spark
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/koreacomk/visao-libertaria-site)](https://www.repo-grade.com/report/koreacomk/visao-libertaria-site)

More graded PHP repos