88
/ 100
Polished and well engineered. Punching above its star count.
All of the required core code
Top fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.
- 2Install and run instructions9pt
Add a section showing how to start or use the project.
- 3Install and run instructions9pt
Add a .env.example listing all required environment variables so contributors know what to set up.
- 4Reproducibility6pt
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.
Scorecard
Every check, grouped by category and sorted worst-first
Documentation
79
README documents how to install the project.
Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.
→ Add setup instructions, code style notes, and how to run tests.
README is present.
Licensed under MIT.
Engineering
89
Lockfile present (composer.lock). Installs are reproducible.
Test files detected (phpunit.xml).
CI is configured (.github/workflows/ci.yml).
PHP linting configured (phpcs.xml).
Issue or PR templates present.
Project health
100
Dependency manifest found (composer.json).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- 232 / 477Commits (30d / 90d)
- 27Forks
- 5Releaseslatest 2mo ago
Community
- 75% - GoodCommunity health
- -authors own >50% of commits
- 270Watchers
Responsiveness
- 4d 22hMedian issue response
- 10d 6hMedian PR merge time
- 27Open issues
Repository files27 root entries
- .githubGood: CI is configured (.github/workflows/ci.yml).Good: Issue or PR templates present.
- .stubs
- .vscode
- bin
- docker
- docs
- phpstan
- skills
- src
- tests
- .gitattributes
- .gitignoreGood: .gitignore present.
- .markdownlint.json
- autoloader.php
- CHANGELOG.md
- CLAUDE.md
- composer.jsonGood: Dependency manifest found (composer.json).
- composer.lockGood: Lockfile present (composer.lock). Installs are reproducible.
- CONTRIBUTING.mdIssue: Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +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).Good: Contributing guide describes the PR/review workflow.Good: Contributing guide includes code examples.
- docker-compose-phpunit.yml
- LICENSEGood: Licensed under MIT.
- phpcs.xmlGood: PHP linting configured (phpcs.xml).
- phpcs.xml.dist
- phpstan.neon
- phpunit.xmlGood: Test files detected (phpunit.xml).
- README.mdGood: 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.Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
- SECURITY.mdGood: Security policy present.
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/berlindb/core)