0
/ 100
Getting some notice. Tests and CI would be the fastest wins.
MusicXML to Vexflow
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 B (84).
See your top fixesTop fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Set scripts.test in package.json to your actual test command, e.g. "vitest" or "jest".
- 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
68
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 MIT.
Engineering
49
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 (src/fonts.test.ts).
CI is configured (.github/workflows/test.yml).
Lockfile present (bun.lock). Installs are reproducible.
Linter or formatter configured (biome.json).
Project health
86
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)
- 10Forks
- 11Releaseslatest 3mo ago
Community
- -Community health
- -authors own >50% of commits
- 39Watchers
Responsiveness
- 13hMedian issue response
- 11hMedian PR merge time
- 0Open issues
Repository files23 root entries
- .agents
- .claude
- .githubGood: CI is configured (.github/workflows/test.yml).
- assets
- bin
- cli
- css
- site
- srcGood: Test files detected (src/fonts.test.ts).
- tests
- xmllint
- .dockerignore
- .gitignoreGood: .gitignore present.
- AGENTS.md
- biome.jsonGood: Linter or formatter configured (biome.json).
- bun.lockGood: Lockfile present (bun.lock). Installs are reproducible.
- bunfig.toml
- CLAUDE.md
- DockerfileGood: Environment pinned via Dockerfile.
- LICENSEGood: Licensed under MIT.
- package.jsonGood: Dependency manifest found (package.json).
- README.mdGood: README is present.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.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.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.Good: README documents how to run the project.
- tsconfig.json
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/stringsync/vexml)