Good community traction and solid fundamentals. Nearly in the top tier.
Pokémon battle simulator.
Documentation
71
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
README is present.
Contributing guide is detailed and thorough.
Licensed under MIT.
Engineering
72
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.
CI is configured (.github/workflows/test.yml).
Lockfile present (package-lock.json). Installs are reproducible.
Test files detected (.mocharc.json).
Linter or formatter configured (.editorconfig).
Project health
97
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
- 42 / 254Commits (30d / 90d)
- 3,409Forks
- 6Releaseslatest 1y ago
Community
- 62% - FairCommunity health
- 4 bus factorauthors own >50% of commits
- 5,741Watchers
Responsiveness
- 8hMedian issue response
- <1hMedian PR merge time
- 319Open issues
Repository files35 root entries
- .githubGood: CI is configured (.github/workflows/test.yml).
- .vscode
- config
- data
- databases
- lib
- logs
- server
- sim
- test
- tools
- translations
- .editorconfigGood: Linter or formatter configured (.editorconfig).
- .gitattributes
- .gitignoreGood: .gitignore present.
- .mocharc.jsonGood: Test files detected (.mocharc.json).
- .npmignore
- .npmrc
- ARCHITECTURE.md
- build
- CODEOWNERS
- COMMANDLINE.md
- CONTRIBUTING.mdGood: Contributing guide is detailed and thorough.Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.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.
- eslint-ps-standard.mjs
- eslint.config.mjs
- LICENSEGood: Licensed under MIT.
- old-simulator-doc.txt
- package-lock.jsonGood: Lockfile present (package-lock.json). Installs are reproducible.
- package.jsonGood: Dependency manifest found (package.json).
- pokemon-showdown
- Procfile
- PROTOCOL.md
- README.mdGood: README is present.Issue: README has little structure (−15 pts). Add 2-3 headings for +8 pts; 4+ earns +15 pts.Fix: Break it into sections (Overview, Install, Usage, Contributing) using Markdown 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.Good: README documents how to run the project.
- simulator-doc.txt
- tsconfig.json