0
/ 100
Excellent work. The main thing left to polish is CI. It just hasn't found an audience yet.
Top fixes
Highest-impact changes first, ranked by point weight
- 1CI/CD14pt
Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 2CI/CD14pt
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
- 3Dependency manifest6pt
Add a one-line description to package.json. It appears in npm search and on GitHub.
- 4Dependency manifest6pt
Add a `repository` field pointing to the GitHub URL so npm knows where the source lives.
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
100
README is present.
README documents how to install the project.
Licensed under AGPL-3.0.
Contributing guide is detailed and thorough.
Engineering
92
CI is configured (.github/workflows/ci.yml).
Test files detected (packages/api/src/__tests__).
Linter or formatter configured (eslint.config.mjs).
Lockfile present (pnpm-lock.yaml). Installs are reproducible.
Issue or PR templates present.
Project health
67
No repository description set on GitHub (−60 pts).
→ Add a one-line description in the repo Settings → About. It appears in search results and social previews.
.gitignore present.
Dependency manifest found (package.json).
Actively maintained (pushed within the last month).
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 0Forks
- 0Releases
Community
- 85% - GoodCommunity health
- 1 bus factorlowauthor own >50% of commits
- 0Watchers
Responsiveness
- -Median issue response
- <1hMedian PR merge time
- 5Open issues
Repository files37 root entries
- .githubGood: CI is configured (.github/workflows/ci.yml).Good: Dependabot covers 2 ecosystems (npm, github-actions). Dependencies stay current.Good: Issue or PR templates present.
- .ideaIssue: Build artifacts or local files may be committed (.idea/dictionaries) (−40 pts).Fix: Remove them and add to .gitignore.
- data
- docs
- migrations
- packagesGood: Test files detected (packages/api/src/__tests__).
- scripts
- .dockerignore
- .env.example
- .gitignoreGood: .gitignore present.
- API_GUIDE.md
- ARCHITECTURE.md
- CODE_OF_CONDUCT.mdGood: Code of conduct present.
- codecov.yml
- CONTRIBUTING.mdGood: Contributing guide is detailed and thorough.Good: Contributing guide includes setup/install instructions.Good: Contributing guide describes code style expectations.Good: Contributing guide explains how to run tests.Good: Contributing guide describes the PR/review workflow.Good: Contributing guide includes code examples.
- crowdin.yml
- DEPLOYMENT.md
- docker-compose.local.yml
- docker-compose.ymlGood: Environment pinned via docker-compose.yml.
- Dockerfile.api
- Dockerfile.bot
- Dockerfile.dashboard
- ENVIRONMENT.md
- eslint.config.mjsGood: Linter or formatter configured (eslint.config.mjs).
- LICENSEGood: Licensed under AGPL-3.0.
- LOCALIZATION.md
- MIGRATIONS.md
- package.jsonGood: Dependency manifest found (package.json).
- pnpm-lock.yamlGood: Lockfile present (pnpm-lock.yaml). Installs are reproducible.
- pnpm-workspace.yaml
- 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.Good: README links to a live demo or deployed app.Good: README includes status badges.Good: README documents how to install the project.Good: README documents how to run the project.
- SCHEMA.md
- SECURITY.mdGood: Security policy present.
- TESTING.md
- TROUBLESHOOTING.md
- tsconfig.json
- TYPESCRIPT.md
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/zeffuro/fakegaming-bot)