77
/ 100
Good shape overall. A few tweaks would push it into the top tier.
render dom nodes
Top fixes
Highest-impact changes first, ranked by point weight
- 1README12pt
Link to a deployed version, docs site, or demo video. Users want to see it running.
- 2Install and run instructions9pt
Add a section showing how to install dependencies.
- 3Install and run instructions9pt
Add a section showing how to start or use the project.
- 4Install and run instructions9pt
Add a .env.example listing all required environment variables so contributors know what to set up.
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
49
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
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.
Licensed under MIT.
Engineering
87
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.
Lockfile present (package-lock.json). Installs are reproducible.
Test files detected (src/index.spec.ts).
CI is configured (.github/workflows/nodejs-test.yml).
Linter or formatter configured (biome.json).
Project health
98
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)
- 74Forks
- 13Releaseslatest 4y ago
Community
- 50% - FairCommunity health
- 1 bus factorlowauthor own >50% of commits
- 142Watchers
Responsiveness
- 6d 16hMedian issue response
- 13hMedian PR merge time
- 1Open issues
Repository files12 root entries
- .githubGood: CI is configured (.github/workflows/nodejs-test.yml).Good: Dependabot covers 2 ecosystems (npm, github-actions). Dependencies stay current.
- srcGood: Test files detected (src/index.spec.ts).
- .gitignoreGood: .gitignore present.
- biome.jsonGood: Linter or formatter configured (biome.json).
- eslint.config.mjs
- LICENSEGood: Licensed under MIT.
- package-lock.jsonGood: Lockfile present (package-lock.json). Installs are reproducible.
- 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.Issue: No live demo link in the README (−20 pts).Fix: Link to a deployed version, docs site, or demo video. Users want to see it running.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.
- SECURITY.mdGood: Security policy present.
- tsconfig.eslint.json
- tsconfig.json
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/cheeriojs/dom-serializer)