Early stage. Tests, CI, and a strong README would raise this score quickly.
Fork of WordPress Core's unit testing to support bootstrapping an existing database and many other enhancements.
Documentation
74
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.
README is present.
README documents how to install the project.
Licensed under GPL-3.0.
Engineering
51
No dependency lockfile found (−70 pts).
→ Commit composer.lock so Composer installs are repeatable.
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.
CI is configured (.github/workflows/create-release.yml).
Test files detected (dev/wp-unit/phpunit.xml.dist).
PHP linting configured (.editorconfig).
Project health
94
.gitignore present.
Dependency manifest found (composer.json).
Repository has a description.
Actively maintained (pushed within the last month).
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- —Commits (30d / 90d)
- 3Forks
- —Releases
Community
- 42% - WeakCommunity health
- —authors own >50% of commits
- 7Watchers
Responsiveness
- —Median issue response
- —Median PR merge time
- 0Open issues
Repository files14 root entries
- .aiassistant
- .githubGood: CI is configured (.github/workflows/create-release.yml).
- .ideaIssue: Build artifacts or local files may be committed (.idea/.gitignore) (−40 pts).Fix: Remove them and add to .gitignore.
- data
- devGood: Test files detected (dev/wp-unit/phpunit.xml.dist).
- includes
- .editorconfigGood: PHP linting configured (.editorconfig).
- .gitattributes
- .gitignoreGood: .gitignore present.
- composer.jsonGood: Dependency manifest found (composer.json).
- LICENSEGood: Licensed under GPL-3.0.
- phpstan.neon.dist
- README.mdGood: 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.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.
- VERSION