65
/ 100
Solid engineering. The biggest lever is setup instructions.
The WordPress Importer
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.
- 2README12pt
Expand with a description, install steps, usage, and examples.
- 3README12pt
Break it into sections (Overview, Install, Usage, Contributing) using Markdown headings.
- 4README12pt
Show a quick-start snippet so contributors can see what using your project looks like.
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
56
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
README is present.
Contributing guide is detailed and thorough.
Licensed under GPL-2.0.
Engineering
78
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.
Test files detected (e2e/import-wxr.spec.js).
Lockfile present (package-lock.json). Installs are reproducible.
CI is configured (.github/workflows/tests.yml).
PHP linting configured (.prettierrc).
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
- 0 / 2Commits (30d / 90d)
- 96Forks
- 14Releaseslatest 1y ago
Community
- 62% - FairCommunity health
- -authors own >50% of commits
- 89Watchers
Responsiveness
- 1d 15hMedian issue response
- 5hMedian PR merge time
- 68Open issues
Repository files18 root entries
- .githubGood: CI is configured (.github/workflows/tests.yml).Good: Dependabot configured for github-actions.
- .wordpress-org
- e2eGood: Test files detected (e2e/import-wxr.spec.js).
- phpunit
- src
- .gitattributes
- .gitignoreGood: .gitignore present.
- .prettierrcGood: PHP linting configured (.prettierrc).
- composer.jsonGood: Dependency manifest found (composer.json).
- CONTRIBUTING.mdGood: Contributing guide is detailed and thorough.Good: Contributing guide includes setup/install instructions.Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.Good: Contributing guide explains how to run tests.Good: Contributing guide describes the PR/review workflow.Good: Contributing guide includes code examples.
- LICENSEGood: Licensed under GPL-2.0.
- package-lock.jsonGood: Lockfile present (package-lock.json). Installs are reproducible.
- package.json
- phpcs.xml.dist
- phpunit.xml.dist
- playwright.config.js
- README.mdGood: 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 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.
- wordpress-importer.php
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/wordpress/wordpress-importer)