baserproject/basercms
Grade a repo

76

/ 100

GradeC

Solid engineering. The biggest lever is setup instructions.

Top 38% of 5,156 graded repos

baserCMS : Based Website Development Project

Documentation59
Engineering78
Health100
PHP194Other11d ago

Top fixes

Highest-impact changes first, ranked by point weight

12 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 step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.

  3. 3
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  4. 4
    CI/CD14pt

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

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

59

Install and run instructions9pt10

No install instructions found in the README (−45 pts).

→ Add a section showing how to install dependencies.

README12pt70

README is present.

Contributing guide5pt72

CONTRIBUTING guide found.

License6pt100

Licensed under Other.

Engineering

78

CI/CD14pt57

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

Tests18pt80

Test files detected (phpunit.xml.dist).

Reproducibility6pt80

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

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

  • 45 / 171
    Commits (30d / 90d)
  • 141
    Forks
  • 60
    Releaseslatest 4y ago

Community

  • 75% - Good
    Community health
  • 1 bus factorlow
    author own >50% of commits
  • 194
    Watchers

Responsiveness

  • 16d 23h
    Median issue response
  • <1h
    Median PR merge time
  • 93
    Open issues
Repository files37 root entries
  • .agents
  • .claude
  • .github
    Good: CONTRIBUTING guide found.
    Issue: CONTRIBUTING guide contents could not be read (−28 pts vs a readable file).Fix: Move the file to the repo root or docs/CONTRIBUTING.md so its setup, style, test, and PR sections can be graded.
    Good: CI is configured (.github/workflows/test.yml).
    Good: Issue or PR templates present.
    Good: Security policy present.
  • bin
  • composer
  • config
  • db
  • docker
  • logs
  • plugins
  • src
  • templates
  • tests
  • tmp
  • vendor
  • webroot
  • .editorconfig
    Good: PHP linting configured (.editorconfig).
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .htaccess
  • .node-version
    Good: Environment pinned via .node-version.
  • .nvmrc
  • AGENTS.md
  • CLAUDE.md
  • composer_installer.php
  • composer.json
    Good: Dependency manifest found (composer.json).
  • composer.lock
    Good: Lockfile present (composer.lock). Installs are reproducible.
  • index.php
  • LICENSE.md
    Good: Licensed under Other.
  • monorepo-builder.php
  • package-lock.json
  • package.json
  • phpdoc.dist.xml
  • phpunit.xml.dist
    Good: Test files detected (phpunit.xml.dist).
  • README.md
    Good: README is present.
    Issue: README has little structure (−15 pts). Add 2-3 headings for +8 pts; 4+ earns +15 pts.Fix: Break it into sections (Overview, Install, Usage, Contributing) using Markdown headings.
    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.
    Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
  • skills-lock.json
  • web.default.config
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/baserproject/basercms)](https://www.repo-grade.com/report/baserproject/basercms)

More graded PHP repos