0
/ 100
Good shape overall. A few tweaks would push it into the top tier.
Manifold Markets: A market for every question
Top fixes
Highest-impact changes first, ranked by point weight
- 1README12pt
Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
- 2README12pt
Show a quick-start snippet so contributors can see what using your project looks like.
- 3README12pt
Add CI/build status badges from shields.io or your CI provider to signal project health.
- 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
76
README is present.
CONTRIBUTING guide found.
README documents how to install the project.
Licensed under MIT.
Engineering
85
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 (yarn.lock). Installs are reproducible.
Test files detected (backend/shared/src/test).
CI is configured (.github/workflows/check.yml).
Linter or formatter configured (.prettierrc).
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)
- 239Forks
- 0Releases
Community
- -Community health
- -authors own >50% of commits
- 508Watchers
Responsiveness
- -Median issue response
- 1hMedian PR merge time
- 51Open issues
Repository files35 root entries
- .claude
- .cursor
- .githubGood: 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.Good: CI is configured (.github/workflows/check.yml).
- .husky
- .vscode
- backendGood: Test files detected (backend/shared/src/test).Good: Environment pinned via backend/api/Dockerfile.
- client-common
- common
- dev-docs
- docs
- mani
- native
- scripts
- twitch-bot
- web
- .firebaserc
- .gitattributes
- .gitignoreGood: .gitignore present.
- .mcp.json
- .prettierignore
- .prettierrcGood: Linter or formatter configured (.prettierrc).
- .yarnrc
- dev.sh
- firebase.json
- knowledge.cursorrules
- knowledge.md
- LICENSE.mdGood: Licensed under MIT.
- manifold-info.knowledge.md
- package.jsonGood: Dependency manifest found (package.json).
- private-storage.rules
- README.mdGood: README is present.Good: README is well structured with multiple sections.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.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.Good: README documents how to run the project.
- SECURITY.mdGood: Security policy present.
- SHOP_SYSTEM.md
- storage.rules
- yarn.lockGood: Lockfile present (yarn.lock). Installs are reproducible.
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/manifoldmarkets/manifold)