0
/ 100
Getting some notice. Tests and CI would be the fastest wins.
JCE - A Content Editor for Joomla
A low grade is a to-do list, not a judgment of your code
Most gaps here are documentation, tests, and setup, not the code itself. Closing your top 3 gaps alone would lift this repo to C (75).
See your top fixesTop 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.
- 2CI/CD14pt
Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 3CI/CD14pt
Add a lint step to catch style issues automatically.
- 4CI/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.
Scorecard
Every check, grouped by category and sorted worst-first
Documentation
53
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 documents how to install the project.
README is present.
Licensed under GPL-2.0.
Engineering
68
No dependency lockfile found (−70 pts).
→ Commit composer.lock so Composer installs are repeatable.
CI is configured (.github/workflows/codeql-analysis.yml).
Test files detected (media/com_jce/editor/tinymce/plugins/clipboard/tests).
Linter or formatter configured (media/com_jce/editor/tinymce/.eslintrc).
Issue or PR templates present.
Project health
53
No dependency manifest detected at root.
→ Add a manifest (package.json, pyproject.toml, Cargo.toml, go.mod, etc.) so others can install dependencies in one command.
No .gitignore found (−60 pts).
→ Add a .gitignore to keep build output, node_modules, and secrets out of version control.
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)
- 12Forks
- 181Releaseslatest 9y ago
Community
- -Community health
- -authors own >50% of commits
- 48Watchers
Responsiveness
- 14hMedian issue response
- <1hMedian PR merge time
- 37Open issues
Repository files8 root entries
- .githubGood: CI is configured (.github/workflows/codeql-analysis.yml).Good: Issue or PR templates present.
- administrator
- components
- language
- mediaGood: Test files detected (media/com_jce/editor/tinymce/plugins/clipboard/tests).Good: Linter or formatter configured (media/com_jce/editor/tinymce/.eslintrc).Issue: Build artifacts or local files may be committed (media/com_jce/editor/tinymce/themes/advanced/skins/default/.DS_Store) (−40 pts).Fix: Remove them and add to .gitignore.
- plugins
- LICENSE.txtGood: Licensed under GPL-2.0.
- 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 some structure (−7 pts). 2-3 headings earns partial credit; 4+ earns the full +15 pts.Fix: Add more sections (Overview, Install, Usage, Contributing) using ## 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.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.Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/widgetfactory/jce)