0
/ 100
Popular for its size, but the engineering basics lag behind the interest.
Translate any word or phrase 🪄✨ and learn it
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".
- 2README12pt
Add more sections (Overview, Install, Usage, Contributing) using ## headings.
- 3README12pt
Show a quick-start snippet so contributors can see what using your project looks like.
- 4Install and run instructions9pt
Add a section showing how to install dependencies.
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
51
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.
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
README is present.
Licensed under AGPL-3.0.
Engineering
60
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 (mobile-app/__tests__).
Lockfile present (package-lock.json). Installs are reproducible.
CI is configured (.circleci/config.yml).
Linter or formatter configured (.editorconfig).
Project health
83
.gitignore present.
Dependency manifest found (package.json).
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)
- 13Forks
- 1000Releaseslatest 3y ago
Community
- 37% - WeakCommunity health
- -authors own >50% of commits
- 209Watchers
Responsiveness
- 1d 2hMedian issue response
- <1hMedian PR merge time
- 8Open issues
Repository files27 root entries
- .circleciGood: CI is configured (.circleci/config.yml).
- .husky
- .ideaIssue: Build artifacts or local files may be committed (.idea/.gitignore) (−40 pts).Fix: Remove them and add to .gitignore.
- assets
- batch-analyze
- dashboard
- extensions
- mobile-appGood: Test files detected (mobile-app/__tests__).
- packages
- platform
- platform-root
- safari-web-extension
- scripts
- sync-server
- .editorconfigGood: Linter or formatter configured (.editorconfig).
- .gitattributes
- .gitignoreGood: .gitignore present.
- .lintstagedrc
- .prettierignore
- .prettierrc
- .releaserc.js
- CLAUDE.md
- DESIGN.md
- LICENSE.mdGood: Licensed under AGPL-3.0.
- package-lock.jsonGood: Lockfile present (package-lock.json). Installs are reproducible.
- 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.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.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.
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/vocably/getvocably)