minhajul/blog
Grade a repo

0

/ 100

GradeC

Solid engineering. The main gap is visibility.

Top 43% of 5,156 graded repos

Minimal blogging platform for personal use built with Laravel, Livewire, Alpine.js, Tailwind CSS.

Documentation51
Engineering77
Health94
PHP81mo 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
    README12pt

    Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.

  3. 3
    README12pt

    Link to a deployed version, docs site, or demo video. Users want to see it running.

  4. 4
    README12pt

    Add CI/build status badges from shields.io or your CI provider to signal project health.

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

License6pt0

No license detected.

→ Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.

Contributing guide5pt25

Contributing guidance is in the README, not a dedicated CONTRIBUTING.md (−20 pts).

→ Moving it to a CONTRIBUTING.md makes it easier to find and keeps the README focused. A dedicated file earns +47 pts base.

README12pt50

README is present.

Install and run instructions9pt100

README documents how to install the project.

Engineering

77

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.

Reproducibility6pt70

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

Tests18pt80

Test files detected (phpunit.xml).

CI/CD14pt100

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

Linting and formatting5pt100

PHP linting configured (.editorconfig).

Project health

94

Housekeeping3pt60

.gitignore present.

Dependency manifest6pt100

Dependency manifest found (composer.json).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Repository health signals

Activity, community, and responsiveness at scan time

Activity

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

Community

  • 28% - Weak
    Community health
  • -
    authors own >50% of commits
  • 8
    Watchers

Responsiveness

  • -
    Median issue response
  • -
    Median PR merge time
  • 0
    Open issues
Repository files34 root entries
  • .agents
    Good: Security policy present.
  • .claude
  • .gemini
  • .github
    Good: CI is configured (.github/workflows/tests.yml).
  • app
    Issue: Build artifacts or local files may be committed (app/.DS_Store) (−40 pts).Fix: Remove them and add to .gitignore.
  • bootstrap
  • config
  • database
  • public
  • resources
  • routes
  • storage
  • tests
  • .editorconfig
    Good: PHP linting configured (.editorconfig).
  • .env.example
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .mcp.json
  • AGENTS.md
  • artisan
  • boost.json
  • bun.lock
    Good: Lockfile present (bun.lock). Installs are reproducible.
  • CLAUDE.md
  • composer.json
    Good: Dependency manifest found (composer.json).
  • composer.lock
  • GEMINI.md
  • opencode.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.
    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.
    Good: README has code examples.
    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.
  • tailwind.config.js
  • vite.config.js
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/minhajul/blog)](https://www.repo-grade.com/report/minhajul/blog)

More graded PHP repos