0
/ 100
Popular for its size, but the engineering basics lag behind the interest.
The website for Hexo. https://hexo.io/
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 A (92).
See your top fixesTop fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Add automated tests. They prove the code works and give contributors confidence to make changes.
- 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
80
README documents how to install the project.
CONTRIBUTING guide found.
README is present.
Licensed under MIT.
Engineering
41
No tests detected anywhere in the repository.
→ Add automated tests. They prove the code works and give contributors confidence to make changes.
No dependency lockfile found (−70 pts).
→ Commit package-lock.json, pnpm-lock.yaml, yarn.lock, or bun.lock so Node installs are repeatable.
CI is configured (.github/workflows/tester.yml).
Linter or formatter configured (eslint.config.js).
Issue or PR templates present.
Project health
89
Dependency manifest found (package.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
- -Commits (30d / 90d)
- 1,331Forks
- 0Releases
Community
- -Community health
- -authors own >50% of commits
- 716Watchers
Responsiveness
- 1d 1hMedian issue response
- 3hMedian PR merge time
- 49Open issues
Repository files15 root entries
- .githubGood: CI is configured (.github/workflows/tester.yml).Good: Dependabot covers 2 ecosystems (npm, github-actions). Dependencies stay current.Good: Issue or PR templates present.
- .husky
- scaffolds
- scripts
- sourceGood: 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.
- themes
- _config.yml
- .gitignoreGood: .gitignore present.
- .npmrc
- crowdin.yml
- eslint.config.jsGood: Linter or formatter configured (eslint.config.js).
- LICENSEGood: Licensed under MIT.
- netlify.toml
- package.jsonGood: Dependency manifest found (package.json).
- 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.
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/hexojs/site)