0
/ 100
Good shape overall. A few tweaks would push it into the top tier.
Collection of userscripts for MusicBrainz, by various authors
Top fixes
Highest-impact changes first, ranked by point weight
- 1README12pt
Show a quick-start snippet so contributors can see what using your project looks like.
- 2README12pt
Add CI/build status badges from shields.io or your CI provider to signal project health.
- 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
41
No license detected.
→ Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.
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.
Engineering
84
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 (pnpm-lock.yaml). Installs are reproducible.
Test files detected (tests).
CI is configured (.github/workflows/build-and-deploy.yml).
Linter or formatter configured (.editorconfig).
Project health
100
Dependency manifest found (package.json).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository files44 root entries
- .githubGood: CI is configured (.github/workflows/build-and-deploy.yml).
- .husky
- .vscode
- assets
- lib
- src
- testsGood: Test files detected (tests).
- tools
- .editorconfigGood: Linter or formatter configured (.editorconfig).
- .gitignoreGood: .gitignore present.
- bandcamp_importer.user.js
- batch-add-recording-relationships.user.js
- boomkat_importer.user.js
- cd1d_importer.user.js
- deezer_importer.user.js
- discogs_importer.user.js
- edit-instrument-recordings-links.user.js
- encyclopedisque_importer.user.js
- eslint.config.js
- expand-collapse-release-groups.user.js
- fast-cancel-edits.user.js
- fma_importer.user.js
- hdtracks_importer.user.js
- juno_download_importer.user.js
- loot_importer.user.js
- mb_1200px_caa.user.js
- mb_discids_detector.user.js
- mb_relationship_shortcuts.user.js
- mb_ui_enhancements.user.js
- metalarchives_importer.user.js
- naxos_library_importer.user.js
- naxos_library3_importer.user.js
- oxfmt.config.ts
- oxlint.config.ts
- package.jsonGood: Dependency manifest found (package.json).
- pnpm-lock.yamlGood: Lockfile present (pnpm-lock.yaml). Installs are reproducible.
- pnpm-workspace.yaml
- qobuz_importer.user.js
- README.mdGood: README is present.Good: README is well structured with multiple sections.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.
- renovate.json
- set-recording-comments.user.js
- takealot_importer.user.js
- tsconfig.json
- vgmdb_importer.user.js
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/murdos/musicbrainz-userscripts)